Domain: uu.nl
Stories and comments across the archive that link to uu.nl.
Comments · 159
-
Can Theoretical Physics explain paranormal phenome
't Hooft has a little FAQ on 'Can Theoretical Physics explain paranormal phenomena?' find it at http://www.phys.uu.nl/~thooft/para.html . also, check out his PostScript pictures, he even has one of a 'living black hole'!
had two classes with this guy, so i am excited to finally see him get what he deserved a long time ago.
patrick. -
Can Theoretical Physics explain paranormal phenome
't Hooft has a little FAQ on 'Can Theoretical Physics explain paranormal phenomena?' find it at http://www.phys.uu.nl/~thooft/para.html . also, check out his PostScript pictures, he even has one of a 'living black hole'!
had two classes with this guy, so i am excited to finally see him get what he deserved a long time ago.
patrick. -
Re:2 gig file limits suck
Please go to Linux Memory Management subsystem; main page and search for the words "large file". You will find a patch that you may want to try out.
-
A new home (Re:Who Exactly Is Homeless?)Of course I agree that Chris should be payed by his paying customers. He really doesn't deserve to be left in the cold.
On the other hand, I don't think he should bear the cost of hosting Open Source projects either. There are some less costly methods of hosting those projects.
For example, I have a host at the University of Utrecht who is allowing me to use some of their bandwidth for free. I am willing to host some open source projects and have all the resources available. Whenever I need more bandwidth, hardware or whatever, there's always been a nice company that came up and offered help.
Just mail me (email on my home page) if you need to host an Open Source project on NL.linux.org...
-
After SunView -- XView, Sun's first open source
When Sun migrated from SunView to X in SunOS 4, they developed XView, a GUI toolkit for X which was mostly SunView compatible. Sun Microsystems then stopped active development of XView and became an early member of the open-source community when they released the entire source code and documentation for the XView toolkit under a liberal X-style license. XView was previously proprietary. Today, although XView is mostly defunct, many Linux distributions still have the XView toolkit together with Sun's excellently documented example programs (often in
/usr/src/xview). Jazz, the first ever Linux MIDI sequencer, was initially written using XView -- Linux Gazette, Vol.12, 1996. and Jazz v2.6 source code.The closest successor to the XView style, and arguably the easiest GUI widget set for beginners, is probably EZWGL.
-
Re:Microsoft will be seen in a positive light?...
This is because M$ has found a testing domain
that at the current time favours the M$ setup.
1. Using a 4 processor machine.
Can you justify using a 4 processor Intel
machine, when you'd be much better off with
a cluster of 4 1 processor machines in terms
of reliability. Anyway, if you need to scale
that badly, get a Digital Alpha or something
like that.
2. Using a kernel level threaded webserver.
Would you want to have a process doing this
on your Linux box? I think not. Apache forked
processes die after serving a number of hits,
so if anything goes wrong the webserver will
return to normal operation after a few hits.
This is MUCH more reliable! Web serving is
about reliability in 99% of case, not speed.
3. Serving static pages.
Nobody serves that many static pages. If you
need to do that get a different web server
(Zeus?). The power of Apache is in things
like mod_perl and PHP3. Apache is more than
fast enough in what it does. You can fill a
T1 line with a Pentium 100, which is more
bandwidth than most sites have.
4. Choice of harware.
The hardware chosen has better drivers for
NT than for Linux. In the original test,
they used a beta driver for the RAID that
wasn't properly SMP aware.
5. Samba?
Samba is a cool product, but why should we
have to do windows file serving, instead of
our native networked filesystem protocols
like NFS? I'm not sure about this test, but
in the first one, they used Win95 clients.
Samba is NOT optimised for Win95 clients for
the simple reason that serious businesses that
can afford such a server would be a lot more
likely to be running NT workstation on the
clients.
6. etc...
Michiel Toneman -
GRIO not in Linux-XFS. What ext3 offers.XFS is a lot more than "just" a journaling FS. One of it's other major components is guaranteed I/O rate partitions
Yes but they are not giving away the guaranteed I/O rate part of it. At least not according to this link though I can't find any mention of that in the news story or the SGI press release.
I haven't seen what EXT3 promises,
It will add journalling (see the white paper Stephen wrote), and probably extent based block lists and btrees by Ted Ts'o will be in there too.
Linux does need a journaling FS and XFS may be the best bet, but it won't happen quickly unless SGI puts some serious resources behind it.
SGI are employing kernel hackers and you can start to see some of the stuff they are getting up to
Also, just who has the resources to test large production systems (4+ CPUs) on an OS under test? Corporates, that's who. And they'll contribute their code to Open Source, right? Because...?
Hell, we've got MS helping us by looking for performance bottlenecks for us and that is already starting to bear fruit (I can't seem to link to that article right. Check out the article "Re:Thank you Microsoft!" by petchema. You will need Alt-F to find it.)
Personally, I think ext3 will rock. This isn't Stephen's first file system by a long chalk.
may have a price current purists will not like but will have to accept (ie less than Open Source code licenses
We can't succeed by destroying ourselves, and I don't think the Linux community will try. If XFS weren't Open Source then it would fail to gain any market share against ext3. But it will be Open Source, so it's a moot point.
-
better-than-ever-before VM system?As far as I can tell, it's not a massive rewrite from the ground up, or anything like that, just lots and lots of little tuning tweaks: a change to how priority is calculated here, swap out pages slightly differently there. Most of the improvement seems to be from smarter swapping; one person reported a compile in 128MB going from 280sec down to 119sec. Poking through the list archives at the Linux-MM page will produce lots of info.
But yes, it is surprising that it's being done this late, at the 2.2pre stage. I suppose the potential improvement is so significant that Linus feels that getting it in for 2.2 is worth the risk.
-
better-than-ever-before VM system?As far as I can tell, it's not a massive rewrite from the ground up, or anything like that, just lots and lots of little tuning tweaks: a change to how priority is calculated here, swap out pages slightly differently there. Most of the improvement seems to be from smarter swapping; one person reported a compile in 128MB going from 280sec down to 119sec. Poking through the list archives at the Linux-MM page will produce lots of info.
But yes, it is surprising that it's being done this late, at the 2.2pre stage. I suppose the potential improvement is so significant that Linus feels that getting it in for 2.2 is worth the risk.