What happened to devfsd and lvm? I know they were talking about replacing lvm, and I was wondering if the new code is in place? Also, I read somewhere that the developers were unhappy about devfsd, since 'nobody was using it'. I'm using it, so I'm hoping they don't remove it.
Not too familiar with gentoo since I never used it, but is problematic that it is so current. A reference implementation needs to be a little out of date, which is what stable is in Debian.
How many different versions did you have of GCC over the last year in gentoo? Almost every GCC in the 3.x serie have been binary incompatible with the previous version.
Isn't LSB just a whitepaper? My point is that with Debian as the reference implementation, you will have an actual distribution to reference.
As to your points, not being that popular works for Debian, since it can't be accused of being partial to one popular distribution over another (which one happen if you made RedHat the reference distribution, for instance).
Breaking binary compatibility won't be a problem for the reference implementation if the reference implementation is the standard, ie. the libdb issue (whatever it was, not familiar with the problem).
I think for Linux to grow more, it needs a reference implementation so that developers and users know that something will work for sure.
I think Debian GNU/Linux should be this system for several reasons. It's non-commercial, meaning SuSe can't complain that the reference system is partial to RedHat or anyone else. It's conservative, which is very important for reference systems. If you write for Debian 3.0, you know it will be around for awhile. This doesn't mean that RedHat can't extend their distribution to add more recent libraries or programs. It just mean that something written for Debian 3.0 will work in the RedHat system that says it follows 3.0.
There used to be a saying during WWII: "When the German flew overhead, the Allied took cover. When the British flew overhead, the German took cover. When the Americans flew overhead, everybody took cover".
There is a difference between the way UNIX and Windows does it. When you open Explorer in Windows, you are basically at your root directory. You are working from C:\. Your whole system is open to you. Labeling the way Windows does it is necessary to work around this problem.
In an UNIX filesystem, you are working within your home directory. Your workplace/home directory is logically separated from the rest of the system. If you as a user wants to install a program for you, you install within your own space.
Most people who work in Windows never stay inside their own "home". The whole system is set up for you tok work outside your home.
Would be nice to use the same module I compiled in 2.4.1 in my new 2.4.19 kernel. That way my 'vendor' (Debian) could just provide one set of modules, instead of one set for each kernel version.
Marvel has something called the Visionaries line of paperbacks. Has most of the important backstories. I would pick up the Byrne Visionaries, and maybe if there are, Claremont Visionaries. You could also get the Phoenix Sage trade paperback (next movie is going to deal with that storyline), and Days of Future Past. Also check out "God Loves, Man Kills" graphic novel.
I saw a report yesterday, either BBC or CNN, that WHO now believes the fatality rate of SARS will be about 10-15%. Much higher than previously believed (this was after China went public with their info)
Even though Planetary is a "Secret history of the Wildstorm Universe", you bring lots of elements from the history of Marvel and DC. Has the direction of Planetary change since your initial proposal?
What happened to devfsd and lvm? I know they were talking about replacing lvm, and I was wondering if the new code is in place?
Also, I read somewhere that the developers were unhappy about devfsd, since 'nobody was using it'. I'm using it, so I'm hoping they don't remove it.
Not too familiar with gentoo since I never used it, but is problematic that it is so current. A reference implementation needs to be a little out of date, which is what stable is in Debian.
How many different versions did you have of GCC over the last year in gentoo? Almost every GCC in the 3.x serie have been binary incompatible with the previous version.
Debian has RPM packaging. I don't know how many people have it installed on their Debian system, but Debian do follow LSB in that regard.
Isn't LSB just a whitepaper? My point is that with Debian as the reference implementation, you will have an actual distribution to reference.
As to your points, not being that popular works for Debian, since it can't be accused of being partial to one popular distribution over another (which one happen if you made RedHat the reference distribution, for instance).
Breaking binary compatibility won't be a problem for the reference implementation if the reference implementation is the standard, ie. the libdb issue (whatever it was, not familiar with the problem).
I think for Linux to grow more, it needs a reference implementation so that developers and users know that something will work for sure.
I think Debian GNU/Linux should be this system for several reasons.
It's non-commercial, meaning SuSe can't complain that the reference system is partial to RedHat or anyone else.
It's conservative, which is very important for reference systems. If you write for Debian 3.0, you know it will be around for awhile. This doesn't mean that RedHat can't extend their distribution to add more recent libraries or programs. It just mean that something written for Debian 3.0 will work in the RedHat system that says it follows 3.0.
email me at john at fjellstad dot org and we can discuss. I wouldn't mind helping out.
Why would you need an IMAP module? Just intercept the email before it comes to the INBOX, and do the bucket assignment there.
I was actually thinking of forking the popfile system to work with IMAP.
If it's the normal TIVO, it has 30sec forward. You just have to enable it.
Been around pretty long.
lvextend to increase the volume.
resize_reiserfs to increase the filesystem.
Only works if you want to increase the filesystem, not shrink it.
There used to be a saying during WWII:
"When the German flew overhead, the Allied took cover. When the British flew overhead, the German took cover. When the Americans flew overhead, everybody took cover".
Doesn't seem like things have changed that much.
That's OK. You still be firing at the Canadians and the British.
Then don't put it under GPL (or the musical equivalent).
There is a difference between the way UNIX and Windows does it. When you open Explorer in Windows, you are basically at your root directory. You are working from C:\. Your whole system is open to you. Labeling the way Windows does it is necessary to work around this problem.
In an UNIX filesystem, you are working within your home directory. Your workplace/home directory is logically separated from the rest of the system. If you as a user wants to install a program for you, you install within your own space.
Most people who work in Windows never stay inside their own "home". The whole system is set up for you tok work outside your home.
Would be nice to use the same module I compiled in 2.4.1 in my new 2.4.19 kernel. That way my 'vendor' (Debian) could just provide one set of modules, instead of one set for each kernel version.
Marvel has something called the Visionaries line of paperbacks. Has most of the important backstories. I would pick up the Byrne Visionaries, and maybe if there are, Claremont Visionaries. You could also get the Phoenix Sage trade paperback (next movie is going to deal with that storyline), and Days of Future Past. Also check out "God Loves, Man Kills" graphic novel.
Why would 1) show up in every .cpp file? It's not valid C++ (or C for that matter).
I saw a report yesterday, either BBC or CNN, that WHO now believes the fatality rate of SARS will be about 10-15%. Much higher than previously believed (this was after China went public with their info)
If there is something Microsoft isn't, is that they're not suffering from NIH syndrome.
The whole idea of NIH is that the developer refuse to use something he didn't write himself.
Well, is that true for Microsoft? Lets see, they licensed IE, they took the TCP stack, their enterprise OS is based on VMS, SQLServer was bought.
Most of the technologies that MS have, are either bought or licensed. To say Microsoft suffers from NIH syndrome is pretty silly statement.
Probably this one
According to Ellis' blog here, it should start coming out late spring 2003.
Even though Planetary is a "Secret history of the Wildstorm Universe", you bring lots of elements from the history of Marvel and DC. Has the direction of Planetary change since your initial proposal?
Doubt most of the people complaining are coders. I suspect the majority of complainers are cheerleaders.
Come to Europe. Never had a dropped call. Then again, the cellphones companies aren't the ones to fix the backbones.
Besides, I doubt this is for the American marked.
Nokia 2100.
It still have text messaging, because quite frankly, it's a useful feature (although not if you are in USA, I guess). Nothing else.
Install the kernel headers for your kernel.
Do apt-cache search kernel-headers to see which kernel headers are available.