Hello, This is the first entry in my life.cfg: > label live > menu label Live > kernel debian-live/i386/vmlinuz-2.6.26-2-486 > append initrd=debian-live/i386/initrd.img-2.6.26-2-486 boot=live > union=aufs netboot=cifs nfsroot=//192.168.1.1/bootimage/
Thanks, ~Juergen On Thu, Apr 30, 2009 at 10:30 PM, Richard Nelson <[email protected]> wrote: > Greetings, > > Could you post your tftpboot boot information? I think the file is > tftpboot/debian-live/i386/boot-screens/menu.cfg > > But it would be helpful to see the append line. > > Thanks. > > On Thu, Apr 30, 2009 at 4:45 PM, Juergen Fiedler > <[email protected]> wrote: >> Hello, >> >> I am trying to build a Lenny net image on a Lenny machine with >> live-helper 1.0.4+20090420.1002 from live.debian.net. >> The build was configured with: >> >>> lh_config --net-root-filesystem "cifs" \ >>> --net-root-server "192.168.1.1" \ >>> --net-root-path "/bootimage/" \ >>> --binary-images "net" >> >> The image boots OK, but when it comes to mounting the root, I see the >> following: >> >>> Begin: Trying netboot from //192.168.1.1/bootimage/ /live/image ... Begin: >>> Trying nfsmount - >>> 0 nolock -o ro //192.168.1.1/bootimage/ /live/image/ ... nfsmount: need a >>> server >> >> The last message ('nfsmount: need a server') repeats until I do a >> ctrl-alt-del. >> So, basically, it would appear that init is skipping the CIFS mount >> and proceeding directly to NFS. >> >> It looks like there is no /sbin/mount.cifs in the initrd, which may be >> the reason why the CIFS mount isn't working. >> Did I leave out an important switch to keep that from being included, >> or do I need a special hook or some such thing? >> I'm sure I am missing something rather obvious, but I've been trying >> for hours and not getting anywhere. >> >> Speaking of obvious: Yes, I can browse //192.168.1.1/bootimage/ with >> smbclient. Right now, it is pinting to the live/ folder withing >> binary/. >> I have also tried sharing binary/ itself as //192.168.1.1/bootimage/, >> but it didn't seem to make a difference. >> >> Can anybody help? >> >> >> Thank you, >> ~Juergen >> >> >> -- >> To UNSUBSCRIBE, email to [email protected] >> with a subject of "unsubscribe". Trouble? Contact [email protected] >> >> > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
