With my thinkpad T30, if I run/sbin/poweroff whilst xorg-x11 is still running, next time I power it on I'll get a load of beeps (indicating "system board failure") when I turn it on again. Power cycling a few times makes it better again. This only started to happen with recent 2.6 kernels. If I quit xorg and then run poweroff then the problem doesn't occur.
They're only 'equivalent' at a really basic level. Sure, from an academic "what can be calculated?" POV they're the same (although *not* when time complexity is considered), but for any practical purpose they are not equivalent. Compare how long it takes to write, say, a program which adds up ten numbers read from stdin in BF or INTERCAL with how long it takes to write the same program in Ruby or Haskell...
Heh, what I always find funny about that is the USE flags section. Sure, most of the comments on there are from morons who're using Gentoo because they heard it was '1337, but some of the comments are actually genuinely correct...
Robert Jordan could then include the exact same material, give or take a few words, in the sequel, and the third in the series and so on, and he could carry on putting out the same book under a different title over and over again.
Given how little (that is, nothing) is turned on in the default install, one remote root hole is pretty damned bad. Remember that that's a remote root hole with *no* services running... Now, if they had only one remote root hole including sshd, a webserver, a mailserver and so on, that'd be something to brag about.
FibreChannel Switched Fabric can do 10GBit full duplex speeds *per link*. The ESSM800T could take sixteen of these links. I've not had a chance to work with any of this newer kit yet, but I'd imagine it's even better off connectivity-wise.
LTO2 tapes are 200GBytes each... Remember that these boxes can flashcopy (instantly do a complete copy of your data, kinda like LVM snapshot support but actually working and a hell of a lot more powerful, oh, and done in hardware), so you don't need to stop your database whilst you're waiting to write it to tape.
IBM's standard is 6+P+S (six normal, one parity, one spare). Since the monitoring setup is damned good, and the CEs are really fast in replacing drives, it seems to work. The only reason raid 6 exists at all is because EMC accidentally shipped a bunch of duff drives once.
...except that workstation class UltraSPARC CPUs, for example, had four or eight megs of cache five years ago. Heck, a ten year old hypersparc has more cache than any x86 CPU.
You're forgetting the tiny cache, the absurdly low number of general purpose registers, the crappy task switching, the lack of register windowing, the insanely long pipeline and all those other design features which aimed for "as cheap as possible" and "higher MHz even if it gives us a terrible per-MHz performance".
Except that generally, ruby *is* pretty fast for non low-level stuff. Since most of the time is generally spent doing code like sorting, text matching etc (well, for some problems anyway...) it's the speed of the underlying interpreter's code that matters.
Give serious thought to FC-IP and director-class fibrechannel kit. Performance-wise it'll thrash Ethernet, and there're various clever tricks you can do with directors clustered together via Open Trunking meaning that a bunch of 160 port boxes (a McData 6140 is your best bet here) will do as well as a larger single box.
Well, it depends upon the arch... On x86 it's about 15%, on ultrasparc it's about 40%, since v7 opcodes have to be emulated. Heck, even debian roll v9 openssl binaries because of it:)
That's because mozilla source tarballs don't compile when shipped. The last three mozilla/firefox releases have all been either broken or incomplete from a compiling-from-source perspective. The current bunch doesn't compile properly with freetype+gtk2 enabled.
The GLSA is getting there, but it's kinda hard when upstream don't release working tarballs... Debian et al have it easy, they only have to make it build on one box with one set of configure options. Gentoo has to make it compile anywhere with any set of build settings.
I don't think the author understands gentoo's kernel naming system... gentoo-sources is 2.4.x, gentoo-dev-sources is 2.6.x. The only reason they've not been merged is that portage is rather too happy to upgrade slotted versions. The -dev- part doesn't indicate that it's any less stable.
Oh, and there is no default kernel on gentoo. You install whatever you want:)
Except, as usual, the ending was totally screwed up. I've seen maybe one decent anime series (Noir) which didn't have a completely fucked conclusion. Why? WHY?
Re:POSIX Compliance issues.
on
Bash 3.0 Released
·
· Score: 4, Informative
It's a problem with autoconf, not with any Gentoo-specific scripts. You're just more likely to see it on Gentoo given how much you end up running autoconf:)
Slashdot Mirror
With my thinkpad T30, if I run /sbin/poweroff whilst xorg-x11 is still running, next time I power it on I'll get a load of beeps (indicating "system board failure") when I turn it on again. Power cycling a few times makes it better again. This only started to happen with recent 2.6 kernels. If I quit xorg and then run poweroff then the problem doesn't occur.
No they don't.
They're only 'equivalent' at a really basic level. Sure, from an academic "what can be calculated?" POV they're the same (although *not* when time complexity is considered), but for any practical purpose they are not equivalent. Compare how long it takes to write, say, a program which adds up ten numbers read from stdin in BF or INTERCAL with how long it takes to write the same program in Ruby or Haskell...
Heh, what I always find funny about that is the USE flags section. Sure, most of the comments on there are from morons who're using Gentoo because they heard it was '1337, but some of the comments are actually genuinely correct...
Robert Jordan could then include the exact same material, give or take a few words, in the sequel, and the third in the series and so on, and he could carry on putting out the same book under a different title over and over again.
Heh. See, idiots like you who think they know how to program but don't are the reason stuff like this is possible.
You're forgetting the millions of other people voting who don't understand any of the issues involved in the election.
Given how little (that is, nothing) is turned on in the default install, one remote root hole is pretty damned bad. Remember that that's a remote root hole with *no* services running... Now, if they had only one remote root hole including sshd, a webserver, a mailserver and so on, that'd be something to brag about.
FibreChannel Switched Fabric can do 10GBit full duplex speeds *per link*. The ESSM800T could take sixteen of these links. I've not had a chance to work with any of this newer kit yet, but I'd imagine it's even better off connectivity-wise.
LTO2 tapes are 200GBytes each... Remember that these boxes can flashcopy (instantly do a complete copy of your data, kinda like LVM snapshot support but actually working and a hell of a lot more powerful, oh, and done in hardware), so you don't need to stop your database whilst you're waiting to write it to tape.
IBM's standard is 6+P+S (six normal, one parity, one spare). Since the monitoring setup is damned good, and the CEs are really fast in replacing drives, it seems to work. The only reason raid 6 exists at all is because EMC accidentally shipped a bunch of duff drives once.
...except that workstation class UltraSPARC CPUs, for example, had four or eight megs of cache five years ago. Heck, a ten year old hypersparc has more cache than any x86 CPU.
You're forgetting the tiny cache, the absurdly low number of general purpose registers, the crappy task switching, the lack of register windowing, the insanely long pipeline and all those other design features which aimed for "as cheap as possible" and "higher MHz even if it gives us a terrible per-MHz performance".
Decent content? And where, pray tell is that? Even the quality of the trolls has gone down hill in the past few years...
Except that generally, ruby *is* pretty fast for non low-level stuff. Since most of the time is generally spent doing code like sorting, text matching etc (well, for some problems anyway...) it's the speed of the underlying interpreter's code that matters.
Give serious thought to FC-IP and director-class fibrechannel kit. Performance-wise it'll thrash Ethernet, and there're various clever tricks you can do with directors clustered together via Open Trunking meaning that a bunch of 160 port boxes (a McData 6140 is your best bet here) will do as well as a larger single box.
888 d8 d8 888 ,"Y88b d88 d88 888eee ,eee, ,eea888 888 888 888 888 888 ,
,8,'88b ,"'
Y8b Y8b Y888P 888eee
.Y8b Y8b Y8P 888 88b "8" 888 d88888 d88888 888 88b d88 88b
..Y8b Y8b " 888 888
...YP Y8P 888 888 "88 888 888 888 888 888 "YeeP"
.dP,e, 888
.8b " 8888 8888 e88'888 888 ee " 888D
888888 8888 8888 d888 '8 888eP 88P
.888 Y888 888P Y888 , 888 b
.888 "88e88" "88,e8' 888 8b "8"
Well, it depends upon the arch... On x86 it's about 15%, on ultrasparc it's about 40%, since v7 opcodes have to be emulated. Heck, even debian roll v9 openssl binaries because of it :)
That's because mozilla source tarballs don't compile when shipped. The last three mozilla/firefox releases have all been either broken or incomplete from a compiling-from-source perspective. The current bunch doesn't compile properly with freetype+gtk2 enabled.
The GLSA is getting there, but it's kinda hard when upstream don't release working tarballs... Debian et al have it easy, they only have to make it build on one box with one set of configure options. Gentoo has to make it compile anywhere with any set of build settings.
I don't think the author understands gentoo's kernel naming system... gentoo-sources is 2.4.x, gentoo-dev-sources is 2.6.x. The only reason they've not been merged is that portage is rather too happy to upgrade slotted versions. The -dev- part doesn't indicate that it's any less stable.
:)
Oh, and there is no default kernel on gentoo. You install whatever you want
d8 888 888 ,e e, dP"Y dP"Y
Y8b Y8b Y888P e88 88e 888,8, d88 888 ee 888
.Y8b Y8b Y8P d888 888b 888 " d88888 888 88b 888 d88 88b C88b C88b
..Y8b Y8b " Y888 888P 888 888 888 888 888 888 , Y88D Y88D
...YP Y8P "88 88" 888 888 888 888 888 "YeeP" d,dP d,dP
d8
.dP"Y d88 e88 88e 888,8, Y8b Y888P
C88b d88888 d888 888b 888 " Y8b Y8P
.Y88D 888 Y888 888P 888 Y8b Y
d,dP 888 "88 88" 888 888
888
888
Except, as usual, the ending was totally screwed up. I've seen maybe one decent anime series (Noir) which didn't have a completely fucked conclusion. Why? WHY?
Well, "ultimate" means last. As we all know, *BSD is dying, so this could well be the case.
Wait for the rsync mirrors to catch up with cvs. -r8 has been in CVS for a while...
/var/cvsroot/gentoo-x86/media-libs/libpng/libpng-1 .2.5-r8.ebuild,v
RCS file:
revision 1.3
date: 2004/08/05 10:22:53; author: ciaranm; state: Exp; lines: +2 -2
Stable on sparc, bug #59424
revision 1.2
date: 2004/08/05 10:20:27; author: lu_zero; state: Exp; lines: +2 -2
marked ppc
revision 1.1
date: 2004/08/05 10:02:19; author: plasmaroo; state: Exp;
Security bump for bug #59424.
It's a problem with autoconf, not with any Gentoo-specific scripts. You're just more likely to see it on Gentoo given how much you end up running autoconf :)