1.I think that consumers are going to want their music online in a variety of formats and the record companies need (and desperately want) to find a way of satisfying those demands.
2.Let's face it -- taping off the radio is time-consuming and quality is lousy. On the Internet however, it is extremely easy to download and the audio quality is near CD.
3.The only issue would be if you decided you wanted to download somebody else's copy of John Denver's Greatest Hits (which was likely from a CD, and a much higher audio quality).
The RIAA dearly wants to be able to tap into the kind of upgrade-fervor that we saw during the rise of the PC. Enter routine quality improvements. The best part, of course, is that its all in software now, no more convincing consumers that they need to go buy a SACD deck, or hardware that supports the latest DVD-releated refinement. The trick is, the improvements must be staggered to reap fat sacks of cash money before people catch on (which probably never will if the RIAA playes their hand right, nice 5.1 system man, really brings out the punchy mids in that 320k AAC track). The problem they face is that the tech industry moves too fast to maximize profits. So they encumber it with legislation, and sue anyone who gets ahead of the game.
Don't like the idea of constantly having to re-buy your entire collection over again at the highest bit rate (taken from the masters so you know that shit is tight!)? No problem, they'll have a subscription plan.
Kavi.com probably needs a competent unix (mostly linux last I knew) sysadmin, they may not pay for shit but atleast you'd be working with cool people who for the most part "get it." I wouldn't let the fact there's no position being actively advertised via the usual routes deter you. Sooner or later they will have to find my replacement.
The market is horrid for some things, unix (by which I don't mean HP-UX or AIX) system administration certainly seems to be unheard of. If you're still hiring you should post the requirements to this thread.
i'd like to take this opportunity to complement the Cobalt Raq Users List members as well. without people like bruce timberlake, jeff lasman, steve werby (a/. contributor) and a whole host of others (can't name everyone) the raq has a vibrant community of admins willing to help even the newbiest of owners.
Well while you're doing that I'd like to thank the NetBSD folks for ensuring that I don't have to worry about any more vendor lock-in on Cobalt's MIPS hardware. Cobalt has a horrid history of providing security updates for their products. Sun's purchase didn't really improve that by any appreciable margin. For their x86 stuff it wasn't that hard to just install your favorite distribution, though it did involve some kernel patching. For the MIPS stuff, NetBSD is the only real answer if you want to stay current and secure. (unless its a qube 2700 in which case your best corse of action is currently buying some dirt and turning it into a planter)
BTW, while the RM5231 is 64bit capable its run in 32bit mode.
Re:Drive reliability/backups are major factors
on
IDE RAID Examined
·
· Score: 1
Build another [preferably bigger] array off-site and use rdiff-backup or something similar to mirror it and its changes over time. You can also get a removable bay and use single IDE drives for incrementals if your change sets are small enough to permit that.
Actually it depends on the mbox varient.
mboxrd can be reversed, mboxo can't, mboxcl and mboxcl2 both suck as well. If I had a link to qmail's mbox(5) man page I would post it, but I don't.
This is not a "Unix bug," this is a bug in the way your MUA is interpretting your mbox-format mail spool. From_ quoting is normal in many varients of the mbox file format. The best fix is to use a better spool format like Maildir that doesn't require any content quoting.
ok, obviously my post will be rejected as this one already made it through (they rejected Marc's initial story which I guess shouldn't surprise me), but here's more linkage about where you can read about the technical details:
I have a classic (one for home one for work actually) and I've been using it for roughly two years now. I really like it. At first, yeah, those combos were a pain, then I decided that they key placement wasn't ideal so I just remapped stuff until I could cope. Hardware remapping is a beautiful thing. The first thing to go was Caps Lock, replaced by ctrl. Once that was done I just about didn't need anything else, combos were a cinch. Note - I use vi. Emacs users would probably have to take further actions if they found the positioning of the other keys inconvenient.
The biggest problem I have with the kinesis is that the firmware is buggy and modes stick. Evidently Kinesis claims this its not the firmware (some of the ergo sites have discussion boards, see those for more details) but I'm pretty sure they're wrong. The revision I have on both of my Kinesis Classics is "$copyright 1986 - 1999 by interfatron-bbc, ltd., rev 2.48a 03/06/99" (hold down both shift keys and press F12 to dump the revision) and occasinally "shift" sticks and I end up typing in all caps without realizing it, pressing shift again (either one) fixes the problem. I'd say it happens about once a day, maybe twice during good use. Now a co-worker of mine bought a Kinesis MPC (has a Macintosh ADB adapter or something IIRC) he had a different firmware revision in his and for him the control key "stuck" once per day or so. If you are thinking about getting a Kinesis (this bug aside I really do like them) don't be surprised when you run into this. Throwing down $200-$300 for a keyboard with a buggy firmware definately isn't for everyone.
While I'm not saying that companies should always be able to get their domain names back from squatters, everyone can agree that a company has the right -- and the need -- to maintain its identity without being taken advantage of by pornographers or warez traders.
No, not everyone. I don't agree that a company has that right, and I bet I'm not alone. As far as I'm concerned, in the chaos of the net you get to sink or swim on your own merits and companies don't get any special perks. The real irony here is that some of these so-called pornographers actually supply more content than the domains they ape, but you suggest we should take measures to prevent that.
(UNFAIR Term applied to advantages enjoyed by other people which we tried to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY, UNDERHAND, and JUST LUCKY I GUESS. --The Hipcrime Vocab by Chad C. Mulligan)
Go ahead and try to find a K7 board from Asus. It isn't easy if you live in the states. Asus apparently makes two, the K7M and the K7V, but they aren't mentioned anywhere on their US site. Initially rumor had it that Asus would be releasing their K7 board(s) in the US in November but would be using a different company to market them so they didn't "insult" Intel. Given the quality of Asus boards I personally planned on buying one regardless, however now I hear they will be openly marketing them themselves, so perhaps there is hope for Asus yet.
No. Using the distribution of your Operating System as a crutch, regardless of the OS, is still wrong. It isn't enough to just keep your software up-to-date. 21 patches from Red Hat, or 5 service packs from Microsoft, neither one is replacement for knowing what the hell you're doing.
But thats the way it always is isn't it? Scads of people indigent about the superiority of their system but who can't be bothered by little details of how it all works. "Don't confuse me with the facts!"
Re:Mother board Madness..
on
K8 Details
·
· Score: 1
A few places have motherboards, I've seen online shops selling FIC, Gigabyte, and MSI boards. However I've heard there is a bug in the AMD-750 chipset and that these boards will be recalled shortly. Personally I'd wait for the ASUS board anyway.
clarification: its bloat in that there are umpteen packages which all prescribe to do something slightly different yet unfortunately some tend to tromple onto others leading to redundancy. Its a natural biproduct of having a big hacker base. Its not really all bad, and its certainly better than having no choice at all.
Re:Maybe it is redundant.
on
On Perl 5.6
·
· Score: 1
Ack! I see what you mean about/. eating the code! Of course it looked grand in the preview but as soon as I submitted my post it posted the translated form of what I was previewing... real slick.
that should have looked like: # given $_ = "XXX <foo bar> quux> XXX"; s/<.*?>//g; print "$_\n"; # will return 'XXX quux> XXX' # where as $_ = "XXX <foo bar> quux> XXX"; s/<.*>//g; print "$_\n"; # will return 'XXX XXX' # its not redundant, just different
Re:Maybe it is redundant.
on
On Perl 5.6
·
· Score: 1
# given $_ = "XXX quux> XXX"; s///g; print "$_\n"; # will return 'XXX quux> XXX' # where as $_ = "XXX quux> XXX"; s///g; print "$_\n"; # will return 'XXX XXX' # its not redundant, just different
For the most part this is probably harmless, adding more cruft to Win32::* is no biggy, and it won't affect us non-windows folks anyway, only help the poor bastards stuck maintaining NT or some such. There is only one concern I have... if they add stuff to the core. Microsoft does not have the respect for programing language design that they should. Look at VB, its practically designed by focus groups. As long as there remains a sanity check in force on what gets added the core of Perl we should be fine. But the last thing Perl needs is a few more weird-ass core methods or syntax kludges, we got enough of those already.
I like Raul. Its very clean, works well in a variety of color depths, and isn't too Linux specific. However it has problems. As someone else mentioned, its similar to a few other logo's. (its probably worthwhile to note that its similar in spirit to the Jini logo, though not in execution)
Jeanette is a high quality logo which would scale well and grabs the eye. I do wonder about the association with a bug though, if we are to believe that a logo should be designed to the fit the frame of mind of the masses then choosing an insect, regardless of the true intent, might not be such a hot idea.
Villate probably won't scale well enough, and might not look real good in lower bit depths. Drop shadows look good on web pages, but translate lousy to other media. (Oh the irony)
Guatamnlad is too linux specific for my tastes. It would however probably scale well and look fine in b&w or 8bit color. Still, I find it unexciting to look at. Redhat has a cool logo, Suse has a cool logo, Debian can do better than this.
Captain Blue Eye must die. I've found this logo disturbing from day 1. Sure it meets the logo criteria for scalability, color, etc. But its just not engaging enough.
So while I really like Raul and I think it would make a fine logo I think we should be concerned about its similarity to other common place logos. A theme I think that Debian would do good to explore is the theme of the Debian wax seal. There was one submission in the Gimp logo contest with this theme, and while it didn't translate well, (bad jpeg compression artifacts really detracted from its beauty I think) it was a really good idea. A stylized wax seal could be just as eye catching as Raul, but avoid the similarity issues. It could easily be transmogrified from a simple 2 tone line drawing to a full-on photorealisitc image, all while retaining clarity and re-enforcing the Debian "brand". All we need now is for someone to go draw it.;-)
I've taken one or two aborted attempts at this idea myself, but I found that I just wasn't deft enough with the Gimp to do it justice. I'm hoping that someone else gives it a try.
Slashdot Mirror
Sure, but portability is still a problem.l
http://cr.yp.to/unix/disablenetwork.htm
Let me just warn anyone who wants to play with that particular combo right now - it doesn't work so hot.
xfs on a raid0 partition will corrupt its logs every time yeilding some spew about "bad clientid"
Been this way since test2 evidently as its been reported to the xfs list already, I just ran into it with test4 and test5.
2. Let's face it -- taping off the radio is time-consuming and quality is lousy. On the Internet however, it is extremely easy to download and the audio quality is near CD.
3. The only issue would be if you decided you wanted to download somebody else's copy of John Denver's Greatest Hits (which was likely from a CD, and a much higher audio quality).
The RIAA dearly wants to be able to tap into the kind of upgrade-fervor that we saw during the rise of the PC. Enter routine quality improvements. The best part, of course, is that its all in software now, no more convincing consumers that they need to go buy a SACD deck, or hardware that supports the latest DVD-releated refinement. The trick is, the improvements must be staggered to reap fat sacks of cash money before people catch on (which probably never will if the RIAA playes their hand right, nice 5.1 system man, really brings out the punchy mids in that 320k AAC track). The problem they face is that the tech industry moves too fast to maximize profits. So they encumber it with legislation, and sue anyone who gets ahead of the game.
Don't like the idea of constantly having to re-buy your entire collection over again at the highest bit rate (taken from the masters so you know that shit is tight!)? No problem, they'll have a subscription plan.
Off topic, but FYI djbdns has support for arbitrary record types, as a good DNS server should.
Kavi.com probably needs a competent unix (mostly linux last I knew) sysadmin, they may not pay for shit but atleast you'd be working with cool people who for the most part "get it." I wouldn't let the fact there's no position being actively advertised via the usual routes deter you. Sooner or later they will have to find my replacement.
The market is horrid for some things, unix (by which I don't mean HP-UX or AIX) system administration certainly seems to be unheard of. If you're still hiring you should post the requirements to this thread.
Build another [preferably bigger] array off-site and use rdiff-backup or something similar to mirror it and its changes over time. You can also get a removable bay and use single IDE drives for incrementals if your change sets are small enough to permit that.
Actually it depends on the mbox varient.
mboxrd can be reversed, mboxo can't, mboxcl and mboxcl2 both suck as well. If I had a link to qmail's mbox(5) man page I would post it, but I don't.
This is not a "Unix bug," this is a bug in the way your MUA is interpretting your mbox-format mail spool. From_ quoting is normal in many varients of the mbox file format. The best fix is to use a better spool format like Maildir that doesn't require any content quoting.
ok, obviously my post will be rejected as this one already made it through (they rejected Marc's initial story which I guess shouldn't surprise me), but here's more linkage about where you can read about the technical details:
Marc's Passport Advisory
I have a classic (one for home one for work actually) and I've been using it for roughly two years now. I really like it. At first, yeah, those combos were a pain, then I decided that they key placement wasn't ideal so I just remapped stuff until I could cope. Hardware remapping is a beautiful thing. The first thing to go was Caps Lock, replaced by ctrl. Once that was done I just about didn't need anything else, combos were a cinch. Note - I use vi. Emacs users would probably have to take further actions if they found the positioning of the other keys inconvenient.
The biggest problem I have with the kinesis is that the firmware is buggy and modes stick. Evidently Kinesis claims this its not the firmware (some of the ergo sites have discussion boards, see those for more details) but I'm pretty sure they're wrong. The revision I have on both of my Kinesis Classics is "$copyright 1986 - 1999 by interfatron-bbc, ltd., rev 2.48a 03/06/99" (hold down both shift keys and press F12 to dump the revision) and occasinally "shift" sticks and I end up typing in all caps without realizing it, pressing shift again (either one) fixes the problem. I'd say it happens about once a day, maybe twice during good use. Now a co-worker of mine bought a Kinesis MPC (has a Macintosh ADB adapter or something IIRC) he had a different firmware revision in his and for him the control key "stuck" once per day or so. If you are thinking about getting a Kinesis (this bug aside I really do like them) don't be surprised when you run into this. Throwing down $200-$300 for a keyboard with a buggy firmware definately isn't for everyone.
> Geeks are little different from lepers, when you look at it.
;)
Won't argue with you there.
No, not everyone. I don't agree that a company has that right, and I bet I'm not alone. As far as I'm concerned, in the chaos of the net you get to sink or swim on your own merits and companies don't get any special perks. The real irony here is that some of these so-called pornographers actually supply more content than the domains they ape, but you suggest we should take measures to prevent that.
(UNFAIR Term applied to advantages enjoyed by other people which we tried to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY, UNDERHAND, and JUST LUCKY I GUESS.
--The Hipcrime Vocab by Chad C. Mulligan)
Go ahead and try to find a K7 board from Asus. It isn't easy if you live in the states. Asus apparently makes two, the K7M and the K7V, but they aren't mentioned anywhere on their US site. Initially rumor had it that Asus would be releasing their K7 board(s) in the US in November but would be using a different company to market them so they didn't "insult" Intel.
Given the quality of Asus boards I personally planned on buying one regardless, however now I hear they will be openly marketing them themselves, so perhaps there is hope for Asus yet.
No.
Using the distribution of your Operating System as a crutch, regardless of the OS, is still wrong. It isn't enough to just keep your software up-to-date. 21 patches from Red Hat, or 5 service packs from Microsoft, neither one is replacement for knowing what the hell you're doing.
But thats the way it always is isn't it? Scads of people indigent about the superiority of their system but who can't be bothered by little details of how it all works. "Don't confuse me with the facts!"
A few places have motherboards, I've seen online
shops selling FIC, Gigabyte, and MSI boards. However I've heard there is a bug in the AMD-750 chipset and that these boards will be recalled shortly. Personally I'd wait for the ASUS board anyway.
clarification:
its bloat in that there are umpteen packages which all prescribe to do something slightly different yet unfortunately some tend to tromple onto others leading to redundancy. Its a natural biproduct of having a big hacker base. Its not really all bad, and its certainly better than having no choice at all.
Ack! I see what you mean about /. eating the code! Of course it looked grand in the preview but as soon as I submitted my post it posted the translated form of what I was previewing... real slick.
that should have looked like:# given
$_ = "XXX <foo bar> quux> XXX";
s/<.*?>//g;
print "$_\n";
# will return 'XXX quux> XXX'
# where as
$_ = "XXX <foo bar> quux> XXX";
s/<.*>//g;
print "$_\n";
# will return 'XXX XXX'
# its not redundant, just different
# given
$_ = "XXX quux> XXX";
s///g;
print "$_\n";
# will return 'XXX quux> XXX'
# where as
$_ = "XXX quux> XXX";
s///g;
print "$_\n";
# will return 'XXX XXX'
# its not redundant, just different
.*? isn't actually redundant, its just the less greedy form of .*
but yeah, as if the regex syntax wasn't hairy enough already...
You know we already have languages specifically for parsing grammars. Extending Perl till its bloated beyond all belief, heh, thats what CPAN is for.
For the most part this is probably harmless, adding more cruft to Win32::* is no biggy, and it won't affect us non-windows folks anyway, only help the poor bastards stuck maintaining NT or some such. There is only one concern I have... if they add stuff to the core.
Microsoft does not have the respect for programing language design that they should. Look at VB, its practically designed by focus groups. As long as there remains a sanity check in force on what gets added the core of Perl we should be fine. But the last thing Perl needs is a few more weird-ass core methods or syntax kludges, we got enough of those already.
I like Raul. Its very clean, works well in a variety of color depths, and isn't too Linux specific. However it has problems. As someone else mentioned, its similar to a few other logo's. (its probably worthwhile to note that its similar in spirit to the Jini logo, though not in execution)
Jeanette is a high quality logo which would scale well and grabs the eye. I do wonder about the association with a bug though, if we are to believe that a logo should be designed to the fit the frame of mind of the masses then choosing an insect, regardless of the true intent, might not be such a hot idea.
Villate probably won't scale well enough, and might not look real good in lower bit depths. Drop shadows look good on web pages, but translate lousy to other media. (Oh the irony)
Guatamnlad is too linux specific for my tastes. It would however probably scale well and look fine in b&w or 8bit color. Still, I find it unexciting to look at. Redhat has a cool logo, Suse has a cool logo, Debian can do better than this.
Captain Blue Eye must die. I've found this logo disturbing from day 1. Sure it meets the logo criteria for scalability, color, etc. But its just not engaging enough.
So while I really like Raul and I think it would make a fine logo I think we should be concerned about its similarity to other common place logos. A theme I think that Debian would do good to explore is the theme of the Debian wax seal. There was one submission in the Gimp logo contest with this theme, and while it didn't translate well, (bad jpeg compression artifacts really detracted from its beauty I think) it was a really good idea. A stylized wax seal could be just as eye catching as Raul, but avoid the similarity issues. It could easily be transmogrified from a simple 2 tone line drawing to a full-on photorealisitc image, all while retaining clarity and re-enforcing the Debian "brand". All we need now is for someone to go draw it. ;-)
I've taken one or two aborted attempts at this idea myself, but I found that I just wasn't deft enough with the Gimp to do it justice. I'm hoping that someone else gives it a try.