Re: Network install of Woody
On Fri, 21 Feb 2003, Eduard Bloch wrote: #include hallo.h * John Summerfield [Fri, Feb 21 2003, 02:10:57PM]: to be a lot of interest, but not too much concrete input. Maybe one of the issues is there are so many ways to get it to work? If I were to write it (assuming I knew enough, which at present I don't), you could probably point out errors, but not the inadequacies. At present, I in my ignorance am well-equipped to locate the latter. If I wait until I have worked through it and found a path that works, then it will become clear enough that I will no longer be able to indentify clearly what's missing, what facts I have assumed but which might not be known to others. What about making notices on your way? Later, you can review them and remember what caused the problems and how another person may solve the problem easier. In my experience, and the experience of others, good documentation can only be written by someone who knows and understands the topic well. This is why authors such as Colleen McCullouch (she spent 13 years researching before writing First Man in Rome) spend so much time in research. While I could muddle my way through, at the end of it I would not have as good a document as I would expect others here would produce. I see my my greatest value in this as a checker; at present I won't make the same assumptions someone to whom it's a trivial undertaking to make. -- Cheers John Summerfield Please, no off-list mail. It won't be read, it will be handled as spam. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Network install of Woody
#include hallo.h * John Summerfield [Fri, Feb 21 2003, 02:10:57PM]: to be a lot of interest, but not too much concrete input. Maybe one of the issues is there are so many ways to get it to work? If I were to write it (assuming I knew enough, which at present I don't), you could probably point out errors, but not the inadequacies. At present, I in my ignorance am well-equipped to locate the latter. If I wait until I have worked through it and found a path that works, then it will become clear enough that I will no longer be able to indentify clearly what's missing, what facts I have assumed but which might not be known to others. What about making notices on your way? Later, you can review them and remember what caused the problems and how another person may solve the problem easier. Gruss/Regards, Eduard. -- Um sich von einer zu großen Liebe oder Duldsamkeit für etwas zu heilen, muß man nicht die Feinde davon lesen, sondern die Freunde. Lavater -- Jean Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Network install of Woody
The documentation for using bootroms (such as PXE) is incomplete. See the (ia386) install guide: 4.5.5 Move TFTP Images Into Place which links to 11.2.3, and contains the text, NOT YET WRITTEN. 5.5 Booting from TFTP This talks about floppies, confusing since I don't plan on using one (unless I lack a working bootrom in the NIC). 4.5.6 Installing with TFTP and NFS Root Doesn't really give any idea about how to do it. How do I create the NFS root to export? It happens I'm running Red Hat Linux, so Debian tools won't work. Maybe if it's on a CD somewhere 11.2.3 Description of Installation System Files This mentions several files called tftpboot.img, but I recall someone on another list found it impossible to boot such large files because at that time the system's in real mode, can address no more than one Mbyte of RAM, and of that, only 640K is available to programs. pxelinux can load a kernel and an initrd, so it doesn't look like those are the right files. Possibly, I could use a rescue image and a root image. I have the inclination to try to get it working. Is there someone who can work with me? What I suggest is someone create corrected text (don't worry about formatting), and I will try it out. When the text checks out, maybe others can try it, but it should go to the maintainer for inclusion. I already have working dhcp, tftp and a couple of machines that do PXE-boot, and I also have an Etherboot ROM-on-a-floppy that boots of the network, so most of the work's done. I don't plan to visit other ways of handing out IP addresses etc. ISC's DHCPD works and is available (AFAIK) to all Linux users. btw Do not reply directly to me. Mail to this address not from an approved source gets treated as spam. If you think the discussion would clutter the list too much, I can contact you using another address. -- Cheers John Summerfield -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Network install of Woody
On Fri, Feb 21, 2003 at 11:58:23AM +0800, John Summerfield wrote: The documentation for using bootroms (such as PXE) is incomplete. See the (ia386) install guide: 4.5.5 Move TFTP Images Into Place which links to 11.2.3, and contains the text, NOT YET WRITTEN. 5.5 Booting from TFTP This talks about floppies, confusing since I don't plan on using one (unless I lack a working bootrom in the NIC). 4.5.6 Installing with TFTP and NFS Root Doesn't really give any idea about how to do it. How do I create the NFS root to export? It happens I'm running Red Hat Linux, so Debian tools won't work. Maybe if it's on a CD somewhere 11.2.3 Description of Installation System Files This mentions several files called tftpboot.img, but I recall someone on another list found it impossible to boot such large files because at that time the system's in real mode, can address no more than one Mbyte of RAM, and of that, only 640K is available to programs. pxelinux can load a kernel and an initrd, so it doesn't look like those are the right files. Possibly, I could use a rescue image and a root image. I have the inclination to try to get it working. Is there someone who can work with me? What I suggest is someone create corrected text (don't worry about formatting), and I will try it out. When the text checks out, maybe others can try it, but it should go to the maintainer for inclusion. Well, I'd suggest the opposite. We included that text based on one person's experience, if you can tell us how to improve the text, based on your experience, we'd be happy to change it. There seems to be a lot of interest, but not too much concrete input. Maybe one of the issues is there are so many ways to get it to work? -- The way the Romans made sure their bridges worked is what we should do with software engineers. They put the designer under the bridge, and then they marched over it. -- Lawrence Bernstein, Discover, Feb 2003 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Network install of Woody
On Thu, 20 Feb 2003, Chris Tillman wrote: On Fri, Feb 21, 2003 at 11:58:23AM +0800, John Summerfield wrote: The documentation for using bootroms (such as PXE) is incomplete. See the (ia386) install guide: 4.5.5 Move TFTP Images Into Place which links to 11.2.3, and contains the text, NOT YET WRITTEN. 5.5 Booting from TFTP This talks about floppies, confusing since I don't plan on using one (unless I lack a working bootrom in the NIC). 4.5.6 Installing with TFTP and NFS Root Doesn't really give any idea about how to do it. How do I create the NFS root to export? It happens I'm running Red Hat Linux, so Debian tools won't work. Maybe if it's on a CD somewhere 11.2.3 Description of Installation System Files This mentions several files called tftpboot.img, but I recall someone on another list found it impossible to boot such large files because at that time the system's in real mode, can address no more than one Mbyte of RAM, and of that, only 640K is available to programs. pxelinux can load a kernel and an initrd, so it doesn't look like those are the right files. Possibly, I could use a rescue image and a root image. I have the inclination to try to get it working. Is there someone who can work with me? What I suggest is someone create corrected text (don't worry about formatting), and I will try it out. When the text checks out, maybe others can try it, but it should go to the maintainer for inclusion. Well, I'd suggest the opposite. We included that text based on one person's experience, if you can tell us how to improve the text, based on your experience, we'd be happy to change it. There seems to be a lot of interest, but not too much concrete input. Maybe one of the issues is there are so many ways to get it to work? If I were to write it (assuming I knew enough, which at present I don't), you could probably point out errors, but not the inadequacies. At present, I in my ignorance am well-equipped to locate the latter. If I wait until I have worked through it and found a path that works, then it will become clear enough that I will no longer be able to indentify clearly what's missing, what facts I have assumed but which might not be known to others. -- Cheers John Summerfield -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
