Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
howtos:network_services:nfs_root [2018/05/28 22:09 (UTC)]
bifferos [Creating the kernel]
howtos:network_services:nfs_root [2018/05/28 22:11 (UTC)]
bifferos [Configuring LILO]
Line 97: Line 97:
 Obviously keep your default linux kernel in another image= section so you can switch between booting the nfsroot and the normal kernel to play around with this stuff. Obviously keep your default linux kernel in another image= section so you can switch between booting the nfsroot and the normal kernel to play around with this stuff.
  
-You cannot specify a normal root= entry in this section because ​lilo doesn'​t recognise /dev/nfs for root (the device doesn'​t actually exist to LILO). ​ So instead just specify it in the append= line which lilo doesn'​t try to interpret, and lilo will include this extra nfsroot image without error.+You cannot specify a normal root= entry in this section because ​LILO doesn'​t recognise /dev/nfs for root (the device doesn'​t actually exist to LILO). ​ So instead just specify it in the append= line which LILO doesn'​t try to interpret, and LILO will include this extra nfsroot image without error.
  
 The v3 seems to be really important in making anything at all happen on boot.  If that isn't set, no communication seems to occur. The v3 seems to be really important in making anything at all happen on boot.  If that isn't set, no communication seems to occur.
  
-The '​rw'​ is also important. ​ It prevents the fsck of the root fs. because root is NFS and can't be checked. ​ Slackware won't boot properly if we give '​ro'​. ​ Instead of using '​rw'​ you could optionally hack fsck out of the slackware ​startup scripts on your NFS root, however simply using '​rw'​ is quicker (albeit dirtier).+The '​rw'​ is also important. ​ It prevents the fsck of the root fs. because root is NFS and can't be checked. ​ Slackware won't boot properly if we give '​ro'​. ​ Instead of using '​rw'​ you could optionally hack fsck out of the Slackware ​startup scripts on your NFS root, however simply using '​rw'​ is quicker (albeit dirtier).
  
 With the kernel compilation finished, copy the kernel into the /boot directory and rename it: With the kernel compilation finished, copy the kernel into the /boot directory and rename it:
Line 107: Line 107:
 <​code>​cp /​usr/​src/​linux/​arch/​x86/​boot/​bzImage /​boot/​vmlinuz-nfsroot</​code>​ <​code>​cp /​usr/​src/​linux/​arch/​x86/​boot/​bzImage /​boot/​vmlinuz-nfsroot</​code>​
  
-It may be created elsewhere depending on your architecture,​ e.g. x64, arm.+It may be created elsewhere ​than arch/​x86 ​depending on your architecture,​ e.g. x64, arm.
  
 Don't forget to run LILO: Don't forget to run LILO:

In Other Languages
QR Code
QR Code howtos:network_services:nfs_root (generated for current page)