Felix Groebert wrote:> hi peter, > > i have the same problem as the guy below this message, i boot over dhcp > (of testing in debian, 2.0pl5-14), and tftpd-hpa (0.28-2.1, > /usr/sbin/in.tftpd -s /tftpboot -r blksize -v -v -v) the pxelinux.0 > (syslinux version 1.75-1) with a subnotebook. a sony vaio c1mzx, with a > transmeta crusoe cpu ( :D ) and a sony realtek 8139(c?) chipset. > pxelinux loads very well and downloading files from the tftpd works, > for example i try to download the the 2.4.18 vmlinuz (i type vmlinuz), > it uncompresses the file and says, ...Ok, booting the kernel. and stops. > but when i try to load linux.bin initrd=root.bin it loops prinit 0108 > and newline. >Once again, WITH FEELING... DON'T NAME YOUR KERNEL SOMETHING ENDING IN .bin This is getting to be such an FAQ it's silly. Anyone want to maintain a FAQ for this mailing list? -hpa
"H. Peter Anvin" <hpa at zytor.com> writes:> Once again, WITH FEELING... > > DON'T NAME YOUR KERNEL SOMETHING ENDING IN .bin > > This is getting to be such an FAQ it's silly. Anyone want to maintain a > FAQ for this mailing list?If lots of people have the same question, it usually means there is a flaw in the design or in the documentation. Searching all of the .doc files in the SYSLINUX 2.0 distribution, the only reference I can find to .bin files is this section of syslinux.doc: The following extensions are recognized (case insensitive): none or other Linux kernel image .cbt COMBOOT image (not runnable from DOS) .bss Boot sector, DOS superblock will be patched in [SYSLINUX only] .bs Boot sector [SYSLINUX only] .bin "CD boot sector" [ISOLINUX only] .com COMBOOT image (runnable from DOS) .img Disk image [ISOLINUX only] .0 PXE bootstrap program (NBP) [PXELINUX only] This text pretty clearly states that .bin is recognized by "ISOLINUX only". I suggest you at least fix the documentation. On the other hand, I do not think this is only a documentation problem. A .bin suffix has a long history of meaning "just a bunch of bytes", the historic equivalent of application/octet-stream. To interpret it differently than no suffix is a mistake, in my opinion, because it will confuse people. Could you use a different suffix for CD boot sectors? Failing that, is there any validation you could do on .bin files? That is, could you look for some signature for CD boot sectors (or Linux kernels)? - Pat
> This is getting to be such an FAQ it's silly. Anyone want to maintain a > FAQ for this mailing list?Anyone know of a tool that would compile a master FAQ from email messages posted to it? My idea is to mail a FAQ-sub@ address with a message. Q: starts the question, A: starts the answer. It would be sent on to the moderator(s) who just read it and hits Reply if it's to be added to the FAQ. One thing I'd put in the FAQ is a note about Kernel Panics and messages about 'init not found' when booting up using pxelinux & NFS. I messed about for days, seaching news groups etc. In the end it came down to missing library files in the NFS mounted root file system. I'd been lazzy and copied files from a running system, missing the odd library in doing so. I'm now up and running on a PII-350 'X Terminal' with 196MB RAM. It's fast and *very* quiet. I'm going to build another one and make a Ogg Vorbis player for the HiFi :o) Many thanks for a great tool! Mark