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
Next revision
Previous revision
Last revision Both sides next revision
howtos:network_services:nfs_root [2018/05/28 22:04 (UTC)]
bifferos
howtos:network_services:nfs_root [2018/05/28 22:11 (UTC)]
bifferos [Configuring LILO]
Line 50: Line 50:
 ==== Creating the kernel ==== ==== Creating the kernel ====
  
-The full huge kernel that comes with Slackware is close to providing everything we need, but we still need to recompile it.  I'd recommend doing the compilation on a 32-bit virtual machine if you are targeting a 32-bit thin client, or 64-bit if your thin client is 64-bit. ​ There are ways to avoid this and cross-compile 32->64 bit and visa versa but virtual machines are cheap and life is short:+The full huge kernel that comes with Slackware ​14.2 is close to providing everything we need, but we still need to recompile it.  I'd recommend doing the compilation on a 32-bit virtual machine if you are targeting a 32-bit thin client, or 64-bit if your thin client is 64-bit. ​ There are ways to avoid this and cross-compile ​kernels ​32->64 bit and visa versa but virtual machines are cheap and life is short:
  
 <​code>#​ cd /​usr/​src/​linux <​code>#​ cd /​usr/​src/​linux
Line 71: Line 71:
 <​code>​File Systems -> Network File systems -> Root file system on NFS [*]</​code>​ <​code>​File Systems -> Network File systems -> Root file system on NFS [*]</​code>​
  
-[OPTIONAL] It's pretty useful to append a local version to this kernel release. ​ I'd advise doing this to differentiate it from your standard Slackware huge kernel and avoid clobbering the modules from that by mistake:+[OPTIONAL] It's pretty useful to append a local version to this kernel release. ​ I'd advise doing this to differentiate it from your standard Slackware huge kernel and avoid clobbering the modules from that by mistake.  We can just add '​-nfsroot'​:
  
 <​code>​(-nfsroot) General Setup -> Local version - append to kernel release</​code>​ <​code>​(-nfsroot) General Setup -> Local version - append to kernel release</​code>​
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)