Recently, Somebody Somewhere wrote these words
> Hi all,
>
> I need some advice from more experienced LFS'ers.
>
> Right now, I build my LFS systems (all two of them) by a customized
> scripted build, which makes it easy to upgrade packages whenever a new
> kernel, glibc, gcc, etc. comes out.
>
> When the build is over, it puts a S99firstboot symlink in rc3.d, and
> reboots the system, which takes over on reboot, and builds things like
> X, KDE, and other BLFS stuff. This lets me run a full rebuild, which
> takes quite a few hours, overnight. When it's done, the firstboot
> script removes the symlink and itself.
>
> The problem comes when I come in the morning, and it's not done yet,
> because it's still building time intensive things like Firefox,
> Thunderbird, KDevelop etc. The problem is, the ttys have not been
> started yet, so I can't do anything interactive.
>
> What I'd really like is to run this script on tty9 or something, so I
> can start X and do other stuff without interrupting the build. How
> would/do you do this? Personal anecdotes requested :)
>
> Thanks, Michael
How about a judiciously placed '&' in the script. If you remember
dialup Internet, I had a box here in those days that was being used by
one awkward <expletive deleted> of my own. When he wanted onto the 'net,
I had to open a root console - large security hole. So I would put him
on with
wvdial & logout
The modem started, the console vanished and the modem continued :-D
Try pointing S99 to something like this
-----
#!/bin/bash
<path to>/firstboot.script & exit 0
-----
The firstboot script starts, that little script ends and boot continues.
Is that OK?
--
With best Regards,
Declan Moriarty.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
