Follow Slashdot stories on Twitter

 


Forgot your password?
Close
typodupeerror
×
Linux Software

Linux Kernel 2.3.41 99

Posted by CmdrTaco from the download-compile-reboot-repeat dept.
sdriver writes "For those of us who enjoy *panic*, *oops*, and suddenly seeing their video BIOS... the newest version is out! Be the first on your block to submit a new patch! ;) " If you don't know where to get it, you probably should stick to your warm and cuddly 2.2.x kernel *grin*. Now outta my way, I wanna crash my laptop!
This discussion has been archived. No new comments can be posted.

Linux kernel 2.3.41 More

Linux kernel 2.3.41

Comments Filter:
  • Well why don't we also post each new FreeBSD 4.0-CURRENT snapshot and each new NetBSD-Current snapshot and each new OpenBSD-Current snapshot to Slashdot, too? It's pretty much the same thing.
  • No, It made 130+ (I had 131 installed). The last batch just were sprayed out lik wildfire :-)
  • Um... its fake. Doesn't exist. Kidding. Joke. Ha ha.
  • they each have there place...

  • This is because the newer kernels are using more and more cutting-edge technologies, like USB, AGP, and stuff (and oh man, it seems there are much more advances in the 2.3.xx tree than the 2.1.xx one, and we're only at the patch level 41, not 120-and-some like 2.1.xx) - and we need more and more testers to test this bleeding new code.

    I just saw that 2.3.41 has a new CPU listed in, "K6/II/II" (typo here), now I'd like to know if it'll speed up my K6-2 by a factor of 5 :P

    I myself don't have this new stuff (USB, FireWire, I2O, I2C), but since USB and AGP support support is the critical part of the 2.3.xx branch, we need ppl to test this. Now if nVidia can release drivers that supports DRI..

  • I've been using LVM [msede.com] for ages now and I think it's great. Works pretty much like HPUX's LVM but I don't know how that compares to AIX as i've never used it!
  • Oh oh its stable.. I am using intellimouse explorer and it works just fine

    no problems with any USB

  • Undoing moderation... (Score:1)

    by Anonymous Coward
    Marked something as funny and then realized that it would be flamebait to most other people in here.

  • Ditto if you mount proc in /dev. But most people don't. Just like most people don't use devfs (yet).
    Not that I'm saying devfs is bad or anything, I want to keep as far away from that holy war as Ican.

  • Agreed. (Score:1)

    by cmc ( 44956 )
    That's really what I meant. Each devel kernel release isn't newsworthy so much as perhaps Debian releasing a new version of its distribution or FreeBSD 3.4 being released. Those are actual release events, rather than snapshots (which is what Linux development kernel version bumps really are analogous to).
  • I love my MS intellimouse explorer. it is god. now if x would only get the other two buttons working as something. Hell, it even works in USB mode.

    pest
  • I've downloaded plenty of "stable" kernels before, so I figured, what the heck, I'll try it...

    Well, after a minor bit of fiddling to get it configured and built, I fired it up. No obvious problems. I did see a couple of interesting new things, like NFSv3.

    Then I checked my RealPlayer. I've been fighting a problem for a while now, ever since I upgraded my MB to one with a built in ESS Solo 1 sound subsystem. All other sounds play fine (Quake, etc), but RealPlayer always screwed up the sample rates. Everything sounded like Alvin and the Chipmunks.

    So, I tried it with the 2.3.41 kernel, and it works now! I haven't read all the release documentation, but there must have been fixes to the ESS drivers.

    Obviously, I'm taking my life and data in my hands, but I just wanted to say that there ARE advantages to being on the cuting edge.

    Just make sure you have good backups...

  • I guess my facetiousness was lost on the moderator. Oh, well...
  • That is one of the things I like about Mandrake 7.0.
    "Logic . . . merely enables one to be wrong with authority"

  • I have recently been required to describe what the heck a "kerenl" is to some people in close relation to myself. Of course there is the obvious for us geeks, but there are two other possible interpretations that I can think of:

    1. Kernel as a rank in the military -- Why would I want one of them on my computer? And I guess the military has very high expectations of these kernels, because they come out with new kernels every couple of weeks. For some reason, some higher-ranking officers don't replace their kernels that often; maybe they like them. But the new kernels have lots of new personality features, and they are even more tough on those below them. There even development kernels, the kernels who have not yet completed their training but are available for use by those of higher rank who might want to try out some of the new features before everyone else, but there is the possability of an occasional slip-up, possibly causing an "oops!" or even a "panic". Worse yet, these development kernels can cause corruption in the system below them. Some kernels, for some officers, have run for a very long time in some of the military systems, and I am very suprised that they don't get tired and fall to the ground. I guess that's the problem withh kernels in the Bill Branch of the military, but the Open Source troops seem to have little problem with this. Well the Open Source commanding officers get to have an in-depth look at how their kernels are trained, so it is possible that this allows the officers at higher ranks to make better decisions about them.
    2. Corn kernels -- Yeah, that fits on my hard drive. I spend endless hours in front of my computer monitor^D^D^D^D^D^Dagnifying glass, examining the various ridges and structures on and in the kernel. I occasionally tap at the kernel to see how the structure responds to stresses. It seems to occupy a lot of people for many hours at a time examining and prodding at these kernels. Sometimes, at lower magnification, the surface of the kernel begins to form the shapes of letters, when viewed by the trained eye. Untrained people are cluless. At higher magnifications pictures sometimes become visible, appearing similar to pictures found in everyday life. Through careful prodding through the prodboard one is sometimes able to coax these pictures into changing. The "mouse" is a fairly new addition to the interface used to study these kernels; it is unknown to us how exactly it influences the kernel without eating it. Micros kernels have always showed a lot of detail initially, but viewing the kernel at a higher magnification showed minute impurities that would cause the kernel to split apart relatively soon after the investigation began. The kernel has remained much the same despite many advances in the apparent detail and complexity as viewed at low magnification. Macintosh kernels started out rathar bland-looking, but they contained many useful features from the beginning that allowed studying to be significantly more efficient. However, until recently, the smaller details of the Macintosh kernels were almost as bad as the Micros kernels. In recent years Macintosh kernels have developed a much more detailed structure at any magnification, and as an added bonus when replacing kernels, some have even begun to taste good (Yum.) Linukernels are regularly updated, but older kernels are still so interesting to look at that people have kept them around for a long time. The development kernels sometimes fall apart due to structural problems, but in general they have offered much more detail. People staring at Linukernels are generally happy with how stable their kernels are and how nice it is to be able to know how the kernels were made. Some people tailor their Linukernels to their specific tastes, something which is usually not possible for investigators of other kernels. The report must be cut short here becuase we are still investigating the role of the "printer" in the kernel investigations. Preliminary findings indicate that often the printer is used to capture a view of the kernel to share with others, but often the output of the printer is much different than the view on the magnifying glass. This may be attributed to a special scanning structure that is able to examine different parts of the kernel and print the results. That is all the information we have at this time.

    And we make Beowulf clusters out of these things?

  • So how is this more important than 2.1-2.2 or any other devel-to-stable releases? (Yeah I know, just wanted to bring up a discussion...)

    You moderators sure don't know what's flamebait. Simple reason: No flames. Hah.

    Ken

  • Okay, never mind, this is too deep to start any discussion. I gotta watch how many times I click in the reply lists :-).

  • This is a joke. This is only a joke. Had this been an actual kernel patch, I probably would have thought about the device creation/usage issue for more than 2 seconds.

    Yep, the admin creates /dev entries, kernel modules and the kernel create /proc entries. Big hairy deal. ;-)

  • ``Unstable''? (Score:3)

    by David A. Madore ( 30444 ) on Saturday January 29, 2000 @06:33AM (#1324501) Homepage

    What exactly does ``unstable'' mean? Or, more accurately, what does ``stable'' mean? The 2.2.13 and 2.2.14 kernels (supposedly ``stable'') have rather nasty inode leaks. And 2.2.11 and 2.2.12 had a memory leak (which is why SGI based their SGI Linux 1.1 [sgi.com] kernel patch on 2.2.10). Hmm... Looks like stability ``leaves somewhat do be desired''.

    Featurefulness perhaps? Well, one patch I find extremely useful is the ext3 filesystem. (Now that seems stable enough, despite the frightening version number: 0.0.2c) But Stephen Tweedie hasn't finished porting that to 2.3.x. Another useful patch is the international crypto patch, and that doesn't come for 2.3.x... Or the Openwall security patch [openwall.com]: ditto. Hmm... Looks like I'll stick to 2.2.x for some time. (And, no, it isn't exactly ``warm and cozy''.)

    I'd like to try the 2.3.x kernels by using User mode Linux [sourceforge.net], but so far the only thing I've got from that is a core dump.

    Sigh...

  • Hmmm, well done mr moderator.
    Give yourself a big pat on the back.
    Then get round to finishing that reading course.
  • Uhm, yeah, my mistake. 132 was the last one
    before the pre-patches.

  • Re:Unstable warning (Score:3)

    by Krakken ( 5124 ) <[nekkark] [at] [gmail.com]> on Saturday January 29, 2000 @06:43AM (#1324504)
    I've been running dev kernels for 2 years now and have never had to hack 'real C'. Yes things get broken, but I watch the linux-kernel mailing list and submit a bug report if I can't find the answer there. Some times its not the code thats broken, but new undocumented proceedures for setup. I test and report, and get a jump new setups. With lilo setup to boot multi versions of the kernel, I can fall back if things are badley broken.

    If you can test, do! We all benifit in the end.


    Krakken
  • Due to the generious coding of Greg and Co at Visor Linux USB project [sourceforge.net], anyone who owns A handspring visor would be able to sync with the USB cradle without having to buy a serial cradle.

    Enjoy.
    --

  • If you're into hacking the linux kernel you should join the kernel mailing list and hack away.

    If for some reason your hardware is not supported by the 2.2.* tree, go for it. Compilation and use are no different than earlier kernels for the most part. By all means be sane and keep an old kernel ready with lilo if something goes wrong, but don't be afraid just because it says developmental. I've been running the 2.3.* tree with xfree's pre4.0 tree for a while. Unstable certainly does not mean it doesn't work.

  • Lets see, a month is typically 30 days.
    A couple of months (2) is around 60 days.
    Many months (your words) I take it to be more than 60 days.

    Last I checked, win95a was hard coded to crash after about 49 days, due to a bug in the OS, of course it was rare to see a win95a machine work for more than 4 hours, so this bug was rarely seen. Stop trollin /. for bucks and go tell your boss to start innovating any time now.
  • As long as the user is aware that the "possible instability (or worse)" could be "filesystem trashing". I had 2.3.33 to 39 triggering BUG() calls in ext2, 2.3.40 had no such problem so far.

    I'm also trying to get ALSA 0.5.1 working but it keeps throwing up due to problems to allocate contiguous memory for DMA buffers. It doesn't seem to be kernel related however, since others have it working in the 30's and 40's. The CPiA (webcam II) video4linux driver doesn't like my system as well.

  • Reiser, maybe. ext3 is definitely 2.5 stuff.
  • USB is useful most times, but at others it loves to lock up my system while in windows when I have my combo USB-PS/2 keyboard and USB webcam plugged in at the same time. I'd love to see how it would hold up in Linux. It certainly does eliminate a lot of different connectors and cables and such.
  • hm i used 2.3 since 2.3.1 and tried out almost every version. never had a problem or a crash anyway. it's pretty stable for me. hope it will be same stable for our new server...
  • I think someone asked this already when another kernel release hit Slashdot, but:

    Is there a TODO list for the Linux Kernel?

    I know there's a lot of people who would like to contribute back to the linux community, but dont know where to start. I search all of the kernel mailinglist, but the only replies to questions like this are people responding with specific things that need help. I was more looking for a long bulleted list, preferable pusblished on kernelnotes.org or similar.
  • Uhm, I thought tulip drivers have been around the kernel since late 2.0.x...

    I really wouldn't worry about 2.3 support for it

  • You're right about the network load. You forgot about server load, though. Assuming the server is running a traditional ftpd (e.g. wu-ftpd), it forks a heavyweight process (as oppose to a lightweight proc == thread) and execs /usr/sbin/in.ftpd for every new ftp session. Again, this only happens once at startup. But don't forget that ftp is a very stateful protocol. Each invocation of the daemon uses a significant amount of RAM, and you have one process for each connection. (err, I guess apache has one proc per connection, but I don't think it touches much RAM after forking.) IMHO, it would be a Good Thing if ftp disappeared as a protocol for anonymous file transfers of a single file. (ftp has the advantage of being able to tell the client how the symlinks go, which is handy for mirroring Debian with its binary-all directory and binary-{alpha,i386,etc.} directories with symlinks back to binary-all for platform independent stuff, like docs and scripts.) Don't argue that FTP can restart transfers.
    HTTP can do that too. Read the man page for wget sometime :)

    In case you're wondering, there was a nice debate about this on our LUG mailing list. Take a look at the archives of the discussion:
    http://nslug.ns.ca/pipermail/nslug/19 99-June/thread.html (the discussion started with an ftp URI for metalab, and I suggested that http is better/faster
    #define X(x,y) x##y
  • No, the newer version support is NOT in kernel 2.3.x (at least as of 2.3.41). You can get updated drivers at ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/kern- 2.3 but I'm not sure when that will be merged into the main devel. branch of Linux.

    To clarify the one of the replies to your question - yes, Tulip support has been in the kernel for some time. However, support for card which require newer drivers has not been, at least until 2.2.14 (and the version included in 2.3.x is the old standard 0.89H).
  • async i/o code is now in the tcp/ip stack with a feature called i/o completion ports, ... Uh, I got the i/o completion ports info from a guy inside Microsoft.

    I/O Completion Ports were introduced in Windows NT 3.51, not Windows 2000.

  • Can you give me your email address so we can discuss this somewhere else than on /.? Else you can write to me.

  • People, be aware that this is an unstable, development kernel. Don't just use it for being "on the edge" if you're not willing to hack some real C.

  • for those who actually *don't* know where to get it (heh)...

    i am a link [kernel.org]
    --
    in a world of deceit, open your eyes

  • Anyone want to comment on how stable/usable USB support is right now?
  • When they started the 2.3 series, I can remember that every decided that we didn't care about the kernel releases, unless they were majorly important. CmdrTaco even said that they wouldn't be posted (IIRC). So why have they started again? This is Freshmeats job.

    Or can I start posting my release info to slashdot front page?

    Well, I released GNOME-Iconedit last week, so http://www.abdn.ac.uk/~u07ih/gnome-iconedit

    enjoy

  • AIX code in Linux (Score:4)

    by jamienk ( 62492 ) on Saturday January 29, 2000 @05:28AM (#1324537)
    I read here [linuxtoday.com] that IBM is offering Linux kernel developers code from AIX to integrate into Linux.

    What does AIX have to offer Linux? Is there anything worth mining? Anything that could help the move towards 2.4?

  • Not an AIX expert, but the volume manager and journalled file system would look sweet in Linux colours. I know that other parties are working on these but the AIX code is widely deployed and pretty mature.

  • v2.3.41 -- test it and help us! (Score:5)

    by tao ( 10867 ) on Saturday January 29, 2000 @05:31AM (#1324540) Homepage
    When it comes to these latest v2.3.xx kernels
    (38 and on), I've not experienced ANY disk-corruption
    whatsoever. There are, however, lost of other bugs,
    both known and unknown. Why? Because us (relatively)
    few developers can't possibly try every hardware
    combination. We have a couple of new subsystems
    in v2.3 which needs a lot of testing (USB (even if
    it exists in v2.2, this one has been rewritten
    quite extensively)    , FireWire, PCMCIA, I2C, I2O), as well as a lot of new drivers for soundcards, videocards, TV/Radio-cards, disk-controllers etc. The list can be made much longer.

    Oh, and if you have an SMP-machine, you should definitely try v2.3.xx; a lot of SMP-related changes has been made, to improve the performance.


    So please, unless you have production-machines, give the v2.3.41 or upcoming developmental kernels a try. You will certainly help both yourself and the Linux-community out in the long run.

    If (when) you find bugs, submit them to linux-kernel@vger.rutgers.edu.

  • Well, I don't know whether they can help us in the
    move towards v2.4 (it is after all supposed to be feature-frozen, eventhough this isn't perfectly true...), but for v2.6, it would be great
    to receive help with, for instance, porting Linux
    to older models of the RS/6000. Also, IBM has a quite
    nice filesystem, which would be a treat to support in
    Linux, at least for compability reasons.

  • [PATCH] New Kernel Module: Uptime.o (Score:4)

    by MrHat ( 102062 ) on Saturday January 29, 2000 @05:41AM (#1324542)
    I would like to take this time to announce a new kernel module, recently ported to Linux 2.3.41 - uptime.o.

    Uptime.o creates a /dev/uptime entry with major number 199, minor number 0. Want to upgrade to the latest development kernel but don't want to lose your precious 325 day uptime? Do you (gasp) not have a 325 day uptime? Uptime.o is the kernel module for you!

    To use, simply run insmod uptime, and then echo the number of seconds of your uptime to /dev/uptime. The kernel module sets your system uptime accordingly. For example, echo "28080000" > /dev/uptime restores your 325-day uptime. Version 0.0.2 will be enhanced with scientific notation support and support for 512-byte uptime values. An example of what is possible with uptime.o:

    10:38am up 50,000,000 days, 1 user, load average: 0.04, 0.05, 0.07

    49 processes: 46 sleeping, 3 running, 0 zombie, 0 stopped
    CPU states: 3.5% user, 7.1% system, 0.0% nice, 89.2% idle

    Never become the target of low uptime jokes again! Download uptime.o today - amaze your friends, terrify your enemies, and become king of all that is Linux!

    - Hat (with too much time on his hands)

  • Re:Unstable warning (Score:4)

    by logicTrAp ( 2864 ) on Saturday January 29, 2000 @05:44AM (#1324543) Homepage
    No, actually Linus himself has said that he *wants* as many people to use development kernels, *even if they're not developers*. So long as you don't mind putting up with some possible instability (or worse), there's no reason not to play with development kernels.

  • Re:USB support? (Score:4)

    by tao ( 10867 ) on Saturday January 29, 2000 @05:45AM (#1324545) Homepage
    Well, it all depends on what you plan to do with
    USB. Keyboard/Mouse/Joystick/Serial ports should work fine,
    together with some less common stuff (some cameras,
    for instance.) All in all, the USB-support itself
    seems quite stable, but the problem is the lack
    of drivers for everything but the most common things
    (that is, those things that share a common standard or
    one of the USB-developers own...)


    If you have some device that isn't supported, why not either write a driver for it (IF you know how to do so, of course),
    or contact the makers of the device and ask them for a Linux-driver (despite what many companies seem to believe, the consumer is always right. Well, apart from those that buy Micro$oft products, of course; they can't be right in their heads...)

  • Recently, the tulip ethernet card driver support was added (I believe in 2.2.14)...support for the newer version, that is...previously using certain tulip cards required compiling your own kernel module. Is anyone aware of whether this support is in the 2.3.x series?

    Daniel

    ---

  • With devfs, modules can create /dev entries as well (if devfs is mounted there).
  • actually this [redhat.com] is the best place to start.
  • Ouch!

    Last night my HD began thrashing like I've never seen, the system crawled to a halt, and happily froze.

    Upon recovery, files are *everywhere* except where they're supposed to be. I did a quick install on an empty partition, and I'm in the process of saving all the important stuff I can find. I'll then wipe the HD clean and do a fresh install.

    This is the first time I have ever had problems with a devel kernel, (and I've been using them for 3 years or so) so it's not too likely, but beware.

    Hopefully 2.3.41 won't put me in this situation.

    Oh well, at least it happened on a friday so I have time to repair.


  • Netfilter (at least in 2.3.40) is optional. You can switch a little flag in the Networking config section that looks something like "use netfilter". Help on that says that if it is not enabled, you get good old ipchains etc.

    Unfourtunately, I don't think you can enable both at the same time.

  • actually this [redhat.com]is the best place to start.


    Why? The primary recommendation of that link is to go out and buy the book [oreilly.com] I linked.

    Would you prefer a Fatbrain link [fatbrain.com] instead?





  • WTF? (Score:1)

    by redmist ( 51090 )
    Correct me if I am wrong, but is this not the sort of think that kernel.org takes care of? I love my Slashdot, but I think that this sort of thing should be posted (especially for devel kernels). If people want to keep up to date on the kernel situation, they can use the kernotes.org Slashbox.

    .{redmist}.
    -------------------------------------------------
  • I mean NOT be posted (lack of sleep).

    .{redmist}.
    -------------------------------------------------
  • He didn't say "Ph1r5t P054", now did he? He just repeated the "use stable kernels" opinion.

  • yay (Score:2)

    by matticus ( 93537 )
    that's one step closer to 2.4. I'm using 2.3.39 right now, and i'm very impressed by some of the new stuff they are doing. In light of Windows 2000 already needing service packs, it's good to know that the kernel is advancing so rapidly. When i hear about 2.4, i like to evaluate someone's conversion to linux from *other* os's as a gradual process--finding that there are alternatives or equals for every task you can do in windows or whatever. When i turned to linux, there were a few things i didn't think i could do without windows, namely, quake3, terminal server client, use my palmpilot, use icq, write cds, use my parallel port ls-120 drive, and so on. i didn't even know that you could access dos hard drives at that time. but through gradual steps including a voodoo3, reading man pages, getting great new software (jpilot comes to mind), i have eliminated every one of these. this was a 2 year project or so. what is my point? well, i know many people who refuse to use linux because of its poor USB support. i had a friend who bought a computer and wanted to install linux on it, and to his dismay found out his keyboard and his mouse were USB, and his motherboard didn't have ps/2 ports. linux was important enough to him, however, that he bought a new motherboard. we need to be able to help even these people without money-spending on hardware. although linux is free, that is often some area that it is not-almost everyone i know has spent a little extra money to get a new one of whatever peripheral was windows-only, or just didn't work as well in linux. the more the kernel advances, the closer we get to ubiquity;-).

    "look at that. breach hull, all die. even had it underlined."-crow

  • And I hate to seem indignant here, but when the heck are they going to release a 2.4pre? I know, they're working hard, as the continued releases show. But 41 minor releases and no pre's is just absurd. IMO.
  • I think that's implied in the "For those who enjoy *panic*, *oops*...", and also from the "If you don't know where to get it, you should probably sticky to your cuddly 2.2.x kernel.
  • Microsoft mice are actually pretty nice. Logitech is the master of cordless, MS has the Borg Eye technology, which I WANT. :)

    I hope the DOJ splits their input device division into a seperate company - watch every other company rot away into oblivion.
  • well, maybe as 2.3 wanes to a close, they're hyping up 2.4. that's perfectly okay with me. they didn't post for the 2.3.2x or 2.3.3x series except for maybe 39, so maybe it's because this is as close as we can get to 2.4 right now, and that's big news in the linux arena to me.

    "how bout i shove my ovipositor down your throat and lay eggs in your chest-but i'm not an alien."

  • While Linus has promised that 2.4 will be much closer in time and features to 2.2 than 2.2 was to 2.0, the 2.1 series went well into the .1xx numbers. :) I think it even passed 150, although I can't be sure.
  • Did you not follow the development of previous kernel versions? There were 95 versions of 1.1->1.2, 99 versions of 1.3->2.0 followed by 14 2.0pre, and 132 versions of 2.1->2.2. So 41 would be an incredibly short development cycle given the trend. If you want to help hurry it along, run the development kernels on a spare box (or your main box if you like) and help squash bugs.
  • Nope, it didn't. v2.1.126. Then came a series of
    pre-patches for v2.2.0...
  • Which version are you using?

    Can I have a look at the console output?

    As far as I know, the latest (2.3.36) user-mode kernel is stable. If you know otherwise, then tell me what's happening, and I'll fix it.

    Jeff
  • How about all people running ipmasq stuff and such. 2.3.x comes with netfilter, the new way of doing these things. I don't know much about existing modules and such, but have been running my own little subnet with it for a few months now.

    I was wondering if anyone has had some trouble migrating from 2.2.x to 2.3.x and if there are some great lessons to learn.

  • I would love to have AIX's volume manager, which has everything you want in a partition manager, and more.

    Unfortunately, I think they license it from someone else (not sure who), so I don't think they can release the source code. :(


    --

  • I'd love to give 2.3 a try (and have tried to do so several times), but unfortunately I need to use the newest tulip-driver (0.91g) for my 21143-ethernet-cards, which are not supported by the older driver which still is in 2.3. and the newer one won't compile with 2.3.

    Thus, I have to choose between 2.3 without net or 2.2 with net. Guess what the choice is...

    Holger
  • There were 132 versions of the 2.1 kernel on kernel.org. A large number of which I installed :P. 41 is more than reasonable. They just dont feel it's ready for 2.4 pre which is fine by me!
  • uptime.o creates /dev/uptime? Either you mean /proc/uptime, "uses /dev/uptime", or you're a pretty warped programmer.


    /Me sighs.... So much for the days of poking in /dev/kmem.

  • Re:USB support? (Score:3)

    by Syberghost ( 10557 ) <.syberghost. .at. .syberghost.com.> on Saturday January 29, 2000 @06:22AM (#1324577)
    If you have some device that isn't supported, why not either write a driver for it (IF you know how to do so, of course),

    Hell, write one even if you *DON'T* know how. You'll learn a shitload.

    Start here:

    Linux Device Drivers [oreilly.com]
  • My Epson 740 (hooked up by USB) works great.
    No driver yet for my USB CompactFlash reader though :(


    BTW I've been useing kernel 2.3.29 since it came out with no problems. No real reason to upgrade.

Slashdot Top Deals

It's been a business doing pleasure with you.

Close