LXC is the core technology, and the part that's actually revolutionary (for linux).
LXC is not really revolutionary, OpenVZ and Linux-VServer provided linux containerization for many many years.
I expect someone to come along any minute now and say that Docker no longer uses LXC anyway, now it uses libcontainer. This isn't true, libcontainer is just another frontend to LXC, libvirt being the first project to run a LXC without using the LXC userland.
I think you're not giving Jobs enough credit even for the first wave of personal computers. The Apple II was probably the most important step into the world of computers in the home, school and business, moving us from the era of hobbiest kit computer to what we view as the standard computer, keyboard and monitor.
Thats a romantic view, but actually its the Commodore 64 that was the machine that brought computers into homes, schools and offices. Faster, better graphics, real sound (Apple ][ could only make beeps and boops), and less than half the price.
Off-line development is the first thing that come to mind.
Its also single-centrally managed server, which is painful for distributed development (but perhaps good for companies). There is P4Proxy, but that is readonly. Remote users on the other side of the world don't have the best experience.
I could list many other things. SCM has grown significantly since 1999, P4 hasn't.
If you're running a serious server you should always do a reboot test after installing any software. I've been burned many times by someone doing a "harmless" installation only to find out 6 months later a critical library was upgraded with an incompatible one (a recent example is expat 2.0) and the server doesn't boot like it should.
Always reboot! Even with the super slow bios you get in servers nowadays it should only take 2 minutes to be back up and running.
But did anyone promise that ubuntu would kill off MS or something? Has it actually failed to deliver?
Hell yeah they did!
Bug #1 reported by Mark Shuttleworth on 2004-08-20 (Activity log) (critical) Bug #1 (liberation): This report is public Microsoft has a majority market share
I for one wrote 150+ modules, of which a grand total of 7 were available on ActivePerl
Perhaps the problem is with the way you code your modules and not with the ActivePerl build farm? ActivePerl has like a brazillion modules available for it.
Perl has been a first class citizen on Win32 starting with the GSAR port back in late 90s, then Perl for Win32 and now ActivePerl.
In fact ActivePerl was more up to date than unix Perl during the late 5.005 and 5.6 because the pumpkin was primarily a Win32 developer.
If you want to find the second class citizens in the Perl world look at OS2, Aix, Hpux, and other strange unixes. I know you want to make Perl better and are working hard on it, but insulting the people who put together the foundation you're now working on is misguided. They did a damn fine job.
Last time the marketing department springs for a t
on
Tabula Rasa To Shut Down
·
· Score: 4, Funny
Last time the marketing department springs for a trip into space...
I'd like to know why Ted Tso and others are working on ext4? Even when ext4 is feature complete it will be the #3 filesystem in linux in terms of features and scalability behind xfs and jfs. I'd like to know what Ted Tso and others grudge against xfs and jfs is because they basically wont even acknowledge those filesystems.
btrfs does have some nice looking features, its basically a gpl rewrite of zfs.
The weakness with linux is in the LVM or EVMS layer. They both suck in that they are not enterprise ready (ie multi TB filesystems, 100+ MB/s sustained read/write) in that they cause unexplained IO hicups, lockups and kernel panics. LVM/EVMS certainly work fine for Joe Blow's HTPC, or a paltry 100GB database but they fall down when under serious load.
This is the problem with open source. Certain areas, like filesystem development attract all the developers, and other areas like LVM/EVMS are seen as busting rocks and nobody wants to work on them. The results is we get a plethora of second rate filesystems (ie ext4) and a buggy LVM/EVMS layer that nobody wants to work on.
In the Pentium 1 era EDO RAM maxed out at 256MB/s and hard disk xfer was 10MB/s.
Now we have 16 GB/s RAM xfer rate and 60 MB/s hard disk.
Notice the difference? RAM transfer rates have gone up by 60x while hard drives only 6x. Hard drives did not keep pace with RAM and no longer provide a usable alternative to RAM.
Anyone who recommends swap doesn't understand what they're talking about. Swap is the new cargo-cult!
Checksum offloading often causes confusion as the network packets to be transmitted are handed over to Wireshark before the checksums are actually calculated. Wireshark gets these "empty" checksums and displays them as invalid, even though the packets will contain valid checksums when they leave the network hardware later.
Anyone know how to get ntpd to stop listening on all interfaces? I have a host with several IPs and ntpd listens on all of them... a little bit annoying.
Lets not forget the intellectual theft perpetrated by Ingo Molnar. No matter how things turn out the guy is a liar, a thief, and a cheat. He sucks.
Ingo fought long and hard for the status quo. Complaints against the current O(1) scheduler (author: Ingo) were met with flames and ignorance. Con spent a year developing a new scheduler and proving that it was better than the scheduler that Ingo wrote. Ingo spent the entire year ignoring and denying Con's scheduler, but one day he saw the light and wrote his own knockoff in "62 hours" and gets it merged the next week. This is bullshit.
The end result is that Con has been driven from Kernel development by asses like Ingo. Whether CFS is better than SD is irrelevant. What has happened is the guy who spawned the entire process of getting an improved scheduler in the kernel and spent a year overseeing and improving it has his concept stolen by Ingo. Ingo did not want a new scheduler, he wanted his name to be on the current scheduler. When he saw that disappearing he had to take drastic action and he "authored" a new, improved scheduler. All for his own glory.
Ingo Molnar is the worst kind of loser: an attention whore. His O(1) scheduler turned out to be a piece of crap and Con Kolivas spent a considerable amount of time implementing a better solution: Staircase Deadline (SD). The SD scheduler is a well tested, good performing scheduler and just when you think its going to be merged into Linus' kernel and replace Ingo's O(1) turd (and remove Ingo's name from some "important" files), Igno spends a couple of days reimplementing SD. I guess he wont be getting his name deleted after all!
This shows the black side of open source. Con developed SD in the open and Igno stole his ideas. It was only after people started pointing out that CFS looked _very_ similar to SD that Igno even admitted that the design was based on Con's SD work.
The only reason CFS is in the kernel and not SD is politics.
Solaris tar sucks. It can't handle long filenames and renames them to some weird looking thing that reminds me of Progra~1 fugly-ness. Just what the doctor ordered a piece of backup software to do. A few random samples of people on the net complaining about Solaris tar:
Slashdot Mirror
Pick one from this selection of images: http://photobucket.com/images/...
LXC is the core technology, and the part that's actually revolutionary (for linux).
LXC is not really revolutionary, OpenVZ and Linux-VServer provided linux containerization for many many years.
I expect someone to come along any minute now and say that Docker no longer uses LXC anyway, now it uses libcontainer. This isn't true, libcontainer is just another frontend to LXC, libvirt being the first project to run a LXC without using the LXC userland.
http://linux-vserver.org/
http://openvz.org/
Bill Gates must be pissed Pen Windows never caught on. First released in 1991!
http://en.wikipedia.org/wiki/W...
I think you're not giving Jobs enough credit even for the first wave of personal computers. The Apple II was probably the most important step into the world of computers in the home, school and business, moving us from the era of hobbiest kit computer to what we view as the standard computer, keyboard and monitor.
Thats a romantic view, but actually its the Commodore 64 that was the machine that brought computers into homes, schools and offices. Faster, better graphics, real sound (Apple ][ could only make beeps and boops), and less than half the price.
http://www.myspace.com/michelle_i_sullivan
"I'm 40 year old transsexual girl ..."
I'm not making this up!
Off-line development is the first thing that come to mind.
Its also single-centrally managed server, which is painful for distributed development (but perhaps good for companies). There is P4Proxy, but that is readonly. Remote users on the other side of the world don't have the best experience.
I could list many other things. SCM has grown significantly since 1999, P4 hasn't.
P4 is awesome and works great for huge repos with lots of developers.
However it is getting stale. I can't think of a single new feature added to it since I started using it in 1999.
If you're running a serious server you should always do a reboot test after installing any software. I've been burned many times by someone doing a "harmless" installation only to find out 6 months later a critical library was upgraded with an incompatible one (a recent example is expat 2.0) and the server doesn't boot like it should.
Always reboot! Even with the super slow bios you get in servers nowadays it should only take 2 minutes to be back up and running.
But did anyone promise that ubuntu would kill off MS or something? Has it actually failed to deliver?
Hell yeah they did!
Bug #1 reported by Mark Shuttleworth on 2004-08-20 (Activity log)
(critical) Bug #1 (liberation):
This report is public
Microsoft has a majority market share
https://bugs.launchpad.net/ubuntu/+bug/1
I for one wrote 150+ modules, of which a grand total of 7 were available on ActivePerl
Perhaps the problem is with the way you code your modules and not with the ActivePerl build farm? ActivePerl has like a brazillion modules available for it.
Perl has been a first class citizen on Win32 starting with the GSAR port back in late 90s, then Perl for Win32 and now ActivePerl.
In fact ActivePerl was more up to date than unix Perl during the late 5.005 and 5.6 because the pumpkin was primarily a Win32 developer.
If you want to find the second class citizens in the Perl world look at OS2, Aix, Hpux, and other strange unixes. I know you want to make Perl better and are working hard on it, but insulting the people who put together the foundation you're now working on is misguided. They did a damn fine job.
Last time the marketing department springs for a trip into space ...
I'd like to know why Ted Tso and others are working on ext4? Even when ext4 is feature complete it will be the #3 filesystem in linux in terms of features and scalability behind xfs and jfs. I'd like to know what Ted Tso and others grudge against xfs and jfs is because they basically wont even acknowledge those filesystems.
btrfs does have some nice looking features, its basically a gpl rewrite of zfs.
The weakness with linux is in the LVM or EVMS layer. They both suck in that they are not enterprise ready (ie multi TB filesystems, 100+ MB/s sustained read/write) in that they cause unexplained IO hicups, lockups and kernel panics. LVM/EVMS certainly work fine for Joe Blow's HTPC, or a paltry 100GB database but they fall down when under serious load.
This is the problem with open source. Certain areas, like filesystem development attract all the developers, and other areas like LVM/EVMS are seen as busting rocks and nobody wants to work on them. The results is we get a plethora of second rate filesystems (ie ext4) and a buggy LVM/EVMS layer that nobody wants to work on.
Swap is useless on modern hardware.
In the Pentium 1 era EDO RAM maxed out at 256MB/s and hard disk xfer was 10MB/s.
Now we have 16 GB/s RAM xfer rate and 60 MB/s hard disk.
Notice the difference? RAM transfer rates have gone up by 60x while hard drives only 6x. Hard drives did not keep pace with RAM and no longer provide a usable alternative to RAM.
Anyone who recommends swap doesn't understand what they're talking about. Swap is the new cargo-cult!
Not Duke Nukem, the game is Prey. The mode is called spirit-walk.
Shrouding does sound like a bit of a ripoff.
There I said it!
Read up on it here: http://www.wireshark.org/docs/wsug_html_chunked/ChAdvChecksums.html
Linux will never be GPL3. Got that? NEVER!
-I does interfaces, not IPs. However in my case it does not ntpd from listening on several IPs. Thanks!
Lets not forget the intellectual theft perpetrated by Ingo Molnar. No matter how things turn out the guy is a liar, a thief, and a cheat. He sucks.
Ingo fought long and hard for the status quo. Complaints against the current O(1) scheduler (author: Ingo) were met with flames and ignorance. Con spent a year developing a new scheduler and proving that it was better than the scheduler that Ingo wrote. Ingo spent the entire year ignoring and denying Con's scheduler, but one day he saw the light and wrote his own knockoff in "62 hours" and gets it merged the next week. This is bullshit.
The end result is that Con has been driven from Kernel development by asses like Ingo. Whether CFS is better than SD is irrelevant. What has happened is the guy who spawned the entire process of getting an improved scheduler in the kernel and spent a year overseeing and improving it has his concept stolen by Ingo. Ingo did not want a new scheduler, he wanted his name to be on the current scheduler. When he saw that disappearing he had to take drastic action and he "authored" a new, improved scheduler. All for his own glory.
Ingo sucks.
Ingo Molnar is the worst kind of loser: an attention whore. His O(1) scheduler turned out to be a piece of crap and Con Kolivas spent a considerable amount of time implementing a better solution: Staircase Deadline (SD). The SD scheduler is a well tested, good performing scheduler and just when you think its going to be merged into Linus' kernel and replace Ingo's O(1) turd (and remove Ingo's name from some "important" files), Igno spends a couple of days reimplementing SD. I guess he wont be getting his name deleted after all!
This shows the black side of open source. Con developed SD in the open and Igno stole his ideas. It was only after people started pointing out that CFS looked _very_ similar to SD that Igno even admitted that the design was based on Con's SD work.
The only reason CFS is in the kernel and not SD is politics.
Solaris tar sucks. It can't handle long filenames and renames them to some weird looking thing that reminds me of Progra~1 fugly-ness. Just what the doctor ordered a piece of backup software to do. A few random samples of people on the net complaining about Solaris tar:
t -setup/Solaris10I nstalling/SOLARIS323_2.shtmle ek-of-Mon-20040809/017086.html5 84.html
http://www.mikehan.com/rant/solaris-tools.html
http://twistedmatrix.com/trac/ticket/1750
http://42.pl/postfix/postfix-2.2.2/examples/chroo
http://www.idevelopment.info/data/MySQL/DBA_tips/
http://lists.cs.uiuc.edu/pipermail/llvm-commits/W
http://justlinux.com/forum/archive/index.php/t-40
Take a look at qpsmtpd:
http://smtpd.develooper.com/
Where is the bug report?