Bug#140579: Report: tftpboot install successfull
I understand that. But just like we have a bunch of architectures, we have a bunch of netboot options. You generally don't have a lot of choices about what your hardware supports. Telling someone whose card doesn't support pxe to use pxe because it's better is no more sensible than telling an m68k user to use the i386 boot floppies because i386 is better. True enough. So why does that prevent us from giving an overview of the various options and providing some criteria to help users pick one or the other? It may be true that generally better or worse doesn't matter -- just anything that works will do. On installing Debian, it would be very difficult for users to get a ROM burning, however there would be a lot of eepro cards which can PXE boot. I would rather like to be able to netboot with grub floppies, so that it only requires one floppy (grub) to start up the installation, but that requires an extracted image of the installation disk to use as NFS root, and a kernel vmlinuz image available via TFTP. I don't think we provide either images per default, but it might be worth considering for an option in the future, if grub cannot load tftpboot images. For using GRUB to start install: set up server to allow TFTP, and provide vmlinuz, and allow nfs export. get grub source and recompile with network card support, and create a floppy using dd command. ./configure --enable-eepro100 make dd if=stage1/stage1 of=image dd if=stage2/stage2 of=image bs=512 seek=1 dd if=image of=/dev/fd0 ; sync Then start the machine with the floppy (the following example will work on many installations): grub ifconfig --address=192.168.1.2 --server=192.168.1.1 grub kernel (nd)/boot/vmlinuz init=/bin/sh root=/dev/nfs nfsroot=192.168.1.1:/,flags=ro init=/bin/sh grub boot The above example will load the kernel via eepro card from /boot/vmlinuz on 192.168.1.1, and use / of the 192.168.1.1 as the / of 192.168.1.2 (the one to be installed) read-only via NFS, using /bin/sh as initial program. It is trivial to start up dbootstrap in this way also. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Fri, Jan 03, 2003 at 12:45:05PM -0600, Adam DiCarlo wrote: So why does that prevent us from giving an overview of the various options and providing some criteria to help users pick one or the other? It doesn't; that would be very good. I thought I had read that the goal was to eliminate all but one method. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Le ven 03/01/2003 à 02:37, Chris Tillman a écrit : On Thu, Jan 02, 2003 at 10:33:36PM +0100, nb wrote: Le jeu 02/01/2003 à 06:25, Chris Tillman a écrit : On Tue, Dec 31, 2002 at 03:50:56PM +0100, nb wrote: 192.168.1.255 would be better OK, got that. In chapter 4.5.5 it is said that the TFTP client will look for is client-ip-in-hexclient-architecture. It is completely wrong. In our case the default file is sufficient. In fact it will try : C0A801 (192.168.1.200 in little endian as in x86) then : 0A01010C8 then : 0A01010C then : 0A01010 . . . then : 0 and finally : default I take it that is wrong for PXE, but is it wrong for other methods of booting? Does it depend on the tftp server chosen or something? It's also wrong for netboot which needs an image and a root fs added to with mknbi. These are the two methods I practised. -- nb [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Le ven 03/01/2003 à 03:37, Adam DiCarlo a écrit : Chris Tillman [EMAIL PROTECTED] writes: I also agree that what I read looked good, but it didn't seem to cover all of the issues mentioned in the bug, such as coming up with an overview of the different netboot options and which is best to use... Yes, and I don't have a clue about that. Well, even if we just list them and provide links, I think that would be enough to close the bug. I think so. Other methods need a removable media so tftpboot is not necessary. It is then possible to use the classical boot-floppies method. This even with new media like pendrives. It becomes a network install with local boot. The same as a cdrom one. I looked at mknbi, I think I could probably document its usage also from what was already given, but it would need to be put into context. ... or, just a link to existing documentation on the web would work too. I agree again with you. Here's the first one : http://etherboot.sourceforge.net/ Rich and very well documented. Thanks for the effort btw... It was a real pleasure. -- nb [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Sun, Dec 29, 2002 at 08:48:48PM +0100, nb wrote: Thanks to Michael R. Schwarzbach and he's post I finally can install debian via tftp. I think the need is going growing to do that and it's really time to update documentation. I've spent 24 hours to do that and sentences like NOT YET WRITTEN are not acceptable today. I hope this will go better. Since you have spent much time on this, and been successful at it, it seems that perhaps you are better qualified to write that documentation than most. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Le jeu 02/01/2003 à 06:25, Chris Tillman a écrit :
On Tue, Dec 31, 2002 at 03:50:56PM +0100, nb wrote:
PXE is the most natural method in the sens that it doesn't need any
supplementary media.
It's the one everyone can use on a real diskless machine.
It finally worked for me and her's what I've done for that.
See what you think of the following doc patch:
A very good job.
See just two remarks.
Index: inst-methods.sgml
===
RCS file: /cvs/debian-boot/boot-floppies/documentation/en/inst-methods.sgml,v
retrieving revision 1.142
diff -u -r1.142 inst-methods.sgml
--- inst-methods.sgml 22 Sep 2002 15:07:44 - 1.142
+++ inst-methods.sgml 2 Jan 2003 05:21:28 -
@@ -1181,14 +1181,61 @@
fixed-address 192.168.1.90;
}
/example
+p
In this example, there is one server varservername/var which performs all
of the work of DHCP, server, TFTP server, and network gateway. You
will almost certainly need to change the domain-name options, as well
as the server name and client hardware address. The varfilename/var option
should be the name of the file which will be retrieved via TFTP.
-
+p
After you have edited the prgndhcpd/prgn configuration file, restart it
-with tt/etc/init.d/dhcpd restart/tt. ]]
+with tt/etc/init.d/dhcpd restart/tt.
+
+![ %i386 [
+p
+Here is another example for a filedhcp.conf/file using the
+Pre-boot Execution Environment (PXE) method of TFTP.
+example
+option domain-name example.com;
+
+default-lease-time 6048;
+max-lease-time 604800;
+
+allow booting;
+allow bootp;
+
+# The next paragraph needs to be modified to fit your case
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.200 192.168.1.253;
+ option subnet-mask 255.255.255.0;
+ option broadcast-address 10.1.1.255;
192.168.1.255 would be better
+# the gateway address which can be different
+# (access to the internet for instance)
+ option routers 192.168.1.1;
+# indicate the dns you want to use
+ option domain-name-servers 10.1.1.3;
+}
+
+host tftpserver {
+# tftp server ip address
+ fixed-address 192.168.1.90;
+# tftp server hardware address
+ hardware ethernet 01:23:45:67:89:AB;
+}
+
+group {
+ next-server 192.168.1.3;
+ host tftpclient {
+# tftp client hardware address
+ hardware ethernet 00:10:DC:27:6C:15;
+ filename /tftpboot/pxelinux.0;
+ }
+}
+/example
+Note that for PXE booting, the client filename filepxelinux.0/file
+is a boot loader, not a kernel image (see ref id=tftp-images
+below).
+!-- end i386 -- ]]
+!-- end supports-dhcp -- ]]
sect1 id=tftpdEnabling the TFTP Server
p
@@ -1210,6 +1257,12 @@
reload/tt (for potato/2.2 and newer systems use tt/etc/init.d/inetd
reload/tt); on other machines, find out the process ID for
prgninetd/prgn, and run ttkill -HUP varinetd-pid/var/tt.
+![ %i386 [
+p
+To use the Pre-boot Execution Environment (PXE) method of TFTP
+booting, you will need a TFTP server with tttsize/tt support.
+On a debian; server, prgntftp-hpa/prgn qualifies.
+]]
![ %mips [
p
@@ -1257,6 +1310,31 @@
First issue the ttobase=16/tt command to set the output to hex,
then enter the individual components of the client IP one at a time.
As for varclient-architecture/var, try out some values.
In chapter 4.5.5 it is said that the TFTP client will look for is
client-ip-in-hexclient-architecture. It is completely wrong.
In our case the default file is sufficient.
In fact it will try : C0A801 (192.168.1.200 in little endian as in x86)
then : 0A01010C8
then : 0A01010C
then : 0A01010
.
.
.
then : 0
and finally : default
+]]
+
+![ %i386 [
+p
+For PXE booting, you can use the boot loader included with
+prgnsyslinux/prgn: filepxelinux.0/file. The boot loader should
+be copied into the file/tftpboot/file folder. Then create a
+subdirectory within file/tftpboot/file named
+file/tftpboot/pxelinux.cfg/file, and within that directory create
+a text file filedefault/file. Here is an example of a
+filedefault/file file's contents:
+example
+default lanlinux
+prompt 1
+
+label lanlinux
+ kernel tftpboot.img
+ append load initrd=root.bin devfs=nomount
+/example
+ttdevfs=nomount/tt is important, because without it there may be
+problems mounting the root.bin file system once the kernel is booted.
+p
+Finally, copy the filetftpboot.img/file and fileroot.bin/file
+files from the Debian ftp archive into the file/tftpboot/file
+folder, where the bootloader will be looking for them.
]]
![ %mipsel [
--
nb [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Le jeu 02/01/2003 à 20:43, Matt Zimmerman a écrit : On Sun, Dec 29, 2002 at 08:48:48PM +0100, nb wrote: Thanks to Michael R. Schwarzbach and he's post I finally can install debian via tftp. I think the need is going growing to do that and it's really time to update documentation. I've spent 24 hours to do that and sentences like NOT YET WRITTEN are not acceptable today. I hope this will go better. Since you have spent much time on this, and been successful at it, it seems that perhaps you are better qualified to write that documentation than most. You are right. I have seen this with Adam DiCarlo and Chris Tillman. -- nb [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
I also agree that what I read looked good, but it didn't seem to cover all of the issues mentioned in the bug, such as coming up with an overview of the different netboot options and which is best to use... -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Thu, Jan 02, 2003 at 04:40:50PM -0600, Adam DiCarlo wrote: overview of the different netboot options and which is best to use... The one that works. You're asking for something like review the currently supported architectures and explain which is the best one to use. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Thu, Jan 02, 2003 at 10:33:36PM +0100, nb wrote: Le jeu 02/01/2003 à 06:25, Chris Tillman a écrit : On Tue, Dec 31, 2002 at 03:50:56PM +0100, nb wrote: 192.168.1.255 would be better OK, got that. In chapter 4.5.5 it is said that the TFTP client will look for is client-ip-in-hexclient-architecture. It is completely wrong. In our case the default file is sufficient. In fact it will try : C0A801 (192.168.1.200 in little endian as in x86) then : 0A01010C8 then : 0A01010C then : 0A01010 . . . then : 0 and finally : default I take it that is wrong for PXE, but is it wrong for other methods of booting? Does it depend on the tftp server chosen or something? -- ** |Chris Tillman[EMAIL PROTECTED] | | To HAVE, GIVE all TO all (ACIM) | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Thu, Jan 02, 2003 at 04:40:50PM -0600, Adam DiCarlo wrote: I also agree that what I read looked good, but it didn't seem to cover all of the issues mentioned in the bug, such as coming up with an overview of the different netboot options and which is best to use... -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ Yes, and I don't have a clue about that. I looked at mknbi, I think I could probably document its usage also from what was already given, but it would need to be put into context. -- ** |Chris Tillman[EMAIL PROTECTED] | | To HAVE, GIVE all TO all (ACIM) | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Michael Stone [EMAIL PROTECTED] writes: On Thu, Jan 02, 2003 at 04:40:50PM -0600, Adam DiCarlo wrote: overview of the different netboot options and which is best to use... The one that works. You're asking for something like review the currently supported architectures and explain which is the best one to use. Um, no, I'm just talking about netboot options on i386. -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Chris Tillman [EMAIL PROTECTED] writes: I also agree that what I read looked good, but it didn't seem to cover all of the issues mentioned in the bug, such as coming up with an overview of the different netboot options and which is best to use... Yes, and I don't have a clue about that. Well, even if we just list them and provide links, I think that would be enough to close the bug. I looked at mknbi, I think I could probably document its usage also from what was already given, but it would need to be put into context. ... or, just a link to existing documentation on the web would work too. Thanks for the effort btw... -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Thu, Jan 02, 2003 at 08:36:11PM -0600, Adam DiCarlo wrote: Um, no, I'm just talking about netboot options on i386. I understand that. But just like we have a bunch of architectures, we have a bunch of netboot options. You generally don't have a lot of choices about what your hardware supports. Telling someone whose card doesn't support pxe to use pxe because it's better is no more sensible than telling an m68k user to use the i386 boot floppies because i386 is better. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
On Tue, Dec 31, 2002 at 03:50:56PM +0100, nb wrote:
PXE is the most natural method in the sens that it doesn't need any
supplementary media.
It's the one everyone can use on a real diskless machine.
It finally worked for me and her's what I've done for that.
See what you think of the following doc patch:
Index: inst-methods.sgml
===
RCS file: /cvs/debian-boot/boot-floppies/documentation/en/inst-methods.sgml,v
retrieving revision 1.142
diff -u -r1.142 inst-methods.sgml
--- inst-methods.sgml 22 Sep 2002 15:07:44 - 1.142
+++ inst-methods.sgml 2 Jan 2003 05:21:28 -
@@ -1181,14 +1181,61 @@
fixed-address 192.168.1.90;
}
/example
+p
In this example, there is one server varservername/var which performs all
of the work of DHCP, server, TFTP server, and network gateway. You
will almost certainly need to change the domain-name options, as well
as the server name and client hardware address. The varfilename/var option
should be the name of the file which will be retrieved via TFTP.
-
+p
After you have edited the prgndhcpd/prgn configuration file, restart it
-with tt/etc/init.d/dhcpd restart/tt. ]]
+with tt/etc/init.d/dhcpd restart/tt.
+
+![ %i386 [
+p
+Here is another example for a filedhcp.conf/file using the
+Pre-boot Execution Environment (PXE) method of TFTP.
+example
+option domain-name example.com;
+
+default-lease-time 6048;
+max-lease-time 604800;
+
+allow booting;
+allow bootp;
+
+# The next paragraph needs to be modified to fit your case
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.200 192.168.1.253;
+ option subnet-mask 255.255.255.0;
+ option broadcast-address 10.1.1.255;
+# the gateway address which can be different
+# (access to the internet for instance)
+ option routers 192.168.1.1;
+# indicate the dns you want to use
+ option domain-name-servers 10.1.1.3;
+}
+
+host tftpserver {
+# tftp server ip address
+ fixed-address 192.168.1.90;
+# tftp server hardware address
+ hardware ethernet 01:23:45:67:89:AB;
+}
+
+group {
+ next-server 192.168.1.3;
+ host tftpclient {
+# tftp client hardware address
+ hardware ethernet 00:10:DC:27:6C:15;
+ filename /tftpboot/pxelinux.0;
+ }
+}
+/example
+Note that for PXE booting, the client filename filepxelinux.0/file
+is a boot loader, not a kernel image (see ref id=tftp-images
+below).
+!-- end i386 -- ]]
+!-- end supports-dhcp -- ]]
sect1 id=tftpdEnabling the TFTP Server
p
@@ -1210,6 +1257,12 @@
reload/tt (for potato/2.2 and newer systems use tt/etc/init.d/inetd
reload/tt); on other machines, find out the process ID for
prgninetd/prgn, and run ttkill -HUP varinetd-pid/var/tt.
+![ %i386 [
+p
+To use the Pre-boot Execution Environment (PXE) method of TFTP
+booting, you will need a TFTP server with tttsize/tt support.
+On a debian; server, prgntftp-hpa/prgn qualifies.
+]]
![ %mips [
p
@@ -1257,6 +1310,31 @@
First issue the ttobase=16/tt command to set the output to hex,
then enter the individual components of the client IP one at a time.
As for varclient-architecture/var, try out some values.
+]]
+
+![ %i386 [
+p
+For PXE booting, you can use the boot loader included with
+prgnsyslinux/prgn: filepxelinux.0/file. The boot loader should
+be copied into the file/tftpboot/file folder. Then create a
+subdirectory within file/tftpboot/file named
+file/tftpboot/pxelinux.cfg/file, and within that directory create
+a text file filedefault/file. Here is an example of a
+filedefault/file file's contents:
+example
+default lanlinux
+prompt 1
+
+label lanlinux
+ kernel tftpboot.img
+ append load initrd=root.bin devfs=nomount
+/example
+ttdevfs=nomount/tt is important, because without it there may be
+problems mounting the root.bin file system once the kernel is booted.
+p
+Finally, copy the filetftpboot.img/file and fileroot.bin/file
+files from the Debian ftp archive into the file/tftpboot/file
+folder, where the bootloader will be looking for them.
]]
![ %mipsel [
--
**
|Chris Tillman[EMAIL PROTECTED] |
| To HAVE, GIVE all TO all (ACIM) |
**
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
PXE is the most natural method in the sens that it doesn't need any
supplementary media.
It's the one everyone can use on a real diskless machine.
It finally worked for me and her's what I've done for that.
What is PXE ?
PXE (Pre-boot Execution Environment) is a protocol designed by Intel
that allows computers to boot through the network. PXE is stored in the
ROM of new generation net
work cards. When the computer boots up, the BIOS loads the PXE ROM in
the memory and executes it. A menu is displayed, allowing the computer
to boot an operating syst
em loaded through the network.
I - here's my dhcp.conf file : (4.5.3 in debian doc)
option domain-name dagami.org;
default-lease-time 6048;
max-lease-time 604800;
allow booting;
allow bootp;
# All the next paragraph need to be modified to feet your case
subnet 10.1.1.0 netmask 255.255.255.0 {
# 10.1.1.10 will be the first given address
range 10.1.1.10 10.1.1.32;
option subnet-mask 255.255.255.0;
option broadcast-address 10.1.1.255;
# the gateway address which can be different (acces to the internet for
instance)
option routers 10.1.1.2;
# indicate the dns you want to use
option domain-name-servers 10.1.1.3;
}
host tftpserver {
# tftp server ip address
fixed-address 10.1.1.3;
# tftp server hardware address
hardware ethernet 00:01:02:1B:16:AF;
}
group {
next-server 10.1.1.3;
host tftpclient {
# tftp client hardware address
hardware ethernet 00:10:DC:27:6C:15;
filename /tftpboot/pxelinux.0;
}
}
You can see that filename is not an image but pxelinux.0
pxelinux.0 is a syslinux component (we wil see that later).
II - TFTP server (4.5.4 in debain doc)
It is neccessary to install a tftp server with tsize support (tftp-hpa
on a debian server), it will not work otherwise.
III - TFTP configuration (4.5.5 in debian doc) : completly wrong.
Here's what I did :
1/ we need a boot loader on the tftp server. syslinux contains a good
pxe one : pxelinux.0
so install syslinux just to copy pxelinux.0 on /tftpboot directory
We will assume /tftpboot is the root tftp directory so it MUST be the
one in /etc/inetd.conf file.
2/ create a pxelinux.cfg directory under /tftpboot and go into it
3/ create a default file with the following content :
default lanlinux
prompt 1
label lanlinux
kernel tftpboot.img
append load initrd=root.bin devfs=nomount
pxelinux.0 is a boot loader which like lilo would do will load
tftpboot.img image.
tftpboot.imp is to be downloaded from tftp images. But it will not work
alone. We need a root image. So we will take the one we need (ide-pci
for instance). It's name
is root.bin.
That's why syslinux will append it to the image.
Note that devfs=nomount is very important. We will otherwise have
problems to open a root fs.
Note also that this default file is only for pxe boot. We could add
local images as in any lilo.conf file.
4/ install tftpboot.img and root.bin in /tftpboot directory.
5/ boot from the client and have fun tftp-installing debian.
In case of problems :
take a look at the tftp server logs (/var/log/syslog on debian)
try to play with the pause key and the space bar to read error messages.
I've had some.
I think this could be a good start for a small modification in
documentation.
Etherboot (or netboot) are, as you said, an other mean for tftp-booting
while using removable media.
I will write a howto on that (if it doesn't already exist).
I hope this will help people to tftp-install debian. Let me know what
you think about this.
I'm ready to read any new (or modified) doc on the subject.
I have to say I was like a child this morning when it worked.
links :
http://clic.mandrakesoft.com/documentation/pxe/index.html
http://etherboot.sourceforge.net
Happy new year.
regards
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#140579: Report: tftpboot install successfull
Processing commands for [EMAIL PROTECTED]: retitle 140579 i386 tftpboot undocumenteed Bug#140579: boot-floppies: [i386] boot-floppies 3.0.21 fail to load root.bin via tftp Changed Bug title. tags 140579 - patch Bug#140579: i386 tftpboot undocumenteed Tags were: patch Tags removed: patch reassign 140579 install-doc Bug#140579: i386 tftpboot undocumenteed Bug reassigned from package `boot-floppies' to `install-doc'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
retitle 140579 i386 tftpboot undocumenteed tags 140579 - patch reassign 140579 install-doc thanks Thanks for your contributions and documentation. We'll do our best to integrate this, and let you know when the install manual is ready for review. -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Le dim 29/12/2002 à 22:07, Adam DiCarlo a écrit : nb [EMAIL PROTECTED] writes: Thanks to Michael R. Schwarzbach and he's post I finally can install debian via tftp. I think the need is going growing to do that and it's really time to update documentation. Can you identify for us exactly what sections in the latest install manual are wrong, and which information is completely missing? This is missing : 1/ different boot methods are not listed (PXE, etherboot/netboot, MBA) - I haven't tried PXE. I will in on month (I've bought an openbrick) - I haven't tried MBA. I don't even know what it is - I have tried etherboot. I didn't know before they where so many methods 2/ about etherboot method. - one needs first to install mknbi - second to download root.bin _and_ tftpboot.img - and then use mknbi to add root.bin to tftpboot.img - after that tftpboot.img is loadable and usable from a client x86 client. I need more help because I don't have an x86 box I can do netbooting with. Is this bug completely just a documentation issue? If so, we should reassign this as an 'install-doc' bug. Yes it's only a documentation issue. If you don't know how it works you can spend much time (24 hours for me and I have many years experience) or even think it's impossible. I've spent 24 hours to do that and sentences like NOT YET WRITTEN are not acceptable today. For you to tell us something isn't acceptable isn't helpful. We are unpaid volunteers -- saying this sort of stuff just annoys us. Try to stay constructive. Providing patches or suggested bits of text is constructive. The sentence NOT YET WRITTEN was in the documentation. http://www.debian.org/releases/stable/i386/ch-install-methods.en.html#s-install-tftp chapter 4.5.5. All what aws written about the ip address and the architecture is completely wrong (I'm talking about x86 plateforme). I have used the following command to build the loadable and executable image : mknbi-linux mknbi-linux --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 tftpboot.img root.bin tftpboot.img in the /tftpboot directory. It's like a miracle I was using before : mknbi-linux --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 tftpboot.img tftpboot.img the only one difference is in root.bin which I have downloaded from ide-pci 1.44Mb (I don't remember exactly the url). I have to add that : a/ I have tried this with etherboot only (I have a 3com 3C905B TX) b/ I will try PXE method in nearly one month and than tell you how it works c/ I have heard about MBA method but don't know anything else about it. d/ I didn't try from a sparc (I have a ss10). I'll do that. I'm very sorry for my poor english. I you want more informations please let me know. -- nb [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Please retain the CC to the bugs.debian.org addresss. nb [EMAIL PROTECTED] writes: Le dim 29/12/2002 à 22:07, Adam DiCarlo a écrit : nb [EMAIL PROTECTED] writes: Thanks to Michael R. Schwarzbach and he's post I finally can install debian via tftp. I think the need is going growing to do that and it's really time to update documentation. Can you identify for us exactly what sections in the latest install manual are wrong, and which information is completely missing? This is missing : 1/ different boot methods are not listed (PXE, etherboot/netboot, MBA) - I haven't tried PXE. I will in on month (I've bought an openbrick) - I haven't tried MBA. I don't even know what it is - I have tried etherboot. I didn't know before they where so many methods Yes. This proliferation of different ways to do it is really the reason why it's not done. We do need to indicate the various etherbooter methods for x86 and help the user decide which is best for her to use. You listed several -- is this pretty complete? Perhaps we can just pick one method which will work in 80% of cases and focus on documenting that, then provide links to other sites for other methods, saying that the instructions would have to be adopted for each. Should we go with etherboot? 2/ about etherboot method. - one needs first to install mknbi - second to download root.bin _and_ tftpboot.img - and then use mknbi to add root.bin to tftpboot.img - after that tftpboot.img is loadable and usable from a client x86 client. I need more help because I don't have an x86 box I can do netbooting with. Is this bug completely just a documentation issue? If so, we should reassign this as an 'install-doc' bug. Yes it's only a documentation issue. If you don't know how it works you can spend much time (24 hours for me and I have many years experience) or even think it's impossible. Yes, well, my point is that the actual instructions need to be provided by someone who has done it. That is to say, I can't do it on my own. But your instructions may help. I've spent 24 hours to do that and sentences like NOT YET WRITTEN are not acceptable today. For you to tell us something isn't acceptable isn't helpful. We are unpaid volunteers -- saying this sort of stuff just annoys us. Try to stay constructive. Providing patches or suggested bits of text is constructive. The sentence NOT YET WRITTEN was in the documentation. http://www.debian.org/releases/stable/i386/ch-install-methods.en.html#s-install-tftp chapter 4.5.5. All what aws written about the ip address and the architecture is completely wrong (I'm talking about x86 plateforme). I have used the following command to build the loadable and executable image : mknbi-linux mknbi-linux --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 tftpboot.img root.bin tftpboot.img in the /tftpboot directory. It's like a miracle I was using before : mknbi-linux --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 tftpboot.img tftpboot.img the only one difference is in root.bin which I have downloaded from ide-pci 1.44Mb (I don't remember exactly the url). No problemo. This helps. I have to add that : a/ I have tried this with etherboot only (I have a 3com 3C905B TX) b/ I will try PXE method in nearly one month and than tell you how it works c/ I have heard about MBA method but don't know anything else about it. d/ I didn't try from a sparc (I have a ss10). I'll do that. No need. SPARC works as documented. I'm very sorry for my poor english. You're English is quite good actually. I you want more informations please let me know. Perhaps you could review the document when we have a draft. -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Le lun 30/12/2002 à 18:47, Adam DiCarlo a écrit : it's really time to update documentation. Can you identify for us exactly what sections in the latest install manual are wrong, and which information is completely missing? This is missing : 1/ different boot methods are not listed (PXE, etherboot/netboot, MBA) - I haven't tried PXE. I will in on month (I've bought an openbrick) - I haven't tried MBA. I don't even know what it is - I have tried etherboot. I didn't know before they where so many methods Yes. This proliferation of different ways to do it is really the reason why it's not done. We do need to indicate the various etherbooter methods for x86 and help the user decide which is best for her to use. You listed several -- is this pretty complete? I haven't found others. Perhaps we can just pick one method which will work in 80% of cases and focus on documenting that, then provide links to other sites for other methods, saying that the instructions would have to be adopted for each. I will try PXE in nearly one month with a realtek chip. I will then give all informations about that. Should we go with etherboot? It's the one I have used and it works. It's not dangerous at all unlike the others which _sometimes_ need the bios (PXE) or the network adapter rom (MBA) to be flashed. I have used it with floppy disk but it should work with any bootable media as well. I have tried this method with an usb pen drive but my motherboard don't want to boot on an usb device. I will try it in nearly a month on an openbrick machine : http://www.openbrick.org/ It is a floppyless machine and even diskless but it has a smart card. So the need is the same. Memory cards tend to be greater and I'm sure in the very near future they the os will completely fit on them. 2/ about etherboot method. - one needs first to install mknbi - second to download root.bin _and_ tftpboot.img - and then use mknbi to add root.bin to tftpboot.img - after that tftpboot.img is loadable and usable from a client x86 client. I need more help because I don't have an x86 box I can do netbooting with. Is this bug completely just a documentation issue? If so, we should reassign this as an 'install-doc' bug. Yes it's only a documentation issue. If you don't know how it works you can spend much time (24 hours for me and I have many years experience) or even think it's impossible. Yes, well, my point is that the actual instructions need to be provided by someone who has done it. That is to say, I can't do it on my own. But your instructions may help. I can tell you what I've done. For that I will uninstall everything concerned and redo it. But side effects risk exists. Eg a program already installed. I have to say I'm working on sid but I don't think there are differences in the way to do an installation. I'm going to do this and to telle exactly what have been done. I'll tell it in a futur mail (where to send it?) I've spent 24 hours to do that and sentences like NOT YET WRITTEN are not acceptable today. For you to tell us something isn't acceptable isn't helpful. We are unpaid volunteers -- saying this sort of stuff just annoys us. Try to stay constructive. Providing patches or suggested bits of text is constructive. The sentence NOT YET WRITTEN was in the documentation. http://www.debian.org/releases/stable/i386/ch-install-methods.en.html#s-install-tftp chapter 4.5.5. All what aws written about the ip address and the architecture is completely wrong (I'm talking about x86 plateforme). I have used the following command to build the loadable and executable image : mknbi-linux mknbi-linux --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 tftpboot.img root.bin tftpboot.img in the /tftpboot directory. It's like a miracle I was using before : mknbi-linux --ip=10.1.1.10:10.1.1.1:10.1.1.2:255.255.255.0:10.1.1.10 tftpboot.img tftpboot.img the only one difference is in root.bin which I have downloaded from ide-pci 1.44Mb (I don't remember exactly the url). No problemo. This helps. I have to add that : a/ I have tried this with etherboot only (I have a 3com 3C905B TX) b/ I will try PXE method in nearly one month and than tell you how it works c/ I have heard about MBA method but don't know anything else about it. d/ I didn't try from a sparc (I have a ss10). I'll do that. No need. SPARC works as documented. OK I'm very sorry for my poor english. You're English is quite good actually. I you want more informations please let me know. Perhaps you could review the document when we have a draft. Why not. It will be the first time for me to do something for free software. -- nb [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Is it just me, or isn't it rather a crippling problem that etherboot requires a floppy or other bootable medium to do the etherbooting? I guess however, since there is no OpenBoot on x86, that's just the breaks. Tell me, why is it interesting/useful to floppy-boot into etherboot rather than just floppy-booting from the rescue/root combo? Just the issue of one floppy vs two? -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Le lun 30/12/2002 à 22:16, Adam DiCarlo a écrit : Is it just me, or isn't it rather a crippling problem that etherboot requires a floppy or other bootable medium to do the etherbooting? I guess however, since there is no OpenBoot on x86, that's just the breaks. I'm not sure I've understood everything Tell me, why is it interesting/useful to floppy-boot into etherboot rather than just floppy-booting from the rescue/root combo? Just the issue of one floppy vs two? I told you I have bought a very small computer. I want to make it a firewall. I want it to be silent (no fans), not necessarily fast (300MHz, for a firewall it's enough) and very very small. So it will not have any floppy drive nor cdrom drive. It will only have : 1/ a smart card 2/ an onboard network adapter with PXE capability. So to put debian on it I need in either cases a tftp/bootp install. I wanted to prepare myself to do it. That's why with a floppy disk I simulate the smart card. But the best solution would be the PXE bios. Thus if for some reason I need to reinstall it one day it would be easy. But you are right. Someone whe has floppy disks has no need to tftp-install. I have myself done many of them either with floppy then network or cd-rom then network. Completly off-topic I think in the near future we will have to usb boot with different devices like pen-drive as I said before. This will be easy with a kernel + a root image on the drive along with something like isolinux. But that's an other story. Last minute ! My motherboard has a network adapter on it and I finally succeded in making it PXE boot. The process of installation has not begun because of a problem of tftp tsize. I will tomorrow install tftpd-hpa which has not this problem. I'm using for this my son's computer as tftp server mine is the client. It's late now I'll tell you tomorrow how this goes. -- nb [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Thanks to Michael R. Schwarzbach and he's post I finally can install debian via tftp. I think the need is going growing to do that and it's really time to update documentation. I've spent 24 hours to do that and sentences like NOT YET WRITTEN are not acceptable today. I hope this will go better. -- nb [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
nb [EMAIL PROTECTED] writes: Thanks to Michael R. Schwarzbach and he's post I finally can install debian via tftp. I think the need is going growing to do that and it's really time to update documentation. Can you identify for us exactly what sections in the latest install manual are wrong, and which information is completely missing? I need more help because I don't have an x86 box I can do netbooting with. Is this bug completely just a documentation issue? If so, we should reassign this as an 'install-doc' bug. I've spent 24 hours to do that and sentences like NOT YET WRITTEN are not acceptable today. For you to tell us something isn't acceptable isn't helpful. We are unpaid volunteers -- saying this sort of stuff just annoys us. Try to stay constructive. Providing patches or suggested bits of text is constructive. -- ...Adam Di Carlo..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
Hi,
it seems nobody ever reported a successfull install with tftpboot.img.
Here's how I did it:
1. From .../woody/main/disks-i386/3.0.23-2002-05-21, I got the files
compact/tftpboot.img
images-1.44/root.bin
2. On my DHCP server, I installed the mknbi package and created an
etherboot image using the command
mknbi-linux --output=tftp-etherboot.img --param=root=/dev/ram
tftpboot.img root.bin
3. I configured the DHCP server:
group {
filename tftp-etherboot.img;
next-server xxx.xxx.xxx.xxx; # my DHCP server
host client { fixed-address yyy.yyy.yyy.yyy;
hardware ethernet aa:bb:cc:dd:ee:ff;
}
}
4. I got an etherboot image from rom-o-matic.net. I chose version
5.0.7, as .lzlilo file for my eepro100, and put it onto a bootable
syslinux floppy.
5. I booted from that floppy. Etherboot loads, identifies the network
card, gets an IP address, and tftp's my image file, which boots and
starts into dbootstrap normally.
May this be a confimation that the proposed patch by Michael Schwarzbach
indeed works.
HTH,
Alex
--
Alexander Jolk / BUF Compagnie
tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
