Windows XP grabs approx 95MB of memory at startup, and soon as you load iexporer > 128MB is being used. 128MB is very tight and swapping begins by just using a fucking browser!::tinfoil hat on:: Even though ram is dirty cheap, I think the reason the industry is giving 128MB is so that the computer is perceived to be slower, and users would then try to upgrade later on with stiff markups(especially since older stuff is more expensive).::tinfoil hat off::
Change Linux resolution in REALTIME!!!
on
PC Annoyances
·
· Score: 1
OMG. The parent poster is heralding the arrival of X windows's newest feature: changing resolution instantly.
It's ironic how today Microsoft declares Win98 EOL'd (which had instant res. changing) and we have this new feature everyone is so excited about.
Thanks for telling me. There is no way I'd spend 600 dollars canadian for a thing that will have no support after 3 months. Probably one can purchase extended warranty?(100 dollars?)
After looking at RH EULA, and seeing how it is not violating the GPL, here is another way to look at it:
If RedHat charges $5000(/w support) for ES and distributes binaries, then they must provide source to the end-user. This end-user can take the GPL'd source and re-distribute it as they see fit. And This is perfectly legitimate under GPL.
But what Redhat is doing instead is that 'support' is not a fixed cost and it depends on the needs of the organization. Rather than forcing everyone to pay $5000(ahem Windows), Redhat has split the cost into a fixed component and a variable component. The fixed cost is the $349 'up-front' or "buffered" payment for ES. The variable cost depends on the actual support needed.
What's interesting in the RH EULA is that it specifically says just because you paid the 'fixed-cost' does not mean you have paid for the program; but rather you must pay/buy variable-cost support for the product as well. This is clever way to comply with section 3 of the GPL.
If they didn't add this requirement, then $349 would be considered the cost of the program and hence they would have to distribute the source.
The benefit of the up-front cost of $349 is that you can install the product on as many servers as you wish(thus spreading over the cost), but you agree to buy support for each of them. If at anytime you don't agree, then you have to grab their SRPMS and build the binaries yourself.
Finally, I think my parent poster is right, RH could restrict how its binaries must be used -- the GPL is only concerned with providing source for the binaries.
Just what is so fucking interesting watching reality tv shows? They try to make it interesting with one party trying to badmouth the next(i.e. "So what do you think of Sasha?").
I don't know why people like it, but people like my bro absolutely love "american idol", "joe blow", "911", "bachelor"(in canada), etc. My bro isn't the 'regular joe'(he's pretty smart), but something of those shows appeals to him. I for one, cannot sit through any reality tv.
Real life is boring, I like to watch more interesting shows such as CSI(amazing drama).
kashif
Man, where is the story and drama of shows these days?
Nope. How is this a "Linux Benefit?". Just because we are all lazy and don't have NTFS repair utils, doesn't mean Linux is simply better because "it mounts it".
Go take a badly scratched CD and try to dd it...won't even work. The same CD can be read under Windows with Cdrwin, with some bad sectors. Is Windows somehow superior now?
"It mounted the drive without problem and was able to read most of the contents (some of it was still gone but I was able to recover my work from that day at least). So in this case Linux was better at handling NTFS than Win2K was."
This is bullshit. NTFS under Win2K was probably mounted RW and performing integrity checks on the filesytem. I would rather NTFS stop now + than continue reading a corrupt filesystem getting more corrupted(i.e. some type of journalling code kicking in even though you just wanna read).
Linux use of NTFS is done using reverse-engineering, and they may have missed integrity checking + it's mounted RO so no harm can be done.
In your case, Linux wasn't better, you were "just lucky".
Speak for yourself. It's the Jews who committed the crime of slaying the 'person on the cross'. The same is being done today by the 'Big Guys' -- if something goes against what they believe it, they declare, "You are with us or against us".
This is why there is hardly any sex depiction in games or mainstream TV...but the top 5 games online are war games: - counter strike - medal of honour - call of duty - rtcw - the free "america" game.
And coupled with domestic problems like an drinking mother and/or father, with lots of fights, yelling/screaming, unpleasant atmosphere, father's mad 'cause he hardly makes enough money to feed his family, etc.
Then they'll screw around in school, not giving a fuck or a rats ass...and if socially the kid can't fit in or has general problems with friends...a kid is just...fucked up.
Video games is just a past-time that does help channel aggression(helps me relieve my anger), but it can't be used to blame the ills of society.
To solve the ills of society, you have to understand how it got there and why. Then what to do about which conflicts with "profit", which leads to gov't/parents trying to blame something instead of themselves.
Have you read the Long email xchanges included within the kernel source? No where does it bring up your point: a dynamically loaded module doesn't have to be GPLed, while a static module has to be GPLed.
The whole point was to consider if a module is 'derived' work of the kernel - is it independant that it can run on different kernel OSs(i.e AIX, Linux, Windows, etc) or does it require linux specific features?
In Nvidia's case, they have a core-driver wrapped around a kernel-specific layer, where the driver was ported from Windows. This was the original intent of allowing non-GPL modules: porting of drivers from other OSs proves that your module is really 'non-derived'.
But if your module was initially developed under Linux and only runs on Linux, then it can be considered 'derived', as you haven't proved otherwise. Since the concept of 'derived' is ambigous, the kernel guys are now labelling symbols as GPL, LGPL, etc. Though it's going to be hard not to mix GPL and LGPL symbols(i.e. can't use a macro that references GPL code from a module that only uses LGPL symbols).
They talk about 'chat' systems in general, and how it's not the same as IM. It's left as an exercise for the reader to pull out the quotes to slap parent poster down.
P.S. Did you actually read all 8 pages of the indepth interview?
To actually support the interviewee, I think he did talk about queued IM messages - but that it wasn't designed for SIP - in that SIP is end-to-end communication system. I won't repeat what he said, but essentially he noted that you need an IM proxy on your computer storing all IMs when in "offline" mode.
Out of all distros, only Ximian seems to have the goal of integrating major apps, which include:
- galeon - open office - evolution
Sure, the other distro-makers are making Gnome/KDE easy to use with centralized GUI configuration tools, but the real work is ensuring you can take a picture in Gimp and pasting it into Open Office. For example, redhat's latest effort is making the desktops look the same under their Bluecurve theme.
The integration of major apps is not perfect yet, but I believe it is in the right direction(and the latest bounty by Gnome confirms this).
Really? Who? Have you looked at the feature-list for RPMs? It has a *LOT* of good features that makes it a joy for packaging software programs. It's very well defined and easy to write spec file format(yes its nit-picky -- but that's good), package signing, package integrity checking(i.e. missing files), package querying, dependent lib checking, SRPMS format, idea of prestine sources, package roll-back(very cool), etc.
What sucks about RPMs is that rpm *installation* utilities are stupid. RPM was designed by Redhat as a format to install/upgrade distro-packages - so all dependencies would already be satisfied. Meaning you have to explicitly provide all dependent RPMs during installation. This is the part that sucks. The higher-level utilities are not smart enough to satisfy dependencies by themselves, and we experience dependency hell.
Using a tool like apt will solve this problem, but it doesn't know if a particular RPM is 'pure' or has been 'tainted'. A 'pure' RPM only uses libs/packages provided by the distro-vendor, while a 'tainted' RPM contains custom "external" dependencies. In the latter case, apt will not be able to figure out dependent RPMs without the user providing an additional repository. However 'tainted' RPMs are the fault of the packager - and it's the packager's responsibility for dependency checking -- not RPM.
Finally, many rpms cannot work interchangibly on different distros(i.e. SuSE and Redhat) or even across multiple vendor versions(i.e. RH9.0 rpm --> RH7.2). Who's fault is this: packager and rpmbuild for making package building too damn easy.
"Looking through the bounty list, a lot of the UI stuff strikes me the same way."
Humans don't like to do a task in many different ways, because we are lazy(case in point: Perl and its TIMODOHI(or whatever they call it) method). Try to make something different for the sake of 'innovation', but not really making tasks easier for us is *not* good.
Right now, desktop environments *need* to learn and mimic ideas from established UIs(Mac, Windows) so they can reach the same level and stop playing catch-up. The Japanese learned this way as well -- they learned and copied car designs from American/Eurupeon manufacturers. Now their cars are nice.
Once catch-up is stopped, innovation can begin.
Re:Is this my first ever troll?
on
iPod-Jacked
·
· Score: 1
I'd piss in my pants from the excitement and goosebumps.
Slashdot Mirror
and 128MB would have been a 'dream'.
::tinfoil hat on:: ::tinfoil hat off::
Windows XP grabs approx 95MB of memory at startup, and soon as you load iexporer > 128MB is being used.
128MB is very tight and swapping begins by just using a fucking browser!
Even though ram is dirty cheap, I think the reason the industry is giving 128MB is so that the computer is perceived to be slower, and users would then try to upgrade later on with stiff markups(especially since older stuff is more expensive).
OMG. The parent poster is heralding the arrival of X windows's newest feature: changing resolution instantly.
It's ironic how today Microsoft declares Win98 EOL'd (which had instant res. changing) and we have this new feature everyone is so excited about.
from article:
"Snapshots are also available through Red Carpet for 5 platforms including SuSE 9 and RedHat 9."
I have Ximian Desktop2 for RH9, and Evolution 1.5 is NOT out on Evolution Snapshot or Development Snapshot Redcarpet2 channels. The latest is ev1.4.5.
Has anyone got Ev. for XD2 yet or know where to get it(without building sources)?
Kashif
Thanks for telling me. There is no way I'd spend 600 dollars canadian for a thing that will have no support after 3 months. Probably one can purchase extended warranty?(100 dollars?)
Well, why don't they just strip out parts licensed from other parties? Then those parts would be re-written with GPL'd code?
The problem with this is code containing patents(i.e. S3TC support).
I don't understand why does redhat charge you $350 bucks then.
When not negotiate a 'per-seat' deal from the start?
After looking at RH EULA, and seeing how it is not violating the GPL, here is another way to look at it:
If RedHat charges $5000(/w support) for ES and distributes binaries, then they must provide source to the end-user. This end-user can take the GPL'd source and re-distribute it as they see fit. And This is perfectly legitimate under GPL.
But what Redhat is doing instead is that 'support' is not a fixed cost and it depends on the needs of the organization. Rather than forcing everyone to pay $5000(ahem Windows), Redhat has split the cost into a fixed component and a variable component. The fixed cost is the $349 'up-front' or "buffered" payment for ES. The variable cost depends on the actual support needed.
What's interesting in the RH EULA is that it specifically says just because you paid the 'fixed-cost' does not mean you have paid for the program; but rather you must pay/buy variable-cost support for the product as well. This is clever way to comply with section 3 of the GPL.
If they didn't add this requirement, then $349 would be considered the cost of the program and hence they would have to distribute the source.
The benefit of the up-front cost of $349 is that you can install the product on as many servers as you wish(thus spreading over the cost), but you agree to buy support for each of them. If at anytime you don't agree, then you have to grab their SRPMS and build the binaries yourself.
Finally, I think my parent poster is right, RH could restrict how its binaries must be used -- the GPL is only concerned with providing source for the binaries.
it's computer science...
If it works on Mondays and Wednesdays, but not on Tuesdays and Thursdays, it's computer science...
If it blue-screens...it's Windows.
Just what is so fucking interesting watching reality tv shows? They try to make it interesting with one party trying to badmouth the next(i.e. "So what do you think of Sasha?").
I don't know why people like it, but people like my bro absolutely love "american idol", "joe blow", "911", "bachelor"(in canada), etc. My bro isn't the 'regular joe'(he's pretty smart), but something of those shows appeals to him. I for one, cannot sit through any reality tv.
Real life is boring, I like to watch more interesting shows such as CSI(amazing drama).
kashif
Man, where is the story and drama of shows these days?
Nope. How is this a "Linux Benefit?". Just because we are all lazy and don't have NTFS repair utils, doesn't mean Linux is simply better because "it mounts it".
Go take a badly scratched CD and try to dd it...won't even work. The same CD can be read under Windows with Cdrwin, with some bad sectors. Is Windows somehow superior now?
"It mounted the drive without problem and was able to read most of the contents (some of it was still gone but I was able to recover my work from that day at least). So in this case Linux was better at handling NTFS than Win2K was."
This is bullshit. NTFS under Win2K was probably mounted RW and performing integrity checks on the filesytem. I would rather NTFS stop now + than continue reading a corrupt filesystem getting more corrupted(i.e. some type of journalling code kicking in even though you just wanna read).
Linux use of NTFS is done using reverse-engineering, and they may have missed integrity checking + it's mounted RO so no harm can be done.
In your case, Linux wasn't better, you were "just lucky".
Kashif
Speak for yourself. It's the Jews who committed the crime of slaying the 'person on the cross'. The same is being done today by the 'Big Guys' -- if something goes against what they believe it, they declare, "You are with us or against us".
This is why there is hardly any sex depiction in games or mainstream TV...but the top 5 games online are war games:
- counter strike
- medal of honour
- call of duty
- rtcw
- the free "america" game.
And coupled with domestic problems like an drinking mother and/or father, with lots of fights, yelling/screaming, unpleasant atmosphere, father's mad 'cause he hardly makes enough money to feed his family, etc.
Then they'll screw around in school, not giving a fuck or a rats ass...and if socially the kid can't fit in or has general problems with friends...a kid is just...fucked up.
Video games is just a past-time that does help channel aggression(helps me relieve my anger), but it can't be used to blame the ills of society.
To solve the ills of society, you have to understand how it got there and why. Then what to do about which conflicts with "profit", which leads to gov't/parents trying to blame something instead of themselves.
...understand?
Have you read the Long email xchanges included within the kernel source? No where does it bring up your point: a dynamically loaded module doesn't have to be GPLed, while a static module has to be GPLed.
The whole point was to consider if a module is 'derived' work of the kernel - is it independant that it can run on different kernel OSs(i.e AIX, Linux, Windows, etc) or does it require linux specific features?
In Nvidia's case, they have a core-driver wrapped around a kernel-specific layer, where the driver was ported from Windows. This was the original intent of allowing non-GPL modules: porting of drivers from other OSs proves that your module is really 'non-derived'.
But if your module was initially developed under Linux and only runs on Linux, then it can be considered 'derived', as you haven't proved otherwise. Since the concept of 'derived' is ambigous, the kernel guys are now labelling symbols as GPL, LGPL, etc. Though it's going to be hard not to mix GPL and LGPL symbols(i.e. can't use a macro that references GPL code from a module that only uses LGPL symbols).
They talk about 'chat' systems in general, and how it's not the same as IM. It's left as an exercise for the reader to pull out the quotes to slap parent poster down.
P.S. Did you actually read all 8 pages of the indepth interview?
To actually support the interviewee, I think he did talk about queued IM messages - but that it wasn't designed for SIP - in that SIP is end-to-end communication system. I won't repeat what he said, but essentially he noted that you need an IM proxy on your computer storing all IMs when in "offline" mode.
Out of all distros, only Ximian seems to have the goal of integrating major apps, which include:
- galeon
- open office
- evolution
Sure, the other distro-makers are making Gnome/KDE easy to use with centralized GUI configuration tools, but the real work is ensuring you can take a picture in Gimp and pasting it into Open Office. For example, redhat's latest effort is making the desktops look the same under their Bluecurve theme.
The integration of major apps is not perfect yet, but I believe it is in the right direction(and the latest bounty by Gnome confirms this).
Kashif
"That doesn't worry me in the slightest. I have never had a master and slave on any of my IDE chains."
Neither have I. Each of the drives figures out who has a bigger penis via Cable Select and declares themselves master:)
nuff said: slave=who's you daddy
master=i am
"finger" -- try using that in a sentence amongst a group of people, "Ummm, hey John did you try to finger him?".
Self-Aware. And now are running the gov't!
"I think everyone agrees that rpms suck."
Really? Who? Have you looked at the feature-list for RPMs? It has a *LOT* of good features that makes it a joy for packaging software programs. It's very well defined and easy to write spec file format(yes its nit-picky -- but that's good), package signing, package integrity checking(i.e. missing files), package querying, dependent lib checking, SRPMS format, idea of prestine sources, package roll-back(very cool), etc.
What sucks about RPMs is that rpm *installation* utilities are stupid. RPM was designed by Redhat as a format to install/upgrade distro-packages - so all dependencies would already be satisfied. Meaning you have to explicitly provide all dependent RPMs during installation. This is the part that sucks. The higher-level utilities are not smart enough to satisfy dependencies by themselves, and we experience dependency hell.
Using a tool like apt will solve this problem, but it doesn't know if a particular RPM is 'pure' or has been 'tainted'. A 'pure' RPM only uses libs/packages provided by the distro-vendor, while a 'tainted' RPM contains custom "external" dependencies. In the latter case, apt will not be able to figure out dependent RPMs without the user providing an additional repository. However 'tainted' RPMs are the fault of the packager - and it's the packager's responsibility for dependency checking -- not RPM.
Finally, many rpms cannot work interchangibly on different distros(i.e. SuSE and Redhat) or even across multiple vendor versions(i.e. RH9.0 rpm --> RH7.2). Who's fault is this: packager and rpmbuild for making package building too damn easy.
"Looking through the bounty list, a lot of the UI stuff strikes me the same way."
Humans don't like to do a task in many different ways, because we are lazy(case in point: Perl and its TIMODOHI(or whatever they call it) method). Try to make something different for the sake of 'innovation', but not really making tasks easier for us is *not* good.
Right now, desktop environments *need* to learn and mimic ideas from established UIs(Mac, Windows) so they can reach the same level and stop playing catch-up. The Japanese learned this way as well -- they learned and copied car designs from American/Eurupeon manufacturers. Now their cars are nice.
Once catch-up is stopped, innovation can begin.
I'd piss in my pants from the excitement and goosebumps.