Sure, just like OpenBSD, NetBSD and DragonFly (for example) have FreeBSD kernel bits. That doesn't make them FreeBSD. The BSD's use each other's kernel code for stuff like bugfixes, drivers and what not. A good example is for instance DragonFlyBSD which has NetBSD's USB stack. That's kernel code. But that doesn't make DragonFlyBSD a NetBSD derivative.
OS X isn't really BSD, because the kernel isn't a traditional BSD kernel, it's a Mach hybrid. The only thing that OSX inherited from FreeBSD (and others) are parts of the userland.
OSX and FreeBSD are actually quite dissimilar. I wish people would realise that not anything that is thought up for FreeBSD (like the Dtrace thing last couple of weeks) can be easily ported over to Darwin/OSX. They are two completely different beasts.
- Gobs of diskspace so you can multiboot many operating systems
Before someone comments about virtual machines and how multibooting sucks (which I don't get, since running something on the bare metal feels nicer IMHO), of course can one use that disk real estate to put VM images on:)
- A fridge within reach - A lot of beer in that fridge - Caffeine I.V. or just a lot of 'dew - AMD64 box with gobs of mem and lotsa Ghz, dual core, more cpu's is better - Gobs of diskspace so you can multiboot many operating systems - A comfy chair - Multiple monitors - Dual head video card - A simple PCI video card for that third head - An IBM type M keyboard, or a Sun type 5 hacked to work on a normal x86-like system - A lock on the door to keep the SO and/or cats out - A 60 GB ipod hooked up to a dock for auditory pleasure - A large desk to put all that crap on - A shell - vi(m)
Do you actually know what the public domain is? If you put your work, which you put blood, sweat and love in, into the public domain, some asswank can just take that stuff, change one byte, and claim that he wrote it.
What you are forgetting to grasp is that the GPL has _NOTHING_ to do with use, and _EVERYTHING_ to do with distribution. The GPL is not an end-user license.
You don't have to agree to it to use, but if you re-distribute, you have to agree to it. It's really that simple.
Because the BSD license calls for correct attribution, the people who wrote the gimp can find a reference to their project in supplied documentation/release notes if they used the BSD license with the advertisement clause.
In short, they get recognition and attribution, and the satisfaction that someone out there didn't reinvent the wheel all over again.
Moving these drivers to the OS level would improve reliability and configurability all around.
And lose that wonderful cross platform ability and userland protection? What color is the sky on your planet?
Moving the drivers into the kernel is crazy. It might simplify the X server code, but it will be a bitch to maintain for several operating systems. Not the whole world wants or does want to run Linux. What is it with the Linux contingent of FOSS-land and dumping everything into ring 0?
Where do you get the notion that the X server takes care of all the input devices? The kernel already provides access to them through/dev anyway. Sure, the GFX side uses blitting directly to video ram, but that's what the others do as well. mmap(), memcpy and friends work fast enough from userland anyway. And don't start about X using sockets to talk to clients, because they have nothing to do with networking (although networking does work, which comes for free). X uses a domain sockets/named pipes (which don't need a network stack) locally, and it's hella fast. Faster than other kludges that other unnamed operating systems use. If you ever see X redraw or rubber-band, don't blame X, blame the toolkit used. X can keep up fine.:)
Wow, I've been waiting for this one. And I was also one of the first 5000 on the website, so I scored myself a nifty free opensolaris tee as well:)
Go Sun!:)
Re:Dvorak is very good
on
Advocating Dvorak
·
· Score: 3, Insightful
Dvorak is _not_ so very good when vi (or vim) is one's standard editor. I tried using dvorak for a while, but my finger muscle memory is so attuned to vi(m) with querty, I destroyed several chunks of code while poking on the wrong keys (yay for CVS and Subversion). It also doesn't "flow" with vi like querty does. "hjkl" is useless with dvorak, as are many other well placed vi command-mode keystrokes.
The dvorak-advocates can blather all about languages and how one can speak several without losing proficiency in one, but muscle memory is a TOTALLY different league and is a bitch to relearn.
Sure, I can remap the keys so they have their "qwerty" equivs, but then I might as well stay with qwerty then.
And no, I'm NOT switching to emacs. They can pry my beloved vi from my cold dead fingers.
I have a better solution: become a BOFH, get your hands on a used LART, learn how to properly use it, and the students will be eating out of your hand in no time.
s/out of your hand/with a straw/g if one applies the LART correctly.
But seriously, I'd set up a DHCP server, hand out IP's through that, and when a machine misbehaves, nullroute the bugger and yank it's lease. The owner of said machine will come by eventually to complain that "Teh intarweb" doesn't work, and you can apply said LART to educate the luser.
Slashdot Mirror
And what, pray tell, is wrong with tits? The nipple is the most intuitive interface on this planet, you know...
Sure, just like OpenBSD, NetBSD and DragonFly (for example) have FreeBSD kernel bits. That doesn't make them FreeBSD. The BSD's use each other's kernel code for stuff like bugfixes, drivers and what not. A good example is for instance DragonFlyBSD which has NetBSD's USB stack. That's kernel code. But that doesn't make DragonFlyBSD a NetBSD derivative.
OS X isn't really BSD, because the kernel isn't a traditional BSD kernel, it's a Mach hybrid. The only thing that OSX inherited from FreeBSD (and others) are parts of the userland.
OSX and FreeBSD are actually quite dissimilar. I wish people would realise that not anything that is thought up for FreeBSD (like the Dtrace thing last couple of weeks) can be easily ported over to Darwin/OSX. They are two completely different beasts.
Before someone comments about virtual machines and how multibooting sucks (which I don't get, since running something on the bare metal feels nicer IMHO), of course can one use that disk real estate to put VM images on :)
No. Go to ebay. Search for IBM type M keyboards. Buy one. Your fingers will thank you. As for mice, well, I just always go for Logitech.
He's talking about hardware and software, not wetware :)
You need:
:)
- A fridge within reach
- A lot of beer in that fridge
- Caffeine I.V. or just a lot of 'dew
- AMD64 box with gobs of mem and lotsa Ghz, dual core, more cpu's is better
- Gobs of diskspace so you can multiboot many operating systems
- A comfy chair
- Multiple monitors
- Dual head video card
- A simple PCI video card for that third head
- An IBM type M keyboard, or a Sun type 5 hacked to work on a normal x86-like system
- A lock on the door to keep the SO and/or cats out
- A 60 GB ipod hooked up to a dock for auditory pleasure
- A large desk to put all that crap on
- A shell
- vi(m)
I guess that's about it
Nah, he's just too lazy to type "stty ^H erase" in the shell. Common oversight by most *nix users, not just the linux weeni^Wusers. ;)
Oh, and it should have a cool self-destruct function. Not that lame one that makes it fizzle and smoke, it has to at least explode a bit.
and don't forget to set DO_WHAT_I_MEAN="YES" as well, to prevent future problems. ;)
Buy out what? SVG is a W3C standard. Can one buy out HTML and XML as well? No.
Okay, when will MS start getting their certification in while kids are in pre-school?
Well said. Good to see the voice of reason and sanity for once instead of the tiresome language/blog-system/OS/whatever-fanboyism and groupthink.
If I had modpoints, I would have modded you up.
Hell no.
Do you actually know what the public domain is? If you put your work, which you put blood, sweat and love in, into the public domain, some asswank can just take that stuff, change one byte, and claim that he wrote it.
No thank you very much.
What you are forgetting to grasp is that the GPL has _NOTHING_ to do with use, and _EVERYTHING_ to do with distribution. The GPL is not an end-user license.
You don't have to agree to it to use, but if you re-distribute, you have to agree to it. It's really that simple.
If you don't like what someone says (in your case, you don't agree with what ESR is saying), you are free to ignore him.
:)
We did that to John Katz too.
Because the BSD license calls for correct attribution, the people who wrote the gimp can find a reference to their project in supplied documentation/release notes if they used the BSD license with the advertisement clause.
In short, they get recognition and attribution, and the satisfaction that someone out there didn't reinvent the wheel all over again.
And lose that wonderful cross platform ability and userland protection? What color is the sky on your planet?
Moving the drivers into the kernel is crazy. It might simplify the X server code, but it will be a bitch to maintain for several operating systems. Not the whole world wants or does want to run Linux. What is it with the Linux contingent of FOSS-land and dumping everything into ring 0?
Where do you get the notion that the X server takes care of all the input devices? The kernel already provides access to them through</rant>
Two words: Janet Jackson (see statue in the back) Ashcroft sure is a badboy ;)
Could you maybe use more paragraphs next time?
Wow, I've been waiting for this one. And I was also one of the first 5000 on the website, so I scored myself a nifty free opensolaris tee as well :)
:)
Go Sun!
Dvorak is _not_ so very good when vi (or vim) is one's standard editor. I tried using dvorak for a while, but my finger muscle memory is so attuned to vi(m) with querty, I destroyed several chunks of code while poking on the wrong keys (yay for CVS and Subversion). It also doesn't "flow" with vi like querty does. "hjkl" is useless with dvorak, as are many other well placed vi command-mode keystrokes.
The dvorak-advocates can blather all about languages and how one can speak several without losing proficiency in one, but muscle memory is a TOTALLY different league and is a bitch to relearn.
Sure, I can remap the keys so they have their "qwerty" equivs, but then I might as well stay with qwerty then.
And no, I'm NOT switching to emacs. They can pry my beloved vi from my cold dead fingers.
Use konqueror instead then. It's not affected by this :) (oh, and it's open source too)
BitTorrent was never designed to anonymize. It was designed to distribute the load of hosting a file. A lot of hoopla about a non-issue.
s/out of your hand/with a straw/g if one applies the LART correctly.
But seriously, I'd set up a DHCP server, hand out IP's through that, and when a machine misbehaves, nullroute the bugger and yank it's lease. The owner of said machine will come by eventually to complain that "Teh intarweb" doesn't work, and you can apply said LART to educate the luser.