similar to: updates to Documentation/nfsroot.txt ?

The in-kernel nfsroot code is obsoleted by kinit. Remove it; it causes conflicts. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 161e1dc16ec1129b30b634a2a8dcbbd1937800c5 tree c30da837d746fe65d8a13ccf6f27bd381948edb4 parent 018604e070e143657abcf0cb256a1e2dda205d97 author H. Peter Anvin <hpa at zytor.com> Sat, 20 May 2006 16:24:05 -0700 committer H. Peter Anvin <hpa at

Hello all, I have observed a problem with a diskless PXE client I am attempting to configure. PXE/NFS/DHCP/TFTPd server is running CentOS5.1 and the Diskless workstation's root and kernel was extracted from a CentOS5.1 (custom kernel due to setting to enable Root File System support). Problem: When the diskless client boots and logs in I notice that my root user is being squashed, even if I

This patch removes support for use of NFS as a root filesystem from the kernel. It also updates the documentation to reflect this. b/Documentation/nfsroot.txt | 97 +++--- b/arch/arm/def-configs/a5k | 1 b/arch/arm/def-configs/adi_evb | 1 b/arch/arm/def-configs/adsbitsy | 1 b/arch/arm/def-configs/anakin | 1

Hi everyone, I got the error: NET4: Unix domain sockets 1.0/smp for linux NET4.0 ds: no socket drivers loaded request_module[block-major-8]: root fs not mounted VFS: Cannot open root device ""or 08:03 Please append a correct "root"boot option The strange thing is that it tries to mount from harddisk. This I got somewhere else: "the kernel looks like it is trying to

Hi This is a PXELinux problem that I'm facing. The problem, in brief, is that I have a set of diskless nodes (AMD Athlon XP 1800+ with 256MB RAM) connected via an internal 172.20.0.0/24 network to a dual AMD Opteron running SuSE Linux 8.3 for AMD64. I want the remote machines to diskless boot off the main server and run independently. The diskless machines have a PXE-compliant BIOS for

Package: klibc-utils Version: 1.5.15-1 Hello! I'm trying to boot Debian from a different nic than the first one. After some digging into klibc and initramfs, it seems like DEVICE=all in /etc/initramfs-tools/initramfs.conf is near a solution (I cannot reliable tell, which name the nic has, it may be eth0, eth1, eth2, eth3, ...; as I've machines with one to four nics). /scripts/functions

hello, sorry for late reply, bin digging through klibc backlog and this seems the only unawswered one. thanks for patience. :) On Tue, 27 Oct 2009, Nico Schottelius wrote: > Package: klibc-utils > Version: 1.5.15-1 hmm, unstable got newer klibc innbetwen, 1.5.17 should fix most of the listed pain, although 1.5.18-1 would be recommended, just uploaded. :) > > I'm trying to

any comments? if nothing else, is there any way to atomically setup bridge? not on list, please cc. ---------- Forwarded message ---------- Date: Wed, 12 Jan 2005 21:08:15 -0000 From: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> To: Adam Sulmicki <adam@cfar.umd.edu>, xen-devel@lists.sourceforge.net Subject: RE: [Xen-devel] nfsroot and brige > hello, > it seems like a catch-22 to

folks, Im trying to boot to runlevel 4 explicitly, using this stanza: ie with a single 4 at end of APPEND line. LABEL 2.6.11-r10c2-soekris-v1 MENU LABEL ^j. runlevel 4 2.6.11-r10c2-soekris-v1 # 4 MENU DEFAULT KERNEL vmlinuz-2.6.11-r10c2-soekris-v1 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/foo

I made a diskless node centos. the pxelinux.cfg/default file : default centos label centos kernel vmlinuz-2.6.18-194.el5 append initrd=initrd-2.6.18-194.el5.nfs.img nfsroot=10.10.10.1:/srv/centos ip=dhcp rw I can successfull*y boot-strap the system with no error.* *But when i shutdown or reboot it . It will show in the screen :* *Unmounting NFS filesystems* *INIT:no more process

the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs

Does anyone have any good how-to's or documentation on setting up read only root NFS for pxe booting diskless computers? A few months ago I stumbled upon an official Redhat doc through a google search(not hosted by redhat and I cannot find it anywhere on the Redhat site) written by Dave Kline named "Configuring diskless clients with Red Hat Enterprise Linux" from 2011. It seemed to

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

This patch removes IP autoconfiguration (CONFIG_IP_PNP and friends) support from the kernel, and ensures that using NFS as the root filesystem (CONFIG_NFS_ROOT) will no longer work. b/arch/alpha/defconfig | 1 b/arch/arm/def-configs/a5k | 1 b/arch/arm/def-configs/adi_evb | 4 b/arch/arm/def-configs/adsbitsy | 4

On Nov 19, 2015, at 3:49 PM, Devin Reade <gdr at gno.org> wrote: > > size of the disk was never the original motivation for > keeping / separate, at least within my memory Prior to SysV, the location of user home directories was not standardized, and AT&T recommended that you put them in /usr.[1] Also, in the PDP days, you had things like the RL and RK series drives, which

changing i386 COMMAND_LINE_SIZE to 1024 attached is a simplistic fix to change kernel's command-line size from 256 to 1024, tomatch capability in syslinux 3.08. It seems to work. Is this all there is to it ? One of the reasons I did this was to figure out what extra options are appearing, and why. b4 extending: (the last bit is truncated) Jun 4 06:31:05 truck kernel: Kernel command

I just checked in changes to kinit, such that it is now a single 29KB executable that replaces the kernel's ipconfig and nfsroot code. The kinit code isn't very elegant, but I figured it was better to save space than to fully generalise it so that it could be extended in a sort of modular fashion. If someone wants modularity, I figure they can spend the few extra KB and run the

> Hi, > > I've got a task to have a small number of laptops netboot Linux over > WiFi. The kernel is loaded off the USB stick of cource, it's off topic > for now. > > The WPA-supplicant daemon is started early by dracut off initrd. It > works. Mostly. > > The problem is that upon shutdown systemd terminates all the processes > FIRST and unmounts filesystems

Hi, I've got a task to have a small number of laptops netboot Linux over WiFi. The kernel is loaded off the USB stick of cource, it's off topic for now. The WPA-supplicant daemon is started early by dracut off initrd. It works. Mostly. The problem is that upon shutdown systemd terminates all the processes FIRST and unmounts filesystems NEXT. Guess what? Upon termination,