Oliver Ob wrote:
Jerry Kreps schrieb:
2. When building a kernel, do you have to build it from scratch?
Unfortunately *deeply sighing!* true. I would be delighted if it were not so.
Everytime you compile a kernel you are builiding an entirely 'new' one! The file in /usr/src/linux called '.config' contains the settings that have been made when the kernel configuration program was last run.
And directly after the installation of Tussinella 6.0 or above that ..config file is empty/not existing. Is that right?
No. Compiling shouldn't delete the .config file that was used. true.
You must be doing a "make distclean', which would delete the .config file and about everything else. what i actually meant was that the original .config which fits the default kernel which you chose is NOT installed. that and more "missed" shots on SUSE are truely annoying to a logical thinking man.
These are on the CDs, but I can't remember exactly where just now - sorry.
the only thing i truely DISlike on many distros (even suse) is the misorder in things like directory arrangement. now the file xxx is here, some versions later it is somewhere completely else. also, the structure of documentation is very disgusting, as you can hardly keep an overview on what - in fact - you are looking after... you often run away from topic and get lost in thousands of lines which describe the highly technical content instead of short step-by-step instructions.
That's why I like the 'locate' command, and why 'updatedb' is run by cron every night! ;)
not enuff. see below.
as I said:
next, which i am missing, is some index-help-base in which you can enter a search word for instance "squid" and get a 2,3 line short description of what it is and a link to the concerned howto, minihowto and doc files.
is there anyrthing like that (before i am again inventing wheels...) or am i just blind and too pragmatically minded?
You mean 'man'? Or 'info'? jlk man and info is by far not structured enuff. also, i want all that (locate, man, info, howto and so forth) started with ONE menu command
This would make it more complicated, IMHO, because these commands aren't all designed to do the same job. You'ld end up with having to specify various options for each of the tasks, which is more daunting to a new user than separate commands. I do see your point about unifying documentation sources, but the argument that you're making isn't necessarily correct. Take man and info, for example - you don't want to combine these. 'info' is the successor to 'man' - the 'man' command is supposed to be phased out in preference to the 'info' command, but this is taking its time. manual/info pages are also, by definition, different from HOWTO documents, so these can't be combined in the same way either. What might be more useful is for 'info' documents to have links to HOWTOs on tasks that you would use that command for. For example, the cdrecord info page may have a link to the CD-Writing-HOWTO, etc. One of the more significant problems would be deciding how the documentation in /usr/share/doc/packages links to the info pages, since this is information of a different sort again. Another significant problem would be that these links between documents would need to be included in the document by the original author, and this leads to problems because a large number of people contribute to various documents which get updated at different rates. Of course, I'm open to practical solutions - it's a nice idea in principle, but hard to implement in practice (unfortunately). Main sources of information: For individual programs: o man/info o /usr/doc/packages o source code For tasks: o /usr/doc/howto For more general info applying to all of the above: o web sites o mailing lists Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\