While we're changing the money to make it more usable for those poor folks that Jesus decided not to heal of their blindness, could we maybe take off this little piece of free advertising for churches? We put IN GOD WE TRUST on the money in 1954 to piss off the Communists, but we don't need it any more since God and Ronald Reagan scared them off. Perhaps it could be replaced with something like the First Amendment.
Expect lots of last-minute election-year legislation from fear-crazed christian republicans in congress intended to protect the children -- yes, we must protect the children! -- from sexual predation from, um, fear-crazed christian republicans in congress.
Sony's new Memory Stick Entertainment Packs are now shipping in 1GB and 2GB sizes and contain a launcher DVD, the packs contain an unlock code which you have the choice of one of these four films, 'Hitch,' 'S.W.A.T.,' 'The Grudge,' or 'XXX: State of the Union.'
Are there some words missing from the middle of that non-sentence?... the packs contain an unlock code which you have the choice...
just doesn't parse for me.
We use both in our port of Linux to proprietary Cray architectures.
Initramfs is synthesized from the stock page and dentry caches. The nice thing about initramfs is that RAM gets released to the dynamic pool when an inode is deleted. So it's a good choice for files that need to be present at boot time but not kept around, like kernel modules. The bad thing: each file occupies at least one page, and that's 64KiB here. An initramfs with lots of little files can waste beaucoup bytes.
RAM "disks" are devices that occupy statically allocated memory. Storage doesn't get reclaimed, but no storage is wasted by rounding up file sizes. An initrd is an image of a RAM disk, possibly compressed.
Note that a cpio archive, possibly compressed, that's loaded in place of an initrd image gets automatically expanded and copied into the initramfs.
Confusingly, the kernel also has its own compressed cpio archive within its own text containing the initial content of the initramfs. At a minimum, it holds/,/dev, and/dev/console.
If you're using an architecture with small pages (read: x86), use initramfs. Otherwise, you may need a clever hybrid solution, such as populating initramfs from a compressed cpio archive and then moving some of its content into a RAM disk.
So do identical twins share one soul? It would then seem to be ethical to kill my identical twin and harvest his organs, yes? If not, when do identical twins get their extra soul stirred into the mix? But wait; cloning is prohibited by the Bible, so why are identical twins not taken out and stoned in the first place? Bah.
The only Christians whose approach to the modern world seems to me to be consistent are the Amish. If you want to live a medieval life without benefit of science, fine; just don't force me to come along.
Someday, therapies based on embryonic stem cells will be available in civilized countries for diseases like Parkinson's. Will today's evangelical Republicans stay at home and quiver, or will they swallow their dogma and travel for therapy, I wonder.
Because public access to social Web sites can only lead to dead blastocysts burning flags in support of gay marriage, and then the terrorists will have won!
For all of you outside the U.S., wondering with amazement at our news: Yes, the majority of us *are* this stupid. We have an anti-evolution screed by a hate-crazed female impersonator near the top of our best-seller list -- and that just affects the dwindling proportion of Americans who actually still read books.
I use the mouse from Microsoft's "Optical Desktop for Bluetooth" with Linux, although I had to write a new driver in order to use it at first. But it works
just fine today with the stock BlueZ HID protocol code in the 2.6 kernel series, along with the Apple Bluetooth keyboard, which I prefer to the
Microsoft keyboard since it looks better when all the keys have been rearranged into a sane (Dvorak) layout.
See this old page where I dramaticize what it took to get these Bluetooth gadgets working.
I think you mean "hear, hear!", an abbreviation for the old cry "Hear him, hear him!".
As punishment, I'm taking away all the spare apostrophes and lower-case 'o's that you probably like to stick into words like "its" and "lose".
And yes, I'm having a bitchy day and I'm taking it out on you. But you wouldn't believe the illiteracy levels I'm seeing in my corporate e-mail inbox lately. When did third-grade composition skills suddenly become optional?
And the real disastrous employees, well, don't worry about them; you don't need reviews to find them, and rarely an excuse to get rid of them. Just wait until the police, fire department or the CDC has identified the idiot who caused the whole mess and get rid of them.
Too simplistic. Organizations accumulate deadwood that must occasionally be cleared out, or progress will grind to a halt.
In my organization, I wish we could give a freshman-level C programming class final exam to everybody whose job requires proficiency in C programming.
These smart, peace-loving God-fearers are called the Amish, I think.
I've got no problem with people who want to live in a community with a sixteenth-century worldview, so long as they're consenting adults and limit themselves to sixteenth-century technology. Where we get into trouble is when modern-day medievalists get their hands on technology created by that Enlightenment thing they've rejected. Whether it's a muslim with C4 or a baptist with an SUV, it's trouble coming from a mismatch of their culture's beliefs and my culture's capabilities.
So pick one or the other and stick with it -- ditch the tribal myths and wake up, or go buy a buggy. Living in both worlds isn't going to get you any more respect than an astrologer should expect from an astrophysicist, or an alchemist from a nanotechnologist.
He's motivated by a belief that killing innocent people will make an imaginary deity happy enough to give him an afterlife best described as a juvenile porno Disneyland.
Religion may be socially acceptable madness, but it's no less crazy for all its popularity.
If you type a lot, you've got to try using an ergonomic keyboard layout.
I used to go home from work with a feeling of numbness on the backs of my hands. This scared me enough to try the Dvorak layout. It worked for me; I'm not really any faster than I was with QWERTY, but I'm *way* more comfortable. I tried to design an even better keyboard layout via evolutionary algorithms, but couldn't; Dvorak got it right, at least for my pair of hands.
Give it a try; you'll thank me later. It's free, too.
The complaint is not about general copy-on-write, it's about BSD's ZERO_COPY_SOCKET feature vs. vmsplice().
Basic explanation: Suppose that a program is doing a lot of output to a file or socket. The program can generate data faster than the kernel can consume it, say. So what should the kernel do with the buffer it receives from the user on each write()? There are three options.
1) Copy its content immediately elsewhere, so that on return to User Mode, the buffer remains writable and writes are safe.
2) Change the access rights of the page containing the buffer, so that no copy need be made unless User Mode attempts
to modify its content before the kernel has completed the write(). If the user attempts to write, it either gets
permission to do so (because the kernel is done) or it gets a writable copy.
3) Let User Mode promise to not modify the buffer's content until told that it's safe to do so, leaving it writable in
the meantime.
The default behavior is (1); BSD's zero copy socket feature is (2), and the point of Torvalds' complaint; vmsplice() is (3).
How would I react to a television broadcaster saying that lighting and focus weren't all that important?
Or a radio station claiming that static was okay?
Proper spelling, grammar, and usage are easy compared to the syntax of a programming language or shell. Get them right and I'll take you more seriously.
It's sad to see legions of/.ers using semiconductor-based memory, microprocessors, and advanced networking technology to diss the achievements of the Apollo program.
We got more out of NASA than Tang and some rocks, boys.
(Personal note: my earliest memory that I can date accurately is being five years old, watching Neil and Buzz hop around the LEM on that late Sunday evening.)
Slashdot Mirror
While we're changing the money to make it more usable for those
poor folks that Jesus decided not to heal of their blindness,
could we maybe take off this little piece of free advertising
for churches? We put IN GOD WE TRUST on the money in 1954 to
piss off the Communists, but we don't need it any more since
God and Ronald Reagan scared them off. Perhaps it could be
replaced with something like the First Amendment.
Expect lots of last-minute election-year legislation from fear-crazed christian republicans in congress
intended to
protect the children -- yes, we must protect the children! -- from sexual predation from, um, fear-crazed
christian republicans in congress.
Are there some words missing from the middle of that non-sentence? ... the packs contain an unlock code which you have the choice...
just doesn't parse for me.
We use both in our port of Linux to proprietary Cray architectures.
/, /dev, and /dev/console.
Initramfs is synthesized from the stock page and dentry caches. The nice thing about
initramfs is that RAM gets released to the dynamic pool when an inode is deleted. So
it's a good choice for files that need to be present at boot time but not kept around,
like kernel modules. The bad thing: each file occupies at least one page, and that's
64KiB here. An initramfs with lots of little files can waste beaucoup bytes.
RAM "disks" are devices that occupy statically allocated memory. Storage doesn't get
reclaimed, but no storage is wasted by rounding up file sizes. An initrd is an image
of a RAM disk, possibly compressed.
Note that a cpio archive, possibly compressed, that's loaded in place of an initrd image
gets automatically
expanded and copied into the initramfs.
Confusingly, the kernel also has its own compressed cpio archive within its own text containing
the initial content of the initramfs. At a minimum, it holds
If you're using an architecture with small pages (read: x86), use initramfs. Otherwise,
you may need a clever hybrid solution, such as populating initramfs from a compressed cpio
archive and then moving some of its content into a RAM disk.
It's spelled "supercede".
lose (verb): to not win
loose (adjective): slack, not tight
Come on, guys. English isn't *that* hard to get right.
So do identical twins share one soul? It would then seem to be ethical to kill my identical twin and harvest his organs, yes? If not, when do identical twins get their extra soul stirred into the mix? But wait; cloning is prohibited by the Bible, so why are identical twins not taken out and stoned in the first place? Bah.
The only Christians whose approach to the modern world seems to me to be consistent are the Amish. If you want to live a medieval life without benefit of science, fine; just don't force me to come along.
Someday, therapies based on embryonic stem cells will be available in civilized countries for diseases like Parkinson's. Will today's evangelical Republicans stay at home and quiver, or will they swallow their dogma and travel for therapy, I wonder.
Because public access to social Web sites can only lead to dead blastocysts burning flags in support of gay marriage, and then the terrorists will have won!
For all of you outside the U.S., wondering with amazement at our news: Yes, the majority of us *are* this stupid. We have an anti-evolution screed by a hate-crazed female impersonator near the top of our best-seller list -- and that just affects the dwindling proportion of Americans who actually still read books.
I use the mouse from Microsoft's "Optical Desktop for Bluetooth" with Linux, although I had to write a new driver in order to use it at first. But it works just fine today with the stock BlueZ HID protocol code in the 2.6 kernel series, along with the Apple Bluetooth keyboard, which I prefer to the Microsoft keyboard since it looks better when all the keys have been rearranged into a sane (Dvorak) layout. See this old page where I dramaticize what it took to get these Bluetooth gadgets working.
Neanderthals mispronounced it as "nuke-you-lurr", opposed embryonic stem cell research, and weren't big fans of evolution either.
I think you mean "hear, hear!", an abbreviation for the old cry "Hear him, hear him!".
As punishment, I'm taking away all the spare apostrophes and lower-case 'o's that you probably like to stick into words like "its" and "lose".
And yes, I'm having a bitchy day and I'm taking it out on you. But you wouldn't believe the illiteracy levels I'm seeing in my corporate e-mail inbox lately. When did third-grade composition skills suddenly become optional?
And the real disastrous employees, well, don't worry about them; you don't need reviews to find them, and rarely an excuse to get rid of them. Just wait until the police, fire department or the CDC has identified the idiot who caused the whole mess and get rid of them.
Too simplistic. Organizations accumulate deadwood that must occasionally be cleared out, or progress will grind to a halt.
In my organization, I wish we could give a freshman-level C programming class final exam to everybody whose job requires proficiency in C programming.
> If I say "George Bush is an alien," should he undergo a medical examination specifically to prove that he is human...
Preferably at Abu Ghraib.
These smart, peace-loving God-fearers are called the Amish, I think.
I've got no problem with people who want to live in a community with a sixteenth-century worldview,
so long as they're consenting adults and limit themselves to sixteenth-century technology. Where
we get into trouble is when modern-day medievalists get their hands on technology created by that
Enlightenment thing they've rejected. Whether it's a muslim with C4 or a baptist with an SUV,
it's trouble coming from a mismatch of their culture's beliefs and my culture's capabilities.
So pick one or the other and stick with it -- ditch the tribal myths and wake up, or go buy
a buggy. Living in both worlds isn't going to get you any more respect than an astrologer
should expect from an astrophysicist, or an alchemist from a nanotechnologist.
He's motivated by a belief that killing innocent people will make an imaginary deity happy enough to give him an afterlife
best described as a juvenile porno Disneyland.
Religion may be socially acceptable madness, but it's no less crazy for all its popularity.
Isn't it fun to imagine spammers being sentenced to a couple hours in the stocks in the village square?
Sigh.
If you type a lot, you've got to try using an ergonomic keyboard layout.
I used to go home from work with a feeling of numbness on the backs of my hands. This scared me enough to try the Dvorak layout. It worked for me; I'm not really any faster than I was with QWERTY, but I'm *way* more comfortable. I tried to design an even better keyboard layout via evolutionary algorithms, but couldn't; Dvorak got it right, at least for my pair of hands.
Give it a try; you'll thank me later. It's free, too.
The complaint is not about general copy-on-write, it's about BSD's ZERO_COPY_SOCKET feature vs. vmsplice().
Basic explanation: Suppose that a program is doing a lot of output to a file or socket. The program can generate data faster
than the kernel can consume it, say. So what should the kernel do with the buffer it receives from the user on each write()?
There are three options.
1) Copy its content immediately elsewhere, so that on return to User Mode, the buffer remains writable and writes are safe.
2) Change the access rights of the page containing the buffer, so that no copy need be made unless User Mode attempts
to modify its content before the kernel has completed the write(). If the user attempts to write, it either gets
permission to do so (because the kernel is done) or it gets a writable copy.
3) Let User Mode promise to not modify the buffer's content until told that it's safe to do so, leaving it writable in
the meantime.
The default behavior is (1); BSD's zero copy socket feature is (2), and the point of Torvalds' complaint; vmsplice() is (3).
"I can explain it to you, but I can't understand it for you."
How would I react to a television broadcaster saying that lighting and focus weren't all that important? Or a radio station claiming that static was okay? Proper spelling, grammar, and usage are easy compared to the syntax of a programming language or shell. Get them right and I'll take you more seriously.
The rules for using apostrophes in English are simple. Why not learn them?
Try zooming all the way in on that map. :-)
What's the problem?
It's just dmr, rms, and some users.
(And where the heck is Larry Wall?)
It's sad to see legions of /.ers using semiconductor-based memory, microprocessors, and advanced networking technology to diss the achievements of the Apollo program.
We got more out of NASA than Tang and some rocks, boys.
(Personal note: my earliest memory that I can date accurately is being five years old, watching Neil and Buzz hop around the LEM on that late Sunday evening.)