This question is coming up as a result of my DMA error messages. Is there a complete list of all possible append entries which can exist in lilo.conf? The man page is woefully deficient in this area. Again, thanks Joshua for your help with the DMA error messages. Jim
This question is coming up as a result of my DMA error messages. Is there a complete list of all possible append entries which can exist in lilo.conf? The man page is woefully deficient in this area. it depends on the modules you're using. a good overvire is in
hi, On Sun, Dec 30, 2001 at 09:45:12AM -0600, James Bliss wrote: the suse handbook. ciao sascha -- Sascha Andres linux@programmers-world.com http://www.programmers-world.com
On Sunday 30 December 2001 16.45, James Bliss wrote:
This question is coming up as a result of my DMA error messages. Is there a complete list of all possible append entries which can exist in lilo.conf? The man page is woefully deficient in this area.
The append entries aren't a property of lilo. They are kernel parameters. You should be looking at the kernel documentation, which is sadly also woefully deficient. Essentially, you're left with looking at the source of the bits you have compiled into your kernel.
From the past few weeks' discusison on the kernel mailinglist, it seems we're in the hands of people who think documentation is for children. When I read comments from various people in charge of crucial parts of the kernel I seriously considered switching OS. With attitudes like that it's almost impossible to produce a professional piece of work. I sincerely hope I've misunderstood them.
regards Anders
Anders Johansson schrieb:
On Sunday 30 December 2001 16.45, James Bliss wrote:
This question is coming up as a result of my DMA error messages. Is there a complete list of all possible append entries which can exist in lilo.conf? The man page is woefully deficient in this area.
The append entries aren't a property of lilo. They are kernel parameters. You should be looking at the kernel documentation, which is sadly also woefully deficient. Essentially, you're left with looking at the source of the bits you have compiled into your kernel.
From the past few weeks' discusison on the kernel mailinglist, it seems we're in the hands of people who think documentation is for children. When I read comments from various people in charge of crucial parts of the kernel I seriously considered switching OS. With attitudes like that it's almost impossible to produce a professional piece of work. I sincerely hope I've misunderstood them.
Hi Anders, you are absolutely right. I remember ending up digging some source code as well. It didn't help me at all, by luck, I found a readme that explained the *syntax* and *possible parameters* for that compaq raid-array card. It sounds like a bad joke, all that is asked for is dokumentaion. I know that some (compaq) network cards need a option to switch from RJ45 to AUI for output. Not much chance to find that. ;-( Juergen PS: But were would you switch to (OS)? -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
participants (4)
-
Anders Johansson -
James Bliss -
Juergen Braukmann -
Sascha Andres