It probably means that it reinforces all the horrible disproportianate Barbie-esque way women get portrayed in video games.
Most every video game within the last 6 years up until recently always had some Big Booby McBoob character who had no reasonable explanation for why they are dressed the way they are. Think Unreal II, Heavy Metal FAKK, etc. FAKK was so bad about this. All the female characters had shrunken head syndrome, but had boobs three times the size of their head (per boob).
Alyx from Half-Life 2 looks to be an excellent turnaround from all this, though.
Computers speed up, software slows down (usually at a greater rate than the computer speeding up).
It's always taken more system resources to do the same amount of work as was done yen years ago. In all fairness, though, the user experience is much nicer now.
Nope, not bootsplash - I'm talking about Fedora actually using the X video driver and taking settings from xorg.conf and using while the system starts up. It looks much nicer since it's not running at 60 Hz like bootsplash always is.
Now I see why the Fedora way of doing a splash screen isn't really catching on - nobody else can seem to tell the difference between that and the older, crustier bootsplash.
Yeah, my next step is booting off the SuSE rescue CD and seeing if I can fsck it from there. It looks pretty hopeless, though, because the automated fsck that runs at boot time fails.
This is the first time I've actually seen an ext2 filesystem fail to let the system boot up after a forced power-down. Something is different here.
Right, but most use the framebuffer kernel extension. That's just a really basic means of getting it done. What you get is a difficult-to-configure screen that's always at 60Hz.
Fedora actually reads your xorg.conf and utilizes the X video driver being used by your system and runs at the same resolution and refresh rate. It looks really slick if you ask me.
I just killed my SuSE linux install's filesystem that way several hours ago because I had to power off due to KDE flagrantly crashing. Now I'm bored out of my mind at work because I can't pull files off of my home machine from here or SSH into it.
It would have helped had I actually been using a journalised filesystem. I wanted to upgrade to ext3 or ReiserFS, but there was no easy path to get there without losing my files and reinstalling the whole OS.
Oh well, I was about to replace it with Debian unstable anyway.
Reminds me of an old Gateway 2000 commercial where a kid is waiting for a computer to start up. It goes through a montage of the kid screwing around in the garage waiting for it.
"No, Mom! It's still starting!"
One of my friends had a theory that held true (up until Windows XP) that Windows (and MacOS at the time, this was 1995) was harmonically tuned to boot up just as long as it would take you to get up and take a piss and come back.
Though some of the Windows 2000 machines here at work make me think I have enough time to take a dump and come back. They're fast, just something is very wrong with them.
How about, uh, you know, actually loading multiple things at once instead of waiting for some service to take its time to start, therby holding everything else up along the way. That's what the problem seems to be - everything has to load in-line.
On another note, I'd like to see other distros do what Red Hat is doing to Fedora's boot screen: Using X resolutions for the startup. Damn, that looks nice! Thought it would be even nicer if the pointless resolution change between bootup and main X server startup was eliminated (it's usually the same res anyway).
When PCs start coming standard with multiple cores in the CPU and a gig or two of RAM, someone will develop Linux for Windows and a nice development environment. When you run the application on Windows, it will simply load Linux (or Linux will be loaded at startup) and run on top of this additional layer. Performance won't matter because there will be oodles to begin with. It won't matter what Microsoft as long as the top layer is consistent for developers.
The general rule has been that when computers double in speed, the applications they run triple the amount of resources used. WordPerfect 5.1 loaded instantaneously on a 286. OpenOffice Writer takes 10+ seconds to load on a typical modern machine. You won't see enough resources to run Linux as an application layer anytime soon, especially since hard drive throughput seems to be the big exception to Moore's Law.
Yes, but it pretty much has to do with providing a perpetually massive list of drivers for support upon install. Other than that, Linux has hit a barrier by not having a HAL so that drivers can be standardized (and precompiled so that regular users can install them!) between minor variations of the kernel.
Since open source developers usually have very limited resources, why is the KDE group wasting theirs on this project? There are plenty of other things that can be done to improve KDE, mainly bugfixes.
To this day, you can't open tar.gz files in a separate application by default or click the navigation buttons in rapid succession in Konqueror. The latter problem makes file browsing so much slower. Things like these need to be addressed first before wasting time on Windows.
Since Outlook SP2 blocks images now, I'm wondering if spammers have found any other workarounds to finding ways to validate users through HTML, such as other embedded objects that Outlook has...*snicker*..overlooked.
Pointless, not useless. The fact that there is usually only one coaxial input on receivers usually forces the user to use optical for other inputs.
Hell, just to use optical I had to modify some deep setting regarding which input is associated with which mode on the receiver (had to associate the coaxial input from CD player to DVD player). This can really mess things up and get confusing, since the labels on the back of the receiver always stay the same.
Can't you just mount it as a USB storage device? I was helping someone set up Linux and it autodetected the player he had and it had already mounted it. No nutty extra software required.
These specific programs just make things more complicated than they have to be. They also tend to be quickly outdated and have support abandoned. So much easier just to treat it like any other external storage device - both for the learning curve and ease of use.
A print server is called a server only because it is the central machine that houses drivers for individual printers, so the client doesn't have to. They serve printers and don't really provide any feedback to the user's machine; it's just a peer in this regard.
The way you say it, it sounds like the X server is the one serving user input to the client, which then returns window information.
Of course, this still sounds backwards for something like, say, a game of Quake or Half-Life, where users' movments and actions are sent to the server by the client and then given consequential updates by the server, which is the machine running the actual physics and such of the game (without counting client-side prediction and whatnot).
Slashdot Mirror
It probably means that it reinforces all the horrible disproportianate Barbie-esque way women get portrayed in video games.
Most every video game within the last 6 years up until recently always had some Big Booby McBoob character who had no reasonable explanation for why they are dressed the way they are. Think Unreal II, Heavy Metal FAKK, etc. FAKK was so bad about this. All the female characters had shrunken head syndrome, but had boobs three times the size of their head (per boob).
Alyx from Half-Life 2 looks to be an excellent turnaround from all this, though.
Computers speed up, software slows down (usually at a greater rate than the computer speeding up).
It's always taken more system resources to do the same amount of work as was done yen years ago. In all fairness, though, the user experience is much nicer now.
Nope, not bootsplash - I'm talking about Fedora actually using the X video driver and taking settings from xorg.conf and using while the system starts up. It looks much nicer since it's not running at 60 Hz like bootsplash always is.
Now I see why the Fedora way of doing a splash screen isn't really catching on - nobody else can seem to tell the difference between that and the older, crustier bootsplash.
Yeah, my next step is booting off the SuSE rescue CD and seeing if I can fsck it from there. It looks pretty hopeless, though, because the automated fsck that runs at boot time fails.
This is the first time I've actually seen an ext2 filesystem fail to let the system boot up after a forced power-down. Something is different here.
Right, but most use the framebuffer kernel extension. That's just a really basic means of getting it done. What you get is a difficult-to-configure screen that's always at 60Hz.
Fedora actually reads your xorg.conf and utilizes the X video driver being used by your system and runs at the same resolution and refresh rate. It looks really slick if you ask me.
I just killed my SuSE linux install's filesystem that way several hours ago because I had to power off due to KDE flagrantly crashing. Now I'm bored out of my mind at work because I can't pull files off of my home machine from here or SSH into it.
It would have helped had I actually been using a journalised filesystem. I wanted to upgrade to ext3 or ReiserFS, but there was no easy path to get there without losing my files and reinstalling the whole OS.
Oh well, I was about to replace it with Debian unstable anyway.
Then it should be a user-configurable preference. I understand there are plenty of people who would much rather prefer the plain text startup.
Reminds me of an old Gateway 2000 commercial where a kid is waiting for a computer to start up. It goes through a montage of the kid screwing around in the garage waiting for it.
"No, Mom! It's still starting!"
One of my friends had a theory that held true (up until Windows XP) that Windows (and MacOS at the time, this was 1995) was harmonically tuned to boot up just as long as it would take you to get up and take a piss and come back.
Though some of the Windows 2000 machines here at work make me think I have enough time to take a dump and come back. They're fast, just something is very wrong with them.
How about, uh, you know, actually loading multiple things at once instead of waiting for some service to take its time to start, therby holding everything else up along the way. That's what the problem seems to be - everything has to load in-line.
On another note, I'd like to see other distros do what Red Hat is doing to Fedora's boot screen: Using X resolutions for the startup. Damn, that looks nice! Thought it would be even nicer if the pointless resolution change between bootup and main X server startup was eliminated (it's usually the same res anyway).
When PCs start coming standard with multiple cores in the CPU and a gig or two of RAM, someone will develop Linux for Windows and a nice development environment. When you run the application on Windows, it will simply load Linux (or Linux will be loaded at startup) and run on top of this additional layer. Performance won't matter because there will be oodles to begin with. It won't matter what Microsoft as long as the top layer is consistent for developers.
The general rule has been that when computers double in speed, the applications they run triple the amount of resources used. WordPerfect 5.1 loaded instantaneously on a 286. OpenOffice Writer takes 10+ seconds to load on a typical modern machine. You won't see enough resources to run Linux as an application layer anytime soon, especially since hard drive throughput seems to be the big exception to Moore's Law.
Yes, but it pretty much has to do with providing a perpetually massive list of drivers for support upon install. Other than that, Linux has hit a barrier by not having a HAL so that drivers can be standardized (and precompiled so that regular users can install them!) between minor variations of the kernel.
Since open source developers usually have very limited resources, why is the KDE group wasting theirs on this project? There are plenty of other things that can be done to improve KDE, mainly bugfixes.
To this day, you can't open tar.gz files in a separate application by default or click the navigation buttons in rapid succession in Konqueror. The latter problem makes file browsing so much slower. Things like these need to be addressed first before wasting time on Windows.
You must be new....uh....to spam :)
Since Outlook SP2 blocks images now, I'm wondering if spammers have found any other workarounds to finding ways to validate users through HTML, such as other embedded objects that Outlook has...*snicker*..overlooked.
D'oh! I meant "just to use coaxial," not optical!
Pointless, not useless. The fact that there is usually only one coaxial input on receivers usually forces the user to use optical for other inputs.
Hell, just to use optical I had to modify some deep setting regarding which input is associated with which mode on the receiver (had to associate the coaxial input from CD player to DVD player). This can really mess things up and get confusing, since the labels on the back of the receiver always stay the same.
You mean, like M3U or PLS file databases - which are also just files on the drive and a de facto standard?
Can't you just mount it as a USB storage device? I was helping someone set up Linux and it autodetected the player he had and it had already mounted it. No nutty extra software required.
These specific programs just make things more complicated than they have to be. They also tend to be quickly outdated and have support abandoned. So much easier just to treat it like any other external storage device - both for the learning curve and ease of use.
As long we have people like him, we will always have plenty of pointless products like monster cable and optical AC-3 inputs for our electronics.
Check out a car that comes from outside North America. My Japanese-region Toyota only displays kph.
Yeah, Technic sets that you can build coathangers with.
* runs away from karma police *
Not fair, he posted within less than a minute of mine independently. I was kinda pissed to see that right above mine.
Way to go on getting your news from posts in past discussions!
A print server is called a server only because it is the central machine that houses drivers for individual printers, so the client doesn't have to. They serve printers and don't really provide any feedback to the user's machine; it's just a peer in this regard.
The way you say it, it sounds like the X server is the one serving user input to the client, which then returns window information.
Of course, this still sounds backwards for something like, say, a game of Quake or Half-Life, where users' movments and actions are sent to the server by the client and then given consequential updates by the server, which is the machine running the actual physics and such of the game (without counting client-side prediction and whatnot).