[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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 <nb@dagami.org>



Reply to: