similar to: NFS error 101, again

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 have been successful with configuring TCP on a 2.4.23 kernel that was built with the "IP: kernel level autoconfiguration" turned on with the following append line: APPEND initrd=rootfs.gz root=/dev/ram0 rw ip=192.168.0.175::192.168.0.1:255.255.255.0 ^ ^ ^ | |

Hi, Thanks for your reply Josef. > In netstat -p |grep rpc I get: > dgram 56732 rpc.nfsd > dgram 55905 rpc.mountd > While client looks for socket 100003/2 or 100005/1, mine rpc.mountd is on socket 55905. Maybe it is a reason for an error 22. >The port numbers are RPC numbers, not sockets. Try 'rpcinfo -p' for these. rpcinfo -p 100005 mountd 100003 nfs So this looks

Okay, now, before 3.10 is finalized... what bug reports am I still forgetting? -hpa

SYSLINUX 3.11-pre5 is hereby a bug fix release candidate. If I don't receive any problem reports, I will release it as-is on Tuesday, August 30. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hello everyone, I am using pxelinux to boot kernel from network, which goes ok. But when root must be mounted from NFS, I get the following code: Looking up port 100003/2 on 192.168.1.1 RPC: sendmsg returned error 22 portmap: RPC call returned error 22 ROOT-NFS: unable to get nfsd port number from server, using default looking up port of RPC 100005/1 on 192.168.1.1 RPC: sendmsg returned error

One feature that I haven't seen in OpenSSH (It may be there) is an automatic blacklisting of IP addresses when a certain number of login attempts are reached from that IP address. It seems like it is popular these days to try brute force access on password cracking and automatic blacklisting may limit these attempts. Best regards/Nils Hammar

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

folks, Im finding that using a config like this: SERIAL 0 19200 #IPAPPEND 2 PROMPT 1 TIMEOUT 100 IMPLICIT 0 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsaddrs=10.10.10.100:10.10.10.2:10.10.10.2:255.255.255.0:soekris:eth0 nfsroot=10.10.10.2:/nfshost/truck panic=15 LABEL deb268 KERNEL vmlinuz-2.6.8-1-386 initrd=initrd.img-2.6.8-1-386 panic=10 LABEL deb268-ram KERNEL vmlinuz-2.6.8-1-386

Hi, everybody! My pxelinux.0/default file is: LABEL linux KERNEL vmlinuz-2.6.16 APPEND initrd=initrd-2.6.16.img root=192.168.4.110:/clients/192.168.4.100/root When mounting I get: switchroot: mount failed: 22 Kernel panic - not syncing: Attempted tp kill init! Before it I get some messages about: Can't find /dev/console. /clients/192.168.4.100/root/dev was empty. I've copied my

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending

I have released SYSLINUX 3.08-pre5. Sparse files should now work correctly in extlinux. Symlink support still needs to be added, though. -hpa

I have finished the work of transmitting sparc64 ROM parameters to kinit via the file /arch.cmd in rootfs. The result is pretty nice, as it gives a clean interface for any other architectures which want to collect architecture-specific options at initialization time. I have also merged my tree with v2.6.17-rc5, although it was a completely orthogonal merge set. The following issues are

Hi folks, is there anywhere an opensource PXE bootdisk (i've only found some from M$ as binary image) or a howto for generating one w/ the syslinux package ? cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT services phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email:

Hi folks, here's a patch which cleans up the nasm call from Makefiles. Abusing libtool and then having to drop in some additional wrapper script to rewrite the commandline again is rather stupid. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/

Hi folks, I've noticed an problem with openssh on GNU/Linux: pressing ctrl+s locks up the ssh client. Only killing it helps. Is this problem already known ? cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service phone: +49 36207 519931 www: http://www.metux.de/ fax: +49 36207 519932 email:

Hello folks, I fried of mine offered us a few metric tons of server hardware that we can use for our CI and testing. He also offered to host and operate it. The only problem is power costs. At his location (Serbia) power costs seem to be relatively low compared to average western countries, but for such a farm still too much for a single hobbyist. So the vital question now is: can we find any

Checkout http://www.voip-info.org/wiki-Asterisk+variables I believe that should have the answer for you. furthermore assuming that your number is always going to be 12 digits. exten => _NXX.,1,SetVar(mynumber=${EXTEN:0:12}) - will give you your number. Hope this helps. Umar On Sun, 13 Mar 2005 09:25:11 +0100, Harald Milz <hm@seneca.muc.de> wrote: > Hi, > > this

I seem to be having trouble getting the NFS root filesystem to mount after the kernel boots. As per thread from 2002 16 January (http://www.zytor.com/pipermail/syslinux/2002-January/000028.html), I double checked my DHCP config files, but to no avail. It cannot seem to attach to the mountd port on the bootserver. Here is some output from the kernel: loop: loaded (max 8 devices) Intel(R) PRO/1000

Sir or Madam, I am in a new project writing software for embedded apps. We use a single board computer consisting of (a) linux (b) syslinux boot loader (c) compact flash file system (d) x86 processor. (see www.embeddedx86.com) (e) other HW and SW. Using vendor provided files, I can easily prepare a compact flash (CF) system which boots 2.4.23 linux just fine. I can telnet in and so on and so