Slashdot Mirror


New Linux Kernel Configuration System

An anonymous reader writes "When Eric S. Raymond tried to replace the Linux kernel's configuration system with "something better", he got booed off the stage. Now Roman Zippel is bravely having his own go at it. Here's an interview with Roman and a look at his new configuration system, aimed for inclusion into the 2.5 development kernel. Also, find some screenshots of his new graphical configuration frontend."

330 comments

  1. Oi! by Coke+in+a+Can · · Score: 1

    No comments yet and it's already been /.ed? What is the world coming to?

  2. If it ain't broke... by kc0dby · · Score: 0, Redundant

    Don't fix it, dangit!!!!

    --
    I apparently forgot that sig != uptime...
    1. Re:If it ain't broke... by hackstraw · · Score: 1

      I'll second this. I have no problem using 'make menuconfig', its intuitive, the help is ususally helpful, it works over a remote connection, etc. Now if we were still stuck with the 'make config' and saying Y/N over and over again, then realizing that you meant to say Y and not N three questions ago, hitting ^C, starting over, and repeating this process, then that would be an entirely different story.

    2. Re:If it ain't broke... by gmack · · Score: 4, Insightful

      It's also broken.. kernel developers are constantly trying to work around it's limitations. The fact that config menuconfig and xconfig all have diffrent bugs doesn't help either.

      We need something unified (same parser doffrent interfaces) and we need something less limmited. We need someone more sane than ESR to do it.

    3. Re:If it ain't broke... by sg_oneill · · Score: 4, Insightful

      Yeah. It certainly is. If you've ever done embedded work before and found oneself subject to the cosmic horror that is slaying $500 worth of flash hardware because the kernel configs made a booboo one will realise just how fantastic ESR's theorem checking autoconfigurator would of been. What a shame it's been beaten off by the anti-python mob.Stupid stupid stupid.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    4. Re:If it ain't broke... by Anonymous Coward · · Score: 1, Interesting

      I get the impression that Linus doesn't like side-effects. If you send him a patch that touches two completely different things, he'll probably reject it. So, I'd expect a new kernel config tool with the side effect of requiring Python to be rejected.

      If it had been written in some other language that was actually available (as in installed - the system already has a C compiler, obviously) everywhere, it would have probably seen a lot more action.

      But that's just me.

  3. Slashdot: Crashing servers since 1972! by Error-404NotFound · · Score: 0

    Interesting story, but it's already been slashdotted... perhaps his new Linux Kernel couldn't handle the load of eager slashdotters? Anybody got a Google Cache?

    --
    -=Errors always defy logic.=-
  4. slashdotted already by Anonymous Coward · · Score: 0

    slashdotted already

  5. Ironic... by cat5 · · Score: 4, Funny

    that the kerneltrap topic id is 404...

    1. Re:Ironic... by Error-404NotFound · · Score: 0

      where do you read the topic id? i haven't been slashdotting for all that long...

      --
      -=Errors always defy logic.=-
    2. Re:Ironic... by cat5 · · Score: 1

      It's in the URL.

      http://kerneltrap.org/node.php?id=404

      See, node.php?id=404.

    3. Re:Ironic... by Error-404NotFound · · Score: 0

      ah i see, overlooked that.

      --
      -=Errors always defy logic.=-
    4. Re:Ironic... by _ganja_ · · Score: 5, Informative



      How is that Ironic? I blame Alanis for this total misuse of the word... That's just a coincidence.

      While I'm at it, will the people that insist on using the word "literally" to mean metaphorically give it a rest: "That was so funny I literally shit myself" or "That last tackle literally ripped his head off".

      --

      A journey of a thousand miles starts with a brutal anal raping at airport security

    5. Re:Ironic... by quinto2000 · · Score: 1

      Democracy = "rule by the mob"

      --
      Ceci n'est pas un post
    6. Re:Ironic... by cheese_wallet · · Score: 1

      so would it be ironic if the topic id was 404, and the page worked?

    7. Re:Ironic... by AntiNorm · · Score: 2

      that the kerneltrap topic id is 404...

      The screenshot itself is more ironic, I think..

      --

      I pledge allegiance to the flag...
      of the Corporate States of America...
    8. Re:Ironic... by Anonymous Coward · · Score: 0

      No, since people generally expect pages to work regardless of the topic id. Irony is about violating expectations.

      What would be ironic is if a page on how to avoid broken links returned a 404.

    9. Re:Ironic... by _ganja_ · · Score: 2

      Just felt like a rant @ 4am :-) Ignore me. Language evolves I guess and meanings change.

      I guess we could say that irony is a method of humorous or subtly sarcastic expression in which the intended meaning of the words is the direct opposite of their usual sense.

      Or as the Oxford English says "A condition of affairs or events of a character opposite to what was, or might naturally be, expected; a contradictory outcome of events as though in
      mockery of the promise and fitness of things."

      An example of situational irony would be a man lost in a hot desert and near death from thirst, he crawled aimlessly in search of water. He could hardly believe his good fortune when he came across an oasis. He crawled forward onto its bank, leaned down and was just about to drink his fill when the bank collapsed under him. He fell in the water and drowned.

      As Ralph Wiggam said "Me fail English? that's unpossible".

      --

      A journey of a thousand miles starts with a brutal anal raping at airport security

    10. Re:Ironic... by Anonymous Coward · · Score: 0

      The true irony would be that you used a MS product to take a screenshot of a missing linux screenshot.

    11. Re:Ironic... by aussersterne · · Score: 2

      While I'm at it, will the people that insist on using the word "literally" to mean metaphorically give it a rest: "That was so funny I literally shit myself"

      My friend, if someone says to you 'Oh man, that was so funny I literally shit myself...' I suggest that you work on putting down paper on your car seats before letting them sit in your car, rather than complaining about their particular euphemism for 'metaphorically'.

      --
      STOP . AMERICA . NOW
    12. Re:Ironic... by mbogosian · · Score: 1

      While I'm at it, will the people that insist on using the word "literally" to mean metaphorically....

      Yeah, I'm anxious to see people start using words in their correct contexts as well.

    13. Re:Ironic... by iabervon · · Score: 1

      It is (now) kind of ironic, because the static page you get instead of the dynamic page actually does contain the interview. Anyway, if hosed sites give any response, they're more likely to give 500, since they recognize the URL but can't manage to serve the page.

      In any case, something which is unintentionally fitting is at least somewhat ironic, unlike the things in the Alanis song, which just suck.

      What would have been really ironic would be if the correct id had been, say 304, not 404. And then it would have been even more ironic if there was then a duplicate article...

    14. Re:Ironic... by Trogre · · Score: 1

      That word has been literally picked up and thrown around until its significance is literally reduced to the size of a grape.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    15. Re:Ironic... by neafevoc · · Score: 1

      How is that Ironic? I blame Alanis for this total misuse of the word... That's just a coincidence.

      Or how Alanis puts it in her songs... unfortunate.

    16. Re:Ironic... by Anonymous Coward · · Score: 0

      I don't like it when people use "anxious" as a synonym for "eager", since "anxious" shares its root with "anxiety". These words should be antonyms, not synonyms.

      Unfortunately for me, dictionaries now include "eager" as a synonym for "anxious".

      I suspect that "literally" will soon fall to the same insanity.

      Oh twell.

    17. Re:Ironic... by askii64 · · Score: 0

      sounds like anarchy to me

      --

      -This quite possibly mangled, stupid, demented comment was brought to you by Askii64.
    18. Re:Ironic... by Anonymous Coward · · Score: 0
      Uh, dude, and what would you call a song named Ironic that didn't have a single example of irony?

      Exactly.

    19. Re:Ironic... by Anonymous Coward · · Score: 0

      No it would be ironic if you're wrong.

    20. Re:Ironic... by Nailer · · Score: 2

      This is how its ironic...

      The American Heritage Dictionary:

      i*ro*ny Pronunciation Key (r-n, r-)
      n. pl. i*ro*nies
      The use of words to express something different from and often opposite to their literal meaning.
      An expression or utterance marked by a deliberate contrast between apparent and intended meaning.
      A literary style employing such contrasts for humorous or rhetorical effect. See Synonyms at wit1.
      Incongruity between what might be expected and what actually occurs: "Hyde noted the irony of Ireland's copying the nation she most hated" (Richard Kain).
      An occurrence, result, or circumstance notable for such incongruity. See Usage Note at ironic.


      Well, one of the most acceptable definitions of an ironic situation was one that seemed to imply otherwise. Hence, `rain on a wedding day' isn't ironic - its just bad luck. But visiting a site talking about the latest useless kernel addon and how it will rule the world, with a link proclaiming it to be a `404' of some kind (seeming to imply it won't rule the world) could indeed be ironic.

      I blame Alanis for this total misuse of the word...


      Me too, but I blame radio DJs who can't think of any better material for making this `its not actually ironic' discussion a popular one, especially when someone uses the word correctly

    21. Re:Ironic... by mbogosian · · Score: 1

      Or how Alanis puts it in her songs... unfortunate.

      C'mon, now you're just being insensitive (okay, I think that's Jann Aarden, but I can't tell the difference between any of them anyway, I guess that's kind of ironic...).

    22. Re:Ironic... by Anonymous Coward · · Score: 0

      if you'd ever been 'eager' for something, you'd know that there is a degree of anxiety involved. Anxiety is the physiological manifestation of of expectation good or bad.

    23. Re:Ironic... by RoofPig · · Score: 1

      "Me too, but I blame radio DJs who can't think of any better material for making this `its not actually ironic' discussion a popular one, especially when someone uses the word correctly"

      Don't forget the hoards of unfunny standup comedians.

    24. Re:Ironic... by Slime-dogg · · Score: 1

      Error 404: Page not found.

      --
      You need to restart your computer. Hold down the Power button for several seconds or press the Restart button.
  6. poor guy by GoatPigSheep · · Score: 3, Insightful

    When Eric S. Raymond tried to replace the Linux kernel's configuration system with "something better", he got booed off the stage.

    Yet another thing to add to my list of "and people wounder why linux is not being readily accepted by everyone" items. I mean, come on, the guy just wanted to help make things better! Getting booed off the stage hurts!

    --
    GoatPigSheep, the 3 most important food groups
    1. Re:poor guy by Error-404NotFound · · Score: 0

      They booed at Edison and the Wright Brothers too, people need to try to fully explore somebody's idea before they say "boo! change is bad! go home!"

      --
      -=Errors always defy logic.=-
    2. Re:poor guy by Anonymous Coward · · Score: 1, Insightful

      Yeah, he did. But his "something better" wasn't. It was a masturbatory exercise in pushing a pet language that resulted in a confusing mess that was at least as bad as the current system.

    3. Re:poor guy by Anonymous Coward · · Score: 0

      well, there's a long history with the linux
      crowd and Eric S. Raymond. I bet a lot of the
      booing didn't have much to do with the code or
      the idea as much as Eric having said it.

      It's not like this was some unknown new guy
      with a suggestion that was shouted down.

    4. Re:poor guy by ceswiedler · · Score: 5, Informative

      Just to add to Bruce's points above: from what I heard, the biggest problem wasn't technical, but rather ESR's refusal to negotiate. The userbase of the kernel config system is the kernel developers; they had several tried-and-true ways of configuring kernels. Many of them were in fact quite happy with the existing system, and didn't see a need to upgrade at all; there was a general consensus that there were some shortcomings in the existing system, but those were very specific.

      ESR solved these problems very well with CML2. By he also added a dozen features and changed a hundred other minor things, simply because he felt it was better that way. ESR was solving problems which only he perceived. For example, he was very interested in making it easy for "Aunt Tillie" to configure a kernel. Unfortunately, Aunt Tillie doesn't have a say in whether something goes into the kernel. Linus was apparently OK with CML2, but most of the other kernel developers were very resistant. No one ever explicitly refused CML2, but it never went in either, and ESR eventually gave up.

      The impression I got was that ESR should have minimized the changes to the UI in his first version. If he had built something exactly like the old config, but with a new language and backend, most of the objections would have gone away. He then could have submitted the other changes; they may or may not have been accepted, but at least the underlying system would have been improved.

    5. Re:poor guy by scotch · · Score: 2
      Linux already is a "mainstream OS" for any reasonable definition of that vague phrase.

      If you think reading slashdot gives you some special insight into the mind of the average linux user, you are woefully wrong. Just about every developer and manager at my company reads slashdot, but most of those people are not linux users.

      --
      XML causes global warming.
    6. Re:poor guy by Mr.roboto · · Score: 1

      Perhaps it was because what was already had works fine (make menuconfig is da schnizzat btw) Why fix what's not broken? Afterall, why add the extra eye candy to the already 32 meg (.tgz, bz2 is less) source download size. Cable is not standard these days, no need for the extra weight. I wish that they'd make it so you could DL just the modules you wanted to, that way you'd cut your download time a good bit. (wait a minute, I should patent that ;))

      --
      Don't call my crazy, that's what they called me back in the home!
    7. Re:poor guy by platypus · · Score: 1

      In that discussion, alan cox pulled an extremely funny joke. Maybe someone else can elaborate, I'm short on time ATM, (or search google's archive of lkml, search for melvin and aunt tillie).
      He set up this page:

      http://www.aunt-tillie.org/

    8. Re:poor guy by dd301 · · Score: 1

      If you think reading slashdot gives you some special insight into the mind of the average linux user, you are woefully wrong. Just about every developer and manager at my company reads slashdot, but most of those people are not linux users.

      You only have to look at the (classified) browser stats to prove this statement. And there are so many people who are publically pro MS (and state that they are MS employees no less).

    9. Re:poor guy by Anonymous Coward · · Score: 0

      whats with all the pussy overrated mods?

    10. Re:poor guy by Anonymous Coward · · Score: 0

      The problem was, as has been seen endless times before and since, that ESR got attached to his code. Linus has never said it, but his one most consistent test has been 'the code is not sacred.' Which is a preposterous system to take for anyone who hasn't rewritten the unix kernel from scratch. Linus's flaw is that he doesn't realize that their are more complex and more important things, and that other people's time is important; but it is the guiding principle that made Linux possible, and the only thing that can ensure that it remains free.

    11. Re:poor guy by mec · · Score: 2, Interesting

      The biggest problem wasn't technical, but rather ESR's refusal to negotiate.

      I was the CML1 maintainer for two years, and I had a front-row seat for the CML2 fiasco.

      ESR went for a big incompatible rewrite, in a new not-universally-deployed language, with a lot of paradigm shifts. Technically, this was okay. It's good to broom things out every now and then and the existing system is a mess. (The hardest part is dealing with module symbol versions, which are truly bletcherous).

      Socially, this made CML2 a big pill to swallow. And ESR didn't help things. In my opinion, he never acknowledged that lots of smart hard-working people were using the existing system to get a lot of work done. He came across as a bad advocate ("your system is stupid, and you are stupid for using it") rather than a good advocate ("this new system will fix the two things that you are bitching about the most").

      Also, it hurt a lot that there was a big mismatch between ESR's priorities of caring and the user's priorities of caring. To ESR, it was unimportant that the system was implemented in Python. To most other people, it was very important. To ESR, a correctness prover was very cool. To most other people, it wasn't very important.

      One notorious mismatch was between Linus's strong desire to break up the monolithic help text into hundreds of files, and Eric's assessment of that task as minor.

      Eventually it turned into a pissing contest, with a lot of people pissing on ESR because he was clueless about making his software work in its social/ecological niche. And when lots of people piss on a guy, of course he pisses back. And then the debacle happens, where no useful software happens, no useful ideas happen, a lot of people waste a lot of time in flame wars and stop listening to each other.

      During this time, Alan Cox was one of the few people who stayed calm and looked at CML2 technically, without getting into the ad hominem battles. I respect Alan very much for his ability to do that. Alan had a negative opinion and gave good reasons why he didn't like it -- reasons that ESR should have listened very carefully to, I think.

      Perhaps the worst part is that CML2 has lots of cool ideas, but we got into a position where the cool ideas can't even serve as experience for the next generation of people who want to take a crack at the problem, because of the ad hominem poisoning.

    12. Re:poor guy by Russ+Nelson · · Score: 2

      I asked Eric, and he says that the command-line changes were subtle, that the X and curses changes were more significant, but that nobody complained about them.

      And were my cousin-in-law's Aunt Tillie to compile a kernel, 1) she would be able to, and 2) she would want it to work without any muss, fuss, and bother, because 3) she would rather spend her time writing applications than fussing with kernel compiles.

      And perhaps Eric just didn't do a good enough sell job, because one of the purposes of CML2 was to obviate "make dep; make clean".
      -russ

      --
      Don't piss off The Angry Economist
    13. Re:poor guy by Anonymous Coward · · Score: 0

      Er, no. He wanted his entire new config system to be implemented all at once to "realise his vision", rather than gradually add it one piece at a time as all other kernel developers do. Please read and understand next time.

  7. down by Anonymous Coward · · Score: 0

    Warning: Too many connections in /prod/www/virtual/kerneltrap.com/www/htdocs/includ es/database.mysql.inc on line 7
    Too many connections

    We already know that this is a apache server with mysql, and the path do the server root. Now let's hope this server is not powered by linux 2.5".

  8. does it pre-configure by oliverthered · · Score: 5, Insightful

    Well the site is /.ed so what i want to know is.

    Does it scan your hardware and create a default kernel configuration with all ther drivers for your hardware pre-selected.

    It could even ask if you running a desktop or server machine and turn on/off low latency, pre-emtion and supermount for the desktop.

    I usually have to enable evrything to get X piece of hardware working corrctly and then disable stuff to find out what the correct drivers/modules were.

    --
    thank God the internet isn't a human right.
    1. Re:does it pre-configure by Anonymous Coward · · Score: 0

      Well, it would be nice if there was something like autodetection, but to be honest I don't trust autodetection since Windows.

      > I usually have to enable evrything to get X piece of hardware working corrctly and then disable stuff to find out what the correct drivers/modules were.

      So why do you enable everything?
      Don't you know what hardware you got in your computer?
      If that's the case then you shouldn't be using Linux.

    2. Re:does it pre-configure by Anonymous Coward · · Score: 0

      It is my opinion that control over which, what, and how hardware is configured is one of the primary reasons anybody would choose Linux over a proprietary operating system that chooses for you.

      I do not want my floppy disk enabled. I do not want my Via KT333 chipset autodetected as an Intel 440BX. And even if I did, I would never trust somebody else's script to know what I wanted.

      Of course, I suppose some people would probably like something like this for one reason or another. But why? It takes less than a minute to properly configure a kernel as it is with 'make menuconfig'.

      Oh well. Still a nice project for this guy, I guess.

    3. Re:does it pre-configure by oliverthered · · Score: 3, Interesting

      Here's how it works.

      1: Run the kernel configuration program.
      2: Select detect my harware option.... It sets up a 'default' configuration for you.
      3: You can then go through and select/de-select anything you want.

      You don't have to run step 2 if you don't want to you still have the choice you had before.

      Now on the auto detection thing, if the script is wrong you can correct it, report a bug or whatever, just like you can with kudzu or USB driver autoloading.

      It could even notify you that you hardware isn't fully supported and look here for an updated driver.

      --
      thank God the internet isn't a human right.
    4. Re:does it pre-configure by AvitarX · · Score: 1

      Nobody wants to force you to use autodetect, they just want the option to do it.
      It might take you less then a minute, but it takes me closer to 30. And I have had positive expierience with autodetection in Linux, so why force me to go through and configure everything on my own? I don't use Linux because I can configure the kernel, I use it inspight of the fact that I must do so.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    5. Re:does it pre-configure by Anonymous Coward · · Score: 4, Informative
      Does it scan your hardware and create a default kernel configuration with all ther drivers for your hardware pre-selected.

      for the curious, you can use dmassage for OpenBSD to get a kernel config file with only your hardware enabled (hardware that was enabled at boot time).

    6. Re:does it pre-configure by Anonymous Coward · · Score: 0

      >Don't you know what hardware you got in your computer?
      >If that's the case then you shouldn't be using Linux.

      Jerkoff.

  9. Re:no wonder by anarchima · · Score: 1

    Hrmph..Is this really a limitation of mySQL or the hardware?

  10. The Linux problem in a nutshell. by NetRanger · · Score: 3, Insightful
    There is too much resistence to change in the Linux community. The problem is a simple one: in the minds of Elitists, easier is not better, it's "lamer", "suckier", or "for wussies". Thus, when someone comes up with the brilliant idea that the average person should be able to actually use the system, they're booed off. Yet these boo-ers are the same people who bash the mass market for using Microsoft or Apple's OS X. OS X is astoundingly good... a simple, intuitive, appealing interface on top of loads of raw power. That's what Linux needs.

    Right now, when you install pretty much anybody's distro, you start up with an interface that has tons and tons of menus, icons, widgets, and whatnot, already up and running. It's an overload, and instead of trying to learn it, newbies are balking at it.

    So why not have an easy-to-use kernel configuration system? Why not have an independent object model, where any distribution or window manager can use each other's dialog pages?

    The only answer we seem to get is: "because it's for wussies!"

    --
    -- We live in a world where lemonade is artificial and soap has real lemon.
    1. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 1, Insightful

      The resistance to change is in all the wrong places. Kernel configuration really needs to be changed. Compare the effect of inserting an "autorun.inf" driver CD and "make xconfig" on a normal user. Yet Linux does change rapidly. The network system changes with every x in 2.x and drivers for 2.4.x don't work anymore in 2.4.x+y. Linux is hard to maintain as a single user machine if you expect all the bells and whistles of a modern system.

    2. Re:The Linux problem in a nutshell. by lpontiac · · Score: 2
      Yet these boo-ers are the same people who bash the mass market for using Microsoft or Apple's OS X.

      Actually, I'm pretty sure the boo-ers are different people, and there's the problem that Linux has - lots of different people trying to take it in different directions.

      Right now, kernel hackers tend to care more about the techie market, and the server market is where the money is, so that's the direction that things are really moving in.

    3. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      >are the same people who bash the mass market for using Microsoft or
      >Apple's OS X. OS X is astoundingly good... a simple, intuitive,
      >appealing interface on top of loads of raw power. That's what Linux
      >needs.
      >
      >
      No we don't need it. We also don't need dipshits like you telling us what we need. If you don't like it then bugger off. We're pretty much not interested in becoming the next Amiga or BE despite the best efforts of GUI-obsessed losers like you. Go find other people to fight your stupid desktop war for you.

    4. Re:The Linux problem in a nutshell. by krogoth · · Score: 2

      No. I think everyone agrees that easier is better, but not everything is as easy as it wants to be. If a program can automatically configure a kernel for me that supports all the hardware and features I need, that's good, but I don't see much difference between a graphical menu and a text-based version of the same menu.

      --

      They that quote Benjamin Franklin on liberty and safety deserve neither.
    5. Re:The Linux problem in a nutshell. by krogoth · · Score: 2

      Why not have an independent object model, where any distribution or window manager can use each other's dialog pages?

      Why not stop war, hunger, poverty? It's a great idea, who wouldn't want it? Maybe it's just a little harder than writing a few words?

      --

      They that quote Benjamin Franklin on liberty and safety deserve neither.
    6. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0


      >The resistance to change is in all the wrong places. Kernel
      >configuration really needs to be changed. Compare the effect of
      >inserting an "autorun.inf" driver CD and "make xconfig" on a normal
      >user.
      >
      >
      Yeah let's talk about this. Let's talk about the viruses and other crap that Microsoft and other companies distrubuted on those "autorun.inf" driver CD's. Let's talk about how those "copy protected" cd's trashed those Mac's when they got inserted in the cdrom drive. Now let's talk about how "make xconfig" requires a person sitting down at the computer making a choice about what to do next.

    7. Re:The Linux problem in a nutshell. by Wdomburg · · Score: 5, Insightful

      >Thus, when someone comes up with the brilliant
      >idea that the average person should be able to
      >actually use the system, they're booed off. Yet
      >these boo-ers are the same people who bash the
      >mass market for using Microsoft or Apple's OS X.

      Let's see.. When I started running Linux way back when I had to manually partition my hard drive, manually configure X (including plugging in video timings for my monitor), manually configure sound (including plugging in I/O addresses and IRQs), had to edit a config file in vi to add icons to my windowmanager (Afterstep Classic), had no real GUI filemanager, took 4 hours to figure out how to get my printer working properly, etc, etc.

      Now, I can stick in a CD, have it autopartition, detect all my hardware, configure X, and has a full desktop environment with a GUI filemanager, where I can simply drag an icon to the panel. I can hot plug USB and PCMCIA devices to my heart's content. I can add new hardware, and it will detect and configure it on boot. I can sit back and let my machine take care of keeping itself up to date with all the latest security patches.

      I must have missed an AWFUL lot of booing somewhere.

      >Right now, when you install pretty much anybody's
      >distro,

      Except for Lindows, Lycoris, Libranet, OEOne, Xandros...

      Come the release of Red Hat 8.0, you can probably add that to the list, given the focus they've put into creating a rational, consistent desktop in the betas.

      >you start up with an interface that has tons and >tons of menus, icons, widgets, and whatnot,
      >already up and running. It's an overload, and
      >instead of trying to learn it, newbies are
      >balking at it.

      Taken a look at Gnome lately? From an end user perspective, all of the changes in Gnome 2.0 are aimed at usability, accessibility, simplification, and consistency. To paraphrase Havoc, they're removing the "crack rock" features, and "proving one good way of doing things instead of six broken ones".

      >So why not have an easy-to-use kernel
      >configuration system?

      Noone has objected to the concept, only to the implementation. At different points there were issues with the rulesets in CML2 differing from CML1 in ways that the developers didn't agree with. The frontends used a different UI. It globally loaded rules for all architectures.

      It has long been Linus' policy not to accept patches which introduce more than one fundamental change. The proper course would have been to make CML2 a drop in replacement for CML1, with no changes to the rulesets, and with front ends that completely emulated the old ones. Then, and only then, discussions on rationalizing the rulesets and providing enhanced interfaces would be appropriate.

      Did it solve the problem it set out to solve - i.e. providing a more flexible syntax and a single parsesr? Sure, but it bundled too many other changes, and when you come down to it, it was replacing a system known to work with an unknown one.

      On a side note, the whole topic is moot. Does Windows provide you with an easy to use kernel configuration tool? Does MacOS? No, because the end user should NEVER have to configure a kernel.

      >Why not have an independent object model, where
      >any distribution or window manager can use each
      >other's dialog pages?

      Umm... what on earth is that supposed to mean?

      Matt

    8. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      >Right now, kernel hackers tend to care more about the techie market,
      >and the server market is where the money is, so that's
      >that things are really moving in.
      >
      >
      Much to the disapointment of you shareware con-artists.

    9. Re:The Linux problem in a nutshell. by slamb · · Score: 5, Insightful
      There is too much resistence to change in the Linux community. The problem is a simple one: in the minds of Elitists, easier is not better, it's "lamer", "suckier", or "for wussies".

      First, as other posters have said, there were valid reasons ESR's system was rejected. They weren't because it was for wussies.

      Second, configuring a kernel will never be easy. You have to make a lot of decisions that require technical knowledge. Whether you do that in a text-based interface or a fancy graphical one doesn't matter very much. That doesn't mean a fancy graphical interface shouldn't be made, but it shouldn't be made for the reason of making it easier for mom to use Linux.

      The correct solution to make hardware configuration usable for the masses is not to make building a kernel easier but to make building a kernel unnecessary. The system has become more modular over time.[1] Hardware has become friendlier to autodetection. Distributions like RedHat come with a single kernel that will work for just about anyone. When you start up with new hardware, kudzu will recognize it, ask you about it, and load the appropriate driver.

      [1] and is still becoming more modular. 2.5 was supposed to completely remove the idea of compiled-in versions of stuff that is modular. I believe this got canned due to time constraints; look for it in 2.7 maybe.

    10. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      Don't mix up trust and complexity. Those are very different problems.

    11. Re:The Linux problem in a nutshell. by ceejayoz · · Score: 2

      Come the release of Red Hat 8.0, you can probably add that to the list, given the focus they've put into creating a rational, consistent desktop in the betas.

      And getting screamed at by the KDE team for it...

    12. Re:The Linux problem in a nutshell. by bfields · · Score: 2
      The only answer we seem to get is: "because it's for wussies!"

      Do you have any evidence for this statement? All these discussions (including the discussion over whether or not to include Raymond's configuration system in the kernel) have taken place on public, searchable forums, so if your claim is true then you should be able to produce tons of evidence. (Here's a start.)

      My memory of the discussion on lkml was that people had a lot of different problems with CML2, which might or might not have been showstoppers. But I don't remember anyone saying "no, this would make kernel configuration too easy for novices, and we don't want that."

      If you accept the premise that "Open Source" development is a magic process for the effortless production of arbitrary amounts of excellent code, or if you assume that it is obvious how to create good user interfaces, then I suppose the only reasonable explanation for a lack of user-friendliness is a conspiracy on the part of developers. Absent those premises, you're free to adopt a more reasonable explanation: writing easy-to-use software is much, much harder than it appears, developers have limited resources, and we just haven't gotten a lot of things right yet.

      --Bruce F.

    13. Re:The Linux problem in a nutshell. by Wdomburg · · Score: 2

      >And getting screamed at by the KDE team for it...

      What do you expect? If a Red Hat employee farted during a KDE presentation at LinuxTag, I wouldn't be suprised if there was speculation on the mailing the next day that it's part of the grand Red Hat conspiricy to sabotage KDE.

      Matt

    14. Re:The Linux problem in a nutshell. by aje · · Score: 1

      You're absolutely right about this - let's say - "OSS paradox". There's a great need for simplicity and unity in the GUI-corner of the complex GNU/Linux-world. KDE and Gnome are two very nice user environments right now, but if GNU/Linux is supposed to attract - for instance - my dad or mother, the system must be built upon a more monolithic structure and philosophy of development. - But that's the diametrical opposite of the original Linux-/OSS-model (the bazaar), which attracts us. Those who're really into computers and dig the shell and compiler all day. :) That's also why Linux is never going to rule the desktop. If Mac OS X got ported to i386, they really could attract a lot of users. But then again, Microsoft would stop porting their programs to the OS. As I see it right now, Mac OS is the only really alternative for average users when looking at OS'es for the desktop. As long as I may dig my Blackbox, I don't care about the rest. :)

      --
      -- Anders
    15. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      Mac OS X has a distinct advantage. The designers of the software know exactly what the hardware is they need to deal with. They don't need to deal with a thousand different kinds of video cards, audio cards, chip sets and all that junk.

    16. Re:The Linux problem in a nutshell. by dd301 · · Score: 1

      Second, configuring a kernel will never be easy. You have to make a lot of decisions that require technical knowledge. Whether you do that in a text-based interface or a fancy graphical one doesn't matter very much. That doesn't mean a fancy graphical interface shouldn't be made, but it shouldn't be made for the reason of making it easier for mom to use Linux.

      As someone said, the idea is to make it as easy as possible, but no easier. Currently, a lot of time is wasted with trivial stuff. Of course, you will have to think a lot about the network and filesystem options. However, there are lot of options that should be selected by default too.

      The correct solution to make hardware configuration usable for the masses is not to make building a kernel easier but to make building a kernel unnecessary. The system has become more modular over time.

      It is almost as important to lower the barrier of entry for kernel hacking, which is very important for Linux's vitality. And speaking of that, I haven't been able to get a decent patch since they implemented bitkeeper for the kernel. What's up with that?

    17. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      We'll have no voices of reason around here, thank you very much.

    18. Re:The Linux problem in a nutshell. by slamb · · Score: 2
      As someone said, the idea is to make it as easy as possible, but no easier. Currently, a lot of time is wasted with trivial stuff. Of course, you will have to think a lot about the network and filesystem options. However, there are lot of options that should be selected by default too.

      Okay, requiring less time, not less skill, seems like a reasonable goal. But also a completely different one than you gave in your first post.

      Again, average users don't need to recompile the kernel. Concessions to their lack of technical expertise would be ineffective and unnecessary.

      It is almost as important to lower the barrier of entry for kernel hacking, which is very important for Linux's vitality. And speaking of that, I haven't been able to get a decent patch since they implemented bitkeeper for the kernel. What's up with that?

      That wouldn't lower the barrier of entry for kernel hacking. Programming the kernel is hard and becoming more so as the system becomes more complex (with more granular locking, etc). The difficulty of running menuconfig is nothing compared to dealing with those issues.

      Second, I'm happy with kernel hackers being an elite group. That's totally different than Linux users being an elite group, which I don't feel is true and am glad for. If kernel hackers were not an elite group, I believe code quality would suffer.

      And speaking of that, I haven't been able to get a decent patch since they implemented bitkeeper for the kernel. What's up with that?

      Don't know. You'd have to give more specifics...

    19. Re:The Linux problem in a nutshell. by isdnip · · Score: 4, Insightful

      Good comment. Easy is perceived as bad. Yes, some easy things (Microsoft Bob) are really bad, and some difficult things are good, but Linux, like Unix in general (sorry to generalize but it's a cultural inheritance), suffers from an "old boys' club" mentality in which earned knowledge of arcana is viewed as an entry point. Sort of like morse code has been to ham radio -- there aren't rational reasons to require it any more (though some of us actually like to use it, sportingly), but removing the requirement brings out all sorts of anger from old timers who had to learn it.

      Where it currently bugs me the most: Gentoo looks like a swell distro. Installing from source ends dependency hell and optimizes performance; I can buy it. But the setup is dreadful, basically more Linux From Scratch than anything else. The topic of an installer came up on Gentoo Forums. The "consensus" of the Gentoo user base is that "Gentoo is a hard distribution, and so the installation should be hard too." What rot! Once installed, no distribution should be gratuitously hard to live with. And while Gentoo lacks some of the GUI tools of say Mandrake or Red Hat, it's basically a clean system that shouldn't be that hard to manage. But the install procedure basically consists of printing out a lengthy set of instructions and doing a lot of hand edits of files, step by step, and hoping your system is enough like the developers' to work right.

      Personally I don't find the current kernel config (make xconfig) to be that hard, just a little nerve-racking where some new options show up that I don't understand. Which is what Bruce set out to fix. We can quibble about implementation details but his heart's in the right place. Linux won't prosper so long as it lives with the old boys' mentality. If I want to join the Freemasons, I will.

    20. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0
      Right! Easier is better!
      We should make becoming a doctor easier!
      Make becoming a airline pilot easier! (damn FAA elitists!)
      Getting through airport security easier!
      Windows certification easier!
      Drivers license tests easier!
      Who needs hard!!! but those damn hippies!

      The only answer we seem to get is: "because it's for wussies!"

      You do know what quotes are for right?
      I doubt anyone said that to you. I also believe that if someone gave you the real reason they are against this. You wouldn't care.
      You haven't been listening if you think their answer was "because it's for wussies!"

    21. Re:The Linux problem in a nutshell. by be-fan · · Score: 2

      That's because Redhat removed identification information from the "About" boxes of KDE applications. You can't blame the KDE guys for getting pissesd that they make this nice software, and the project doesn't get recognized for it. Sure its allowable by the GPL, but it isn't polite by any means. And there was no reason to do it. What did they think, that mentioning the KDE project could confuse users? ("But I thought I was running Redhat!") Come on. Take a look at common Windows apps like Yahoo messenger and AIM. They've got branding information all over them. Does it confuse users? I doubt it. People aren't that stupid.

      --
      A deep unwavering belief is a sure sign you're missing something...
    22. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      > So why not have an easy-to-use kernel configuration system? Why not have an independent object model, where any distribution or window manager can use each other's dialog pages?

      You have never tried to configure the kernel with the current system. Havn't you?

      Are you sure it is really necessary to do your own compilation? Are you sure that latest offering on the CD doesn't suit your needs?

      Do you really want to do all this stuff by yourself while the perfectly working kernel lives inside the CD, along with all the working drivers that your vendors took hours to compile and months to test???

      You see, these compile-my-own-kernel-is-so-cool thing got you, you miss a few steps and something didn't work, then you go on complaining having to read a manual.

      Tsk, tsk tsk.

    23. Re:The Linux problem in a nutshell. by Flarelocke · · Score: 1

      There are dozens of excellent programmers who use Linux, but don't hack the kernel. Lowering the barrier in general will allow them to work on the kernel if they feel like it, without lowering the quality of work on the kernel.

      Not to mention that, even if 1000 crappy programmers submitted crappy patches to the respective maintainers, they simply wouldn't get the patches included. We don't need to make it difficult for them just so we don't have to write 2 or 3 more replies("Rejected. Code quality sucks." is all that's required) every day.

    24. Re:The Linux problem in a nutshell. by Wdomburg · · Score: 2

      >That's because Redhat removed identification
      >information from the "About" boxes of KDE
      >applications.

      No, they removed the "About KDE" boxes from KDE applications.

      >You can't blame the KDE guys for getting pissesd
      >that they make this nice software, and the >project doesn't get recognized for it.

      The "About" box that IS left in still lists what version of KDE the program is built on, so yes, they do get recognized for it. They just don't get credited TWICE.

      >And there was no reason to do it.

      I personally think it's unnecessarily redundant, and potentially confusing for new users. Should they put in an About box for every single library they link against? I for one would rather not go to the Help menu and find About, About KDE, About QT, About libxml2, etc, etc.

      >Does it confuse users? I doubt it. People aren't
      >that stupid.

      You haven't done desktop support much, have you?

    25. Re:The Linux problem in a nutshell. by mark_lybarger · · Score: 2

      "make xconfig" on a normal user

      most normal users never need to venture into the make menu config. you're stepping into the aunt millie terrortory here. most modern distributions include all drivers for all hardware (at the time if distribution) as a kernel module. if your specific hardware isn't supported by a current distribution, chances are you can compile just the driver needed (or obtain a compiled driver). hell, most sysadmins don't go around building their own kernel. they use the one that comes on the cd, and worry about their other work. kernel building is really more of a geek thing than anything else. trying to scrape that extra 5-10% performance improvement.

    26. Re:The Linux problem in a nutshell. by dd301 · · Score: 1

      Again, average users don't need to recompile the kernel. Concessions to their lack of technical expertise would be ineffective and unnecessary.

      How do you know technical expertise is what is needed?

      That wouldn't lower the barrier of entry for kernel hacking. Programming the kernel is hard and becoming more so as the system becomes more complex (with more granular locking, etc). The difficulty of running menuconfig is nothing compared to dealing with those issues.

      Kernel hacking is intellectually stimulating and there is no point in putting off people with things like these which could be classified as grunt work at best.

      Second, I'm happy with kernel hackers being an elite group. That's totally different than Linux users being an elite group, which I don't feel is true and am glad for. If kernel hackers were not an elite group, I believe code quality would suffer.

      Fortunately, there is some sort of hierarchy that has been setup to handle just this. Most people don't submit patches to Linus directly. There is no need to eliteness. You can always start working up from the mailroom.

      Don't know. You'd have to give more specifics...

      I was talking about the patch files. I can only see the full tarball nowadays.

    27. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      Pay Redhat (or someone better) for support. The volunteer developers are under no onus to make installing Linux or compiling your kernel easier for you. In fact, no are they the only ones who allow you to do that, they do a better job than many other companies with greater resources.

    28. Re:The Linux problem in a nutshell. by PzyCrow · · Score: 1

      The "consensus" of the Gentoo user base is that "Gentoo is a hard distribution, and so the installation should be hard too." What rot!

      Gentoo, as you say, wants the users to learn the ins an outs of a GNU/Linux system. Nothing, however, is stopping you from implementing a Gentoo based distribution with ease of use and usability in mind. After you have coded the install GUI, you could start setting the default KDE and GNOME setups and make an emerge-wrapper for packages to add correct menuitems.

    29. Re:The Linux problem in a nutshell. by Anonymous Coward · · Score: 0

      It means that he wants only one way of building a GUI library, and new ideas should just be trashed, instead of being made into a competing library.

      I.e. we had QT, why try to make Gnome better.

    30. Re:The Linux problem in a nutshell. by stor · · Score: 1

      >You haven't done desktop support much, have you?

      Haha!
      *ring* *ring*
      "Good afternoon RedHat support, Stor Speaking, how may I help you?"
      "Hello! I'm having a problem with the cd player"
      "OK sure, what version of RedHat are you running there?"
      "KDE"
      "Ahh you have KDE, OK. That's the Desktop Environment. What version of RedHat are you running there?"
      "KDE"
      "OK."

      Cheers
      Stor

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
    31. Re:The Linux problem in a nutshell. by ceejayoz · · Score: 2

      Next...

      "Alright, please take the computer back to where you bought it and tell them it's defective. Tell them it's an ID10T error, they'll know what to do."

  11. /.'d by Suppafly · · Score: 1, Offtopic

    14 total comments on a sunday morning and the site with the pictures is /.'d already.. that can't be a good sign of things to come..

    At least its a good endeavor.

    1. Re:/.'d by Anonymous Coward · · Score: 0

      Better be careful with /. links ... someone might think that too many hits to a website is "Domestic Terrorism"

  12. Roman's system is realy great... by frankske · · Score: 3, Interesting

    It's a shame that Linus doesn't want to change, becuase Roman's system is realy great: faster, easier, and at the moment it still leaves the old system as default...

    1. Re:Roman's system is realy great... by Anonymous Coward · · Score: 0

      Let's fork the kernel!

    2. Re:Roman's system is realy great... by Anonymous Coward · · Score: 0

      Roman's "tree-based" interface looks ok, except for the problem of seeing option settings on the far right ("Y=build into kernel", "M=build as module", data, etc.). Having the selected line extend to the whole width of the window (so that the far right options are selected too), would help. Probably should submit this as a bug/feature request:)

    3. Re:Roman's system is realy great... by Anonymous Coward · · Score: 0

      What would your mother say if she knew you were using language like that?

  13. unix people and security by Anonymous Coward · · Score: 1, Informative

    http://kerneltrap.org/includes/database.inc
    http: //kerneltrap.org/includes/database.mysql.inc

    There are probably more...

    For gods sake put stuff like that outside the web root if you can't set apache up properly.

    1. Re:unix people and security by ceejayoz · · Score: 2

      Well, it doesn't have the password/usernames in there, so it's not as bad as it seems... but you're right, it's a bad idea to leave it out in the open.

  14. Damn slashdotters! by Anonymous Coward · · Score: 0

    Warning: Too many connections in /prod/www/virtual/kerneltrap.com/www/htdocs/includ es/database.mysql.inc on line 7
    Too many connections

  15. They need a new security person or php developer by cyberlotnet · · Score: 0, Offtopic

    http://kerneltrap.org/includes/database.mysql.inc

    Lovely php code... Anyone care to look for possible flaws so someone can hack there server..

    If your going to use includes in such a format, AT LEAST setup a .htaccess file so .inc files can not be viewed online..

    I mean come on...

    1. Scan include directory for other .inc files
    2. View them and look for some coding mistake
    3. Root Server

  16. 416 Slashdotted by Anonymous Coward · · Score: 0, Funny

    Slashdotted
    The requested URL could not be accessed by any more hot grits.

    Additionally, a 416 Slashdotted error was encountered while trying to use a Beowulf cluster to cache the request.

    Apache/1.3.26 Server at www.cowboyneal.net Port 80

  17. Maybe it's not a ./ effect... by moby · · Score: 1

    ...but the site has already been hacked!

  18. Re:no wonder by mariube · · Score: 1
    Hrmph..Is this really a limitation of mySQL or the hardware?
    Although it would be slow, it would probably be reachable if one dropped the SQL interface to the file system in favour of pure filesystem access, yes. But the ease of development and reduction in maintenance is obviuosly more important than withstanding a /. now and then. I'd do the same.
  19. Why Change? by PoiBoy · · Score: 4, Insightful
    Seriously, what's wrong with typing "make menuconfig" now? To me at least, an ncurses-based menu system is just as easy to use as a GUI (yuk).

    Moreover, it's not like complete newbies are going to be doing kernel compiles. For anyone with enough experience to recompile the kernel, an ncurses-based system is adequate IMHO.

    --
    Sig (appended to the end of comments you post, 120 chars)
    1. Re:Why Change? by PigleT · · Score: 1

      I think it might be more a case of dependencies - "if you're going to have ACPI, you need..." and so on. This was something Eric's system sort of touched on, mostly - regrouping things in a slightly more sensible way is fine by me.

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
    2. Re:Why Change? by Psiren · · Score: 1, Redundant

      Seriously, what's wrong with typing "make menuconfig" now? To me at least, an ncurses-based menu system is just as easy to use as a GUI (yuk).

      Seriously, what's wrong with typing "make xconfig" now? To me at least, a GUI menu system is just as easy to use as an ncurses-based one (yuk).

      Some people prefer a GUI. Live with it.

    3. Re:Why Change? by garcia · · Score: 1, Redundant

      how is this method going to stop you from typing make menuconfig?

      Prior to the ncurses method there was make config, I am sure that no one particularly cared for make menuconfig (I use it but I hate it). If the newbie wants to use a GUI based configuration for kernel compiles that is NOT going to disable menuconfig.

      Get real.

    4. Re:Why Change? by Anonymous Coward · · Score: 0

      Well having to spend an hour turning off or on every damn thing you want in a kernel config with over 1000 options when a tool will auto-configure 99% is one reason why I think menuconfig sucks when compared to it. I would not care if this was simply a text tool if it would simply eliminate that issue alone. Have you ever missed somthing in a complex kernel config and had to redo compile the sucker. I hate that. I also like GUIs because they allow you to multi task while most text menu and a command lines do not. They also allow you to see and organize information more clearly. I get sick of the people who say if you use a GUI your a wuss. In my opinion, if all you want is text menus and command lines, you have no life. The true mark of an expert is knowing how to do something at the command line level when they need to but having enough common sense to want and to use good tools to make such efforts rare and thus thier work quicker and easier.

    5. Re:Why Change? by Anonymous Coward · · Score: 0

      >Some people prefer a GUI. Live with it.
      >
      >
      So go use a GUI-based OS and leave us the hell alone. Oh, you GUI-types can't *DO* that. You have to make sure that everyone has to have a GUI shoved down their throat wheter they want it or not, because in the GUI-universe choosing not to use a GUI is not an option. It's the main reason you people can't stand linux development,because it threatens to undo all the crap you've managed to force on people over the years.

    6. Re:Why Change? by Anonymous Coward · · Score: 0

      In a properly commented GENERIC or LINT config file in FreeBSD, the user should be aware of all the dependencies for the driver he's interested in. Chances are there won't be many, especially if he uses kernel modules instead.

    7. Re:Why Change? by Psiren · · Score: 2

      Congratualtions. Thats the largest pile of bullshit I've read in a long while. The GUI isn't being forced on anyone. If you want to sit at a console all day, go ahead. No one's stopping you. The GUI is an option. The point I was making to the previous poster was that just becuase he doesn't want/use/like it, doesn't mean that everyone else feels the same. It's all about choice, the whole reason Linux exists in the first place. Linux will never become GUI only configuration, by virtue of the fact that many of the systems it runs on are incapable of using said GUI.

    8. Re:Why Change? by Anonymous Coward · · Score: 0

      Heh, I use 'make menuconfig' all the time when I'm building servers. No point of installing X11 on servers and all that... And it works just as well as the GUI version anyway, so I use it for my desktop too. The GUI version doesn't have any extra functionality...

    9. Re:Why Change? by Anonymous Coward · · Score: 0

      GUI won't work on servers... Unless you want to install X11 on your servers. But why do that if all you're ever going to use X11 for is to configure a kernel? Heh, come on man. Experts use whatever tool they're used to and gets the job done faster, and for me that's 'make menuconfig'.

    10. Re:Why Change? by gimpboy · · Score: 1

      I also like GUIs because they allow you to multi task while most text menu and a command lines do not.

      really? so if i have 5 xterms up each running a text only taks am i not multitasking? or if i'm sitting in the console and type the following:

      $cd ~/
      $grep -ir sometring * > /tmp/somefile&
      $pine

      am i not multitasking?

      really though it's easy to multitask using only text commands. plus if you're admining a computer half way across the world, you might not want to wait for the pull down menu to be drawn on the screen.

      i'm not trying to be an eliteist or any of that stuff, but to say you cannot multitask using text programs is a very odd thing to say.

      --
      -- john
    11. Re:Why Change? by Anonymous Coward · · Score: 0

      Ok, let's say that you have a system that only works with Xfb, and a kernel with no framebuffer support. So you need to change the kernel config to add framebuffer support. Now show me that the GUI kernel config is just as easy as the ncurses version.

  20. tip for web sites that get linked off slashdot by Anonymous Coward · · Score: 0

    dont serve up your web pages from a database.

    1. Re:tip for web sites that get linked off slashdot by anarchima · · Score: 1

      So then anyone who could potentially be linked from slashdot should just change the entire technology supporting their site? Hehe, don't think so!

    2. Re:tip for web sites that get linked off slashdot by Fragmented_Datagram · · Score: 1

      The default is to allow a maximum number of 100 connections. You can set it higher if needed:

      http://www.mysql.com/doc/en/Too_many_connections .h tml

  21. Compiling kernels? by koali · · Score: 1

    Hey, anyway, compiling kernels is rarely needed. Your distro's kernel should come with *everything* that can be compiled as a module, and sane defaults for everything else.

    I don't really recall that many things that require a kernel compile (although I do compile my own, of course :).

    1. Re:Compiling kernels? by Anonymous Coward · · Score: 0

      redhat CONTINUALLY refuses to include ntfs modules with their distros. sucks penis mang.

    2. Re:Compiling kernels? by Anonymous Coward · · Score: 0

      and all distros refuse to enable DMA or AGP on my f***ing laptop. now if i could just figure out how to recompile with out kiling half of the installed software.(mostly ALSA and X based programs)

  22. Re:no wonder by Dave2+Wickham · · Score: 1
    How ironic; There's this ad at the top of the page...
    "Don't let Your Database Slow You Down"
  23. Re:Man... by testadicazzo · · Score: 1
    Way OT so I shouldn't be responding to this, but...

    Ironic yes, but I think it's more funny than sad. I mean, there's more anti ms info here than pro... I don't think MS will win any developers away from Linux here, so I consider it a bad business move for MS, glad they can help support the site...

    just my 5 rappen.

  24. Re:They need a new security person or php develope by Anonymous Coward · · Score: 0

    Torch the site via a POST to the variable $query using a delete.

  25. ...and the Linux solution? by Anonymous Coward · · Score: 0

    Who cares? You can still make whatever you want, it's all open-source. Anyone could make an easy-to-use distribution -right now- if they wanted to, some companies are even doing it to a certain extent. I understand what you're saying, and it is a problem, but it's not one that isn't easily worked around.

  26. Maybe other nuts ... by A+nonymous+Coward · · Score: 3, Informative

    I believe ESR got booe doff for two reasons. One, the new config required Python. Two, he wanted to change everything at once in ne huge patch, rather than bits and pieces which are easier to understand, back out and correct, and so on.

    1. Re:Maybe other nuts ... by Anonymous Coward · · Score: 0
      the whole "i've lowered myself to fix your problems out of the goodness of my heart, now bow down before me" attitude had something to do with it too.

      Requiring Python as part of the kernel building toolchain did put people off, but it wasn't as much of an issue as some have made it out to be; consider what's already required.

    2. Re:Maybe other nuts ... by Ed+Avis · · Score: 2

      Can someone explain the objection to using Python for the configuration system? Surely the kernel developers don't believe that C is the be-all-and-end-all of languages. If it's quicker and more maintainable to write in a high-level language then why not just do the job - and use the time you saved compared to writing in C for other things? It's not as if Python is something wacky or proprietary or a resource hog.

      --
      -- Ed Avis ed@membled.com
    3. Re:Maybe other nuts ... by Anonymous Coward · · Score: 1, Informative

      For people such as myself, it would mean that we now have to install Python on our systems - nothing major, just annoying. I'm not thinking that using C would be the best option either, but it makes sense in that the kernel is written in C, those who develop the kernel are familiar with C, so C should probably be used for a utility that configures the kernel.

    4. Re:Maybe other nuts ... by Anonymous Coward · · Score: 0

      >Can someone explain the objection to using Python for the
      >configuration system? Surely the kernel developers don't believe that
      >C is the be-all-and-end-all of languages. If it's quicker and more
      >maintainable to write in a high-level language then why not just do
      >the job - and use the time you saved compared to writing in C for
      >other things? It's not as if Python is something wacky or proprietary
      >or a resource hog.
      >
      >
      Because you don't want to use something that requires 3rd party sofware like Python in order to run. If this was written in C it could be complied into a package that could run on it's own. It's like using complied BASIC vs Interpered BASIC.

    5. Re:Maybe other nuts ... by WNight · · Score: 2

      I think the main resistance to using other languages in the kernel-building process is that you have to have them installed. Neither Perl nor Python produces a stand-alone runtime.

      One of the goals is to make the same code compile on any platform with only a makefile difference. If you require fairly heavy-weight runtimes you limit the platforms you can run things on.

    6. Re:Maybe other nuts ... by joto · · Score: 2

      First reason false. Second reason true. Third reason: it was complex, and nobody understood it...

    7. Re:Maybe other nuts ... by joto · · Score: 2

      Yes Python can do that. And that was one of the reasons Eric chose it. But it would of course be huge, slow, and basically contain a Python interpreter. Perl can also do that, but I think it actually needs to link with libperl, so it would be a little bit more silly...

    8. Re:Maybe other nuts ... by kcbrown · · Score: 2
      I believe ESR got booed off for two reasons. One, the new config required Python.

      Yeah ... we all know the kernel config process doesn't at any time rely on any language other than C. For instance, we know that doing a "make xconfig" won't invoke Tcl/Tk, right? Oh, wait...

      Including a configuration option isn't a problem provided that it isn't the only configuration option. Right now there are at least three ways of configuring the kernel ("config", "menuconfig", and "xconfig"). As long as the simplest method remains as a fallback, it should be okay to include another config method, even if it depends on Python.

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    9. Re:Maybe other nuts ... by Anonymous Coward · · Score: 0

      because then you need to have python to build a computer. That makes python a system requirement. Perl doesn't even have that status. In fact, other projects have been rejected that would have required perl

    10. Re:Maybe other nuts ... by WNight · · Score: 2

      Yeah, I knew about encapsulating. I meant, runtimes of a reasonable size as you said.

    11. Re:Maybe other nuts ... by CreamsicleSeventeen · · Score: 1

      "make xconfig" depends on Tcl/Tk, but if you don't want or can't get Tcl/Tk on your system you can still "make menuconfig" on the console or an xterm. You can even "make config" if you don't have ncurses. Keeping the required development environment to a minimum is a laudible goal.

  27. Why not? by brunes69 · · Score: 3, Insightful

    Its not like they are saying "Lets ditch menuconfig and replace it with this!". For you and whoever else there is still make menuconfig. But I for one would welcome a better GUI than make xconfig, which I find pretty honkey. Since when are more options bad? It's not like they are forcing you into switching.

    1. Re:Why not? by gimpboy · · Score: 1

      as a honkey i take offense :).

      i must say that when i saw the screen shots it was a little disappointed. perhaps the way it works is a little different, but i dont see the changing the buttons into a tree as being that significant. now if there were a menu that said: click here for x and it either selects alot of crap for your, or prompts you with a list of questions to customize your hardware that would be neet.

      say you click on "enable scsi support", then it asks you: which type of adapter do you have? buslogic, adaptec, etc. then it says do you have scsi cd rom drives? yes/no, etc.

      that would be nifty. romans tool might do this, if so then that would be dandy. i just dont think a treelike interface is really that big of a deal.

      i agree with you that more options are better though.

      --
      -- john
  28. They weren't without reason by Bruce+Perens · · Score: 5, Informative
    The kernel developers are a pretty open-minded bunch. Eric's design was cool, he explained it to me a few years back, and it has seen use in other projects than the kernel. But I could see that it would be difficult for the kernel developers to accept:

    • It required Python to build the kernel.
    • It was complicated. It included an entire theorem prover. This was sort of cool in that it would not allow you to generate a non-working configuration, but really more than was required for the job.
    • Its language was arcane. The main language idiom is the suppress-unless statement, which is sort of the logical negation of if-then statements.
    • And some folks questioned his motivation for getting this grandiose project into the kernel - was it just to help out, or was it primarily to establish additional hacker reputation for Eric? I'd be willing to give him the benefit of the doubt on this - he did the work.
    I think he had a chance of getting it in, but he would have had to refactor the entire thing, write it over in C, make the language cleaner, and I guess that didn't come about. But to his credit, he didn't just talk about it. He generated a working software product with functionality that did not previously exist in Open Source as far as I could tell. His project is worth studying, and I'd encourage works derived from his ideas. I'm sure there's a paper about it online.

    Bruce

    1. Re:They weren't without reason by great+throwdini · · Score: 3, Insightful

      [Eric's design] was complicated. It included an entire theorem prover. This was sort of cool in that it would not allow you to generate a non-working configuration, but really more than was required for the job.

      I grasp the significance of the other three points of contention you mention, but the fourth (above) doesn't jump out and grab me as an issue in and of itself. On the one hand, it may be that the method was overly complex (evidenced in part by the Python requirement and an unfamiliar idiom). Disallowing an unworkable configuration doesn't seem unreasonable, though. Is there a down-side to building that safety into the configurator apart from any flaws [heightened complexity] in Eric's particular implementation?

    2. Re:They weren't without reason by Anonymous Coward · · Score: 0

      The kernel developers are a pretty open-minded bunch

      Yes. Like you. "The new BSD license is great. It allows the code to be protected by the GPL." Your mind is open, so long as it follows your adjenda eh Bruce?

    3. Re:They weren't without reason by billbaggins · · Score: 1
      It was complicated. It included an entire theorem prover. This was sort of cool in that it would not allow you to generate a non-working configuration, but really more than was required for the job.
      What do you expect from someone who put a LISP interpreter into a text editor? "When in doubt, make it as general as possible" seems to be the motto...
      --
      "The best argument against democracy is a five minute chat with the average voter."
      --Winston Churchill
    4. Re:They weren't without reason by Anonymous Coward · · Score: 3, Interesting
      Python wasn't the problem, a few people didn't like it. I don't even remember anyone trying to veto it for it's complexity or anything either. There were 2 issues. It didn't do what Linus wanted it to do, namely decentralize a few thing, Eric simply ignored the requests for that. And then he tried to slide it in some how without peer review by trying to get developers closer to Linus to endorse it an include it rather than doing it in the open.

      Eric was playing games and his solution was technically superior. Done deal.

    5. Re:They weren't without reason by ElMiguel · · Score: 1

      If you're talking about emacs, that was Stallman, who likes Lisp because he comes from MIT.

    6. Re:They weren't without reason by PissingInTheWind · · Score: 1

      1- Having a LISP interpreter in a text editor is one of the best things I've ever seen,
      (well, do you know LISP? if not, why are you talking about things you don't understand?).

      2- ESR didn't write Emacs, RMS did. Get your acronyms straight.

      --

      A message from the system administrator: 'I've upped my priority. Now up yours.'
    7. Re:They weren't without reason by dd301 · · Score: 1

      Disallowing an unworkable configuration doesn't seem unreasonable, though.

      I suppose this is OK as long as there is some mechanism to override it for experienced users. Imagine if ESR had left after it was merged into the kernel. Can you imagine the nightmare?

    8. Re:They weren't without reason by dd301 · · Score: 1

      What do you expect from someone who put a LISP interpreter into a text editor? "When in doubt, make it as general as possible" seems to be the motto...

      You can still write code with magnets on the hard drive, if that suits you. But all (good) editors will tend to emacs in the limit. ;-)

    9. Re:They weren't without reason by tdelaney · · Score: 1

      Indeed. Python would be a much better choice.

      Which is available by the way ... (pymacs).

    10. Re:They weren't without reason by Anonymous Coward · · Score: 0

      One question:

      Can menuconfig still work with the hmm new system?

  29. Re:Man... by cioxx · · Score: 1

    I said the exact same thing couple of days ago in another topic.

    It's hillarious. I'm gonna have to go with a "smart choice" option on behalf of MS.

    Think about it. They are giving away a FREE DVD. Lots of people probably grabbed it for shits and giggles. Out of those 3,000 people, if MS locks just 1%, then the mission is accomplished.

  30. Re:no wonder by dmp123 · · Score: 1

    Erm......Slashdot doesn't get slashdotted..... and it runs MySQL... hmm... You don't think it might be the fact that they need to turn up the Maximum Concurrent Connections option? Maybe? David

  31. Eh? No security issue I can see. by brunes69 · · Score: 2

    After looking at these two pages I see nothing that could be classified as a security compromise. No passwords, no ports, no UID's, nothing. They are just files with some functions in them. Sure it maybe neater if they had named them .php so visitors couldn't view them, but its not a security issue.

    1. Re:Eh? No security issue I can see. by codepunk · · Score: 2

      And you are a complete and utter moron. A simple http post containing a delete statement passed as the variable $query will torch the site.

      Go home script kiddie!

      --


      Got Code?
    2. Re:Eh? No security issue I can see. by brunes69 · · Score: 2

      Er... only if the site admin did not use the default PHP settings and turn register_globals on in their PHP.ini, which no one in their right mind ever does. Next time know what youa re talking about before you start spouting off like an idiot.

    3. Re:Eh? No security issue I can see. by Anonymous Coward · · Score: 0

      why even have includes in the docroot?

      php_admin_value include_path "/not_avail_to_web/:."

    4. Re:Eh? No security issue I can see. by 3Ddgg · · Score: 1

      Is that in a gui config tool somewhere? :-)

      --
      No warranty of any kind is offered as to the quality of this post.
  32. The Developers Arent Always Right & Politics S by FreeUser · · Score: 5, Insightful

    Yet another thing to add to my list of "and people wounder why linux is not being readily accepted by everyone" items. I mean, come on, the guy just wanted to help make things better! Getting booed off the stage hurts!

    First, GNU/Linux will never be accepted "by everyone." Nor will FreeBSD, nor will BeOS, nor will Apple's OS X.

    Nor will Microsoft Windows, unless Palladium and DRM is legislated into law by the likes of "Disney" Hollings, and even then Apple is likely to be kept around as a token "competitor," paying hefty patent fees to Microsoft for the privelege of being allowed to manufacture "legal" hardware in the US. Unless, of course, you get off your butt and do something about it, but I digress.

    The problem is a simple and obvious one, and the solution as elusive today as it was the first time humans came to live together (and likely predates our ability to speak): Politics is ugly and banal, and people are fallible. This includes the Linux kernel developers and Linus Torvalds himself.

    Example: The ggi project wanted to provide a kernel abstraction layer for video hardware in the same manner such abstractions are presented for everything else, from your ethernet adapter to your system's RAM and hard drive. Linus thought the idea sucked, then ended up doing a "poor man's" version of frame buffer support instead. How much better things would have been if the original vision of the GGI folks had been realized and supported we'll never know.

    Example: PCMCIA. It is still a mess. The more capable userspace version got sidelined in favor of a broken and less capable rewrite ... I can only ascribe that to politics and personal pull, which every group, no matter how altruistic and well meaning, falls prey to now and then.

    There are other examples, and perhaps Eric S. Raymond's effort is one (though I hesitate to make that assumption), but the purpose of this post is not to catalogue the mistakes Linus and others have made, or to air my own disagreements with them (but what the hell: when will we get XFS into the main kernel tree damn it! :-)), but rather to point out their humanity and fallability, a trait they share with everyone reading this comment, the guy posting it, and probably with every sapient being, everywhere.

    Mistakes happen, everywhere, by everyone. The measure of a group or project's success isn't their perfection (as is so often implied in political discussions), it is by how much their mistaken decisions are outweighed by their correct decisions.

    And using that metric, the Kernel developers, including Linus Torvalds, have done very well indeed.

    --
    The Future of Human Evolution: Autonomy
  33. Take a good look at CML2 before you are so sure. by Bruce+Perens · · Score: 5, Insightful
    You might change your mind if you examine the project in question. See this comment.

    Bruce

  34. Don't you know what hardware you got in your compu by oliverthered · · Score: 1

    Well I don't know all the chipsets i have and exactly what i need to get my IDE up, etc...
    Do i want framebuffer? do i need it...
    Oh and I forgot scsi-cdrom support for my CD-RW.

    I do know more-or-less what hardware I have, hardware detection can be a lot better under Linux than windows, a lot of USB devices auto load the drivers based on vendor ID/product ID.

    A lot of the Linux drivers are generic for XYZ chipset, under windows you need the exact driver. I should imagine that Linux also detects what hardware you have when binding devices.

    I takes a short while to select all the default hardware for your system, and sometimes you might miss something. Why not automate this process.

    --
    thank God the internet isn't a human right.
  35. Re:They need a new security person or php develope by faeryman · · Score: 1

    this is probally a stupid question, but how would a programmer protect against someone doing that?

    --


    ,
    faeryman
  36. Apple? Kernel conf? by Anonymous+Bullard · · Score: 1

    There just might be a reason why Apple has it much easier in the "easy-to-use kernel configuration system" department...

    All things considered, even the current Linux method works amazingly well. Not everything gets included in the official kernel releases, for various reasons, but users (incl. distro builders) are free (as in speech&beer) to add any features they feel will add value to their case.

    Sometimes it's in the best long-term interests not include the first available stab at a new feature.

    Personally, I have no reason not to trust Linus & Co's judgement in these matters.

    Or was your rant targeted more at the object model and UI issues instead of the ability to configure kernels?

    --

    Should invading one's peaceful neighbours be opposed, or rewarded with trade deals?

  37. They also open their include files to the world by Anonymous Coward · · Score: 0

    Very bad.

    http://kerneltrap.org/includes/database.mysql. inc

  38. Re:no wonder by Lysol · · Score: 1

    Get a real Dbase like Oracle or Sql 2000(if you can afford it)

    Wow, you must have a MCSE or somethin...

  39. Re:The Developers Arent Always Right & Politic by Anonymous Coward · · Score: 0

    >and hard drive. Linus thought the idea sucked, then ended up doing a
    >"poor man's" version of frame buffer support instead. How much better
    >things would have been if the original vision of the GGI folks had
    >been realized and supported we'll never know.
    >
    Bullshit. The ggi project was a overly-complicated pile of crap that Linus was right in rejecting. Pretty much the same bunch of X-hating losers who back things like Berlin was pushing ggi. Why? I suspect they thought they could use ggi as a back door to getting Berlin and other Amiga/PC Gamerish things intergrated into the linux kernel where they didn't belong.

  40. Re:The Developers Arent Always Right & Politic by Psiren · · Score: 2

    This will happen more and more. I really do expect that at some point someone will just say fuck it and branch their own version of Linux. I see this as possibly a good thing. If this branched version gets all the cool patches that Linus and co are turning down, and they work, it may prove to be a catalyst for change. Either that or the branched version will become better than the original. It happened with XEmacs (which IMHO is much better than Emacs), I see no logical reason it couldn't happen here aswell.

  41. Re:Don't you know what hardware you got in your co by AvitarX · · Score: 5, Informative

    You want too see the beauty of Linux Auto detection possibilities boot into knoppix.
    I booted of the CD, got fully configured X, working sound, Working Xawtv, Working network with DHCP enabled, and therefore working broadband, and a working CD burner. It took a whole of like one minute to boot and it was everything I neaded. I Actually use it instead of Debian now for my main distro, mounting my old hard drive as scrap space.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  42. Re:They need a new security person or php develope by ealar+dlanvuli · · Score: 2

    sanity checking in your input values

    basic rule of thumb, don't let people past your nic see anything but html; don't accept anything but stuff that you can *prove* is safe.

    --
    I live in a giant bucket.
  43. but.... by oliverthered · · Score: 1

    Did it re-compile a nice tight quick Kernel to match you configuration?

    I have working everything using a Mandrake distro, I had to take apart my Adsl modem and search for a driver for the chipset and get the latest version of the USB drivers to stop gphoto2 crashing.

    --
    thank God the internet isn't a human right.
    1. Re:but.... by Nothinman · · Score: 1

      Everything is modular so the kernel is already as tight and quick as you'd need it.

    2. Re:but.... by oliverthered · · Score: 1

      What?
      The kernel isn't that modular, look at the 2.6 change logs...

      If I compile somthing into the kernel(and not as a module) then that driver is quicker but the kernel is bigger.

      yada yada yada ......

      If there's loads of 'junk' in the kernel then the kernel is bigger than it needs to be, kernel compiles take longer than they need to.

      I can also compile the Kernel for my processor which makes it a bit faster....
      SMP makes the kernel a bit slower on a single processor machine but you need it if you have more than one processor.

      Some options make linux more responsive to the user, but can slow down high load servers.

      --
      thank God the internet isn't a human right.
    3. Re:but.... by AvitarX · · Score: 1

      If a program can pick what modules to load, I would imagine i could pick what to compile into the kernel if you had a check box that said no modules. Autodetect does not mean no user intervention. If you can give someone instructions on what to pick based on their hardware, the configuration can do the same by scanning and picking, and asking questions for what can't be scanned. And a checkbox, this is a high load server is so much harder to implement then Low latency?

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    4. Re:but.... by Nothinman · · Score: 1

      I said 'as you'd need it', you can't expect it to be 100% perfect for everyone. Knoppix is more of a demo distro than something you'd use day to day.

    5. Re:but.... by oliverthered · · Score: 1

      'You can't expect it to be 100% perfect for everyone'

      Well that my point, if you have the kernel source code, why not compile a Kernel that is perfect for you?

      --
      thank God the internet isn't a human right.
    6. Re:but.... by Anonymous Coward · · Score: 0

      Maybe so, but it still kicks the crap out of Debian proper.

    7. Re:but.... by ipjohnson · · Score: 1

      Because not every one needs or even wants to ... if you have a fast machine its not going to make that much of a difference.

      I'm a computer nerd but often I'd rather do my work or other things than f*ck around with configs ... then again thats why I own a mac.

  44. Re:no wonder by Fragmented_Datagram · · Score: 1

    The default is to allow a maximum number of 100 connections. You can set it higher if needed:

    http://www.mysql.com/doc/en/Too_many_connections.h tml
    (Fix the html link that Slashdot breaks)

  45. Improvements in this new system? by Thoron · · Score: 1
    What does this new system offer that "make xconfig" does not already have?

    Those screenshot shows me a system that it's even harder to use than the current one.

    Why do you have re-invent whell always?

    Current configuration system is under change on 2.5.x series, anyway and already.

  46. Re:The Developers Arent Always Right & Politic by gmack · · Score: 4, Insightful

    GGI tried to do too much and it abstracted too far.

    Userspace PCMCIA drivers? That's a new one. I can only imagine that you were refering to the external set of drivers that used to be the standard and where characterised as being so hard to install that Linus himself had trouble with it. I completly understand his reasons for wanting that mess replaced.

    ESR's configureator was massive overkill and it made life harder for developers. On top of that what killed it in the end wsa not Linus but ESR's refusal to update the patches to handle changes Linus made to the core code.

    Not everything gets to be black and white.

  47. A great start. by FreeLinux · · Score: 3, Insightful

    After finally being able to get the page, I think that it is a great start and a tremendous improvement over Xconfig.

    That said, I think he still needs to go further. Most users don't have a clue what all the options are or mean. Even with the descriptions and recommendations they will quickly become overwelmed.

    I feel that users should be presented with a very basic and lean initial configuration screen. One that lists generic features for them to enable and disable. For example a single check box for IDE and SCSI HD support or a single checkbox to enable HAM radio support with generic or "standard" options preselected for those devices. Then there should be an advanced button that brings them to the complete configuration options, such as Roman's example.

    This, combined with some form of modprobe hardware detection, would make kernel configuration a breeze, even for MCSEs. Also, the fact that this configurator reads the existing config, rather than starting with a blank slate everytime, is great!!

  48. fa! by Anonymous Coward · · Score: 0

    Woo hoo! Betcha Roman's system requires 500 megs of Gnome libraries, 500 more of xml libraries, 700 megs of "skins", animations, and icons.

  49. OMG It tells me what each option does!!! by io333 · · Score: 1

    It tells me what each option does in a little help screen below.

    It runs on the desktop.

    It tells me what each option does in a little help screen below!!!!!

    It tells me what each option does!!!

    It tells me what each option does.

    I want this so bad. I can't wait until there's a Gentoo ebuild!!!!!

    Yea!!! Hooray!!!!!! Yea!!!!

    Yes I am stupid and don't know what every option does. I don't care, I want it I want it I want it. Because: IT TELLS ME WHAT EACH OPTION DOES!!!!!!!!!

    What part of "It tells me what each option does!!!" do you not understand?

    1. Re:OMG It tells me what each option does!!! by cioxx · · Score: 1

      Yes, I noticed that in the screenshots. The infobox is an incredible feature.

      So this was the poor guy who got booed off the stage? WOW.

    2. Re:OMG It tells me what each option does!!! by Anonymous Coward · · Score: 0

      actually, menuconfig and xconfig also tell you wha each option does.

    3. Re:OMG It tells me what each option does!!! by damiam · · Score: 1

      It's not the guy who got booed off the stage. And the infobox is nothing more than a slightly more accessible version of the "Help" button that's already next to every item in 'make xconfig'.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
  50. anybody for ./configure && make && by richie123 · · Score: 1

    I would be best if installing a kernel was as simple
    as installing most Linux software.

    I would like to see some type of system that detected
    all the hardware in my system, and built the matching
    drivers and standard kernel modules for a desktop
    or server system.

    The user should need to change as few options as
    possible.

  51. Look at the details, this shows the process by AxelTorvalds · · Score: 4, Insightful
    ESR got himself booed off the stage by trying to undermine the process. His solution was technically superior in ways, it didn't do what Linus and others wanted and he was playing politics and games trying to get it in to the kernel. When that was exposed it was done. Technically superior or not, the games undermine everything, it's a very open process and they like peer review and things done in the open. Bottom line, not too many people aren't replacable and any work you do can probably be done by somebody else, they don't need politicians. There were a few times when Linus made it very clear what he wanted changed and ESR simply didn't fix it, it was as if he didn't even hear it; look at the threads in the kernel archive. I don't know what ESR's motivation was but he made it look a little corrupt.

    Further, people are working on the configuartion language but there are bigger problems to be solved, everyone knows it and still the efforts don't fully address them. Like how do you know the configuation options used on the kernel you are running? There is no reason to change just for the sake of change and compilation speed isn't a huge issue, my dual amd compiles kernels so fast I don't care if I cut the speed in half. Plus, when you're hacking you usually work on a module or two and don't rebuild the whole thing.

    The process is good, they don't take crap. The VM system and the IDE system are other prime examples. Al Viro is kind of mean to people but everyone else makes it pretty clear what needs to be done, why things aren't accpeted, even Al has expectations that he makes clear. There are expectations for robustness, it's more important than performance. Hans Reiser has had issues with that, he can't explain the robustness or answers concerns but he can point to benchmarks; clue: they don't give a shit if it's not robust.

    There have been a handful of people who just don't cut it. Believe me, they can be replaced. It sucks, it'll be a dark day when Alan Cox or Dave Miller quit, if they ever do but they also know the rules, they play by them and they have their own forks if they don't agree. If Linus or someone else don't like your code, it doesn't get in, fork and show that they are wrong or make it better. This isn't bullying or anything like that, it's not that they are elitests, they have real expectations that aren't meet some times. Are some people and some parts of the kernel more equal than others? Of course, we're all human.

    I take exception to the suggestion that the kernel team is throwing out great stuff for non technical reasons. They aren't they throw it out because it doesn't do what it is supposed to, people are trying to get it in for non-technical reasons with non-technical means or because it's not robust. It's not easy to write a VM or IDE system, there are a ton of expectations, it's a hard job, there are working solutions already that you have to do better than.

    1. Re:Look at the details, this shows the process by iabervon · · Score: 2

      In particular, a new configuration system has to be able to run on rules that the old configuration system can run on, so that both can be in the kernel until people are satisfied with the new one (ironic that Linus rejected CML2 for largely this reason, but then didn't follow this principal with IDE, where it would have been much easier). In order to replace something that everyone has to use, you have to replace it with something that just works for everybody, including the people writing rules, people who want to keep their old configs, people who want to maintain code for both the new kernels and old kernels, and so forth. The whole "Aunt Tillie" thing really is an issue, because important kernel developers don't want to spend more thought on configuring the kernel they're building than Aunt Tillie would, and they already have routine ways of doing that.

      "Technical superiority" is a subjective thing, and "does it configure the kernel" is not the only factor. At least as important is "is switching to it easier than continuing to use the existing tools".

      Incidentally, the problem with the old build system was not that it was too slow to build but that, if you changes a few things and rebuilt, either you did a complete rebuild, which was too slow, or you just rebuilt the module you were working on, which didn't necessarily catch all of the changes. The new versions are moving toward giving you the ability to rebuild only those things which actually need to be rebuilt without making you know what things these are. People frequently report problems where they've forgotten to do the right thing after they've changed something.

      Making the current kernel's configuration available isn't actually difficult at all; it's just that userspace generally has the information anyway (most people copy the config file somewhere parallel to the kernel image). The hard thing is configuring a new kernel version to match the effects of the config file for an old kernel version: sometimes the options change, sometimes there are new options required for old things, etc.

    2. Re:Look at the details, this shows the process by kcbrown · · Score: 2
      Like how do you know the configuration options used on the kernel you are running?

      This one should be so simple to solve that I don't understand why it's an issue at all, namely: include a copy of the .config file in the kernel image and add a handler so that /proc/kconfig maps to it. On my system, the .config file is 36k in size -- small compared with the size of most running kernels these days.

      Obviously that should be another configuration option, but it would certainly solve most of the problem, if not all of it.

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    3. Re:Look at the details, this shows the process by CreamsicleSeventeen · · Score: 1

      Peter T. Breuer wrote a patch that puts your .config options in /proc/config. The tarball is (was?) called proconfig-foo. Check ftp://oboe.it.uc3m.es/pub/Programs/

  52. ESR's software won't work by burris · · Score: 1, Funny

    Many people are suggesting that a primary reason why ESR's work was rejected is because it required Python to build the kernel. Well, I would like to interject that a new build system is still desperately needed. I built a kernel the other day and had to install all sorts of extra crap to do so. Can we please have a configuration system that doesn't depend on outside tools? I do not want to have to install gcc, gmake, libc, etc... just to build a new kernel!

    burris

    1. Re:ESR's software won't work by Anonymous Coward · · Score: 0

      May you suggest how we can compile a kernel WITHOUT a C compiler????????

    2. Re:ESR's software won't work by Figaro · · Score: 1

      Insightful??

      I hope this was a joke. How the heck are you supposed to *build* a new kernel without gcc?!?!

      --
      :wq
    3. Re:ESR's software won't work by Anonymous Coward · · Score: 0

      The point isn't trying to build the kernel without a C compiler. It's trying to build the kernel without the GCC C compiler and GNU make and the GNU libraries and 20 other GNU programs. There's too many GNU extensions used in the code and the build system for other tools to work.

    4. Re:ESR's software won't work by Anonymous Coward · · Score: 0

      There's too many GNU extensions used in the code and the build system for other tools to work.

      GNU/Linux 'nuff said

    5. Re:ESR's software won't work by hazyshadeofwinter · · Score: 1
      > I hope this was a joke. How the heck are you supposed to *build* a new kernel without gcc?!?!
      1. Learn C.
      2. Learn [your-arch-here] assembler.
      3. Learn the quirks that (reportedly) make Linux only build on gcc
      4. Translate by hand to machine language
      5. Whistle resulting 1's and 0's into modem. Be sure to whistle *really* *high* if it's a DSL modem
      6. HTH.
      --
      Click here if you just like to click on shit.
  53. linux kernel vs. linux as an operation system by dollargonzo · · Score: 1

    there is a big difference between the kernel and the desktop application of the kernel underneath it. i think that change in the kernel should come slowly, after every element has been thought and rethought of. if the kernel breaks, so will the systems built on it. if there is any doubt, PLEASE don't change the underlying structure. it is the same with murder cases.

    i do agree that sometimes, the resistance to change in the kernel transfers over to the other elements of the system, but you should bring up that point NOT to kernel developers but the others. the average user should not be compiling kernels every day. those who do it should know what is going on. abstraction is good, but autodetection on the kernel level is NOT good, for example, because this should happen when u install the distribution, NOT the underlying system.

    --
    BSD is for people who love UNIX. Linux is for those who hate Microsoft.
  54. How about this.... by Chanc_Gorkon · · Score: 2

    Kernel changes that modularize everything that can be (pretty much that way now) and everything loaded on need (it's done that way now too mostly). So why compile your kernel (besides the because you can thing). One thing I would like is to see a standard way for non GPL'd drivers to be added to the kernel without a recompile, or having to half way compile (proprietary core) with a kernel interface needing compiled. It's kind of that way with some, but only if your binary is developed against the same kernel (the LTMODEM drivers used to be and may be still this way). Microsoft does not write all of their drivers. We should not have to either. Seems to me this would sure make alot more hardware work under Linux! I know the GNU bigots won't like it much, but I just want to be able to have more stuff supported out of the box then I do now.

    --

    Gorkman

  55. Shouting down a bad implementation may be good... by Anonymous Coward · · Score: 0

    It show the community drives the evolution of Linux and not one person. If only some brave souls were around to do the same when the sap at Microsoft layed out the idea for Microsoft Bob and (later neutered implementation) Clippy it may have saved them some embaressment.

  56. Re:The Developers Arent Always Right & Politic by grumpygrodyguy · · Score: 0

    This is a good argument for some kind of QA process in open-source development. Most professional software shops have good compartimentalization between development and testing/QA.

    It's very important to get user feedback also...not developer feedback...but actual user feedback.

    I've always thought one of the biggest drawbacks to open source was the lack of user feedback/input. But unfortunately that shows little sign of changing...the developer community is very closed and tight-knit.

    I really doubt that the OSS movement will produce software that the other 99.99% of the population wants or can use.

    Linux is a good example...the only people who really have any business using linux are programmers, UNIX people, and server admins. That excludes just about everyone in your zip code except you and that guy you met at the user group last month.

    --
    The government has a defect: it's potentially democratic. Corporations have no defect: they're pure tyrannies. -Chomsky
  57. Best Quote from the article by UnknownSoldier · · Score: 2

    "Shit... don't inflate my stock more than it's worth." - Jeff Garzik

    Now if only more [people] were at least this humble...

    1. Re:Best Quote from the article by Prior+Restraint · · Score: 2

      Now if only more [people] were at least this humble...

      I didn't see it as humility, but more as a polite way of saying, "Don't bother kissing my ass; it won't work."

  58. Here are your coloring books and crayons... by Anonymous Coward · · Score: 0
    Good grief.

    You're compiling the damned kernel!! What fucking candy-assed wuss needs or even wants a GUI for that?

  59. the next step by oliverthered · · Score: 1

    The next step would be to connect to an online database of linux drivers/patches and see if there any updates to drivers for your hardware.

    This would make a great addition to gentoo

    --
    thank God the internet isn't a human right.
  60. Re:no wonder by anarchima · · Score: 1

    It says that Linux users should expect about 500-1000 connections at any one time to be the max amount. This doesn't seem like a lot when thinking of websites that get a LOT of traffic and store all their website material in databases. Are the commercial DB's more capable?

  61. What Open Source communities DO lack by Idou · · Score: 2, Informative

    are the marketing and PR departments to cover up or put spin on anything that could be even remotely considered a mistake.

    To parent poster: Do you honestly believe that worse things don't happens behind corporate walls!? Have you been living in a bubble!? The great thing about open source is, whatever happens, you will always have enough information to form your own opinion. As a corporate drone, I can safely assure you that you will NEVER get that level of detail from a corporation (even though the Internet has helped expose a lot). Personally, I think your shock is due to a lack of exposure to a REAL community (people argue all the time . . . that's how things get worked out), rather than anything having to due witht the Kernel developers. Goes to show how corporate our society has become . . .

    --
    Sdelat' Ameriku velikoy Snova!
  62. Re:no wonder by CaptnMArk · · Score: 1


    What is needed in this case is some more
    serialization of the database access.

    If you have 1000 clients requesting the same page data from DB it would be a good idea to not to fetch the data from the DB for each of them.

    A well designed system could reuse the data fetched once to server several clients.

  63. why are custom kernels needed? by mrm677 · · Score: 4, Interesting

    My question is why custom kernels are needed anyways? Except for embedded applications, such as Tivo, why should the common user have to build a custom kernel to get certain hardware support? Is the Linux device driver model really flawed as many claim?

    Certainly its nice for development, or experimental patches such as low-latency patches. However it often seems necessary to build a kernel to get certain modules or hardware functionality.

    Any comments on the Linux device driver model?

    1. Re:why are custom kernels needed? by WetCat · · Score: 1

      I use custom kernels when I need to incorporate non-mainstream patches , such as http://www.solucorp.qc.ca (vserver) and rsbac(www.rsbac.de).

    2. Re:why are custom kernels needed? by be-fan · · Score: 2

      Its largely not needed anymore. Even from a performance standpoint, its not really an issue because Linux links in drivers as just another .o file. Thus, there is the new Linux driver model in 2.5 (it'll be awhile before everything uses it though) and Linus has stated that he wants to remove compiled-in drivers and make everything dynamic.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:why are custom kernels needed? by TurdFurgeson · · Score: 0

      and you get modded as flamebait? nice...

      i was wondering why the X still looks like ass. you would think that with the entire linux community working on these projects that they could surely beat out a few thousand devs at microsoft

    4. Re:why are custom kernels needed? by Bishop · · Score: 2

      As an end user I have had no trouble with Linux device drivers. I suspect that most users with standard machines will have no trouble with device drivers. I use Debian. It compiles many drivers into the kernel directly. It includes the rest as modules. The list of hardware that a default Debian does not run on is pretty small.

      I do however use a custom kernel. Not because I have to, but because I want to. In the case of Debian I wish to use devfs which is experimental. I also wish to remove the unneeded drivers, modularize other drivers, and compile the kernel specifically for the target CPU.

      If you must recompile your kernel it is the fault of your distrobution not the Linux kernel.

      Is the Linux device driver model really flawed as many claim?

      I take exception to your statement that "many claim." It makes you look like a troll. If you wrote "some claim" I would accept that. Regardless, I disagree. From a technology perspective Linux device drivers can do anything that "that other OS" kernel can. The big difference is that linux drivers don't usually come precompiled. There is no good reason for this other then history.

    5. Re:why are custom kernels needed? by mrm677 · · Score: 2

      I take exception to your statement that "many claim." It makes you look like a troll. If you wrote "some claim" I would accept that. Regardless, I disagree. From a technology perspective Linux device drivers can do anything that "that other OS" kernel can. The big difference is that linux drivers don't usually come precompiled. There is no good reason for this other then history.

      I guess I hear this too much by being in the academic world (Computer Science). However I do know that many linux device drivers, such as the OpenAFS client file system module, rely on knowing the exact offsets of fields in the task_struct. There is no run-time method of retrieving these offsets as far as I know. So our administrators are forced to re-compile the openafs module everytime they apply a patch, or run a different kernel on a system that has changed the layout of task_struct. When maintaining systems that may serve different purposes, I can see why this would be an administration headache. We use a distributed filesystem where most binaries, such as device drivers, are maintained on a central server instead of being on each local box.

      Constrast this scenario which Solaris, which is claimed to have a great device driver model by these people I speak of. I can use the same device driver binary I used in Solaris 2.6 as I use in Solaris 8.0.

      Regards...I wasn't trying to be a troll.

    6. Re:why are custom kernels needed? by Anonymous Coward · · Score: 0

      One very important reason is security. On my servers, I only compile in the options and drivers the box needs. I turn off kernel module support because one of the more popular ways to hose your box is to install an trojan kernel module. Therefore, turning off module support can greatly enhance security. This strategy also requires statically compiling each option and driver needed.

  64. Re:no wonder by Anonymous Coward · · Score: 0

    "something" learn to spell stupid and no slashdump runs on DB2.

  65. Re:The Developers Arent Always Right & Politic by dd301 · · Score: 1

    GGI tried to do too much and it abstracted too far.

    AFAIK, they had a lot of problem using the hardware acceleration in the video card.

    ESR's configureator was massive overkill and it made life harder for developers.

    Why would anyone object to a text based adventure game in the configuration system? Surely not the MS excel users. ;-)

  66. missing the point by g4dget · · Score: 3, Interesting
    I'm sorry, but tinkering around with another graphical configuration app isn't going to fix the fundamental problems with Linux kernel configuration. (In fact, if anything, I find a single window application with a tree widget worse than xconfig.)

    We shouldn't have to decide for hundreds of packages whether we want them or what options they should be pre-configured with in the first place. Almost everything should always be dynamically loadable and should always be dynamically loaded. Modules should be independent between minor kernel versions. There should be very few options, and those that are there should be configurable at runtime. The few remaining compile-time options shouldn't require some complicated interface. If we want single-file kernel distribution, we should be able to create a single file archive of the kernel and the required modules in a way that the bootstrap loader understands.

    While parts of the Linux kernel are great--the variety of kernels and file systems, for example--I think overall kernel architecture and configuration is by far the weakest part of the Linux operating system. It's not the GUI that inhibits Linux adoption by the masses--Linux GUIs are up to par with other platforms--it's the fact that a large number of people end up having to recompile the kernel to get things like audio, FireWire, power management, cameras, and USB working, even with the modularized kernels in some distributions.

    1. Re:missing the point by Mark+Bainter · · Score: 1
      What a crock. It'll be a sad day for linux when you can't customize your kernel. I don't WANT all the freaking modules for every piece of hardware the kernel supports. That's just ridiculous. I only actually USE a very small percentage. Are you going to suggest that the same kernel be bootable across all architectures too? Or maybe we should just always have to have a kernel and a copy of the full binary module tree for every possible hardware platform the kernel supports?

      Sheesh. It's people like you that give laziness a bad name.

      --
      "No nation could preserve its freedom in the midst of continual warfare."
      --James Madison
    2. Re:missing the point by g4dget · · Score: 2
      Or maybe we should just always have to have a kernel and a copy of the full binary module tree for every possible hardware platform the kernel supports?

      We should do what we do with every other piece of software on Linux: have separate packages. You have a GeeWhiz audio card? Install the GeeWhiz audio package. Want ReiserFS? Install the ReiserFS package. Want networking? Install the networking package. Kernel modules are a start, but they need a lot more work.

      It'll be a sad day for linux when you can't customize your kernel.

      I do want to be able to customize the kernel. In fact, I want to be able to do so much more and much more easily than I can now. I want to be able to add functionality to the kernel as easily as I can add a new command line command. We stopped recompiling our command line interpreters to add new commands some time in the 1960's--and Linux should stop requiring recompiling the kernel to add new functionality.

      Sheesh. It's people like you that give laziness a bad name.

      It's people like you that give Linux a bad name.

    3. Re:missing the point by Eil · · Score: 2


      I thought pretty much the same thing when I saw the screen shots. "Okay, looks like a QT version of menuconfig. But what does it DO differently than the current config utilities?" And the answer, near as I can tell: nothing at all.

      I mean, maybe I'm missing the entire point of this new wonderful utility, but from what I've read, I could have done the same thing by hacking with Tcl/Tk for a half an hour.

      I'm right in line with you: what the Linux kernel needs desparately more than GUI menuconfig is the complete removal of any configuration process altogether. Many operating systems have proven in the past that a fast stable kernel that you never have to touch is indeed possible, and presumably, not overly difficult either.

  67. Linux is often misleading by Trepidity · · Score: 5, Interesting

    I know what hardware I have in my computer. But Linux often either labels it strangely, or labels it completely wrongly because of its bizarre way of operating. For example, I have not a single piece of SCSI hardware in my system. Yet for my IDE CD burner to work, I have to load the ide-scsi module, because apparently CD burning in Linux has only been implemented for SCSI burners, so the only way to get IDE burners to work is to emulate them as SCSI burners. Not intuitive.

    Not to mention the millions of chipset names. In Windows, you choose the name of your card, and it figures out the chipset (that's in the worst case; usually it just auto-detects it in the first place). In Linux, you have to figure out who made the chipset on your card, which often isn't labeled on the box or in the manual, so requires some guessing or googling. An easy-to-find example is the emu10k1 for Soundblaster Live cards (this is actually documented by Creative); a harder-to-find example is the tulip driver for LinkSys network cards (most of the $10 LinkSys cards don't come with a manual, and the box doesn't mention what chipset they use). And so on for ever.

    The Debian way of solving this is by default to build almost everything in the kernel as a module. That way if you discover you need some functionality, you don't have to recompile the kernel; just load the required module. It makes kernel compiling take a bit longer (~20 mins on my Athlon 1.33 GHz), but it's worth it IMHO for never having to recompile it again (until the next kernel upgrade anyway).

    1. Re:Linux is often misleading by vadim_t · · Score: 2, Informative

      Nope, it makes perfect sense. Most CD drives and burners use ATAPI.
      From the google glossary at labs.google.com:

      Advanced Technology Packet Interface: a specification that defines device side characteristics for an IDE connected peripheral, such as CD-ROM or tape drives. ATAPI is essentially an adaptation of the SCSI command set to the IDE interface.

      ide-scsi is not really SCSI emulation. It is just SCSI over IDE. And Windows works the same, it just doesn't tell you about it.

    2. Re:Linux is often misleading by dyslexia · · Score: 1, Funny

      Unless they've changed, linksys puts a readme on the floppy that tells you to use the tulip driver.

      RTFM I guess...

      --
      --Have a Johsonville brat.
    3. Re:Linux is often misleading by Trepidity · · Score: 2

      And Windows works the same, it just doesn't tell you about it.

      Well that's the point -- it figures out how to get it working, and does so. It'd be nice if Linux did something like that. To get my cd burner working in Linux, I had to read through the relevant HOWTO, and do the following (my cd-r drive is on /dev/hdc):

      unload the ide-cd module
      reload the ide-cd module with "ignore=hdc"
      load the ide-scsi module
      change the /dev/cdrom symlink to point to /dev/scd0 instead of /dev/hdc

      Not too difficult once you figure out what to do (especially if you use modconf on Debian so your modules and module parameters automatically get saved for the next boot), but not exactly newbie-friendly either.

    4. Re:Linux is often misleading by danalien · · Score: 1


      Why not just put (add) "hdc=ide-scsi" to your Lilo (in the approprite place, ofcource).
      and do the symlink:thinge?

      --
      I don't claim I know more than I know, and if you know you know more than I know, then by all means, let me know.
    5. Re:Linux is often misleading by Trepidity · · Score: 2

      I suppose that'd work too. The reason I did it the way I did is that's how the HOWTO I read recommended. That and Debian has a nice modconf utility for setting up modules and their parameters, while for lilo I'd have to figure out how to edit it properly myself.

    6. Re:Linux is often misleading by kasperd · · Score: 2

      it figures out how to get it working, and does so.

      You say it like it is some kind of magic. There is no magic to this, somebody has to figure out how the hardware is working. If you don't want to figure that out by yourself, you shouldn't compile your own kernels. All distributions comes with precompiled kernels, and you can usually also download precompiled updates.

      BTW I found almost everything I needed to know about CD recording in the CD-Writing-HOWTO.

      --

      Do you care about the security of your wireless mouse?
    7. Re:Linux is often misleading by captaineo · · Score: 2

      I would actually place the blame for this on hardware makers, for making it so difficult to find out exactly what chipset is driving their product.

      e.g. I was given a spare Asante ethernet card recently, and neither the vendor's site nor an extensive Google search could tell me what chipset it used. In desparation I peeled off the "Asante" sticker on the big chip in the middle of the board, and guess what, beneath the chip said "PNIC" on it. If the vendor had cared to mention its card was PNIC-based, I would not have had to waste so much time...

      Network card makers seem to be the worst about this, followed by sound card companies. At least with video cards the chipset is usually part of the product name. (e.g. Super Whizbang Turbo Alpha Killer Mega GeForce 2)

    8. Re:Linux is often misleading by Anonymous Coward · · Score: 0

      actually, your ATAPI cd burner uses SCSI command packets encapsulated in ATA PIO-mode transfers. now, the linux scsi emulation is obviously an ugly hack, and there's no standard api that abstracts atapi and scsi, but that doesn't mean linux doesn't know what hardware you have. drivers don't care about the label on the box, they care about the chipset and the interface. the linksys driver web page documents the specific chipset on each revision of their cards, by the way. this is how it should be!

      loadable kernel modules should not be used in production systems. that is all.

    9. Re:Linux is often misleading by 3Ddgg · · Score: 1

      Whether or not it is essentially scsi over anything, it is atapi and having to use scsi names for ide hardware is quaint. Now (in_.jp) almost all CD-R(W), DVD-R(W) DVD+R(W) is either atapi, usb2 or firewire. Wether or not it 'really' is scsi, perception is reality and the box says its atapi and it works as a cd-rom using ide-atapi drivers, but EVERYONE has to go searching through the documentation to find out that Linux has this quaint approach to burners.

      Why not just say THESE ARE ATAPI DRIVERS FOR YOUR ATAPI BURNER and if everyone should know that it's really just scsi over ide, tell them that it requires scsi and explain why in a note somewhere, but make the ATAPI drivers as ATAPI drivers instead of creating this headache. The use of CD and DVD media is an area where Linux is a LONG way behind in terms of usability and this is NOT just an issue with codec use in the USA. Could the virtual_/dev system coming up fix this.

      1.../dev/cdrom
      2.../dev/cd-r and a disk cache
      3.../dev/cd-rw

      ABC

      anyway back to how after why. If someone could make a better configure tool to know all of these things and do a check for compatibility requirements before saving, like a package management tool and give you a chance to go back and check that one box you missed, without having to make, install and boot your kernel only to discover that you missed something somewhere (maybe).

      The heirarchical package selection system in a single window used by package managers might groan a little, but if it could allow you to look at a single screen and say I want drivers for CD burners (atapi or USB? :-) and USB HIDs and core linux, legacy , network and/or CD/DVD file systems and whatever else, then allow those who want/need to, to go in and look for their cards, devices, file systems, character sets, whatever.

      --
      No warranty of any kind is offered as to the quality of this post.
    10. Re:Linux is often misleading by Tomble · · Score: 1
      Not to mention the millions of chipset names.[SNIP]In Linux, you have to figure out who made the chipset on your card, which often isn't labeled on the box or in the manual, so requires some guessing or googling.
      Hmm, since I started using Linux, my own approach to this has been, to firstly get a very clear idea of what devices and chipsets Linux currently supports, and then go look for those exact devices or devices that I can see have those chipsets.

      The only problem arises that my Hauppauge WinTV card (supported by the bttv module), conflicts with my c-media sound card (supported by cmpci module) and apparently some other aspect of my system, to cause my machine to lock solidly if I try to use the TV card. -Note that I say there is some other aspect to it, because every other sound card I've tried with it (there have been a few) has made the TV card screw up in one stupid way or another. I've tried emailing the BTTV developer for *any* advice, or any experience of such lock-ups, etc, but he never replied.

      So what can I do? Well, basically I can either never use my TV card until I'm able to buy parts for a second (well, fourth...) system just to do TV capture, or I can keep trying various settings to see if I can ever make it stop hanging, whilst my FS gets slowly corrupted.. Mmm, fun.

      Anyway, regarding your point again, my approach doesn't really cut it for most people, especially the most everyday computer users. The situation isn't the fault of Linux or of Linux programmers, though, it's down to the manufacturers- they supply disks of drivers for windows, which AFAIK mostly consist of the chipset manufacturer's drivers, plus data to tell windows that this product is to be using those drivers, or something along those lines. Those that produce stuff that also works with Linux could fairly easily indicate so on the packaging, and some of them actually do, but most don't, because they wouldn't be able to supply some pretty installer program that would cover up the details like they could for Windows.

      Oh, actually, perhaps they could. Oh I don't care, it just sucks either way.

      --
      Be careful! New moon tonight.
    11. Re:Linux is often misleading by hazyshadeofwinter · · Score: 1

      Interesting. Of all the hardware I own (which isn't much compared to most on this board) only two cards actually have manufacturer Linux support: my generic 56k hardware modem, for which the support is limited to a sticker on the box saying "Supports Linux, Windows 95/98/Me, Windows NT/2000,. yadda yadda yadda" and my D-Link ethernet card, which actually came with the driver source on floppy and a README saying (in effect) "gcc rtl8139.c && insmod 8139." I generally use the HOWTOs as first information source when installing new hardware, then if it doesn't work hit Google, and more or less expect the manufacturer's resources to be useless... Not exactly "Aunt Tillie" friendly, is it? But I expect the situation would be different if Linux was on 95% of desktops.

      --
      Click here if you just like to click on shit.
    12. Re:Linux is often misleading by Xpilot · · Score: 2


      Not to mention the millions of chipset names. In Windows, you choose the name of your card, and it figures out the chipset (that's in the worst case; usually it just auto-detects it in the first place)


      Unless autodetect fails, and you don't know the name of the card (if you bought a pre-assembled computer), you still have to open it up and see the chipset.


      In Linux, you have to figure out who made the chipset on your card, which often isn't labeled on the box or in the manual, so requires some guessing or googling


      The chipset is usually labelled on the chip. Duh.

      Personally I like the Linux way. The chipset is what drives the hardware, no matter who manufactured the card itself. And you have to remember, it's rare to find hardware vendors that distribute drivers for Linux.

      --
      "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
    13. Re:Linux is often misleading by zerocool^ · · Score: 2

      Come on. Do you expect windows 95 to know what that soundblaster live is? Then get a current linux distro. Red Hat 7.3 autodetects all that stuff. And the tulip driver? That and the 8139 are the most common drivers i've seen. The 8139 works for almost everything the tulip doesn't. And both are included with almost all linux distro's today.

      If you're still living with XF86Config, you need to upgrade versions. Some great things have been going on. links -source http://go-gnome.org |bash - linux is doing a lot of stuff on it's own, and some of them have good GUI control panels now.

      We're getting there

      --
      sig?
    14. Re:Linux is often misleading by Trepidity · · Score: 2

      Well Debian's current version isn't exactly ancient (I'm talking about the current version if you apt-get unstable, not the currently released stable version, which is 6-12 months behind due to rigorous testing).

      But in any case, getting the tulip driver to work wasn't a problem. But a newbie installing Linux has likely never heard of a tulip driver, and is unlikely to leap to the conclusion that his LinkSys network card needs it. Auto-detecting it would be nice, or at least having the install say "you probably need either the tulip or the 8139".

      As for X, i tried the new "XFree86 -configure" method, but it hung my computer (couldn't switch virtual consoles even; had to ssh in to kill it). So I ended up manually configuring with xf86config. The new config might be nice if it works, but I haven't had a chance to see it in action...

    15. Re:Linux is often misleading by Anonymous Coward · · Score: 0

      And what do you do, in windows, when you don't know the name of the card, because it is on-board? In linux I looked at the chip, and i said MGA G200 - fine, I use the MGA G200 driver.

      In windows the drivers have names like "Matrox Millenium", but never says which one is the G200. So I tried every Matrox driver, and none worked. I ended up rebooting to linux, going to www.matrox.com and spending way too long looking for a driver for a G200 card, then rebooting back to windows, to install the driver.

    16. Re:Linux is often misleading by crush · · Score: 2

      In Linux, you have to figure out who made the chipset on your card, which often isn't labeled on the box or in the manual, so requires some guessing or googling. An easy-to-find example is the emu10k1 for Soundblaster Live cards (this is actually documented by Creative);

      That's a terrible example:

      /sbin/lspci -vv | grep audio
      00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 05)
      That does it very easily and nicely. How much does it take to figure that out? If you're not capable of that then one of the recent releases of Red Hat, SuSE or Mandrake will autoconfigure it for you. I've had that particular card set up automatically with NO intervention on my part by the last two releases of Red Hat.

      What you argue may be true for very arcane hardware or may have been true 6 months ago, but it's hard to support that position now.

    17. Re:Linux is often misleading by Anonymous Coward · · Score: 0

      How odd. All I did to get it working was install Red Hat 7.3. Worked straight away. VERY newbie friendly.

  68. Wanna see something cool? by 13Echo · · Score: 3, Insightful
    "It tells me what each option does."


    KDE 3 does this via it's configurator with the current kernel/module system.

    Here's a screenshot.

    Really, I see no problem with the current system. It works well, and is totally modular. You never really even have to recompile your standard, vanilla kernel.

    But hey. This new system should be given a chance, I suppose, though I see no use for it personally. I would prefer that it wasn't forced upon me in 2.5.
    1. Re:Wanna see something cool? by Anonymous Coward · · Score: 0

      A kernel configuration control center applet... yep... yes, indeed... that is, without a doubt, the stupidest thing I've ever seen.

    2. Re:Wanna see something cool? by Anonymous Coward · · Score: 0

      Yeah, but KDE doesn't even get past parsing the architecture of a 2-4-19 kernel.

      "Either your kernel sources contain invalid configuration rules or you just found a bug in the KDE Kernel Configurator."

  69. Bruce, you are a GOD! by schlach · · Score: 1

    See this comment [slashdot.org].

    Even your comments that merely tell people to read your other comments are modded up...

    1. Re:Bruce, you are a GOD! by Bruce+Perens · · Score: 1

      All I can do is try to use my notoriety for good :-)

  70. Okay, okay... by billbaggins · · Score: 1

    Y'all can shut up now. I have been duly advised that I had the wrong TLA person writing Emacs, and that Emacs is the One True Editor. I was trying to make a point, but I missed horribly. At the time, a lisp interpreter in a text editor was a horrendously big thing to do. I use and love Emacs, I just think that, at first look, it's a ridiculous concept.

    --
    "The best argument against democracy is a five minute chat with the average voter."
    --Winston Churchill
  71. Darn tootin' by Kappelmeister · · Score: 1

    I can't agree with your second point more.

    "Literally" is a word that you use when you want to cut through layers upon layers of misued metaphors, ambiguous sarcasm, and other kinds misdirection,

    It's like a reserved word. Or, better yet, it's like an escape character. Whatever follows it should not be interpreted by some high rhetorical parser; instead, it means what it says it means.

    Somewhere along the line, though, people misinterpreted "literally" as just another word for emphasis, so now everyone is talking about how they are "literally dying of thirst" and so on.

    Go ahead and redefine the rest of the language to mean new, exciting things, but take your hands off of "literally" -- it's sacred.

    This will probably get modded down as Offtopic, but whenever someone says they'll probably get modded down as Offtopic, they end up with 5.

  72. modular. by oliverthered · · Score: 1

    I would have thought making everything modular would have saved time, testing, debugging and waiting for the time when linux is modular enough that hardware vendors will actually write drivers.

    --
    thank God the internet isn't a human right.
  73. New Kernel Configuration by hackus · · Score: 2

    The primary problem I have with "graphical" anything, is that this is a Windows era issue of "every program written has to use a mouse and a window or it isn't user friendly."

    Simply not true. When all I had was a VT100 command set, I wrote terminal interfaces that a 4 year old could use for fairly complicated pieces of software, no mouse required.

    Although it did use windows....of a sort.

    As for configuring and building a kernel, beyond:

    1) Interfaces to remove and pull out components on demand....

    2) The interface should provide optional documentation and guidelines as well as best practices for most kernel configs given the applications the machine is going to be running.
    (i.e. Will it be a router, firewall, an app server or database server?)

    3) The configuration system should be easily scriptable with a minimal set of gcc utils.
    (sh, make, config..etc.) This is so that it requires less software to build the kernel.

    This implies inherent reduced security risks, smaller kernel distribution and less dependancies for linux systems integrators.

    Eric S Raymonds vision fails on all three accounts as far as I can tell, on how a kernel should be built and what the logical assumptions are for building a kernel in the first place.

    Primarily, users, shouldn't be building kernels anyway. Which is what I think the root problem is here. No, I don't think either, that there is something wrong with Linux if a user can't do EVERYTHING with a mouse and windows.

    Lets be realistic here: Users do not have the background to properly build a kernel, and building a nice graphical front end too build a kernel for a sophisticated developer gets in the way. It also, doesn't detract from Linux one iota simply because this fact exists.

    That is what the argument here is, and that is why many people who write kernel programs don't use graphical tools ANYWAY. Which I think breaks another assumption made by Mr. Raymond about a new config system.

    Dependancy graphics are nice, rules seperation parsers built to create such graphics with a language are nice.

    But this is really OLD SCHOOL stuff. Any computer science/computer professional can buy a book on such theory and compeently learn everything there is to know about REINVENTING the wheel.
    (ISBN: 0-13-1555045-4 Start reading at 7.3.2)

    And you too can write a configuration system similair to Eric's...

    But WHY WASTE YOUR TIME?

    The existing kernel configuration system is very scriptable, has supporting documentation available with each modules or options, and works with a very minimal set of build tools on the command line.

    Very nice, simple and it works very well very nicely without Python, X, windows, Mice a supported video driver and a whole new set of tools that basically give us the same thing we have now, just a whole lot more complicated.

    I would like to see Eric address points 1-3 and tell use exactly why we need all this stuff as kernel developers. He hasn't done so.

    His website just shows pretty pictures of a kernel configuration system.

    Hack

    --
    Got Geometrodynamics? Awe, too hard to figure out? Too bad.
    1. Re:New Kernel Configuration by Russ+Nelson · · Score: 2

      CML2 is not about a graphical config tool. It's about having a set of rules rather than steps for configuring the kernel. CML2 is designed to be scriptable. It's designed for higher-level analysis than CML1 can ever make. It lets you say (for example) "I have no ISA bus", and all the drivers for ISA hardware get turned off.
      -russ

      --
      Don't piss off The Angry Economist
    2. Re:New Kernel Configuration by hackus · · Score: 2

      I think the CML2 design is NOT what is at issue here. I also never said anything about CML2, I don't think CML2, itself is the issue here. I also never said that CML2 is a graphical interface.

      I am talking about assumptions, issues in my previous post that Mr. Raymond, makes, all of which I think are irrelevant or bad assumptions about a CML2 implementation for building a kernel.

      I am not interested in a graphical interface for a CML2 implementation, quite frankly.

      As I stated earlier, graphical interfaces require too much baggage to implement when we are talking about "bootstrap" software such as an OS kernel configuration utility.

      I also pointed to the fact that you can make very competent and very easy to use interfaces using simple menu's and windows with a curses library for example, in a CML2 implementation.

      I finally make note of the fact that users shouldn't be and will never need to build thier own kernel. They are users, and by definition not systems people.

      You can't give a calculus book to a kindegardener and then fault calculus for being TOO HARD, or designed WRONG, because the kindegardener can't figure it out.

      Fundamentally the arguments for making kernels buildable by users are wrong, incorrect, and detract a lot of precious time from improving the system we have that works right now.

      We have this mentality that everything should be driven using a mouse, and a GUI, which is fundamentally incorrect.

      I can't tell you how many times I have watched over bloated Microsoft crap drive perfectly competent hardware costing thousands less into the ground, simply because the idiots at Microsoft think you have to have a GUI on a server for everything....

      Just in case you want to load and run StarCraft or Dark Reign 2, on your SQL Server.

      Hack

      PS: Two of my personal Favorites by the way...

      --
      Got Geometrodynamics? Awe, too hard to figure out? Too bad.
    3. Re:New Kernel Configuration by Russ+Nelson · · Score: 2

      You said: That is what the argument here is, and that is why many people who write kernel programs don't use graphical tools ANYWAY. Which I think breaks another assumption made by Mr. Raymond about a new config system.

      You also said:

      Since it is Eric Raymond who is working on CML2, I have to wonder why you keep harping on graphical tools unless you think CML2 is just a graphical kernel configuration system.
      -russ

      --
      Don't piss off The Angry Economist
  74. Linux guis up to par? by Otis_INF · · Score: 2

    Check out the second screenshot. 2 scrollbars of 2 different applications. One has a normal, ugly X scrollbar, the other has a nice look, probably inheriting the selected theme.

    That, my friend, is a result of the true error in the whole picture: there is no consistency. People are doing what they think is right, but there is no big, guideline which will bring the whole system to a certain level because it's all worked out.

    That is true for the gui, it's also true for kernel configuration. You are right about the fact that people shouldn't be hassling over which package should be installed and which option should be compiled into the kernel. On windows I just run setup and the system configs itself. I never have to recompile any kernel, because 1) I don't have the sourcecode (;)) but 2) I don't have to: WinXP will config itself and will work no matter what hw card I jam into the pci slots: install the driver (or better: xp has the driver already) and off you go. There is no need for compilation of a certain subsystem into the 'kernel'.

    --
    Never underestimate the relief of true separation of Religion and State.
    1. Re:Linux guis up to par? by g4dget · · Score: 2
      On windows I just run setup and the system configs itself. I never have to recompile any kernel, because 1) I don't have the sourcecode (;)) but 2) I don't have to: WinXP will config itself and will work no matter what hw card I jam into the pci slots: install the driver (or better: xp has the driver already) and off you go. There is no need for compilation of a certain subsystem into the 'kernel'.

      Yes, kernel modules work better on Windows and Macintosh OS X. That's the kind of kernel configurability Linux should aim for.

      That, my friend, is a result of the true error in the whole picture: there is no consistency. People are doing what they think is right, but there is no big, guideline which will bring the whole system to a certain level because it's all worked out.

      Windows and Macintosh had to make dynamic kernel configuration work because recompilation just wasn't an option in their markets.

      Your analogy to GUIs misses the point. Hardware vendors on Windows or Macintosh don't make their drivers work because of some consistent guidelines, they make they work because otherwise they couldn't sell their products. Hardware vendors did this long before DOS/Windows even had a kernel or guidelines. Linux kernel configuration is, if anything, more consistent and standardized than Windows, it just happens to be more cumbersome for end users, too.

    2. Re:Linux guis up to par? by g4dget · · Score: 2
      VisualStudio.NET bombs the Linux developer right back to the stone age.

      Indeed. As a Linux developer, I always feel like I'm back in the stone age when I use VisualStudio.

    3. Re:Linux guis up to par? by Anonymous Coward · · Score: 0

      after a few months of using visualstudio.net I feel like I'm using a really beta version of delphi 1.0.

  75. Wow! Look at that! by freebsd45 · · Score: 1, Insightful

    I've never needed more than vi to configure, make and install my kernel on BSD:

    vi MYKERNEL
    cd /usr/src
    make buildkernel && make installkernel

    phew! I'm done.

  76. Custom kernels for custom systems. by FreeLinux · · Score: 2, Informative

    Custom kernels are necessary because Linux is a monolithic kernel. That means that in order to use certain hardware or other features, the drivers have to reside in the kernel itself.

    Now, lets suppose that you just got the latest gee wiz device and you want to use it on your Linux box. You hook your "flux capacitor" up to the firewire port and nothing happens. Why, because either a firewire or a flux capacitor driver (or both) is required and the kernel doesn't have it installed. This means that you must rebuild the kernel with the appropriate driver in order for your new flux capacitor to work.

    Now, some may argue that the kernels should be pre-built with all the drivers and everything. Indeed, many distros do something like this for their stock kernels. But that still doesn't account for hardware that is yet to be invented. It also causes the kernel to grow into a giant that gives the term monolithic a whole new meaning. This large size means slow boot times and slower overall performance, in some cases. Surely, you don't want that?

    Indeed, many people want to trim the size of their kernel to an absolute minimum to improve the performance of their system, not to mention the security enhancement of removing unneccessary services. Do you really need HAM radio support? Most people don't, so why would most people want the HAM drivers loaded in their kernel? Do you need NTFS file system support, as I do? Probably not, especially with write access, so why include it? But at the same time, why prevent me from using it, as I need to?

    Even without the above reasons requiring the custom kernel, there is one more reason in favor of it. Part of the whole idea behind Linux is the ability to modify and customize it to your heart's content. That means if you want to modify your kernel you can. And this project will make such modifications easier than in the past. If you don't want to bother with customizing your kernel, then use the latest stock kernel from a major distribution, which will have mostly everything included. But, if it is slow or your flux capacitor isn't supported, you'll just have to wait and hope that the distro includes the support in its next release.

    1. Re:Custom kernels for custom systems. by bhsx · · Score: 2

      Mostly correct; but the kernel is not necessarily monolithic. It CAN be; but every distribution I've used comes with a modular kernel, with most options compiled as modules which are loaded and unloaded as needed. This is also how most people compile their kernels. It is very possible to compile them monolithically; but then you're guaranteeing that you'll need a recompile with any hardware changes.

      --
      put the what in the where?
    2. Re:Custom kernels for custom systems. by Anonymous Coward · · Score: 0

      Even the modular kernels are monolithic. Below monolithic kernels are microkernels and those require separation of kernel subsystems, not just drivers from the kernel.

    3. Re:Custom kernels for custom systems. by Nailer · · Score: 2

      You hook your "flux capacitor" up to the firewire port and nothing happens. Why, because either a firewire or a flux capacitor driver (or both) is required and the kernel doesn't have it installed. This means that you must rebuild the kernel with the appropriate driver in order for your new flux capacitor to work.

      No it does not. It means, in this case, you must rebuild a module. Rebuilding an entire kernel for this purcpose is a waste of time and energy.

      But realistically, you'd already have the module available - to follow your own example, user A might not use NTFS support, but having the driver available as a module doesn't harm his own system - the kernel isn't bigger because of it. It also allows user B to mount his Windows disk easily with only a slight overhead from loading the driver as a module rather than having it compile into the kernel. The solution is more modularity.

    4. Re:Custom kernels for custom systems. by Eil · · Score: 2


      Er, the term "monolithic," when used in references to kernels, has nothing to do with loadable modules. Linux *is* a monolithic kernel, period, because all of its code runs at the kernel level.

      Contrast with microkernels which only consist of the bare minimum of code needed to manage the OS. Most of the drivers (network, disk, maybe even some memory stuff) live outside of the main kernel and execute in user space, similar to any other process only with slighly elevated priority and access to hardware.

      The type of loadable modules implemented in the Linux kernel gives it one of the primary advantages of a microkernel--the ability to load and remove *certain* drivers at run-time--but it doesn't change the fact that it's still monolithic.

      (Corrections, clarification appreciated. I'm not a kernel guru.)

  77. Linus is just a celebrity figurehead by Anonymous Coward · · Score: 0

    Linus is now irrelevent. So is Alan Cox, Rik Van Riel, and most other key Linux kernel developers. All the real progress being made on the Linux front is being done on vendor maintained trees and side projects. Linus' tree has been stagnant for a while now and isn't going anywhere any time soon.

    I'm sorry, but that's just the way it is. Linux has become a much bigger system than one person (even a brilliant person) can micromanage. The members of the kernel "leadership" (for lack of a better word) all have become too egotistical and territorial to be team players. The ad hoc development processes that they cling to like gospel don't scale to development tasks of any significant size and now the process has pretty much broken down entirely. Few people even want to contribute to the main tree anymore. It's dead. Get over it.

  78. What's wrong with that last? by Ungrounded+Lightning · · Score: 4, Insightful

    And some folks questioned his motivation for getting this grandiose project into the kernel - was it just to help out, or was it primarily to establish additional hacker reputation for Eric? I'd be willing to give him the benefit of the doubt on this - he did the work.

    What's wrong with being motivated by hacker reputaion points? Isn't that what was supposed to replace money in the open source motivational system?

    ... was it just to help out, ...

    So an open source developer is evil unless he's motivated solely by altruism?

    (That humming sound you hear is the beat between the spin rates of Ayn Rand and Friedrich Hayek.)

    C'mon, Bruce. You know better than that.

    Regardless of how much we want to help out humanity and all that, SOME of us aren't the leisure class - with old money, idle time, and an indoctrination in the obligations of nobility to give us internal satisfaction when we do something "just to help out" the benighted masses of the common man. Some of us ARE those commoners, with a family, a mortgage, and (if we haven't been laid off in the latest recession) a paycheck that is all that stands between using a shopping cart for groceries and using it for a mobile home.

    If we're to contribute time and effort to the open-source codebase we need a way to keep that paycheck coming. Like "reputation points" to put on a resume, to find work the next time the current project is over or the current company goes belly-up.

    Maybe Eric doesn't need any more points. But let's not have a big name flaming him for maybe wanting some - and thus convince thousands of onlookers that working open source is a good way to get a BAD rep, so they'd be better off getting that MCSE instead.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:What's wrong with that last? by Bruce+Perens · · Score: 2
      Well, this time I'm just reporting the news, and don't endorse the feeling I'm reporting. So, I'm not going to take this one any farther.

      Bruce

    2. Re:What's wrong with that last? by Anonymous Coward · · Score: 0

      Don't worry, those of us in the silent majority agree with you, Bruce.

  79. Suckit LeepSheets by Anonymous Coward · · Score: 0

    Works the same in Linux.

  80. Re:The Developers Arent Always Right & Politic by Anonymous Coward · · Score: 0

    You have moved into a dark place
    It is pitch black. You are likely to be eaten by a penguin.

  81. Non commercial doesn't imply unprofessional. by aXi · · Score: 0

    Don't forget that a lot of Linux programmers are professionals who "donate" their spare time to linux programming. Also a lot of them are doing the coding in their free time at school. And yet others get paid by big companies to do the work.

    It seems like the only non-linux-professionals are those who whould make such a remark about linux.

  82. Literally = Escape Character? by jellybear · · Score: 1

    On the other hand, people use the word "like" to indicate that a simile or metaphor is coming up, sort of like a substitution marker.

    So, for 5pts, trace the output of the following sentence:

    "I'm, like, literally dying of thirst."

  83. This isn't the real problem anyway by drinkypoo · · Score: 2
    xconfig is good enough for me. The problem is that dependencies between drivers aren't tracked (at least not well) so it is easy to turn on an option and break your kernel. Solve THAT problem and you win a cookie; Fail to solve it and you're just painting pretty pictures.

    In addition, requiring the Qt or GTK libraries is ridiculous. I don't want to link to anything that large. If you can't get it done with Xaw (or something similarly small) I'm not interested in your stupid config tool. I'd rather use something fast and ncurses-based.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:This isn't the real problem anyway by Anonymous Coward · · Score: 0

      Too bad that almost everything is fast on modern computers.

      Perhaps you need to get one.

    2. Re:This isn't the real problem anyway by Russ+Nelson · · Score: 2

      The problem is that dependencies between drivers aren't tracked (at least not well) so it is easy to turn on an option and break your kernel. Solve THAT problem and you win a cookie;

      Eric solved that problem with CML2, and all he got was flamed. I think there's a whole pile of people who should apologize to Eric, starting with Linus.
      -russ

      --
      Don't piss off The Angry Economist
  84. And what game might that have been? by Afrosheen · · Score: 2

    Eric was playing games and his solution was technically superior. Done deal.

    Lemme guess... ...Eric's Solitaire? (bu dum-pssssh)

    Thank you, I'll be here all week. Remember to tip your waittress.

  85. fuck you cunt. by Anonymous Coward · · Score: 0

    get a life.

    1. Re:fuck you cunt. by Anonymous Coward · · Score: 0

      See, that's actually ironic, that someone like you who has nothing better to do than troll /. would tell someone else to get a life.

  86. irrelevant by Anonymous Coward · · Score: 0

    Just run FreeBSD and you won't have any of these linux problems.

  87. This is a great idea, but it's not that new. by Trogre · · Score: 2, Interesting

    It looks surprisingly similar to the KDE Kernel Configurator.

    Control Center->System->Linux Kernel Configurator

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  88. Re:Don't you know what hardware you got in your co by Perdo · · Score: 2

    Exactly!

    How is it that Knoppix can get it so right and the major distros are a hash?

    Of my 7 personal computers:

    Knoppix boots them all, with all their devises functioning.

    Mandrake 8.2 fails to initialize USB on 3 of them.
    Redhat 7.3 fails to initialize the video on 2 of them (and therefore fails to start X)
    Debian 3.0r0 fails to intialize a standard PS/2 mouse on one and ethernet cards on 4.
    SUSE 8.0 does not recognize the second CPU in a dual processor machine!?

    I just don't understand.

    --

    If voting were effective, it would be illegal by now.

  89. Just remember by xenocide2 · · Score: 2

    Just remember that ESR was the one who wrote about the reputation and the like to begin with, in addition to the rules of social interaction in the OSS world. He didn't write them, he wrote about them. Whether he's correct on all these points is another matter. It may be that hackers write for reputation but it seems that the appearance of writing for reputation is bad.

    --
    I Browse at +4 Flamebait

    Open Source Sysadmin

  90. Disagree by einhverfr · · Score: 2

    If it ain't broke, there is no reason not to try to improve it, IMHO.

    However, the changes usually should be incrimental rather than all-at-once. This forces better code, and better systems, and all-round better products.

    --

    LedgerSMB: Open source Accounting/ERP
  91. Looks more complicated and is the wrong approach by hattig · · Score: 2


    The screenshots look more complicated to me - just a horrible GUI interface with a single giant tree list. How horrible.

    The sad thing is that you should need to recompile the kernel to add support for various bits of hardware. What is wrong with using drivers that are not compiled into the kernel, and being able to add them at runtime?

    I can understand recompiling the kernel for certain reasons:

    1) Want to compile for your architecture to get the best performance

    2) Want to make use of a kernel patch, or non-standard kernel feature

    The monolithism of the Linux kernel is primitive. It should be fully modular - a small kernel core with additional services for various aspects of the kernel, and with full runtime driver addition and removal, etc. This will become even more necessary with systems that need 99.99% uptime using hot-swap PCI and the like.

    The kernel configuration should basically be an automated process - check how many processors you have, optimise for that processor type, etc. Compile all hardware support as drivers/modules. Install.

  92. a fast machine by oliverthered · · Score: 1

    A personal kernel will give you a 'faster' machine, especially when you take into account SMP, low latency, pre-emptive kernel, the extra few MB that doesn't have to be paged to your slowwwww HDDD, page faults that occure when you have to goto a module.

    You don't have to touch the configs, it's automated, that's the point!

    --
    thank God the internet isn't a human right.
  93. compiled-in drivers by oliverthered · · Score: 1

    Well even if all the drivers are modular (a good thing!) your still left with am I a server or am I a workstation options. Descktop kernels require a quick response(10 milliseconds tops) but this may reduce the performance under server type coditions were a few hunderd millisecond responce is good enough.

    --
    thank God the internet isn't a human right.
  94. And this is why the Linux community struggles.. by Anonymous Coward · · Score: 0

    Because even the most notable contributors seem to be anal retentive bastards who bicker and squabble like little children. Where the hell is the motivation to work on projects, when your fellow coders think its more fun to make personal attacks on you rather than working to constructively develop systems and programs? I remeber seeing such attitudes and opinions when Hans Reiser wanted to get this journaling file system included in the kernel..

    Maybe thats where the majority of the nerdy end users get this impression that they are somehow superior to users of 'inferior operating systems' such as Windows.. so much so that they adopt this eliteist attitude.

    It pisses me off - I encounter it all the time, and it is in my opinion one of the biggest weaknesses of the community.

  95. Re:Don't you know what hardware you got in your co by powerlinekid · · Score: 1

    Mandrake does the same. Redhat probably does too.

    --

    can't sleep slashdot will eat me
  96. Four Hours? by cortense · · Score: 1
    It took you 4 hours to get your printer working?

    I've spent 4 years, and mine still doesn't work!

  97. Eric's motivation for doing CML2 and defying Linus by iskander · · Score: 2
    There were a few times when Linus made it very clear what he wanted changed and ESR simply didn't fix it, it was as if he didn't even hear it; look at the threads in the kernel archive. I don't know what ESR's motivation was but he made it look a little corrupt.

    I think I may have found the answer in the following excerpt from his World Domination guest editorial on Linux Journal:

    Of course, articles like this are part of that game. We hackers are a playful bunch; we'll hack anything, including language, if it looks like fun (thus our tropism for puns). Deep down, we like confusing people who are stuffier and less mentally agile than we are, especially when they're bosses. There's a little bit of the mad scientist in all hackers, ready to discombobulate the world and flip authority the finger--especially if we can do it with snazzy special effects.

    I can't help wondering whether, in this case, Linus and Jeff are "the bosses"; indeed, stuff like pretty pictures and theorem provers and various other kitchen sinks associated with CML2 qualify (amply) as those "snazzy special effects" of which he is so fond.

    Now, love him or hate him, Eric is not going anywhere, even after getting booed off a very important stage. And in light of his, um, staying power and in consideration of the CML2 affair, it should be of some comfort to his detractors that at least Eric the Rich Guy hasn't lost his hackitude and keeps producing worthwhile stuff. When Eric first threatened to quit politics, I looked forward to the return of Eric the Hacker and the retirement of Eric the Politician ; alas, half an Eric must, ipso facto, half not be, and I'll take a whole Eric over half an Eric any day, thank you very much.

  98. Re:Don't you know what hardware you got in your co by AvitarX · · Score: 1

    So more then just knoppix can autodetect beautifully and seamlessly, great.
    Why can't I do make autoconfig for my kernel then?
    That would be the totaqlly kick as thing to have happen IMHO. The fact that more then just knoppix got this down tells me it should be a trivial task.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  99. Re:Looks more complicated and is the wrong approac by DaCool42 · · Score: 1

    Ummmm......the linux kernel _IS_ modular if you compile everything as modules. What do you think many distributions like redhat or mandrake are doing? You can quite successfully use their percompiled kernels on almost any system.

    The whole point of kernel configuration is that you can actually not compile what you don't need and you can make a kernel perfectly suited to your system. Without modules if you don't have a reason for them. If you never change anything, why would you need to have module supporting sitting around in your kernel?

    --

    ----
    All of whose base are belong to the what-now?
  100. but they don't work automatically by Trepidity · · Score: 2

    At least with Debian, the precompiled kernel doesn't automatically have CD burning properly set up. You have to load the required modules and pass them the proper arguments, as I described in my previous post (and yes, I got the requisite steps from the CD-Writing-HOWTO). In Windows, it detects the hardware and sets it up for you.

    1. Re:but they don't work automatically by Anonymous Coward · · Score: 0

      Perhaps you should take a look at mandrake instead?

      (I have nothing against debian, but the guy is obviously complaining that debian doesn't have what mandrake (AFAIK) has)

    2. Re:but they don't work automatically by kasperd · · Score: 2

      In that case, you are on the wrong thread. This discussion is about the kernel configuration utility. This is not a utility any newbie should ever touch. The people at Debian, Mandrake, Redhat, and all the others could be going to use this utility to configure the kernel for their distributions. But this is in no way related to the hardware detection and setup you are talking about.

      The installation and configuration utilities you are talking about are developed mostly by the individual distributors, and is a completely different issue.

      If a newbie want to compile his own kernel, he should use the .config file that came with his distribution and then just use "make oldconfig". A graphical version of oldconfig, that provides help about the options and sane defaults, is the best we can do to help newbies that insist on compiling their own kernels.

      Except from this the newbies should only use the kernel configuration utility if they know exactly what option they need to change.

      --

      Do you care about the security of your wireless mouse?
  101. re: kratia = power by pyrrho · · Score: 1

    kratos:

    I think that it also is a specific kind of power. Supported credibly if not completely enough by it's use as shown in in this document which I found when googling for a little support for my hypothesis. What kind of power it is colors it's relationship with the other word part. I believe it's an oppressive sort of power, essentially the military power required to win and the spoils that are the reward (power over the people, to tax and control their economy. Taken this way Democracy has a different meaning, probably justifiable but incomplete. The people should have power over the government but should they take the position with regard to it that historically military governments do? Similarly if people have power of the "government", this is "govern" the correct root for that word? If the intent is to free the people to govern themselves, and free the economy, "democracy" is possibly the wrong approach.

    Philosophy is stored in these terms. Breaking these terms open, or comparatively considering the distinctions between irony and coincidence, ironic coincidence or literal metaphors. I post this to you because of your clear like for making closer study of terms (I paused to grok your distinction between irony and coincidence), and because you also have a pragmatists view of language, a relatively rare combination. It allows one to look for the meaning of words as a philosophist rather than as a grammarian, trying to impose as RULES what are merely interesting philological patterns.

    --

    -pyrrho

  102. Re:The Developers Arent Always Right & Politic by nathanh · · Score: 2
    Example: The ggi project wanted to provide a kernel abstraction layer for video hardware in the same manner such abstractions are presented for everything else, from your ethernet adapter to your system's RAM and hard drive. Linus thought the idea sucked, then ended up doing a "poor man's" version of frame buffer support instead. How much better things would have been if the original vision of the GGI folks had been realized and supported we'll never know.

    I don't agree with your interpretation for why the GGI failed.

    The way I saw it, the GGI developers had very grand ideas but insufficient time/resources. In the end, the GGI lost out because FB and the DRI offered something tangible with a reduced complexity. Maybe you could argue that GGI offered more but that's just confirmation of the classic 80/20 rule.

  103. why XFS is not in the kernel. by Anonymous Coward · · Score: 0

    The reason behind XFS's non-acceptance: the XFS source code is an ugly non-Linux beast that refuses to talk the 'Linux VM/VFS speak', for the sake of keeping a common XFS core between Irix and Linux.
    If SGI really wanted XFS to be accepted into the kernel then they should clean it up and make it a Linux filesystem - instead of hacking an additional layer into Linux to have Irix APIs internally....

  104. It should be based on by Anonymous Coward · · Score: 0

    Qt. Otherwise it's just a waste of time.

  105. Re:Linux is oft.. ..Package manager by 3Ddgg · · Score: 1

    I've finally got to the site, and seen something like what I was talking about, and it's not scripted so it could be quite fast, don't you think? WOW

    Sorry :-)

    --
    No warranty of any kind is offered as to the quality of this post.
  106. Question about Kernel Config and Compilation by Why+Should+I · · Score: 1

    I run two machines at home, one which I compile everything for and test new kernels on, and one that I do dev and personal work one.

    The dev/personal machine runs redhat 7.2 and uses up2date (i.e. redhat rpm's) to update all software on the system. Its the easiest way for me to have up to date, stable apps with which to run my system and get my work done. The down side is, I cant compile any extras if I want to change the kernel.

    That is a limitation I accept as a consequence of my wanting an easily updatable stable system. And if I need to run anything from compile I use my other machine. Here is the problem though....

    Both linux machines dual boot into win2k (I use for games). How do I mount the ntfs partition with my redhat box? I need to re-compile kernel with the ntfs read-only driver to beable to mount it, but that would mean I don't get to use the redhat up2date to update my kernel.

    An answer to that one would really make me happy in "userland" on my red hat machine.

  107. Re:tip for web sites that run MSSQL 2000. by Anonymous Coward · · Score: 0

    Yeah, it wouldn't even be up:-)

  108. linux 2.5.31,32,33 borked by dgp · · Score: 2

    Ive never had as much trouble with a kernel build as i have had since 2.5.31.

    the IRDA stuff just wont compile, the orinoco driver wont compiler either. ive never seen the kernel not compile like this. Im having to take out module after module to get something that builds.

    Don

  109. Re:Don't you know what hardware you got in your co by powerlinekid · · Score: 2

    Actually all you might have to do is boot up the default kernel which in most systems is full of just about every single modules and run a script that takes an lsmod and generates a config file out of it. I really can't see why this is so damn difficult, you'd think someone would of done this by now. I'm sure this isn't the right way to go about it but... hey... what do you want from a slashdot comment ;).

    --

    can't sleep slashdot will eat me
  110. Re:Don't you know what hardware you got in your co by oliverthered · · Score: 1

    Or look in /proc and look-up the device ID's in a database.

    --
    thank God the internet isn't a human right.
  111. Graphical??? by Anonymous Coward · · Score: 0

    How do I use that over a serial terminal server in my server farm? Duh!

  112. I'm with ya' on this one... literally! by CreamsicleSeventeen · · Score: 1
    I think there's even more to abusing the word "literally" than giving it the opposite meaning. People who talk like that also mean some form of "very", or worse, a kind of, "Take me seriously this time because I reeaaalllly mean it!"

    Oddly, even though misuse of "literally" irritates the living f### out of me, I think it should have the meaning people end up giving it when they (mis)use it to add emphasis. For example:

    "That was so funny I literally shit myself."

    "How disgusting. You will go home and change your underwear. Right?"

    "No I won't you cyborg. There isn't any poop in my pants. It was just an expression. I meant that in a literary way!"

  113. OT: Your .sig by turgid · · Score: 1

    :-) Darn lameness filter!

  114. lftp ftp.us.kernel.org/pub/linux/kernel/v2.4 by CreamsicleSeventeen · · Score: 1

    ls | grep patch
    ...
    patch-2.4.19.bz2
    patch-2.4.19.bz2.sign
    patch-2.4.19.gz
    patch-2.4.19.gz.sign
    ...

    1. Re:lftp ftp.us.kernel.org/pub/linux/kernel/v2.4 by dd301 · · Score: 1

      Must be my local mirror then. Thanks for the info.

  115. devfs already does this (was:Linux is often mis..) by fizbin · · Score: 2

    Whether I have the ide-scsi module installed or just the ide-cd module, my CDs are accessible at /dev/cdroms/cdrom0
    and /dev/cdroms/cdrom1

    Which drive is which does indeed switch depending on the order in which I choose to load the modules, but anyone who's installed a removable disk driver on windows will tell you that all the disks there jump around too. (e.g.: my wife installed the driver for a compactflash reader on her windows 98 machine, and the CD rom was moved from D: to E: to make room for the compactflash device. Later, we had to re-install it and D: and E: swapped places again)

    Anyone saying that linux requires you to use the scsi names hasn't tried devfs lately.

  116. tell it like it is by Anonymous Coward · · Score: 0

    From: Rik van Riel
    Subject: Re: Disgusted with kbuild developers
    Date: Fri Feb 15 2002 - 12:02:21 EST

    This makes me wonder whether Eric works in a cathedral or in an ivory tower ...

    Rik

  117. Re:The Developers Arent Always Right & Politic by Bloater · · Score: 2, Informative

    > GGI tried to do too much and it abstracted too far.

    KGI (the code to go into the kernel) was just a bit more sophisticated than DRI. Under KGI, the mode switching would be provided by the kernel so that you never lost all use of your console because of X crashing, text blitting routines would be included in the kernel to support Linux's in kernel terminal, for hardware with an accel engine an interface is provided for the driver to tell userspace what accel methods are available. It is as simple as that. KGI was never "acceleration in the kernel" as was shouted about a lot, it was "operations that can render your console or system bus unusable are allowed with care taken to ensure that nothing bad can happen while maintaining DRI level performance".

    For matrox (a good, stable accel interface), userspace could query what interface is available and the driver might respond "matrox mmap interface" since it is safe to mmap the accel registers from userspace. If there were any code to operate the accel registers they would be in a badly designed driver (or a driver for badly designed hardware), and nothing to do with KGI *at* *all*.

    KGI is the minimum necessary to safely support high performance graphics from userspace and that's not a lot.

  118. Re:The Developers Arent Always Right & Politic by Russ+Nelson · · Score: 2

    ESR's refusal to update the patches to handle changes Linus made to the core code.

    Sorry, you don't have permission to rewrite history. Eric updated his patches, and updated and updated, all the while waiting for Linus to suck in CML2 *like Linus promised*. Finally, he got burned out, and started to publicly wonder WTF was going on. All this time he was being roundly, soundly, and viciously abused by various people on the LKML.

    All of which goes to show that Linus's promises are worth nothing. But we all knew that, didn't we?

    --
    Don't piss off The Angry Economist
  119. You still have to compile it... by mmol_6453 · · Score: 2

    Whether you compile code as a module or into the kernel, what difference does it make? You still have to compile the code, so it still takes the same amount of time t ocompile.

    --
    What's this Submit thingy do?
    1. Re:You still have to compile it... by Anonymous Coward · · Score: 0

      It should be quicker to compile as a module, but it's even quicker still not to compile it at all.

  120. Oh, you mean my CONFIG patch? by Russ+Nelson · · Score: 2

    Like how do you know the configuation options used on the kernel you are running?

    You just cat /proc/config, and it spits out all the CONFIG_* options that were defined when the kernel was compiled. I sent that patch to Linus years ago.
    -russ

    --
    Don't piss off The Angry Economist
  121. Re:The Developers Arent Always Right & Politic by gmack · · Score: 2

    He instisted in keeping in synch with both the stable and unstable versions and the killer was here followed by Linus making the changes and ESR never updating to match.

  122. cd /boot; echo vmlinuz by Anonymous Coward · · Score: 0

    cowabunga - shazzzam..

  123. Liar. by jotaeleemeese · · Score: 1

    What do you do during that vi session?

    Linux kernel configuration tools make easier to make those same changes.

    And if you are a masochist you can also use vi.

    --
    IANAL but write like a drunk one.
  124. the carpenter song by Anonymous Coward · · Score: 0

    if I had a magic hammer,
    that couldn't smash my thumb.
    I'd hammer down everything,
    till my arm was numb.

    But even magic hammers
    when held by a stupid dumbass
    will be pushed beyond it's limits
    and one's thumb it will soon blast

    So when playing with the kernel
    and you're pulling out your hair
    it's time to hire a carpenter
    and pay him what is fair

  125. Re:devfs already does this. by 3Ddgg · · Score: 1

    Yeah I've installed windows systems before and its really not up to scratch. Cheers, I'll check out devfs.

    however the issues with the kernel config and cd burners still seems to apply

    --
    No warranty of any kind is offered as to the quality of this post.
  126. Re: kratia = power by _ganja_ · · Score: 2

    I hope you read this as the topic is a few days old. You managed to pick up on something that I am very interested in, language & how it got the way it is. If only I had more time (and intellgence).

    "Philosophy is stored in these terms."

    I couldn't agree more, there seem to be "clues" or code regarding something scatered about in language, especially root words and they seem to link in to old myths & legends.

    I am not nearly bright enough to express this very eloquently nor to figure it out but language seems to hold a lot more value than just basic communication and something we take for granted.

    If only the birds could talk.

    Also, time for a new .sig :-)

    --

    A journey of a thousand miles starts with a brutal anal raping at airport security

  127. Re: kratia = power by pyrrho · · Score: 1

    all the battles in philosophy, by which I mean not the academic ones but the real battles that go on within cultures and when they collide, are all stored, I believe, in the terms and phrases of language.

    I think it's fair to say that philosophers mostly mine language for knowledge, as special kinds of philologists. As for the additional part, the creativity, it's mostly aimed in the direction of creating new words and new understandings for them, and is therefore just another part of the same process.

    I hope to talk with you about this more in the future at some point.

    Cheers.

    --

    -pyrrho

  128. Linux Future by Anonymous Coward · · Score: 0

    Several days ago, I read an old news article about the Shuttle Programming Group's high quality and ultra-high reliability.

    Linux has to begin to emulate this model to survive! How many super-programmers are out there versus newbie programmers that have brilliant ideas. Linux has to build a structure that can capture each of those nugggets and expand on them or teach the newbies to implement them.

    There needs to be an easier system to programming so that anyone can help out in the smallest way. These are very different tools than the Pros are using, but only the pros can build them.

    Also, Knowladge about process, setup, and troubleshooting needs to be captured and put in a form for anyone to contribute and everyone to benifit. I envision a system where I can experiment with an install and the next guy can benifit immeditely from my findings. Gentoo to the next level!

    all done