Hi All
Ok, I took the plunge and upgraded to 3.5.3 in my quest to use an
alternate kernel, build my own, or simply add modules.
I noticed si_mkbootpackage and after a few changes got it to build me
the boot package. But I get the same /dev issue below when booting off
my kernel of choice. My questions are
1. John, where is it you are adding the rsync exactly?
2. Is there another wrapper script that uses UseYourOwnKernel.pm? The
cvs header shows it as newer than si_mkbootpackage, but didn't know it
existed.
This seems like the best route to go, but until then I guess I'll try
building my modules into the systemimager kernel again :)
thanks
charles
Email Archive: sisuite-users (read-only) Search
From: John Jolet <[EMAIL PROTECTED]>
Re: no devfs support when using 3.5.3
2005-11-02 03:57
I ran into a similar problem with gentoo. I just went around the
problem and added an rsync /dev/* to /a/dev right before the crhoot.
On Nov 1, 2005, at 9:01 PM, Ashley Gould wrote:
> I'm trying to install based on the kernel and initrd.img created
> with UseYourOwnKernel.pm. I copied them from my goldenclient into
> /tftpboot on the image server. These load from tftp and the kernel
> boots
> fine. But as soon as init starts, I see problems.
>
> init started: BusyBox ...
>
> mount: /proc/mounts: No such file or directory
> Loading tmpft...
> mount: /proc/mounts: No such file or directory
