Re: [dev] fast-booting to text editor

If your editor of choice doesn't sport a built-in shell, you may
consider starting a text editor on one virtual console, and a general
purpose shell on another. You'll probably need a simple init (I
recommend a rc script written against a statically compiled /bin/rc)
to allocate the consoles (unless it's still possible to allocate them
statically) and start the editor and shells, or run them inside of
dvtm [http://www.brain-dump.org/projects/dvtm/].

On 3/21/11, Thomas Spurden <thomas_AT_ado.is-a-geek.net> wrote:
> On 20/03/11 18:21, David Tweed wrote:
>> Hi, one of those general suckless software questions:
>>
>> I'm in a position where I'll be both commuting a lot and needing to
>> write a lot of text (review coments) over the coming months. I've got
>> a "spare" old but very small, low weight notebook PC I plan to try and
>> use. The only requirements I have are that there be a decent text
>> editor, a filesystem that can hold several files and the ability to
>> move files onto/off-of my permanent full-capacity PC. (I'd actually
>> prefer not to have any other facilities.)
>>
>
> I would suggest building yourself a cross-toolchain (is your target is a
> different arch). Then build a kernel with suspend support and whatever
> else you need (framebuffer console?). Then a static busybox and vim (or
> whatever editor you prefer). Throw said kernel/binaries on a partition
> and create a link called linuxrc to your favorite text editor (assuming
> you can run commands from your text editor - exiting it will panic the
> kernel). I guess you'll also want a swap partition to suspend to. To
> suspend echo 'disk' or 'mem' to /sys/power/state. To transfer stuff to
> your main machine you could add dropbear (ssh) - assuming you have some
> form of networking.
>
> It'll definitely boot/unsuspend faster than ewwbuntwo.
>
> --
> Thomas Spurden
>
>
Received on Wed Mar 23 2011 - 21:36:06 CET