-- "Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
Re:Additional misspelling patch...
by
Paul+Crowley
·
· Score: 2
Oddly enough, I agree. I'm from the UK and I use UK spelling, but I've worked on a project where I had to correct my "honour" to "honor" because the standard was US spelling. This was a company founded in the UK with offices in the US, and I thought they made the right decision to standardise on US spelling. Er, I mean standardize. --
Re:Permanent compressed filesystem support
by
pod
·
· Score: 1
I was just thinking of how great a compressed filesystem would be, even given the CPU performance hit, but then a bit of nastiness hit me... how do you handle the case where someone goes in and changes a middle byte in a 200 MB file and the recompressed block won't fit back into its place? Do you just end up rewriting the whole file? Or are blocks in a list and you have a fragmented file (but then what's the point of compressing files if you'll just end up wasting space anyways)? I don't think a patch is going to do it, a whole new filesystem would be needed. I wonder how current implementations do it (say in Windows 2000)?
2.4.2-ac1 should include any patches that didn't make it from 2.4.1-ac20 into 2.4.2.
So if you like the experimental stuff, go with 2.4.2-ac1. If you prefer stability, go with 2.4.2.
Re:Last Palindromic Release
by
GrenDel+Fuego
·
· Score: 1
2.5.2 (development kernel) is most likely going to lead to the 3.0 stable kernel. Skipping the ones you mention there.
Re:...And A Patch Close Behind It.
by
Tack
·
· Score: 1
I emailed him about that hours after he released the patch. No reply yet.:)
Jason.
2.4.2 fixed a seriously critical bug for us
by
Tack
·
· Score: 2
Our (6-way) router has been experiencing stability problems for some time now. I upgraded to 2.4.2-pre4 after one of the ChangeLog entries caught my eye, and the stability problem went away. (I believe the problem was in the 3com drivers.) Finally I've found a stable kernel for our router. No more down time!:)
First, for crying out loud - you can get 30 gig hard drives for $99.:-)
But have you tried cramfs? It works pretty well for systems that are relatively static - I don't think you can use it on/home, for example. It's funky in that you create the filesystem _with_ the data all at once. This is what I'm using on my iopener... to avoid having to resize partitions whenever I want to add new stuff to the cramfs filesystem, I'm just taking the cramfs filesystem image and mounting it on loopback...
...well, as soon as the loopback bug gets fixed.:)
Re:This kernel numbering is confusing
by
KlomDark
·
· Score: 2
Yah, but turning off javascript means that a large number of sites will not work (Internet banking, webmail, auto-cursor focusing) All kinds of creature-features that I'm not willing to do without. I run Javascript under Win98, WinNT4, and Win2K with no problems.
Now, if I could just get javascript to work reliably with Netscape 6 or Konqueror under Linux, talk about flaky. I hope changing to Mozilla.8 will help... I am sick of dual-booting and would like to just go for the Linux uptime record instead of rebooting every time I need to do something that I cannot do with Linux browsers...:(
Look at your login screen, dumbass.
by
KlomDark
·
· Score: 2
The text login screen displays the kernel version. If you have your machine set to auto-start X, then hit CTRL-ALT-F1 to switch to text mode, look at the screen, then hit CTRL-ALT-F7 to switch back to X.
Re:This kernel numbering is confusing
by
KlomDark
·
· Score: 2
> In Windoze it's easy, you click on my computer/properties/version and it tells you.
Exactly how long did it take you to figure that out? I'm sure it wasn't so intuitive that you just knew. First you have to know to right-click, rather than left-click, to get the properties menu. That alone is nothing I would call more intuitive than looking at the login screen (You don't even have to log in...) and about equal with the uname -r as far as intuitiveness.
Open you mind a bit, remember that there was a day that you were just as lost with Windows as you seem to be currently with Linux. You'll learn, it'll get easier.
They may not be able to make it fool-proof, but they can already use it to show proof of fools.
Sid is Debian's forever "unstable" release. The "testing" distribution is the one which will get a new name once "woody" is done.
Ganesan
Re:Permanent compressed filesystem support
by
pen
·
· Score: 1
Actually, Internet Exploiter can handle gzip, as long as the web server specifies the MIME type correctly. This is how mod_gzip works. (Yes, they are slightly different things on the server side, but the same stuff happens on the client side.
Re:Permanent compressed filesystem support
by
pen
·
· Score: 1
What do you mean by feeding it locally? If you just opened the file with it, there was noone there to give it a MIME type.
Re:New 2.4.x Compilation issues under Debian unsta
by
cymen
·
· Score: 1
I've compiled both 2.4.1 and 2.4.2 just fine with Debian unstable. I am completely up to date though - are you?
Re:New 2.4.x Compilation issues under Debian unsta
by
cymen
·
· Score: 1
Ugh! It just hit me and I was up to date but not with debian.org but a mirror.
Re:This kernel numbering is confusing
by
zyklone
·
· Score: 1
Troll, But I'm hungry.
The major problem people have with service packs is that they are huge.
A service pack is likely to introduce half the number of bugs it fixes, if you are unlucky one of the new bugs will affect you.
In the linux world we have kernel releases more often. You can upgrade if you want to, if you are satisfied with the older kernel but need a bug fixed you can usually patch just that bug.
You usually won't get much help from Microsoft unless you are running the latest service pack. If you don't they will tell you to install it.
There is another rather huge difference also, this is a kernel release. A Windows Service Pack can affect anything on the system while a kernel upgrade usually only affects the kernel.
New 2.4.x Compilation issues under Debian unstable
by
benmhall
·
· Score: 2
Hi.
I'm not too sure what's going on, some can someone help me: I downloaded 2.4.2 and was hapily compiling it until at the end of "make bzImage" I got an error about ld not being able to find "binary." The line in the makefile was something along the lines of:
(forgive me if I'm a little off, I'm away from the machine at the moment..)
I quickly flipped through the ld manpage and saw that -oformat is a valid option. I then tried recompiling 2.4.1 which I had installed cleanly when it came out and got the same problem. I looked at the Makefile in 2.2.18 and there is no -oformat for the ld call there.. at last I can still compile it..
Does anyone have any ideas about what my problem is? I don't know too much about the Gnu linker, but it looks like maybe the version in sid doesn't jove with the Linux kernel..
My girlfriend has informed me that Sid was the bad kid in the first movie. I haven't seen it though, so don't quote me on it..
Ben
Re:192 days? My MS Whistler has you beat
by
sinan
·
· Score: 1
Maybe, but it is beginning to appear not..... We have multiple SparcStations and PC's in our house, and until this week, on couple of PCs, We had Win2K/WinME and Linux Installed on separate carriage Hard Disks. Because when it came to certain things, still it was hard to beat Win2k. As a matter of fact , just for that reason, I had been a professional subscriber to MSDN. (Last update was just this January.) However after installing 2.4.1 and then 2.4.1 with KDE 2.1.x beta and loading the ALSA drivers ( now up to version 0.9), I am totally impressed. Now I can do things with my RME Hammerfall (full) , MidiMan DIO2448 , SBLive platinum and Ensoniq 1371 cards that I could not even dream of before. We started salvaging the HDs that win2k/Win98/WinME were taking and changing them into nfs shared disks. This is a diffusion equation with exponentially growing distributed sources. Any one with some physics/math background already knows that the outcome is inevitable. With the LiVid's latest DVD players, and Matrox's support for G400 dual head(one machine) and G450 dual head (in the other) and with my Sony PCG-XG18 and my wife's Fujitsu Lifebook, we are in heaven. However I will keep all the 600 or so MSDN CDs and 50 or so MSDN DVDs for future reference. As it stands now they are relegated to the upper shelf ( and yes I did see a whistler beta there, but frankly I don't care anymore. Not with ASP/.NET concept and the secure path.... I even stopped downloading Win2k updates after they screwed up my multi region DVD player hw/sw...) I basically do not trust any closed source s/w anymore. The last s/w I am ordering is Mathematica 4.1 , but I am also coming up on Maxima (open source Macsyma). I already use {Star,Open}Office. Word 2000 came with my Sony PCG-XG18, but I never installed it. StarOffice/Cygwin/Forte/Netbeans catered to every need I had on Win2k, and they do just fine on Linux. Oh BTW, Konqueror is great. Now I no longer need Netscape or IE either....
The 2.4.1ac series included a couple of fixes for the Matrox G450 card. The changelog for 2.4.2 says "sync up more with Alan", but it doesn't say what changes were sunc. How can I find out if the Matrox fixes went in or not?
Thanks,
Stuart.
Re:Matrox G450 patches?
by
Erik+Hensema
·
· Score: 1
Watch Alan as he releases 2.4.2acN and check wether your desired patch is still in the ac kernels. If it's not, it's in the main kernel.
Yes, hardly scientific, but it works.
--
This is your sig. There are thousands more, but this one is yours.
2.4.1ac also fixes my 3c905... No mention of WHAT he sync'd up. This is one thing that bothers me about Linus' changlog's... They suck.:)
-- --
[ta]
Re:Journaling Filesystems?
by
cloudmaster
·
· Score: 1
Furthermore, you can't run NFS of a ReiserFS partition yet
I could swear that I was sharing a couple of ReiserFS volumes over NFS last summer... Yeah, I must've, because the whole lab ran exclusively Reiser (installed with SuSE). NFS doesn't care what file system is below it, it's a user-space thing (except when it's a kernel-space thing, in which case it still shouldn't even know what FS is underneath it).
Re:Journaling Filesystems?
by
cloudmaster
·
· Score: 1
Doh. I seem to have forgotten about ""
BTW, what's up with this:
Slow down cowboy!
Slashdot requires you to wait 1 minute between each submission of/comments.pl in order to allow everyone to have a fair chance to post.
It's been 1 minute since your last submission!
Re:Permanent compressed filesystem support
by
jms
·
· Score: 1
It all depends on what you want to spend your money on, or what you happen to have a surplus of. Processing power or disk space.
If your webserver is so busy that a compressed filesystem adversely affects your performance, then obviously a compressed filesystem would be a poor choice. On the other hand, if you have a very lightly used web server with a large volume of data, then it might be a good idea.
Nice to have the option
Re:Permanent compressed filesystem support
by
jms
·
· Score: 2
Don't forget web pages! Those are generally stored uncompressed, and a large web site can literally have gigs of HTML files.
C coding is not taught in any standard form in current university settings. I have learned Pascal, C++, bash, ksh, and csh but I never touched C because it wasn't
formally taught.
If you know C++, then C's easy. It's just C++ without all the good parts.
No problem here. I compile my kernels using gcc 2.95.2 (from Debian potato).
I don't think you can compile it with the 'new' compiler that came with Redhat 7.0, but I'm not sure.
-- Je ne parle pas francais.
Re:Journaling Filesystems?
by
Erik+Hensema
·
· Score: 1
ReiserFS is generally stable and works for most persons without any trouble. I've been using it for months now on my desktop and I'm really impressed with it. Pressing reset almost becomes fun;-)
However, last time I checked, ReiserFS didn't support quota (this may have changed, I'm sure patches exist). It also doesn't support a bad-block map, so be carefull with partially damaged harddisks.
Furthermore, you can't run NFS of a ReiserFS partition yet.
ReiserFS is very fast. You can really notice difference to ext2, mainly in large directories.
--
This is your sig. There are thousands more, but this one is yours.
Re:Best way of reporting problems
by
Erik+Hensema
·
· Score: 1
First, try 2.4.1. Knowing if 2.4.1 works for you is fital in finding the bug.
Then, when you know what version broke the driver, you may or may not investigate further on your own. You might want to try some 2.4.2-preX kernel to futher pin down the breakage.
Eventually, just file a bug report to the Linux kernel mailing list. Be sure to be as accurate as possible: describe your hardware and the symptoms as exact as possible.
--
This is your sig. There are thousands more, but this one is yours.
Re:Journaling Filesystems?
by
Mr.+Flibble
·
· Score: 1
I actually have a few systems set aside for the following at home:
Open BSD 2.7, FreeBSD, and perhaps NetBSD if I have the time (Then again, I might make it a Solaris box).
I am unfamiliar with BSD, hence why I wish to try it, what are softdeps? The term reminds me of "symlink" for some reason (as in the way a symlink appears on the inode table).
Re:This kernel numbering is confusing
by
rark
·
· Score: 1
What hypocrisy?
Windows service packs affect more code than just the kernel. They don't allow me to selectively fix what I want, either. And they tend to break more than they fix.
With the linux kernel updates I can update just the kernel, rather than the kernel, the webserver and the kitchen sink. If I want to upgrade the webserver I'll do that separately, thank you. Also, I honestly see fewer changes in between 2.4.1 and 2.4.2 (or 2.4.0 and 2.4.2, really) than the average service pack fixes.
It isn't about how often updates are required, it's about whether those updates are out when I need them (esspecially security fixes) and how much control I have over running them. And not breaking more stuff.
Re:Permanent compressed filesystem support
by
Inataysia
·
· Score: 1
i think you should be looking at the mode rather than the average file size to determine savings to be had from shrinking blocksize. consider the situation in which you have 1e7's of 10-byte long files and a couple 1e9-byte files.
Boy, you've got a slow system if it takes you two months to compile three releases. Maybe if you invest in some more RAM or faster hard disks, you won't have this problem.
The other alternative is to stick with 2.2.19 or 2.0.39.
-- I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
You can't buy Whistler at Fry's or anywhere else. You'll never be able to buy Whister... only Windows XP. Unless you're using some weird pre-alpha, Whistler builds haven't even been around for 342 days.
Re:This kernel numbering is confusing
by
bnf
·
· Score: 1
Okay, I'll bite.
The benefits of linux release methodology over the Microsoft release methodology:
- I can quickly get a sense of what is being improved with each kernel release by looking at the changes notice that is included with each kernel.
- I can find in depth discussion of some changes by following the kernel development list or the major discussion by reading the kernel traffic summaries that are published weekly at http://kt.zork.net/kernel-traffic/latest.html - I can go read the code in the kernel to try to discern what is going on
- I can try to contact a kernel developer directly to seek information on a particular improvement
- I can offer my own improvements to the code
- I can tell what the benefits or a particular improvement are and who will benefit from this improvement
- I do not have to blindly go forth into the mire of a service pack and hope that it fixes a problem in a correct and well thought out manner and hope that it truly offers a benefit and does not only serve the interests of one entity
Does this mean that some bad ideas don't get brought into kernel releases? No. Does this mean that I have to expend less effort in deciding upon and then executing a update of my system? No. But I do have more tools available and better information to help me to decide if this is the right decision.
--
this space intentionally left blank (oops)
Re:This kernel numbering is confusing
by
bnf
·
· Score: 1
Yes, lets take a look at that. Here's the first article I looked at under that link...
http://support.microsoft.com/support/kb/articles/Q 253/6/07.ASP
Includes
SYMPTOMS
When you add a second NNTP virtual server, master/slave feeds and control messages may not work when Microsoft Exchange 2000 Server Release Candidate 1 (RC1) is also installed.
CAUSE
A property is incorrectly set in the metabase on the control and slave groups as to which driver to use. By default, Windows 2000 assumes the Exchange store rather than NTFS store. This breaks both control messages and master/slave feeds.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, please see the following article in the Microsoft Knowledge Base:
Q260910 How to Obtain the Latest Windows 2000 Service Pack
And this really doesn't give me much to chomp on with regard to if this is a good idea for my system. And considering that I may not be running exchange, may not be serving NNTP, and may not be running two virtual NNTP servers on my box, is this something that I need anyways? And how do I judge this on it's merits? There is little diagnostic information available and basically they ask for blind trust in a situation which time and time again they have shown that they are not deserving of it.
--
this space intentionally left blank (oops)
Re:This kernel numbering is confusing
by
bnf
·
· Score: 1
> So, if you're not running Exchange and don't have two virtual NNTP servers, then the bug does not affect you.
Then why should the solution?
> You can understand kernel source code, but can't read English. Are you a bot?
Yes, ofcourse I'm a bot. In fact, I'm the first bot to be able to understand kernel source code and evaluate it's effectiveness for use. You should fear for your job!
One of the reasons 2.4.0 was released when it was was to get a larger base of testers. Distros aren't goint it use 2.4 for a while yet, RedHat started using 2.2.0 (and 2.2.1/2.2.1 were released pretty quickly after 2.2.0..)
Uhhh...it *IS* out of experimental. It was included in 2.4.1 production. I migrated my home machine and my webserver over to it. No fsck is a good thing especially when your home machine locks up from a buggy nvidia x driver;) hehehe
-- "Fighting the underpants gnomes since 1998!"
"Bruce Schneier knows the state of schroedinger's cat"
Sorry, but I don't buy that. They have a version of the code known as sid already, which stands for 'still in development'. Naming a release sid would only cause unnecessary confusion.
--
GPL made simple: What was my stuff is now our stuff. If you improve our stuff, please keep it our stuff.
and which unreleased version of Whistler is this?
by
cpeterso
·
· Score: 2
Re:...And A Patch Close Behind It.
by
Black+Parrot
·
· Score: 2
> o Fix 48 misspellings of interrupt (André Dahlqvist)...
Maybe they need to add a make spellcheck step to kernel compilation.
--
-- Sheesh, evil *and* a jerk. -- Jade
Permanent compressed filesystem support
by
bliss
·
· Score: 1
I speak for people with small drives everywhere when I say:
When will the kernel support default compression of filesystems.
-- The death of one man is a tragedy; the death of a million is a statistic --Joseph Stalin
Re:Permanent compressed filesystem support
by
rullskidor
·
· Score: 1
Then use reiserfs or some other fs which packs the tails together.
-- De lyckliga slavarna är frihetens bittraste
fiender, legalisera!!!
Re:Permanent compressed filesystem support
by
coyote-san
·
· Score: 2
Think about it, I'm sure that most of the real "disk hogs" are things like
mp3s, mpgs, tar.gz's and.zips.
You might be surprised. When I was playing with a local news spool I had to reformat the partition because I ran out of inodes. At the same time I dropped the blocksize from the default 4k to 2k, and recovered nearly 1 GB out of a 4 GB partition.
Further research showed that the average file size was around 5k, so it required 8k of disk space (3k unused). A 2k blocksize required 6k of disk space (1k unused). A 1k blocksize freed up even more space.
If you have a lot of small files you can eat up a surprising amount of disk space in the tail of your files.
-- For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
Re:Permanent compressed filesystem support
by
cyberdemo
·
· Score: 1
Re:Permanent compressed filesystem support
by
cyberdemo
·
· Score: 1
On a busy webserver, if you compress those, you'll end up wasting much more processing power than you'd need if the files were uncompressed. Think about large sites like NASA's having everything compressed-decompressed... Insane.
--
--
I have no sig at all.
Re:Permanent compressed filesystem support
by
cyberdemo
·
· Score: 1
Man, I think that, besides your post being off-topic, you're just ignoring other high-quality distributions, like Debian (which I use), that have very smooth updates, besides other things that make it the best in the moment.
--
--
I have no sig at all.
Re:Permanent compressed filesystem support
by
cyberdemo
·
· Score: 1
Agreed:)
--
--
I have no sig at all.
Re:Permanent compressed filesystem support
by
cyberdemo
·
· Score: 1
Not when you have an extremely large website. Consider the fact that a site that has lots of stuff compressed gets/. all the sudden. How about that?
--
--
I have no sig at all.
Re:Permanent compressed filesystem support
by
AndroSyn
·
· Score: 1
You might want to take a look at reiserfs for your news spool. Reiserfs doesn't have inodes(not in the traditional sense anyways). What it does it creates a unique hash for each file and uses that for an inode, so you end up having basically an unlimited number of inodes.
Also reiserfs is not block oriented so you end up with little to no wasted disk space when dealing with small files. Also with extremely small files, the data is often stored with the metadata rather than allocating a chuck of disk space elsewhere.
Re:Permanent compressed filesystem support
by
carleton
·
· Score: 1
How about instead just running a script that looks in all directories for a COPYING file. It then checks to see if it is truly the GPL, and if so, replaces the file, which takes up a whole several k of diskspace, with a symbolic link to a master copy of the GPL. On many systems, this could free up as much as whole megabyte (you got it, 1024 whole k) of space, which is probably considerably more than the savings you'd get from trying to blindly compress everything.
Re:Permanent compressed filesystem support
by
psocccer
·
· Score: 3
I don't think it'll help much though. Think about it, I'm sure that most of the real "disk hogs" are things like mp3s, mpgs, tar.gz's and.zips. I included the tgz and zips because most people uncompress, compile, install, delete. Some keep them around, but most do not keep around the uncompressed tgz for most things.
All those things don't well, if at all, so a compressed filesystem would just be redundant. The exegz thing might help some, but stripping your binaries is probably just about as good without the runtime performance hit. And I'd think that even if you compressed your whole root partition with a scheme like this, the savings would be negligible but everything you did would require packing/unpacking stuff so the whole system would be generally slower.
With the ever expanding size of hard drives, I think this is a pretty small issue.
Yes, I realize that maybe single floppy distros and embedded devices may find this kind of thing useful, but I'm talking about the other 95% of the linux community here.
Re:Permanent compressed filesystem support
by
aap
·
· Score: 1
$150 buys a 30GB drive these days. Oh, wait, those all seem to be backordered, but you can settle for 40GB for $135 and have it tomorrow. Much more reliable than compressed filesystems, I'd imagine...
Re:Permanent compressed filesystem support
by
Sarin
·
· Score: 1
A compressed filesystem is perfect to store your logfiles on, since they are in clear text.
You don't have to store everything on that partition ofcourse, but it's also nice for storing my "e"-books on which take around 4 gig of space now, I hate to have them all (g)zipped, cause I want to be able to read them anywhere with a web browser.
Re:Permanent compressed filesystem support
by
valdis
·
· Score: 1
"Even if you compressed your whole root partition... the savings would be negligible"
AIX has supported LZ compression of files in the file system for several years. I've found about a 30% savings in disk space for/usr and/home (although I'm not into the mp3/mpg scene, so a lot of it is source files). Hardly "negligible", and
it's only using LZ compression (mostly for the speed issue).
"the whole system would be generally slower"
Surprisingly enough, on a lot of boxes, using filesystem compression made it *faster*. On a system that is not already CPU constrained, it's often faster to fetch 4 512-byte sectors of compressed data and unpack them into a 4K block than it is to fetch 8 512-byte sectors. If your disks are being beat to hell already, it's even more of a win - ever had to move stuff from drive to drive because your web server was serving up HTML and the fetches were clogging things? How'd you like to get rid of 2/3 of the I/O?;)
Re:Permanent compressed filesystem support
by
ocelotbob
·
· Score: 1
If you use nutscrape you can GZip those ebooks anyway. It's smart enough to know how to handle compressed files. Internet Exploiter, and Mozilla, OTOP, can't handle them, so use this advice with caution.
--
Marxism is the opiate of dumbasses
Re:Permanent compressed filesystem support
by
ocelotbob
·
· Score: 1
Hrmm. That gets me wondering if something's screwy on the system I'm using or if it handles local files differently, 'cuz when I fed a gzipped web page to it locally, it gave the "what the hell am I supposed to do with this" dialogue.
--
Marxism is the opiate of dumbasses
Re:Permanent compressed filesystem support
by
Bob+Abooey
·
· Score: 1
Bah, who gives a hoot about the new kernel. I jsut want a God Damn linux distro that works like it should right out of the box. I lament the day I went from Mandrake 7.1 to 7.2. Don't they test these things before boxing them up? Jesus H Christ on a city bus, it takes a week to update and fix all the borken stuff before you get back to where you were before the upgrade.
Linux has a big problem with trying to do too much cool stuff and not enough quality stuff. I'm a friggin geeky nerd too, I can't imagine what Joe Bagadonuts would do with this mess, probably go running right back to Windows 9x while talking about how all those Linux zealots are a bunch of fools. Yeah yeah yeah, I can here you, "well Bob, why did you upgrade if 7.1 was working fine for you?" That's a real good question.... maybe I bought into the Linux hype myself, maybe I wanted to believe sooooo badly that I overlooked all the crap. Sigh... now if you'll excuse me I have to spend some time and research why my fucking sound keeps dieing under KDE 2. Then I have to spend some time to figure out why my network card keeps getting these dirty node errors which are filling up my/var/log/messages pretty quickly.
Yours,
--
All the best, --Bob
Re:Permanent compressed filesystem support
by
kyz
·
· Score: 2
It's technically called 'clustering', but think of it like this: take the raw bits of your hard drive and divide them into 8k blocks, or whatever. Now compress those blocks and store them on another filesystem. The filesystem-under-the-compressed-filesystem takes care of where to put these physically compressed blocks. In the worst case scenario, it says 'out of space' and the write of the new bytes fail.
-- Does my bum look big in this?
Re:Permanent compressed filesystem support
by
kyz
·
· Score: 2
Interestingly, disk caches store data uncompressed. Therefore, the pages that are actually read will most likely be available from memory or swap uncompressed.
-- Does my bum look big in this?
Re:Permanent compressed filesystem support
by
kyz
·
· Score: 2
Not when you have an extremely large website. Consider the fact that a site that has lots of stuff compressed gets/. all the sudden. How about that?
You're missing the point. Any file that gets read more than once is likely to be in the cache. Just depends on how much RAM you have. As for/.ing, decompression only happens on the first page hit, and the following 10000 hits are served direct from RAM. Unless the/.'ed content is larger than you have RAM for, there's no issue.
-- Does my bum look big in this?
Re:Permanent compressed filesystem support
by
kyz
·
· Score: 3
I speak for people with small drives everywhere when I say:
When will the kernel support default compression of filesystems.
Use gzexe - which needs no special kernal magic, or apply the ext2compr patch to the kernel, which isn't that great.
"Well bitch, don't be so fucking lazy and code it up yourself. Isn't that the beauty of Open Source? "
Well bitch here's the rundown.
1. learning all the ins and outs of the kernel is a full time job in itself. I don't have the time to spend 6 months learning exactly what goes where.
2. C coding is not taught in any standard form in current university settings. I have learned Pascal, C++, bash, ksh, and csh but I never touched C because it wasn't formally taught.
3. Writing kernel code is approximately 200% harder and more precise than writing an application program.
4. I don't have expertise levels of OS design.
Those things being stated I feel that at least on the surface once those things have been removed it wouldn't take say Linux or Alan Cox much more than 5 minutes of their time to get it working once and for all. Basically you just have something sitting above the call to storing or writing data and have your favorite compression algorithm there to act as an intermediary.
I hope this is more lucid than your reply.
-- The death of one man is a tragedy; the death of a million is a statistic --Joseph Stalin
Re:coding and maintaining
by
timefactor
·
· Score: 1
If you know C++, then C's easy. It's just C++ without all the good parts. C++ == C + objects + dreck;
Objective C == C + objects;
Maybe you should read the the announcements that come with every kernel release before proclaiming that:
Don't just go out and grab 2.4.2...
From Linus's announcement:
The IDE driver bug that Russell found has, to my knowledge, never been shown to happen on anything but his ARM machine, but for all we know it could be quite bad even on x86. Similarly, the elevator bug could cause corruption, but probably has not actually bit people in practice. But both are definitely deadly...
I don't know about you, but I think this may be significant and worth the upgrade if you use IDE in your systems.
--
Remembering your name in the morning is already a good start...
What I've been able to tell from digging through mailinglist archives is that the bug in 2.95.2 is only triggered for i386 targets - or at least not i686.
-- / Peter Schuller
--
peter.schuller@infidyne.com
http://www.scode.org
The current Linux codebase is good, but for it to be great, the developers must stop patting eachother on the back...
Glad to hear that you are going to do the rewrite. The source is all there. Are you setting up your efforts on sourceforge or will you just announce it view usenet ala Linus?
Re:Last Palindromic Release
by
spoon42
·
· Score: 1
heh. can't forget the "older" kernels. does 2.2.22 count? how bout 2.0.102 ?:)
-- --- this comment is presented in WIDE SCREEN STEREO!!!
Re:This kernel numbering is confusing
by
Crimson+Midget
·
· Score: 1
I hope you're not being serious.
How is following a path of clicks and right clicks any more "intuitive" than using 'uname'? That's ludicrous.
Some of the developers may use cvs on the sections they maintain, but eventually it all has to be sent in the form of patches to Linus who merges together the official tree using whatever voodoo he uses to manage all of the updates. treke
Re:Permanent compressed filesystem? WHY?!?!?!?!
by
Porag_Spliffing
·
· Score: 1
.........and a serious mp3 collection is allready compressed. Any compressed fs is not going to get much more out of it.
I spent almost a week downloading Red Hat's 2.4.0 beta and getting it installed (all I really wanted was iptable support). And, after getting it installed and customizing it so it would actually work (Hey! It's a beta distro...) I was amazed at the overall speed and performance. But, iptables would not work (xinetd required a backpedel to an earlier version) and I was forced to use IPChains. As it is, the box is still sitting behind my firewall rather that on the front line.
Downloaded 2.4.1 and tried to compile it. It broke things in the RD distro. Downloaded the most current iptables and recompile the 2.4.0-99..whatever RH kernel. iptables still would not work.
Today, out of a whim, I downloaded and recompiled 2.4.2. Not only did it compile without any issues, but iptables works as well (imagine that).
Can't wait to see tomorrow if, when I reboot, that it tells me nfsstatd didn't start like 2.4.0 and 2.4.1 did when I recompiled. Well, I gotta see, recompiled the kernel from home and it just sounds too good to be true.
RD
Re:This kernel numbering is confusing
by
Inoshiro
·
· Score: 2
The reason, which you and the people who replied to you seem to have missed, is because Microsoft said themselves that Windows 2000 would never required fixes. They lied to the corporate managers and other people who choose what to run on the servers in order to get more money.
That is what people don't like about MS Win2k. Linus never claimed that 2.4.0 would be bugfree (or if he did, he did it tongue-in-cheek). If MS had more truth in their advertising, I know I'd be happier.
--
-- -- Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
Give us a break. The whole point of linux is "do what works" not "do what's propper." Not to mention, why don't you quit gabbing about it and do it yourself. That's the beauty here. If you think Linus is doing an ass job, he actively encourages you to try and do better. You don't have to overrule him to make some changes, you just do it.
--
Someone you trust is one of us.
Re:This kernel numbering is confusing
by
eggnet
·
· Score: 1
If I'm not mistaken, Debian does that at least to some degree... which means there is a whole distribution's worth of people doing that.
The kernel traffic editions since the release of 2.4.0. It's talked about as 'filesystem corruption', and was tracked to the VM (IIRC).
-- Ideology breeds Hypocrisy. Just how much is up to you.
Re:Permanent compressed filesystem? WHY?!?!?!?!
by
technomancerX
·
· Score: 2
There are already file sysyems being
developed for embedded work (like cramfs), I was
assuming he was talking about something similar to
the compressed disk option in windows... basically my point was implementing this for a desktop system is a complete waste of time (or even for a laptop... my Vaio C1VN is about as small as they
come and it's got a 12 gig drive in it...)
.technomancer
-- .technomancer
Permanent compressed filesystem? WHY?!?!?!?!
by
technomancerX
·
· Score: 3
Geeze, with 20 gig drives less than $100 what's
the point? Even when I was in college working
15 hours a week I could scrounge that much with
a little effort... and unless you're a major MP3
fiend, doing video editing, or mirroring large
ftp/web sites, 20 gigs is enough space for a Linux box (hell, I've got a network gateway box doing
email, http, ftp, and dns on a 1 gig drive
and it's fine)
.technomancer
-- .technomancer
Re:Permanent compressed filesystem? WHY?!?!?!?!
by
drift+factor
·
· Score: 3
Geeze, with 20 gig drives less than $100 what's the point?
Could have something to do with the fact that his wife, Tove, was pregnant and gave birth in late November I believe. I think that would take a bit more priority over tbe release of 2.4.0
Obviously you never read the flame war between Tannenbaum and Linus that took place in 1991. Theoritical design is one thing, but writing something that works and works well is another.
But, if you don't like how things are going with the linux kernel, nobody is stopping you from starting your own fork of the linux kernel. Import the whole source tree into your own CVS repository, get some developers and get some work done.
Re:This kernel numbering is confusing
by
rhedin
·
· Score: 1
Don't just go out and grab 2.4.2. Odds are you don't even need it. It's merely another stable release that spreads what Linux can run on.
You haven't read the fscking Changelog have you?! 2.4.2 fixes a serious IDE multimode write bug. If anyone has even somewhat-modern IDE hard drives in their system, it is certainly worth their while to get it.
I think SCSI-only boxen can wait, though -- but Linux was (and still is, to a degree) all about Unix on low-cost x86 hardware, so methinks there be plenty of IDE-based Linux systems around...
--
Serious IDE Write Bug in 2.4.1 Fixed in 2.4.2
by
alexburke
·
· Score: 3
From the changelog:
-pre2:
- Russell King: fix serious IDE multimode write bug!
If you have IDE hard drives, I recommend you pop 2.4.2 into place purdy quick. Write bug == bad.
--
Re:Serious IDE Write Bug in 2.4.1 Fixed in 2.4.2
by
shippo
·
· Score: 2
Does this resolve the problems with VIA chipsets?
Re:This kernel numbering is confusing
by
slamb
·
· Score: 1
Maybe you're right, maybe I do just know where the workarounds are under Linux. But that does come back to Linux's basic openness...there are lots of diagnostic tools available (ps, strace, ltrace, gdb, lsof, netstat, lspci,/proc, etc) and the source is available, so it's very, very easy to see what's going on in the system and where problems are. So if I do know where the workarounds are under Linux...I think that's why. Windows just doesn't ship out of the box with those kinds of tools. Some I've managed to find (PrcView is a decent approximation of ps, for example), some I haven't.
As to my specific problems...I just checked, the "JavaScript debugging disabled" option is on. I assume that means debugging is disabled. So, that doesn't seem to be my problem, but thanks anyway.
For the curious, here are a couple of the weird problems I'm having with IE5.5 right now:
It doesn't like really long/complicated forms. Specifically, I was a Slashdot moderator recently. I tried to browse at -1/nested so I could moderate, but it didn't work out very well. The form elements just sort of came and went on the screen, completely unrelated to where they were placed in the HTML. I also tried it on a friend's computer, the same thing happened.
The scroll wheel occasionally stops working. I can always move it up and down, but if I hit the button, a circle is supposed to pop up that lets me scroll by moving the whole mouse. After some unknown trigger (I've been trying to find out what it is), Internet Explorer stops liking this. It instead pops up a dialog box basically saying that Internet Explorer screwed up and will quit. The current IE window then goes away when I hit OK. If I start another window and tap the scroll wheel again, the same thing happens. It doesn't get better unless I ctrl-alt-del explorer and let it restart. This might be some weird interaction with my mouse drivers, I should really check to make sure I'm at the latest version.
Re:This kernel numbering is confusing
by
slamb
·
· Score: 4
Buy windows 2000 and you have to download 1 service pack and thats means its a terrible OS that needs constant patching. Download linux 2.4.0 then 2.4.1 and then 2.4.2 in less than half that timespan and rather than meaning that 2.4.0 was a terrible OS that needs constant patching it is an innovative OS with a rapid turnaround. Am I the only one who spots the hipocracy here?
I see no hypocrisy.
First, when I make a judgement like that about a Microsoft product, it's not because of the number of service packs. I realize that all software of that complexity has bugs. It's instead that their software doesn't work well for me, even after applying all the service packs. Their service packs just don't seem to fix all the important problems for me, no matter how many I apply. For example, I've patched my Windows 98 system to the latest Windows Update stuff, but I'm still having some weird problems with Internet Explorer.
Second, Linux x.y.z releases are not just bugfix releases. In this case, it probably is...x.y.[1-5] typically are. But there are many new features introduced in point releases. 2.2.18 (or was it 2.2.19?), for example, backported USB support to the 2.2 series. I see a lot of important new features introduced in new Linux point releases, which I don't see in Windows service packs. Having a specific x.y just means the basic architecture is constant, not that the feature set is.
Third, as someone else mentioned, you don't need to upgrade to a new kernel revision to fix a bug. You have the source code, and you have the full patches. If you just want to fix one bug, you can do that. You don't have that option with Microsoft code, since it's not open-source.
Netware has this and it works well
by
bad-badtz-maru
·
· Score: 1
Netware has a compressed file system that works very well. It background compresses files that have not been accessed in x hours/days. When read access to a compressed file is necessary, one of two events occurs. If the file has been read accessed less than y times in z hours/days, the file is uncompressed to a temporary space and deleted a while later. If the file is accessed y times, the file is uncompressed and remains that way until the initial compression criteria is again met. This works extremely well, frequently accessed files are not compressed and the space used by infrequently accessed files is minimized.
maru
there is no "hipocracy" there at all (that i see)
by
Forrestina
·
· Score: 1
the linux kernel is in a constant state of development. people know exactly what they are getting into if they choose to use a 2.4.0 release. there were no promises made that it was the most stable thing on the planet, or that it would have no bugs. it's never even finished.
windows 2000 is a finished, final product. they said, hey, we're done. this to me seem a promise, that it is finished. i understand of course that nothing is ever bug free, and patches are expected. but.... i doubt that microsoft tells you, 'hey, this is still under development, expect major bugfixes all the time!'.
-------
--
-------
"don't smoke, don't drink, don't fuck
at least i can fucking think"
Minor Threat
Geez, these kernels just keep popping out. Can you folks give us a month or two to get used to 'em first?
Re:This kernel numbering is confusing
by
prog-guru
·
· Score: 1
Like you can't have 10 simultaneous connections on NT4 Workstation, but if you buy Server...
That's the hardest part of building an NT server for me. I can configure DNS, DHCP,etc, but I can never remember if I want per seat licensing or whatever.
Back to the topic though, what is up with the frequency of these releases? 2.4-test releases never came out so quick, and the changelogs aren't that long. Just curious, is it customary to release a slew of maintenance releases weeks after an x.x.0?
--
chris@xanadu:~$ whatis/.
/.: nothing appropriate.
Re:This kernel numbering is confusing
by
prog-guru
·
· Score: 1
Some of us weren't born knowing uname -r gives you the version #, so here's an easier way to find out:
apropos kernel (gives a list of manpages that have information about the kernel)
in the list you'll see:
uname (2) - get name and information about current kernel
then of course:
man uname
etc...I'd say that's more intuitive, next apropos rocketscience...
--
chris@xanadu:~$ whatis/.
/.: nothing appropriate.
Re:...And A Patch Close Behind It.
by
Lizard_King
·
· Score: 5
From the Alan's email to LWN:
o Fix 48 misspellings of interrupt (André Dahlqvist)
o Fix 20 misspellings of successful (André Dahlqvist)
o Fix 11 misspellings of suppress (André Dahlqvist)
o Fix 46 misspellings of address (André Dahlqvist)
o Fix 26 misspellings of receive (André Dahlqvist)
o Fix 7 misspellings of acquire (André Dahlqvist)
o Fix 4 misspellings of unneccessary (André Dahlqvist)
o Fix 13 misspellings of until (André Dahlqvist)
André Dahlqvist is fusing the line between English major and CS major.
-- "My mother never saw the irony in calling me a son-of-a-bitch." - Jack Nicholson
Re:This kernel numbering is confusing
by
Ig0r
·
· Score: 1
Rocket science?
No, a simple "uname -r" will suffice.
--
-- Soma: because a gramme is better than a damn.
Re:This kernel numbering is confusing
by
Ig0r
·
· Score: 1
I knew uname returned system information, but I didn't know what option to use for just the kernel version. However, here's a very simple way to find things like that. The --help option is fairly universal, so I just looked at the help output and found my answer in a matter of seconds.
And anyway, if you're using GNOME, you can check your kernel name/version, dist version, processor type, your username, and your hostname by looking that the main screen of the GNOME Control Center (gnomecc).
I would bet money that KDE gives similar information in it's incarnation of a UI preferences system.
-- "Do not meddle in the affairs of wizards,
for they are subtle and quick to anger."
Wow... that was short news! *nt*
by
aardwolf64
·
· Score: 1
*nt*
Re:This kernel numbering is confusing
by
proxima
·
· Score: 3
If you are truly being serious, the reason is because a kernel number makes it MUCH easier to understand the sort of kernel you are using.
The first number is a major code change, fundamental in nature. After about 7 years we are now up to 2.x.x. The second number also shows major revisions, but of a less fundamental variety than the first number. An odd second number denotes a development series, not intended to be used for production computers. This is why most users went from 2.0.x to 2.2.x to 2.4.x, because 2.1.x and 2.3.x were development versions. When the development version is deemed stable enough to be used in some production platforms, it moves to an even second number, like the recent 2.4.0. However, the 2.2.x kernel series is still being maintained for use as an ultra-stable kernel, while the 2.4.x is more cutting-edge for the latest hardware support and performance.
The third number indicates a small change, usually bugfixes but some small amounts of new features supported. When going to purchase new hardware it is easy to tell if you have a "2.2.0 or later kernel".
Finally, a service pack generally implies a large set of bugfixes, as Microsoft had somewhere around 7 (maybe 8) for NT 4. The Linux Kernel version system allows for a few small changes to be made at every release, decreasing the waiting time for users to wait for a desired bugfix or feature (instead of months for a new service pack).
If my overgeneralization of the Linux kernel was incorrect, my apologies, but I think an overall understading of how the Linux Kernel numbering system works is important for those who don't know yet.
-- "The universe seems neither benign nor hostile, merely indifferent." --Carl Sagan
Re:192 days? My MS Whistler has you beat
by
idiot900
·
· Score: 1
Don't you mean 215.28 days, like it says in your post? Is that bad? What's this you said about research and feet?:)
That said, I'm a happy Linux user who just wants his OS of choice to be intelligently defended...
MS engineers are carefully sheilded from the public for this sort of reason.
-- 'There is a Light that never goes out.'
Re:This kernel numbering is confusing
by
brsett
·
· Score: 1
I am 95% sure that you have debug on javascript option enabled. TURN IT OFF (it doesn't do what you think it does anyway). I used to have all kinds of flakiness with IE in Win 98 until I learned of that problem (it comes disabled by default, I turned it on thinking it did something different than what it does, should have rtfm).
I'm not chiding you, but most linux people I know read all sorts of stuff about how to workaround problems in linux. I know very few people who are willing to put forth that effort in Windows. Both linux and windows are extremely buggy. I suspect the bug metrics for both pieces of software are similar. My guess is OpenBSD probably has much better metrics -- mind you I can handle the bugs and so I run both Win 98 and linux.
Re:This kernel numbering is confusing
by
brsett
·
· Score: 1
Clearly, you and I had different degrees of flakiness in mind. I'm sorry that I can't help you.
Re:Journaling Filesystems?
by
InsaneGeek
·
· Score: 1
Having just gone through a fairly rigorous review of the possiblity of using Linux for our production environment, a couple of things I've found.
NFS works, but can cause lots of grief (file handle cache, etc.)
Their are apps that cause problems with ReiserFS (Qmail has to be patched)
Root filesystem is pretty iffy
None of the journaled filesystems support nfs locking, also using a journaled fs on the root partition is pretty much use at your own risk for all of the fournaled fs at this time. Qmail has some issues with synchronous tasks with ReiserFS (FAQ at Namesys explains this)
People are throwing up ReiserFS in front of me, when I say production Linux with lots of storage of storage (we deal in lots of terabytes here...) is a "no" right now. I just throw back that if I have to worry about the app not working with my filesystem and by the way don't do any writes over NFS, then I don't feel comfortable running it in production (not to mention that nasty root compromise with ReiserFS just a few weeks ago).
Don't get me wrong I'm running both XFS & ReiserFS currently and like both, but they ain't getting anywhere near my production EMC storage, until they grow up a bit more. (on a side note we are using Linux in production, but only on things with 50 gig of storage or less, and can sustain some downtime, with limited revenue loss)
Re:I know you're just a dumbass Troll
by
madking2099
·
· Score: 1
Agreed.
-- Well ladies and gentleman, assuming that such an endanger species somehow made it into this discussion......
Unfortunately the Linux kernel still does not comply with the principles of good kernel design highlighted in Tannenbaum's "Operating Systems Design And Implentation": the clean (and I do emphasize that that is important) implementation of a scheduler, memory managment aspects, IPC, device drivers etc.
Linus and Tanenbaum have had "discussions" over this before. See this archive. Some choice bits: Tanenbaum state Linux should have had a microkernel arcitecture. Linus replies with: "If the GNU kernel had been ready last spring, I'd not have bothered to even start my project". He wrote that in 1992. We still don't have a 1.0 Hurd release 9 years later. Another piece has Tanenbaum arguing that Linux is too closely tied to the x86 architecture, a valid point back then but amusingly shortsighted to us now.
You and Tanenbaum seem to share the belief that the architecture of the OS is the highest priority. Linus seems to focus instead on practicality and performance, although he does value architectural simplicity and elegance very highly too.
perhaps a CVS system instead of randomly throwing out tarballs....and a proper built-in kernel debugger. (Linus himself apparently dissaproves of things like this)
Linus has good reasons for the decisions he's made. You can read about them at Kernel Traffic. And in the end Linus appears to have been proven correct, after all Linux has far higher market share than the other OSes you mentioned: BeOS, QNX, and Plan 9.
but in matters such as this perhaps it's time he was overruled, in order to take the kernel onto the next level
There are people who agree with you (see the Buy Linus a Spine page), but no one has stepped up to the plate and tried to take over which I think indicates that most reasonable people are willing to live with Linus' "quirks" because his usually his ideas have turned out to be right.
Re:Interesting that you should say that.
by
RedWizzard
·
· Score: 3
all of the improvements and changes that I would make are things that HURD project pretty much has covered
This is exactly why your focus on architecture is wrong and Linus' focus on practicality is right. The HURD sounds fantastic in theory, but it's taken something like 12 years of development and they're up to 0.3 (or something). Linus OTOH was able to get Linux to the point where it was usable in a fairly short time.
Re:This kernel numbering is confusing
by
Some+Dumbass...
·
· Score: 1
Because the linux advocates constantly criticise microsofts service packs means of upgrading. Buy windows 2000 and you have to download 1 service pack and thats means its a terrible OS that needs constant patching. Download linux 2.4.0 then 2.4.1 and then 2.4.2 in less than half that timespan and rather than meaning that 2.4.0 was a terrible OS that needs constant patching it is an innovative OS with a rapid turnaround.
Am I the only one who spots the hipocracy here?
You're the only one who sees any hypocracy here, mainly because you're the only one who believes in that statement about Windows 2000 you made. The complaint I keep hearing about MS OSes is that they have bugs, and that you can't download patches for them until the next service pack arrives. Notice the difference between what I heard and what you've claimed. I don't think that anyone actually complains that MS OSes are buggy because you can only download patches as a big service pack. That complaint doesn't even make sense. But people do complain that 1) MS OSes are buggy and 2) They hate waiting for a service pack to get their patches for those bugs. The problem with Windows 2000 is that "it's a terrible OS which needs constant patching" but we can't constantly patch it, because there are no patches for many problems." Also, big service packs tend to create multiple new bugs, but that's another issue.
"Rapid turnaround" is the key here. We all want "rapid turnaround" for bug fixes. If a bug is out there, we want it fixed now! Which OS gives you this, Linux or Windows 2000 (gives you this more often, at least)?
Don't just go out and grab 2.4.2. Odds are you don't even need it. It's merely another stable release that spreads what Linux can run on.
If it ain't broke, don't fix it. Currently, 2.4.1 is the latest "something for everyone" kernel, and only because of a change in memory handling. Read the changelogs before downloading the kernels and see if there is anything you'll actually USE!
The problem with capped Karma is it only goes down...
-- SIG: HUP
Re:New 2.4.x Compilation issues under Debian unsta
by
garett_spencley
·
· Score: 5
You have a new version of binutils installed that handles the -o flag differently. You need to edit/usr/src/linux/arch/i386/boot/Makefile and change all -oformat to --oformat.
Aparently this has been known about for a couple weeks and a patch has been made but for some reason didn't make it in 2.4.2
Now, I know this probably is not the place to ask, but I would need the sym53c500 module for my PCMCIA SCSI card....Doesn't seem to be supported since 2.2.14...At least I don't manage to compile a tarball that I found for 2.2.14 under kernel 2.4.1 (Which doesn't surprise anyone)
I really use my SCSI card quite a lot, and a link would be most helpfull. I really get fed up dual booting W9x to backup my data:-(
Yes, I know...offtopic, sorry...
-- Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
Interesting that you should say that.
by
Cliffton+Watermore
·
· Score: 1
I have been thinking about starting a movement to do this. I even mentally mapped the areas of code I would being rewriting first. But when I pondered the matter further, I realized that all of the improvements and changes that I would make are things that HURD project pretty much has covered. I won't stop using GNU/Linux, but when the HURD is ready I would recommend checking it out.
-- "A few atoms won't even light a match" - Dr Jones, 1933
Re:Interesting that you should say that.
by
TOTKChief
·
· Score: 3
Ahhhh, but when the HURD is heard from, will the herd keep HURD from being heard?
Word. --
Unfortunately the Linux kernel still does not comply with the principles of good kernel design highlighted in Tannenbaum's "Operating Systems Design And Implentation": the clean (and I do emphasize that that is important) implementation of a scheduler, memory managment aspects, IPC, device drivers etc. I'm not bashing the kernel though, and I do use GNU/Linux extensively....
The only solution to the Linux kernel problem is a complete rewrite of the codebase. This will ensure that no messy code is left behind and that the kernel can effectively take on modern kernel implementations, such as BeOS and QNX, and Plan 9's kernel.
The current Linux codebase is good, but for it to be great, the developers must stop patting eachother on the back and start seriously thinking about proper change control - perhaps a CVS system instead of randomly throwing out tarballs....and a proper built-in kernel debugger. (Linus himself apparently dissaproves of things like this). Sure Linus has been invaluable to the success of the Linux kernel, but in matters such as this perhaps it's time he was overruled, in order to take the kernel onto the next level.
-- "A few atoms won't even light a match" - Dr Jones, 1933
Re:This kernel numbering is confusing
by
Decado
·
· Score: 5
Because the linux advocates constantly criticise microsofts service packs means of upgrading. Buy windows 2000 and you have to download 1 service pack and thats means its a terrible OS that needs constant patching. Download linux 2.4.0 then 2.4.1 and then 2.4.2 in less than half that timespan and rather than meaning that 2.4.0 was a terrible OS that needs constant patching it is an innovative OS with a rapid turnaround.
Am I the only one who spots the hipocracy here?
--
Slashdot: Proof that a million monkeys at a million typewriters can create a masterpiece
rotating disks cheap, solid state disks expensive
by
phr1
·
· Score: 1
I prefer to use solid state disks (CF card with PC card adapter) because I don't like the noise that a hard disk makes in my laptop in a quiet room. A 128 meg CF card is around $200. That's enough space for a reasonable Linux system and some user files, but not enough to let you be wasteful. So a compressed fs would be helpful.
Re:It's about freaking time!
by
Score+0
·
· Score: 1
There is support for the via82c686 in the 2.2.18 kernel and has been in 2.4.x since at least 2.4.0pre10 (that was the first one I tried).
Re:New 2.4.x Compilation issues under Debian unsta
by
BlowCat
·
· Score: 1
Re:This kernel numbering is confusing
by
update()
·
· Score: 2
In the linux world we have kernel releases more often. You can upgrade if you want to, if you are satisfied with the older kernel but need a bug fixed you can usually patch just that bug.
I don't know if that makes much difference. Let's say SP 1 == kernel x.y.1 through 5. How many people will be running x.y.5 without the changes introduced in the 2->3 transition? Yes, I know you can do it and yes, I know how to do it. But realistically there's almost no one doing that. For most users, using kernel x.y.z means using all the patches introduced between 0 and z.
Re:192 days? My MS Whistler has you beat
by
update()
·
· Score: 2
Huh?
How does the fact that an NT box somewhere has a 3 day uptime means the guy you're responding to doesn't have a 342 day uptime?
And why are you assuming that whatever web server Netcraft is tracking is part of the Datacenter Server setup that's supposed to be providing the 99.999% uptime?
Come on, my Linux box at home isn't even on now - does that mean Linux doesn't run at all?
Re:This kernel numbering is confusing
by
ackthpt
·
· Score: 1
That would be the job of RedHat, SuSe, Caldera, et al.;-)
--
--
A feeling of having made the same mistake before: Deja Foobar
...And A Patch Close Behind It.
by
Dr.+Dew
·
· Score: 3
Re:...And A Patch Close Behind It.
by
jeebee
·
· Score: 1
o Fix 4 misspellings of unneccessary (André Dahlqvist)
... but that's not how to spell unnecessary.
Sorry, I couldn't resist.
Best way of reporting problems
by
JayJayEm
·
· Score: 1
Having just got my aged P90 to compile 2.4.2, I was slightly disappointed to find that support for its equally aging SCSI card (AIC7xxx onboard) seems to have been broken.
Because I have upgraded straight from 2.4.0 (which worked fine) I am not sure whether this problem first surfaced in 2.4.1, because I can't find anything particularly SCSI controller specific in the.2 changelog.
It claims my controller is "disabled" during bootup (although it finds its IRQ), and then kernel panics with lack of a root file system.
I've never had compatibility problems with kernels before - where is the best place to report this issue?
It's about freaking time!
by
AFCArchvile
·
· Score: 1
- Vojtech Pavlik: update via82cxxx driver to handle the vt82c686
Yay, so FINALLY a Linux kernel will recognize my Celeron's chipset correctly. Microsoft got its 82c686 driver set finished about a year ago. That was back in the days of 2.2.14.
-- "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
Re:This kernel numbering is confusing
by
alen
·
· Score: 1
There is a reason it's huge. A MS Service pack will patch all versions of Windows. SP1 for Win2000 will patch Pro thru Advanced Server. And it has replacement files for all the components even if you don't have all of them installed.
I had just gotten my system all up on 2.4.1 from 2.2.x. What an experience it was getting the dsl/pppoe, iptables and nat all switched over. I saw the new 2.4.2 last night and was kind of pissed, wondering if 2.4.3 would be out before I got this one installed! But, I had my system patched and running in about an hour. It was rather pleasant knowing I had a kernel running just 2 1/2 hours after the thing was released.
"...the kernel can effectively take on modern kernel implementations, such as BeOS and QNX, and Plan 9's kernel."
Maybe they are too busy taking on operating systems that people actually use to worry about conforming to an academic's idea of how software should be architected..
That sounds like I'm advocating market share over correctness, but I'm not. I'm saying that "correctness" is in the eye of the beholder. And the beholders who agree with you and Tannenbaum haven't made much headway in the Real World whereas Linus has. --
http://www.geekizoid.com/article.pl?sid=01/03/03/1 346238&mode=thread
--
Non-meta-modded "Overrated" mods are killing Slashdot
(Hey Ryan! Here's your proof!)
Dude, don't pop a blood vessel in your forehead...
by
Nick+Driver
·
· Score: 1
Try SuSE 7.0. I used to be a Slackware fanatic, then I tried all the rest and settled on SuSE. I started with 6.1 and applied the upgrades one after another and now I'm up to 7.0 with the 2.4.0 kernel and I'm impressed with how the SuSE distro gets more and more refined with each release. Just like Humphrey Bogart's line in the old "African Queen" movie: "Them Germans, they lay down a system and they stick with it."
If you really want a free unix that works right out of the box with no headaches, try FreeBSD. It's a much more refined product than most all Linux distros. (let the flames begin:)
FreeBSD... different. (picture a Dodge car/truck TV commercial ripoff with little Chuck daemons dancing around instead of peppers)
Churning 'em out a little quick?
by
AlgUSF
·
· Score: 1
I am still walking my l4m3r friends through compiling 2.4.1.:-)
--
I want my rights back. I was actually using them when our government stole them after 9/11.
Re:192 days? My MS Whistler has you beat
by
Cap'n+enigma
·
· Score: 1
You use Whistler? And you call typical geek a loser? Read the blurb at the top, "News for Nerds. Stuff that matters."
Microsoft so doesn't matter!
Can't we ban these Microsoft idiots?
Mandrake has allowed RieserFS installs since at least version 7.1 in the ``expert'' install mode. [My laptop is currently drake 7.2 with ``RieserFS everwhere'' except for a 20M/boot.]
SGI provides a
Modified Red Hat 7.0 Installer that allows installing linux on top of their XFS filesystem. I haven't tried the XFS under Linux, but I've been impressed with XFS under IRIX. [One of the larger machines I currently admin has several terabyte-sized XFS filesystems.]
Re:192 days? My MS Whistler has you beat
by
hammock
·
· Score: 2
On http://www.microsoft.com/windows2000/guide/server/ solutions/overview/reliable/default.asp Microsoft explains how Windows 2000 is "Five nines 99.999% uptime", and on the right is a link to a Starbucks Windows 2000 study.
It goes on to say how much better the coffee is and how much happier customers are because of Windows 2000.
However, this is one of the sites that netcraft tracks for uptime.
Note: Uptime - the time since last reboot is explained in the FAQ
Plotted Value : Windows 2000
No. samples : 250
Max : 215.28
Latest : 3.18
3 days uptime is not something to brag about, Microsoft. Do some research before you stick your foot in your mouth, but only after shooting it.
Re:This kernel numbering is confusing
by
skt
·
· Score: 1
I remember when a M$ rep came to talk to our usergroup. He told us that the service packs for win2k would be under 5MB! It's not that I actually believed this guy though, so I guess I wasn't too surprised when the service pack came in at 85MB (or 17 times the promised size).
Re:This kernel numbering is confusing
by
skt
·
· Score: 1
yeah - just a few minor things like load balancing, memory support up to 64GB - you know the small stuff.
ahh, but besides a few registry entries and a couple of programs, win2k pro could do the same thing as advanced server. The EULA and the registry and the cost really ARE the biggest differences. Of course, Redhat has two different installs you can do depending on what the primary use of the machine will be (server or workstation), but the kernel and basic features (like memory support and load balancing) remain the same. In addition to that, linux distros do not intentionally cripple their installs just to force the user into paying them huge sums of money for an "advanced server".
I remember reading this. If memory serves, Tannenbaum was bitching that Linux wasn't a microkernel. The arguments have been made and repeated over and over. If someone doesn't like the Linux kernel, there is no reason why they can't use Hurd. But the next time someone says that Minix is so much better, tell them to read the book. I did. Tannenbaum's opinions are formost opinions and should be treated as such.
-- You are all fartheads.
This kernel numbering is confusing
by
typical+geek
·
· Score: 5
Why can't Linux just name it, like Linux 4, Service Pack 2?
Re:This kernel numbering is confusing
by
Flabdabb+Hubbard
·
· Score: 1
That would be true, if only there was an easy way to find out what kernal you are running. What command would tell me this. In Windoze it's easy, you click on my computer/properties/version and it tells you. How can you do this easily in Linux, without resorting to rocket science commands like awk and grep and sed ?
Re:This kernel numbering is confusing
by
Flabdabb+Hubbard
·
· Score: 1
This is not exacly intuitive though, is it ?
I mean, if the command was called something like 'kernalversion' and did not take an obscure argument '-r' WTF ?
I'm sorry but Linux has a long loooong way to go before it has the simplicity of Bill's (admittedly flakey) product.
Re:This kernel numbering is confusing
by
cavemanf16
·
· Score: 2
I think M$ already patented that form of naming an update. It is now illegal to say 'Service Pack' without agreeing to their EULA. Just kidding.:)
Re:Journaling Filesystems?
by
flynn_nrg
·
· Score: 1
He spelled it wrong, is actually called 'softupdates' and AFAIK is only available for FreeBSD.
That is the reason I switched over to linux. Linus and others make it a priority to fix *bugs* whatever they are in the code. Not merely spending time on surface issues that would affect *most* people. Every bug is important. Every change to the kernel that improves its functionality with obscure hardware is an improvement. My.02
I find it interesting that it took a relitivly large amout of time to finalize the 2.4.0 release, and now here we are around 2 months after the release and we already have 2.4.2.
Makes you wonder what linus was doing in those days leading up to the 2.4.0 launch;-)
> My MS Whistler has been up 342 days loser.
Cool. So you didn't apply any security patches. Can I have the IP of this machine, please ?
Cheers,
--fred
Am I the only one who spots the spelling error here?
all your this is slashdot not freshmeat are belong to us.
This just in...
Anyone remember how 2.2.2 was released on 2/2 (99)? That was insanely cool. Too bad they couldn't have waited until 4/2...
--
* CmdrTaco is an idiot.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
Oddly enough, I agree. I'm from the UK and I use UK spelling, but I've worked on a project where I had to correct my "honour" to "honor" because the standard was US spelling. This was a company founded in the UK with offices in the US, and I thought they made the right decision to standardise on US spelling. Er, I mean standardize.
--
Xenu loves you!
I was just thinking of how great a compressed filesystem would be, even given the CPU performance hit, but then a bit of nastiness hit me... how do you handle the case where someone goes in and changes a middle byte in a 200 MB file and the recompressed block won't fit back into its place? Do you just end up rewriting the whole file? Or are blocks in a list and you have a fragmented file (but then what's the point of compressing files if you'll just end up wasting space anyways)? I don't think a patch is going to do it, a whole new filesystem would be needed. I wonder how current implementations do it (say in Windows 2000)?
"Hot lesbian witches! It's fucking genius!"
Torvalds and Tannenbaum hashed out this argument long ago.
Tannenbaum lost . . .
hawk
This form of governmnet can only last until the hippo decides to sit on the horses . . .
hippocracy, n. The use of one hippo-like status (i.e., fat, bloated, and heavy) in the market to squish competitors. see also "Microsoft"
:)
hawk, who knows better than to flame spilling, but this was just to juicy
*cackles outrageously*
Somehow, I just don't see stability and me mixing. :)
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
It's good for Linus to want to keep the 2.4.x kernels stable, but at the same time, I don't want to "downgrade" to a later kernel. :)
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
2.5.2 (development kernel) is most likely going to lead to the 3.0 stable kernel. Skipping the ones you mention there.
I emailed him about that hours after he released the patch. No reply yet. :)
Jason.
Our (6-way) router has been experiencing stability problems for some time now. I upgraded to 2.4.2-pre4 after one of the ChangeLog entries caught my eye, and the stability problem went away. (I believe the problem was in the 3com drivers.) Finally I've found a stable kernel for our router. No more down time! :)
Jason.
Try O'Reilly.
---
But have you tried cramfs? It works pretty well for systems that are relatively static - I don't think you can use it on
...well, as soon as the loopback bug gets fixed.
---
http://www.google.com/search?q=cramfs
---
Yah, but turning off javascript means that a large number of sites will not work (Internet banking, webmail, auto-cursor focusing) All kinds of creature-features that I'm not willing to do without. I run Javascript under Win98, WinNT4, and Win2K with no problems. Now, if I could just get javascript to work reliably with Netscape 6 or Konqueror under Linux, talk about flaky. I hope changing to Mozilla .8 will help... I am sick of dual-booting and would like to just go for the Linux uptime record instead of rebooting every time I need to do something that I cannot do with Linux browsers... :(
The text login screen displays the kernel version. If you have your machine set to auto-start X, then hit CTRL-ALT-F1 to switch to text mode, look at the screen, then hit CTRL-ALT-F7 to switch back to X.
Exactly how long did it take you to figure that out? I'm sure it wasn't so intuitive that you just knew. First you have to know to right-click, rather than left-click, to get the properties menu. That alone is nothing I would call more intuitive than looking at the login screen (You don't even have to log in...) and about equal with the uname -r as far as intuitiveness.
Open you mind a bit, remember that there was a day that you were just as lost with Windows as you seem to be currently with Linux. You'll learn, it'll get easier.
They may not be able to make it fool-proof, but they can already use it to show proof of fools.
Sid is Debian's forever "unstable" release. The "testing" distribution is the one which will get a new name once "woody" is done. Ganesan
Actually, Internet Exploiter can handle gzip, as long as the web server specifies the MIME type correctly. This is how mod_gzip works. (Yes, they are slightly different things on the server side, but the same stuff happens on the client side.
What do you mean by feeding it locally? If you just opened the file with it, there was noone there to give it a MIME type.
I've compiled both 2.4.1 and 2.4.2 just fine with Debian unstable. I am completely up to date though - are you?
Ugh! It just hit me and I was up to date but not with debian.org but a mirror.
Troll, But I'm hungry.
The major problem people have with service packs is that they are huge.
A service pack is likely to introduce half the number of bugs it fixes, if you are unlucky one of the new bugs will affect you.
In the linux world we have kernel releases more often. You can upgrade if you want to, if you are satisfied with the older kernel but need a bug fixed you can usually patch just that bug.
You usually won't get much help from Microsoft unless you are running the latest service pack. If you don't they will tell you to install it.
There is another rather huge difference also, this is a kernel release. A Windows Service Pack can affect anything on the system while a kernel upgrade usually only affects the kernel.
Hi.
I'm not too sure what's going on, some can someone help me: I downloaded 2.4.2 and was hapily compiling it until at the end of "make bzImage" I got an error about ld not being able to find "binary." The line in the makefile was something along the lines of:
ld -elf [..] -s -oformat binary bootsect.s bootsect.o
(forgive me if I'm a little off, I'm away from the machine at the moment..)
I quickly flipped through the ld manpage and saw that -oformat is a valid option. I then tried recompiling 2.4.1 which I had installed cleanly when it came out and got the same problem. I looked at the Makefile in 2.2.18 and there is no -oformat for the ld call there.. at last I can still compile it..
Does anyone have any ideas about what my problem is? I don't know too much about the Gnu linker, but it looks like maybe the version in sid doesn't jove with the Linux kernel..
Help?
Ben
My girlfriend has informed me that Sid was the bad kid in the first movie. I haven't seen it though, so don't quote me on it..
Ben
Maybe, but it is beginning to appear not..... We have multiple SparcStations and PC's in our house, and until this week, on couple of PCs, We had Win2K/WinME and Linux Installed on separate carriage Hard Disks. Because when it came to certain things, still it was hard to beat Win2k. As a matter of fact , just for that reason, I had been a professional subscriber to MSDN. (Last update was just this January.) However after installing 2.4.1 and then 2.4.1 with KDE 2.1.x beta and loading the ALSA drivers ( now up to version 0.9), I am totally impressed. Now I can do things with my RME Hammerfall (full) , MidiMan DIO2448 , SBLive platinum and Ensoniq 1371 cards that I could not even dream of before. We started salvaging the HDs that win2k/Win98/WinME were taking and changing them into nfs shared disks. This is a diffusion equation with exponentially growing distributed sources. Any one with some physics/math background already knows that the outcome is inevitable. With the LiVid's latest DVD players, and Matrox's support for G400 dual head(one machine) and G450 dual head (in the other) and with my Sony PCG-XG18 and my wife's Fujitsu Lifebook, we are in heaven. However I will keep all the 600 or so MSDN CDs and 50 or so MSDN DVDs for future reference. As it stands now they are relegated to the upper shelf ( and yes I did see a whistler beta there, but frankly I don't care anymore. Not with ASP/.NET concept and the secure path .... I even stopped downloading Win2k updates after they screwed up my multi region DVD player hw/sw...) I basically do not trust any closed source s/w anymore. The last s/w I am ordering is Mathematica 4.1 , but I am also coming up on Maxima (open source Macsyma). I already use {Star,Open}Office. Word 2000 came with my Sony PCG-XG18, but I never installed it. StarOffice/Cygwin/Forte/Netbeans catered to every need I had on Win2k, and they do just fine on Linux. Oh BTW, Konqueror is great. Now I no longer need Netscape or IE either....
YMMV
sinan
The 2.4.1ac series included a couple of fixes for the Matrox G450 card. The changelog for 2.4.2 says "sync up more with Alan", but it doesn't say what changes were sunc. How can I find out if the Matrox fixes went in or not?
Thanks,
Stuart.
Furthermore, you can't run NFS of a ReiserFS partition yet
I could swear that I was sharing a couple of ReiserFS volumes over NFS last summer... Yeah, I must've, because the whole lab ran exclusively Reiser (installed with SuSE). NFS doesn't care what file system is below it, it's a user-space thing (except when it's a kernel-space thing, in which case it still shouldn't even know what FS is underneath it).
Doh. I seem to have forgotten about ""
/comments.pl in order to allow everyone to have a fair chance to post.
BTW, what's up with this:
Slow down cowboy!
Slashdot requires you to wait 1 minute between each submission of
It's been 1 minute since your last submission!
It all depends on what you want to spend your money on, or what you happen to have a surplus of. Processing power or disk space.
If your webserver is so busy that a compressed filesystem adversely affects your performance, then obviously a compressed filesystem would be a poor choice. On the other hand, if you have a very lightly used web server with a large volume of data, then it might be a good idea.
Nice to have the option
Don't forget web pages! Those are generally stored uncompressed, and a large web site can literally have gigs of HTML files.
If you know C++, then C's easy. It's just C++ without all the good parts.
No problem here. I compile my kernels using gcc 2.95.2 (from Debian potato).
I don't think you can compile it with the 'new' compiler that came with Redhat 7.0, but I'm not sure.
Je ne parle pas francais.
ReiserFS is generally stable and works for most persons without any trouble. I've been using it for months now on my desktop and I'm really impressed with it. Pressing reset almost becomes fun ;-)
However, last time I checked, ReiserFS didn't support quota (this may have changed, I'm sure patches exist). It also doesn't support a bad-block map, so be carefull with partially damaged harddisks.
Furthermore, you can't run NFS of a ReiserFS partition yet.
ReiserFS is very fast. You can really notice difference to ext2, mainly in large directories.
This is your sig. There are thousands more, but this one is yours.
First, try 2.4.1. Knowing if 2.4.1 works for you is fital in finding the bug.
Then, when you know what version broke the driver, you may or may not investigate further on your own. You might want to try some 2.4.2-preX kernel to futher pin down the breakage.
Eventually, just file a bug report to the Linux kernel mailing list. Be sure to be as accurate as possible: describe your hardware and the symptoms as exact as possible.
This is your sig. There are thousands more, but this one is yours.
I actually have a few systems set aside for the following at home:
Open BSD 2.7, FreeBSD, and perhaps NetBSD if I have the time (Then again, I might make it a Solaris box).
I am unfamiliar with BSD, hence why I wish to try it, what are softdeps? The term reminds me of "symlink" for some reason (as in the way a symlink appears on the inode table).
Try to hack my 31337 firewall!
Ummm SUSE already has a 2.4 distro out.
Adults are obsolete children. - Dr. Seuss
What hypocrisy?
Windows service packs affect more code than just the kernel. They don't allow me to selectively fix what I want, either. And they tend to break more than they fix.
With the linux kernel updates I can update just the kernel, rather than the kernel, the webserver and the kitchen sink. If I want to upgrade the webserver I'll do that separately, thank you. Also, I honestly see fewer changes in between 2.4.1 and 2.4.2 (or 2.4.0 and 2.4.2, really) than the average service pack fixes.
It isn't about how often updates are required, it's about whether those updates are out when I need them (esspecially security fixes) and how much control I have over running them. And not breaking more stuff.
i think you should be looking at the mode rather than the average file size to determine savings to be had from shrinking blocksize. consider the situation in which you have 1e7's of 10-byte long files and a couple 1e9-byte files.
--Phil
Boy, you've got a slow system if it takes you two months to compile three releases. Maybe if you invest in some more RAM or faster hard disks, you won't have this problem.
The other alternative is to stick with 2.2.19 or 2.0.39.
I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
It's not the size, it's how you use it.
--
--
"Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
Bullshit.
You can't buy Whistler at Fry's or anywhere else. You'll never be able to buy Whister... only Windows XP. Unless you're using some weird pre-alpha, Whistler builds haven't even been around for 342 days.
Okay, I'll bite.
The benefits of linux release methodology over the Microsoft release methodology:
- I can quickly get a sense of what is being improved with each kernel release by looking at the changes notice that is included with each kernel.
- I can find in depth discussion of some changes by following the kernel development list or the major discussion by reading the kernel traffic summaries that are published weekly at http://kt.zork.net/kernel-traffic/latest.html
- I can go read the code in the kernel to try to discern what is going on
- I can try to contact a kernel developer directly to seek information on a particular improvement
- I can offer my own improvements to the code
- I can tell what the benefits or a particular improvement are and who will benefit from this improvement
- I do not have to blindly go forth into the mire of a service pack and hope that it fixes a problem in a correct and well thought out manner and hope that it truly offers a benefit and does not only serve the interests of one entity
Does this mean that some bad ideas don't get brought into kernel releases? No. Does this mean that I have to expend less effort in deciding upon and then executing a update of my system? No. But I do have more tools available and better information to help me to decide if this is the right decision.
this space intentionally left blank (oops)
Includes
And this really doesn't give me much to chomp on with regard to if this is a good idea for my system. And considering that I may not be running exchange, may not be serving NNTP, and may not be running two virtual NNTP servers on my box, is this something that I need anyways? And how do I judge this on it's merits? There is little diagnostic information available and basically they ask for blind trust in a situation which time and time again they have shown that they are not deserving of it.
this space intentionally left blank (oops)
> So, if you're not running Exchange and don't have two virtual NNTP servers, then the bug does not affect you.
Then why should the solution?
> You can understand kernel source code, but can't read English. Are you a bot?
Yes, ofcourse I'm a bot. In fact, I'm the first bot to be able to understand kernel source code and evaluate it's effectiveness for use. You should fear for your job!
this space intentionally left blank (oops)
One of the reasons 2.4.0 was released when it was was to get a larger base of testers. Distros aren't goint it use 2.4 for a while yet, RedHat started using 2.2.0 (and 2.2.1/2.2.1 were released pretty quickly after 2.2.0..)
Uhhh...it *IS* out of experimental. It was included in 2.4.1 production. I migrated my home machine and my webserver over to it. No fsck is a good thing especially when your home machine locks up from a buggy nvidia x driver ;) hehehe
"Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
cpeterso
I've heard the Debian's next release is codenamed Sid, but which Toy Story character was Sid? I've never seen the movies.
cpeterso
Whistler Beta 1?
cpeterso
If you'd prefer that they slow down the release cycle and include more changes in each release, then just install every other kernel.
Staying on the bleeding edge does sting, that's why they call it that...
Kevin Fox
--
Kevin Fox
> o Fix 48 misspellings of interrupt (André Dahlqvist)...
Maybe they need to add a make spellcheck step to kernel compilation.
--
Sheesh, evil *and* a jerk. -- Jade
I speak for people with small drives everywhere when I say:
When will the kernel support default compression of filesystems.
The death of one man is a tragedy; the death of a million is a statistic --Joseph Stalin
"Well bitch, don't be so fucking lazy and code it up yourself. Isn't that the beauty of Open Source? "
Well bitch here's the rundown.
1. learning all the ins and outs of the kernel is a full time job in itself. I don't have the time to spend 6 months learning exactly what goes where.
2. C coding is not taught in any standard form in current university settings. I have learned Pascal, C++, bash, ksh, and csh but I never touched C because it wasn't formally taught.
3. Writing kernel code is approximately 200% harder and more precise than writing an application program.
4. I don't have expertise levels of OS design.
Those things being stated I feel that at least on the surface once those things have been removed it wouldn't take say Linux or Alan Cox much more than 5 minutes of their time to get it working once and for all. Basically you just have something sitting above the call to storing or writing data and have your favorite compression algorithm there to act as an intermediary.
I hope this is more lucid than your reply.
The death of one man is a tragedy; the death of a million is a statistic --Joseph Stalin
Maybe you should read the the announcements that come with every kernel release before proclaiming that:
Don't just go out and grab 2.4.2...
From Linus's announcement:
The IDE driver bug that Russell found has, to my knowledge, never been shown to happen on anything but his ARM machine, but for all we know it could be quite bad even on x86. Similarly, the elevator bug could cause corruption, but probably has not actually bit people in practice. But both are definitely deadly...
I don't know about you, but I think this may be significant and worth the upgrade if you use IDE in your systems.
Remembering your name in the morning is already a good start...
Does anyone know if 2.4 still requires an old version of gcc?
Or; can anyone confirm that I'm "safe" when compiling to the i686 target with gcc 2.95.2?
/ Peter Schuller
--
peter.schuller@infidyne.com
http://www.scode.org
It certainly wasn't out of it in my copy of 2.4.1.
Unless the Debian guys put it back in.
/ Peter Schuller
--
peter.schuller@infidyne.com
http://www.scode.org
body to body
headhunter
serial killers don't kill their boyfriends
this is the version i'll run forever now.
<duck>
I'm a leaf on the wind. Watch how I soar.
Although it's only just gone into the kernel in 2.4, reiserfs has been stable and working for a while, and is already included in a number of distros.
I use Mandrake 7.1 (current is 7.2) which has reiserfs - I use it for all my non-root filesystems to avoid the fsck checks.
but it is how to spell 'unneccessary'
Old Joke
Teacher: 'Johnny, how do you spell cat?'
Johnny: 'K A T'
Teacher: 'That doesn't spell cat'
Johnny: 'well, what does it spell?'
It works better if you say it out loud.
MrCreosote Meow!Thump!Meow!Thump!Meow!Thump! "You're right! There isn't enough room to swing a cat in here!"
Glad to hear that you are going to do the rewrite. The source is all there. Are you setting up your efforts on sourceforge or will you just announce it view usenet ala Linus?
heh. can't forget the "older" kernels. does 2.2.22 count? how bout 2.0.102 ? :)
--- this comment is presented in WIDE SCREEN STEREO!!!
I hope you're not being serious.
How is following a path of clicks and right clicks any more "intuitive" than using 'uname'? That's ludicrous.
MAN are you DULL.
As my father lik@(munch munch)...
Actually the parent was modded down, so it could look like I replied to the original thread MOTHER.
Perhaps THIS is what INCURRED your response?
As my father lik@(munch munch)...
Technically if you go by the Greek roots, a hippocracy would be a government under the rule of a horse or a body of horses.
----
"Here to discuss how the AOL merger will affect consumers is the CEO of AOL."
grep -ri 'should work'
Now if only you could spell it.
Slashdot - the place where you can look like a genius by restating the obvious
I had the same problem, and unless something was upgraded in the last 2 hours I am in fact completly up to date.
treke
Some of the developers may use cvs on the sections they maintain, but eventually it all has to be sent in the form of patches to Linus who merges together the official tree using whatever voodoo he uses to manage all of the updates.
treke
.........and a serious mp3 collection is allready compressed. Any compressed fs is not going to get much more out of it.
PPPPPPPPpppppfffffffffffzz.............
Maybe you live in interesting times
after reading the changelog, I dont see EXT2 corruption mentioned anywhere..... where did you get that from?
I spent almost a week downloading Red Hat's 2.4.0 beta and getting it installed (all I really wanted was iptable support). And, after getting it installed and customizing it so it would actually work (Hey! It's a beta distro...) I was amazed at the overall speed and performance. But, iptables would not work (xinetd required a backpedel to an earlier version) and I was forced to use IPChains. As it is, the box is still sitting behind my firewall rather that on the front line.
Downloaded 2.4.1 and tried to compile it. It broke things in the RD distro. Downloaded the most current iptables and recompile the 2.4.0-99..whatever RH kernel. iptables still would not work.
Today, out of a whim, I downloaded and recompiled 2.4.2. Not only did it compile without any issues, but iptables works as well (imagine that).
Can't wait to see tomorrow if, when I reboot, that it tells me nfsstatd didn't start like 2.4.0 and 2.4.1 did when I recompiled. Well, I gotta see, recompiled the kernel from home and it just sounds too good to be true.
RD
The reason, which you and the people who replied to you seem to have missed, is because Microsoft said themselves that Windows 2000 would never required fixes. They lied to the corporate managers and other people who choose what to run on the servers in order to get more money.
That is what people don't like about MS Win2k. Linus never claimed that 2.4.0 would be bugfree (or if he did, he did it tongue-in-cheek). If MS had more truth in their advertising, I know I'd be happier.
--
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
Give us a break. The whole point of linux is "do what works" not "do what's propper." Not to mention, why don't you quit gabbing about it and do it yourself. That's the beauty here. If you think Linus is doing an ass job, he actively encourages you to try and do better. You don't have to overrule him to make some changes, you just do it.
Someone you trust is one of us.
If I'm not mistaken, Debian does that at least to some degree... which means there is a whole distribution's worth of people doing that.
When will Reiser FS (or any other journaling fs) be out of the experimental stage?
I'm tired of fsck (not that I see it often...)
Sticking feathers up your butt does not make you a chicken - Tyler Durden
You still have to select "Prompt for development and/or incomplete code/drivers" to even get the option to build Reiser FS.
If it's stable then why is this?
Maybe I'm missing something, if so just let me know.
Sticking feathers up your butt does not make you a chicken - Tyler Durden
You still can't play any cool games from the $10 bin at Bestbuy/CompUSA though.
This post brought to you by your friendly neighborhood MBA.
Well, 2.4.2 fixes the ext2 filesystem corruption problem. Lots of people run ext2 :)
Ideology breeds Hypocrisy. Just how much is up to you.
The kernel traffic editions since the release of 2.4.0. It's talked about as 'filesystem corruption', and was tracked to the VM (IIRC).
Ideology breeds Hypocrisy. Just how much is up to you.
.technomancer
.technomancer
.technomancer
.technomancer
someone mod Androsyn up! the original poster is clearly a troll and has never read Linus famous arguements with Tannenbaum.
see the archive at ORA
Could have something to do with the fact that his wife, Tove, was pregnant and gave birth in late November I believe. I think that would take a bit more priority over tbe release of 2.4.0
Obviously you never read the flame war between Tannenbaum and Linus that took place in 1991. Theoritical design is one thing, but writing something that works and works well is another.
But, if you don't like how things are going with the linux kernel, nobody is stopping you from starting your own fork of the linux kernel. Import the whole source tree into your own CVS repository, get some developers and get some work done.
Just for the record, if someone was curious as to exactly what was fixed in a Windows service pack they could go to The Windows Service Pack Home Page and from there see What was fixed in Win2K Service Pack One which plainly lists problems with a detailed description.
rob.
Yeah, he said javascript DEBUGING.
So, if you're not running Exchange and don't have two virtual NNTP servers, then the bug does not affect you.
You can understand kernel source code, but can't read English. Are you a bot?
In the changelog it says "USB and Firewire updates". Does this mean IEEE1394 patches are now included in the kernel source so this actually works.
Ciao
----
FB
Let's see if we can flood the download mirrors by all downloading the kernel at once!!!
Yaaaaay!
-- Sometimes you have to turn the lights off in order to see.
Don't just go out and grab 2.4.2. Odds are you don't even need it. It's merely another stable release that spreads what Linux can run on.
You haven't read the fscking Changelog have you?! 2.4.2 fixes a serious IDE multimode write bug. If anyone has even somewhat-modern IDE hard drives in their system, it is certainly worth their while to get it.
I think SCSI-only boxen can wait, though -- but Linux was (and still is, to a degree) all about Unix on low-cost x86 hardware, so methinks there be plenty of IDE-based Linux systems around...
--
From the changelog:
-pre2:
- Russell King: fix serious IDE multimode write bug!
If you have IDE hard drives, I recommend you pop 2.4.2 into place purdy quick. Write bug == bad.
--
Maybe you're right, maybe I do just know where the workarounds are under Linux. But that does come back to Linux's basic openness...there are lots of diagnostic tools available (ps, strace, ltrace, gdb, lsof, netstat, lspci, /proc, etc) and the source is available, so it's very, very easy to see what's going on in the system and where problems are. So if I do know where the workarounds are under Linux...I think that's why. Windows just doesn't ship out of the box with those kinds of tools. Some I've managed to find (PrcView is a decent approximation of ps, for example), some I haven't.
As to my specific problems...I just checked, the "JavaScript debugging disabled" option is on. I assume that means debugging is disabled. So, that doesn't seem to be my problem, but thanks anyway.
For the curious, here are a couple of the weird problems I'm having with IE5.5 right now:
Buy windows 2000 and you have to download 1 service pack and thats means its a terrible OS that needs constant patching. Download linux 2.4.0 then 2.4.1 and then 2.4.2 in less than half that timespan and rather than meaning that 2.4.0 was a terrible OS that needs constant patching it is an innovative OS with a rapid turnaround. Am I the only one who spots the hipocracy here?
I see no hypocrisy.
First, when I make a judgement like that about a Microsoft product, it's not because of the number of service packs. I realize that all software of that complexity has bugs. It's instead that their software doesn't work well for me, even after applying all the service packs. Their service packs just don't seem to fix all the important problems for me, no matter how many I apply. For example, I've patched my Windows 98 system to the latest Windows Update stuff, but I'm still having some weird problems with Internet Explorer.
Second, Linux x.y.z releases are not just bugfix releases. In this case, it probably is...x.y.[1-5] typically are. But there are many new features introduced in point releases. 2.2.18 (or was it 2.2.19?), for example, backported USB support to the 2.2 series. I see a lot of important new features introduced in new Linux point releases, which I don't see in Windows service packs. Having a specific x.y just means the basic architecture is constant, not that the feature set is.
Third, as someone else mentioned, you don't need to upgrade to a new kernel revision to fix a bug. You have the source code, and you have the full patches. If you just want to fix one bug, you can do that. You don't have that option with Microsoft code, since it's not open-source.
Netware has a compressed file system that works very well. It background compresses files that have not been accessed in x hours/days. When read access to a compressed file is necessary, one of two events occurs. If the file has been read accessed less than y times in z hours/days, the file is uncompressed to a temporary space and deleted a while later. If the file is accessed y times, the file is uncompressed and remains that way until the initial compression criteria is again met. This works extremely well, frequently accessed files are not compressed and the space used by infrequently accessed files is minimized.
maru
windows 2000 is a finished, final product. they said, hey, we're done. this to me seem a promise, that it is finished. i understand of course that nothing is ever bug free, and patches are expected. but.... i doubt that microsoft tells you, 'hey, this is still under development, expect major bugfixes all the time!'.
-------
-------
"don't smoke, don't drink, don't fuck
at least i can fucking think"
Minor Threat
Ummm....releasing the 2.3.x series at about this same pace?
Looking at some of these other posts you'd think it were a bad thing to have bug fixes and updates in a timely fashion.
forgot 02.4.20
Je t'aime Stéphanie
until 2.5.2 (or 3.0.3)
Je t'aime Stéphanie
Read the Kernel Traffic and find out!
Too ... many ... patches ....... system ... always ... compiling ....
SLOW THE HELL DOWN OVER THERE!!!!
Geez, these kernels just keep popping out. Can you folks give us a month or two to get used to 'em first?
Like you can't have 10 simultaneous connections on NT4 Workstation, but if you buy Server... That's the hardest part of building an NT server for me. I can configure DNS, DHCP ,etc, but I can never remember if I want per seat licensing or whatever.
Back to the topic though, what is up with the frequency of these releases? 2.4-test releases never came out so quick, and the changelogs aren't that long. Just curious, is it customary to release a slew of maintenance releases weeks after an x.x.0?
chris@xanadu:~$ whatis /.
/.: nothing appropriate.
apropos kernel (gives a list of manpages that have information about the kernel)
in the list you'll see:
uname (2) - get name and information about current kernel
then of course:
man uname
etc...I'd say that's more intuitive, next apropos rocketscience...
chris@xanadu:~$ whatis /.
/.: nothing appropriate.
André Dahlqvist is fusing the line between English major and CS major.
"My mother never saw the irony in calling me a son-of-a-bitch." - Jack Nicholson
Rocket science?
No, a simple "uname -r" will suffice.
--
Soma: because a gramme is better than a damn.
I knew uname returned system information, but I didn't know what option to use for just the kernel version. However, here's a very simple way to find things like that. The --help option is fairly universal, so I just looked at the help output and found my answer in a matter of seconds.
And anyway, if you're using GNOME, you can check your kernel name/version, dist version, processor type, your username, and your hostname by looking that the main screen of the GNOME Control Center (gnomecc).
I would bet money that KDE gives similar information in it's incarnation of a UI preferences system.
--
Soma: because a gramme is better than a damn.
.. still appears to be broken :-/
/neurox
"Do not meddle in the affairs of wizards, for they are subtle and quick to anger."
*nt*
If you are truly being serious, the reason is because a kernel number makes it MUCH easier to understand the sort of kernel you are using.
The first number is a major code change, fundamental in nature. After about 7 years we are now up to 2.x.x. The second number also shows major revisions, but of a less fundamental variety than the first number. An odd second number denotes a development series, not intended to be used for production computers. This is why most users went from 2.0.x to 2.2.x to 2.4.x, because 2.1.x and 2.3.x were development versions. When the development version is deemed stable enough to be used in some production platforms, it moves to an even second number, like the recent 2.4.0. However, the 2.2.x kernel series is still being maintained for use as an ultra-stable kernel, while the 2.4.x is more cutting-edge for the latest hardware support and performance.
The third number indicates a small change, usually bugfixes but some small amounts of new features supported. When going to purchase new hardware it is easy to tell if you have a "2.2.0 or later kernel".
Finally, a service pack generally implies a large set of bugfixes, as Microsoft had somewhere around 7 (maybe 8) for NT 4. The Linux Kernel version system allows for a few small changes to be made at every release, decreasing the waiting time for users to wait for a desired bugfix or feature (instead of months for a new service pack).
If my overgeneralization of the Linux kernel was incorrect, my apologies, but I think an overall understading of how the Linux Kernel numbering system works is important for those who don't know yet.
"The universe seems neither benign nor hostile, merely indifferent." --Carl Sagan
That said, I'm a happy Linux user who just wants his OS of choice to be intelligently defended...
MS engineers are carefully sheilded from the public for this sort of reason.
'There is a Light that never goes out.'
I am 95% sure that you have debug on javascript option enabled. TURN IT OFF (it doesn't do what you think it does anyway). I used to have all kinds of flakiness with IE in Win 98 until I learned of that problem (it comes disabled by default, I turned it on thinking it did something different than what it does, should have rtfm).
I'm not chiding you, but most linux people I know read all sorts of stuff about how to workaround problems in linux. I know very few people who are willing to put forth that effort in Windows. Both linux and windows are extremely buggy. I suspect the bug metrics for both pieces of software are similar. My guess is OpenBSD probably has much better metrics -- mind you I can handle the bugs and so I run both Win 98 and linux.
Clearly, you and I had different degrees of flakiness in mind. I'm sorry that I can't help you.
Having just gone through a fairly rigorous review of the possiblity of using Linux for our production environment, a couple of things I've found.
NFS works, but can cause lots of grief (file handle cache, etc.)
Their are apps that cause problems with ReiserFS (Qmail has to be patched)
Root filesystem is pretty iffy
None of the journaled filesystems support nfs locking, also using a journaled fs on the root partition is pretty much use at your own risk for all of the fournaled fs at this time. Qmail has some issues with synchronous tasks with ReiserFS (FAQ at Namesys explains this)
People are throwing up ReiserFS in front of me, when I say production Linux with lots of storage of storage (we deal in lots of terabytes here...) is a "no" right now. I just throw back that if I have to worry about the app not working with my filesystem and by the way don't do any writes over NFS, then I don't feel comfortable running it in production (not to mention that nasty root compromise with ReiserFS just a few weeks ago).
Don't get me wrong I'm running both XFS & ReiserFS currently and like both, but they ain't getting anywhere near my production EMC storage, until they grow up a bit more. (on a side note we are using Linux in production, but only on things with 50 gig of storage or less, and can sustain some downtime, with limited revenue loss)
Agreed.
Well ladies and gentleman, assuming that such an endanger species somehow made it into this discussion......
You and Tanenbaum seem to share the belief that the architecture of the OS is the highest priority. Linus seems to focus instead on practicality and performance, although he does value architectural simplicity and elegance very highly too.
Linus has good reasons for the decisions he's made. You can read about them at Kernel Traffic. And in the end Linus appears to have been proven correct, after all Linux has far higher market share than the other OSes you mentioned: BeOS, QNX, and Plan 9. There are people who agree with you (see the Buy Linus a Spine page), but no one has stepped up to the plate and tried to take over which I think indicates that most reasonable people are willing to live with Linus' "quirks" because his usually his ideas have turned out to be right.Because the linux advocates constantly criticise microsofts service packs means of upgrading. Buy windows 2000 and you have to download 1 service pack and thats means its a terrible OS that needs constant patching. Download linux 2.4.0 then 2.4.1 and then 2.4.2 in less than half that timespan and rather than meaning that 2.4.0 was a terrible OS that needs constant patching it is an innovative OS with a rapid turnaround.
Am I the only one who spots the hipocracy here?
You're the only one who sees any hypocracy here, mainly because you're the only one who believes in that statement about Windows 2000 you made. The complaint I keep hearing about MS OSes is that they have bugs, and that you can't download patches for them until the next service pack arrives. Notice the difference between what I heard and what you've claimed. I don't think that anyone actually complains that MS OSes are buggy because you can only download patches as a big service pack. That complaint doesn't even make sense. But people do complain that 1) MS OSes are buggy and 2) They hate waiting for a service pack to get their patches for those bugs. The problem with Windows 2000 is that "it's a terrible OS which needs constant patching" but we can't constantly patch it, because there are no patches for many problems." Also, big service packs tend to create multiple new bugs, but that's another issue.
"Rapid turnaround" is the key here. We all want "rapid turnaround" for bug fixes. If a bug is out there, we want it fixed now! Which OS gives you this, Linux or Windows 2000 (gives you this more often, at least)?
If it ain't broke, don't fix it. Currently, 2.4.1 is the latest "something for everyone" kernel, and only because of a change in memory handling. Read the changelogs before downloading the kernels and see if there is anything you'll actually USE!
The problem with capped Karma is it only goes down...
SIG: HUP
Aparently this has been known about for a couple weeks and a patch has been made but for some reason didn't make it in 2.4.2
--
Garett
Now, I know this probably is not the place to ask, but I would need the sym53c500 module for my PCMCIA SCSI card....Doesn't seem to be supported since 2.2.14...At least I don't manage to compile a tarball that I found for 2.2.14 under kernel 2.4.1 (Which doesn't surprise anyone) :-(
I really use my SCSI card quite a lot, and a link would be most helpfull. I really get fed up dual booting W9x to backup my data
Yes, I know...offtopic, sorry...
Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
"A few atoms won't even light a match" - Dr Jones, 1933
"A few atoms won't even light a match" - Dr Jones, 1933
Because the linux advocates constantly criticise microsofts service packs means of upgrading. Buy windows 2000 and you have to download 1 service pack and thats means its a terrible OS that needs constant patching. Download linux 2.4.0 then 2.4.1 and then 2.4.2 in less than half that timespan and rather than meaning that 2.4.0 was a terrible OS that needs constant patching it is an innovative OS with a rapid turnaround.
Am I the only one who spots the hipocracy here?
Slashdot: Proof that a million monkeys at a million typewriters can create a masterpiece
I prefer to use solid state disks (CF card with PC card adapter) because I don't like the noise that a hard disk makes in my laptop in a quiet room. A 128 meg CF card is around $200. That's enough space for a reasonable Linux system and some user files, but not enough to let you be wasteful. So a compressed fs would be helpful.
There is support for the via82c686 in the 2.2.18 kernel and has been in 2.4.x since at least 2.4.0pre10 (that was the first one I tried).
It's in patch-2.4.2-ac1
I don't know if that makes much difference. Let's say SP 1 == kernel x.y.1 through 5. How many people will be running x.y.5 without the changes introduced in the 2->3 transition? Yes, I know you can do it and yes, I know how to do it. But realistically there's almost no one doing that. For most users, using kernel x.y.z means using all the patches introduced between 0 and z.
How does the fact that an NT box somewhere has a 3 day uptime means the guy you're responding to doesn't have a 342 day uptime?
And why are you assuming that whatever web server Netcraft is tracking is part of the Datacenter Server setup that's supposed to be providing the 99.999% uptime?
Come on, my Linux box at home isn't even on now - does that mean Linux doesn't run at all?
--
A feeling of having made the same mistake before: Deja Foobar
Alan Cox is doing that voodoo he do do: LWN report on 2.4.2ac1. Also, the ftp link.
More on 2.4.2 from the LWN is here.
Having just got my aged P90 to compile 2.4.2, I was slightly disappointed to find that support for its equally aging SCSI card (AIC7xxx onboard) seems to have been broken.
.2 changelog.
Because I have upgraded straight from 2.4.0 (which worked fine) I am not sure whether this problem first surfaced in 2.4.1, because I can't find anything particularly SCSI controller specific in the
It claims my controller is "disabled" during bootup (although it finds its IRQ), and then kernel panics with lack of a root file system.
I've never had compatibility problems with kernels before - where is the best place to report this issue?
Yay, so FINALLY a Linux kernel will recognize my Celeron's chipset correctly. Microsoft got its 82c686 driver set finished about a year ago. That was back in the days of 2.2.14.
"Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
There is a reason it's huge. A MS Service pack will patch all versions of Windows. SP1 for Win2000 will patch Pro thru Advanced Server. And it has replacement files for all the components even if you don't have all of them installed.
I had just gotten my system all up on 2.4.1 from 2.2.x. What an experience it was getting the dsl/pppoe, iptables and nat all switched over. I saw the new 2.4.2 last night and was kind of pissed, wondering if 2.4.3 would be out before I got this one installed! But, I had my system patched and running in about an hour. It was rather pleasant knowing I had a kernel running just 2 1/2 hours after the thing was released.
how can the windows wistler have over 300 days uptime, its still hasn't finnished booting
"...the kernel can effectively take on modern kernel implementations, such as BeOS and QNX, and Plan 9's kernel."
1 346238&mode=thread
Maybe they are too busy taking on operating systems that people actually use to worry about conforming to an academic's idea of how software should be architected..
That sounds like I'm advocating market share over correctness, but I'm not. I'm saying that "correctness" is in the eye of the beholder. And the beholders who agree with you and Tannenbaum haven't made much headway in the Real World whereas Linus has.
--
http://www.geekizoid.com/article.pl?sid=01/03/03/
Non-meta-modded "Overrated" mods are killing Slashdot
(Hey Ryan! Here's your proof!)
Try SuSE 7.0. I used to be a Slackware fanatic, then I tried all the rest and settled on SuSE. I started with 6.1 and applied the upgrades one after another and now I'm up to 7.0 with the 2.4.0 kernel and I'm impressed with how the SuSE distro gets more and more refined with each release. Just like Humphrey Bogart's line in the old "African Queen" movie: "Them Germans, they lay down a system and they stick with it."
:)
If you really want a free unix that works right out of the box with no headaches, try FreeBSD. It's a much more refined product than most all Linux distros. (let the flames begin
FreeBSD... different. (picture a Dodge car/truck TV commercial ripoff with little Chuck daemons dancing around instead of peppers)
I am still walking my l4m3r friends through compiling 2.4.1. :-)
I want my rights back. I was actually using them when our government stole them after 9/11.
You use Whistler? And you call typical geek a loser? Read the blurb at the top, "News for Nerds. Stuff that matters."
Microsoft so doesn't matter!
Can't we ban these Microsoft idiots?
Mandrake has allowed RieserFS installs since at least version 7.1 in the ``expert'' install mode. [My laptop is currently drake 7.2 with ``RieserFS everwhere'' except for a 20M /boot.]
SGI provides a Modified Red Hat 7.0 Installer that allows installing linux on top of their XFS filesystem. I haven't tried the XFS under Linux, but I've been impressed with XFS under IRIX. [One of the larger machines I currently admin has several terabyte-sized XFS filesystems.]
On http://www.microsoft.com/windows2000/guide/server/ solutions/overview/reliable/default.asp Microsoft explains how Windows 2000 is "Five nines 99.999% uptime", and on the right is a link to a Starbucks Windows 2000 study.
r bucks.com indeed says "The site www.starbucks.com is running Microsoft-IIS/5.0 on Windows 2000." not a big surprise.
It goes on to say how much better the coffee is and how much happier customers are because of Windows 2000.
http://uptime.netcraft.com/up/graph/?host=www.sta
However, this is one of the sites that netcraft tracks for uptime.
Note: Uptime - the time since last reboot is explained in the FAQ
Plotted Value : Windows 2000
No. samples : 250
Max : 215.28
Latest : 3.18
3 days uptime is not something to brag about, Microsoft. Do some research before you stick your foot in your mouth, but only after shooting it.
I remember when a M$ rep came to talk to our usergroup. He told us that the service packs for win2k would be under 5MB! It's not that I actually believed this guy though, so I guess I wasn't too surprised when the service pack came in at 85MB (or 17 times the promised size).
ahh, but besides a few registry entries and a couple of programs, win2k pro could do the same thing as advanced server. The EULA and the registry and the cost really ARE the biggest differences. Of course, Redhat has two different installs you can do depending on what the primary use of the machine will be (server or workstation), but the kernel and basic features (like memory support and load balancing) remain the same. In addition to that, linux distros do not intentionally cripple their installs just to force the user into paying them huge sums of money for an "advanced server".
I remember reading this. If memory serves, Tannenbaum was bitching that Linux wasn't a microkernel. The arguments have been made and repeated over and over. If someone doesn't like the Linux kernel, there is no reason why they can't use Hurd. But the next time someone says that Minix is so much better, tell them to read the book. I did. Tannenbaum's opinions are formost opinions and should be treated as such.
You are all fartheads.
Why can't Linux just name it, like Linux 4, Service Pack 2?
He spelled it wrong, is actually called 'softupdates' and AFAIK is only available for FreeBSD.
> ...and start seriously thinking about proper
> change control - perhaps a CVS system instead
> of randomly throwing out tarballs.
Are you seriously saying that they don't use CVS?
Running ident(1) on some of the kernel files shows that atleast someone is using either RCS or CVS.
Perhaps I am missing your point. Do you mean that there should be a public anoncvs that allows the users to check out the newest version?
That is the reason I switched over to linux. Linus and others make it a priority to fix *bugs* whatever they are in the code. Not merely spending time on surface issues that would affect *most* people. Every bug is important. Every change to the kernel that improves its functionality with obscure hardware is an improvement. My .02
Bør bør bør, din mama er af smør...
.NOT
No, Linux
(I know)
Will work for bandwidth
I find it interesting that it took a relitivly large amout of time to finalize the 2.4.0 release, and now here we are around 2 months after the release and we already have 2.4.2. Makes you wonder what linus was doing in those days leading up to the 2.4.0 launch ;-)