According to the report, pkgsrc is now supported in DragonflyBSD. So is DragonFly going to use pkgsrc, ports, or cook up their own solution? I'd guess that since DragonFly is free to be rather experimental that they'll try something new, but I'm sure they'll need to use something else in the mean time.
It's the fact that you can't see the big brother story that makes this so nafarious. It's there SOMEWHERE... I don't know where, but it's there dammit!
Maybe they figure all those people who bitch about the one button mouse can finally get their own. We're reaching a saturation point in America where we're only going to need the actual box - most of us already have a monitor/keyboard/mouse, and most people I know already dumped the default ones that came with the computer and got something better.
After having to use the "puck" mouse with the no numberpad keyboard, I think I'll pass on apple periperals. In any event I'm going to wait for the second generation... or maybe when the third generation comes out so I can get the second generation cheap.
I called a vendor about a problem with a MSSQL database. The girl on the phone reading out of a SQL book was worrysome enough. When she said "Doy" I got pretty worried.
In the end I just fixed it myself after she sent me the "SQL fix statment" in a Word document (yeah like I have office installed on all my servers). Guess the red flag going up after her saying "doy" was a pretty good indicator =)
It's interesting that 64bit windows requires more memory. If that applies across the board, I wonder if some people will suffer a degradation in performance because their RAM pool decreased. I doubt anyone with a 64 bit processor would skimp on RAM, but it's something to consider.
Sort of like in Linux if it's worth turning himem support on if you have a gig of ram I guess.
I'm still not sure if I buy the 2 lines per 100 though. Because after you reach a certain point of complexity, it's hard to say if application 'x' has a function that calles 3-4 routines deep if they all do "what they're supposed to" and there was faulty logic in the model of the program itself. So I'd say it's hard to base bugs off of a raw code count. But then again I don't know because really understanding how a million lines of code is pretty far over my head.
And since when is conjecture trolling? Unless using terms such as "Generally I'd say" and "I'm wondering" elude to "These are absolute facts". These statements are simply my opinion that the parent is probably not accurate based on my perceptions. Maybe windows has 360000 bugs, maybe 10 billion more - I highly doubt it and I doubt there are any facts to prove or disprove it either.
I'd think it would be smarter to use/sbin/nologin. I used to set shells to/dev/null (although FreeBSD would bitch about it not being executable) until someone pointed out that you would probably want to KNOW that someone had tried to use that account, and see it in your logs...
Well really you don't have to directly exploit sudo. You could for instance change the users path and point it at YOUR sudo which intercepts the password before passing it along to the real sudo (so the user isn't aware of what happened). Since the process is already running under the user's context that means the bad sudo can also use sudo to do whatever it wants to (I think that's how sudo works anyway)
His post is naturally tainted because of his terminology of "Windows" and "Linux". Windows IS the GUI, the shell and all that other crap that is installed by default. Any problem with anything installed by default is a hole in the OS.
Linux is just a kernel, taking vulnerabilties in "Linux" is irrelevent. You need to look at a distribution, and all distributions are different, and many FORCE you to choose options (even if you don't want to).
From my memory this is the first "Linux" privelege escalation I recall for quite a while, but it is also local. Windows has had probably about 10-12 in the last year, and many of those were remotely exploitable. (note those are vague ballpark estimations) But again you have to use the context of a distro for comparison.
Well based off of what you say, software is never improved nor fixed. Generally I'd say mature and tested software will have significantly LESS bugs than what you say. Note that a lot of crap qualifies as being a part of windows 2000, notepad, telnet, and a slew of other stuff know one knows what to do with. Some of this stuff has been drug along since NT4 or earlier, so I would say that the core windows os has much less than 360,000 bugs, even if you do coun't the garbage with it. I'm also wondering if those bugs cover logic errors where all code is correct, but there are still problems between layers and modules. God knows windows' complexity breeds enough of that...
The efficiency will transfer for a while. But then it will revert to whatever levels is "normal". The big impact that this WILL have is that people will be able to cope with hard times easier when they come again. My grandmother rationed during WWII, but that was peanuts compaired to getting through the great depression - so in her experience it wasn't really as bad as it could have been. A side effect is that no matter how good times were thereafter she never let much of anything go to waste for the rest of her life.
A company will regain the fat levels, but they'll know exactly where to trim the fat next time around, unlike some businesses that cut their core employees to suppliment overpaid worthless middle managers...
Assumably you could have a lot of data pushed down the pipe and have the hard drive cache queue the data until it can be transferred to the drive. Obviously you wouldn't get anywhere near 3Gb sustained transfer though. I'm thinking that 3Gb has more to do with the SATA standard, and nothing to do with the fact that hard drive technology is no where near that level.
For example, if you have an infestation of pests in a crop and can't use chemicals to get rid of them, at minimum you lose part of the crop and possibly lose the whole thing.
Well there's the kicker, you don't have to lose the whole thing to lose an entire field. Most farmers don't operate on really huge margins to begin with, so at what point do you say fuck it and just till the entire thing under? I'd say half, but I really don't know. So the other option is to harvest whatever you can get from a field and just charge a lot more. A lot of people just think stuff will always hop right out of the ground. Most years it's either too dry, too wet, some bug comes and eats everything, or some disease comes out of the woodwork and destroys everything. There's a reason why farmers can produce more now than they ever had, and it's not just because of machenery.
Well besides that, growing things without fertilizers means you never replinish the nutrients in the ground (or certainly not as fast as they need to be), so you have to let the ground rest more. So now you also have the added cost of not growing anything every few years (more often) on a given field.
Windows 2000 does as well, you just have to turn it on (using something like Tweak-UI). Completion doesn't have to be done using a tab either, you can bind it to other key combinations - you can also have different keys to complete either a file or directory (although I'm not sure I find that very useful).
Although this got flamebait I think I'd have to agree with general the premise. If you don't want choice and you don't want to make a decision, then by all means stay on windows. Linux (KDE/Gnome) doesn't need a bunch of people who bitch about how everything is different, they need people who want a better desktop enviornment.
What's interesting about that is how it gets stuck, but every other unix system (at least Linux and FreeBSD) all go to 1901. OSX being based off of a BSD you would think would have "time" ingraned in the system and behave in a similar fashion. I wonder why it doesn't.
The result is a homogenous, bland experience, where everything looks exactly the same.
Pfft, I don't know what sort of apps you use, but I've seen assloads of windows apps that all look and respond differently. Nero, EZ CD creator, that crap program to read pictures from my camera, PowerDVD... windows has turned into a skinning DISASTER area. And it's something that really pisses me off about windows since right around 2000 everything was nice and clean and fairly consistent. Then come the skinning apps, and comes Windows XP itself - just give me my regular widgets back!
In this environment, nothing is super simple to use, but everything is at least equally difficult to figure out.
That's very true and I think you hit the nail on the head there. I don't need stuff like photoshop filters that produce windows that look like spaceships, I need things that clearly point to what I'm trying to do.
I'd say months to a few years most likely. But with the sort of passwords that most people choose, we're probably talking a couple hours. (but that's per password)
I recall talking to a MS rep about something and he indicated that all the backend MS services for things like MSN, Hotmail, and other MS sites is handled via passport. While MS may have decided not to push passport on others, they are heavily entrenched in it at this point, and I doubt they're going to change their infastructure either.
Slashdot Mirror
According to the report, pkgsrc is now supported in DragonflyBSD. So is DragonFly going to use pkgsrc, ports, or cook up their own solution? I'd guess that since DragonFly is free to be rather experimental that they'll try something new, but I'm sure they'll need to use something else in the mean time.
As any college student writing a term paper knows, it depends on how big the font is (for the library of congress).
Seriously, where's the BIG BROTHER story here?
It's the fact that you can't see the big brother story that makes this so nafarious. It's there SOMEWHERE... I don't know where, but it's there dammit!
Maybe they figure all those people who bitch about the one button mouse can finally get their own. We're reaching a saturation point in America where we're only going to need the actual box - most of us already have a monitor/keyboard/mouse, and most people I know already dumped the default ones that came with the computer and got something better.
After having to use the "puck" mouse with the no numberpad keyboard, I think I'll pass on apple periperals. In any event I'm going to wait for the second generation... or maybe when the third generation comes out so I can get the second generation cheap.
I called a vendor about a problem with a MSSQL database. The girl on the phone reading out of a SQL book was worrysome enough. When she said "Doy" I got pretty worried.
In the end I just fixed it myself after she sent me the "SQL fix statment" in a Word document (yeah like I have office installed on all my servers). Guess the red flag going up after her saying "doy" was a pretty good indicator =)
but maybe in this instance he mistyped 'doh'
It's interesting that 64bit windows requires more memory. If that applies across the board, I wonder if some people will suffer a degradation in performance because their RAM pool decreased. I doubt anyone with a 64 bit processor would skimp on RAM, but it's something to consider.
Sort of like in Linux if it's worth turning himem support on if you have a gig of ram I guess.
Fair enough, point taken. =)
I'm still not sure if I buy the 2 lines per 100 though. Because after you reach a certain point of complexity, it's hard to say if application 'x' has a function that calles 3-4 routines deep if they all do "what they're supposed to" and there was faulty logic in the model of the program itself. So I'd say it's hard to base bugs off of a raw code count. But then again I don't know because really understanding how a million lines of code is pretty far over my head.
And since when is conjecture trolling? Unless using terms such as "Generally I'd say" and "I'm wondering" elude to "These are absolute facts". These statements are simply my opinion that the parent is probably not accurate based on my perceptions. Maybe windows has 360000 bugs, maybe 10 billion more - I highly doubt it and I doubt there are any facts to prove or disprove it either.
And my post is trolling how?
Yes I've looked over MS code and no I didn't find anything good or bad about it - mainly because I don't care.
I'd think it would be smarter to use /sbin/nologin. I used to set shells to /dev/null (although FreeBSD would bitch about it not being executable) until someone pointed out that you would probably want to KNOW that someone had tried to use that account, and see it in your logs...
Well really you don't have to directly exploit sudo. You could for instance change the users path and point it at YOUR sudo which intercepts the password before passing it along to the real sudo (so the user isn't aware of what happened). Since the process is already running under the user's context that means the bad sudo can also use sudo to do whatever it wants to (I think that's how sudo works anyway)
His post is naturally tainted because of his terminology of "Windows" and "Linux". Windows IS the GUI, the shell and all that other crap that is installed by default. Any problem with anything installed by default is a hole in the OS.
Linux is just a kernel, taking vulnerabilties in "Linux" is irrelevent. You need to look at a distribution, and all distributions are different, and many FORCE you to choose options (even if you don't want to).
From my memory this is the first "Linux" privelege escalation I recall for quite a while, but it is also local. Windows has had probably about 10-12 in the last year, and many of those were remotely exploitable. (note those are vague ballpark estimations) But again you have to use the context of a distro for comparison.
Windows has approximately 360 000 bugs
Well based off of what you say, software is never improved nor fixed. Generally I'd say mature and tested software will have significantly LESS bugs than what you say. Note that a lot of crap qualifies as being a part of windows 2000, notepad, telnet, and a slew of other stuff know one knows what to do with. Some of this stuff has been drug along since NT4 or earlier, so I would say that the core windows os has much less than 360,000 bugs, even if you do coun't the garbage with it. I'm also wondering if those bugs cover logic errors where all code is correct, but there are still problems between layers and modules. God knows windows' complexity breeds enough of that...
You can kill someone with a screwdriver. It doesn't make a murder law silly, but it does make it silly to ban screw drivers.
The efficiency will transfer for a while. But then it will revert to whatever levels is "normal". The big impact that this WILL have is that people will be able to cope with hard times easier when they come again. My grandmother rationed during WWII, but that was peanuts compaired to getting through the great depression - so in her experience it wasn't really as bad as it could have been. A side effect is that no matter how good times were thereafter she never let much of anything go to waste for the rest of her life.
A company will regain the fat levels, but they'll know exactly where to trim the fat next time around, unlike some businesses that cut their core employees to suppliment overpaid worthless middle managers...
Assumably you could have a lot of data pushed down the pipe and have the hard drive cache queue the data until it can be transferred to the drive. Obviously you wouldn't get anywhere near 3Gb sustained transfer though. I'm thinking that 3Gb has more to do with the SATA standard, and nothing to do with the fact that hard drive technology is no where near that level.
For example, if you have an infestation of pests in a crop and can't use chemicals to get rid of them, at minimum you lose part of the crop and possibly lose the whole thing.
Well there's the kicker, you don't have to lose the whole thing to lose an entire field. Most farmers don't operate on really huge margins to begin with, so at what point do you say fuck it and just till the entire thing under? I'd say half, but I really don't know. So the other option is to harvest whatever you can get from a field and just charge a lot more. A lot of people just think stuff will always hop right out of the ground. Most years it's either too dry, too wet, some bug comes and eats everything, or some disease comes out of the woodwork and destroys everything. There's a reason why farmers can produce more now than they ever had, and it's not just because of machenery.
Well besides that, growing things without fertilizers means you never replinish the nutrients in the ground (or certainly not as fast as they need to be), so you have to let the ground rest more. So now you also have the added cost of not growing anything every few years (more often) on a given field.
if you don't buy from Micro$oft you are a Communist!
If you "pirate" MS software does that make you a "freedom fighter"? =P
Windows 2000 does as well, you just have to turn it on (using something like Tweak-UI). Completion doesn't have to be done using a tab either, you can bind it to other key combinations - you can also have different keys to complete either a file or directory (although I'm not sure I find that very useful).
Although this got flamebait I think I'd have to agree with general the premise. If you don't want choice and you don't want to make a decision, then by all means stay on windows. Linux (KDE/Gnome) doesn't need a bunch of people who bitch about how everything is different, they need people who want a better desktop enviornment.
What's interesting about that is how it gets stuck, but every other unix system (at least Linux and FreeBSD) all go to 1901. OSX being based off of a BSD you would think would have "time" ingraned in the system and behave in a similar fashion. I wonder why it doesn't.
The result is a homogenous, bland experience, where everything looks exactly the same.
... windows has turned into a skinning DISASTER area. And it's something that really pisses me off about windows since right around 2000 everything was nice and clean and fairly consistent. Then come the skinning apps, and comes Windows XP itself - just give me my regular widgets back!
Pfft, I don't know what sort of apps you use, but I've seen assloads of windows apps that all look and respond differently. Nero, EZ CD creator, that crap program to read pictures from my camera, PowerDVD
In this environment, nothing is super simple to use, but everything is at least equally difficult to figure out.
That's very true and I think you hit the nail on the head there. I don't need stuff like photoshop filters that produce windows that look like spaceships, I need things that clearly point to what I'm trying to do.
From the ZynAddSubFX page: Please don't use this program to make music that is against God and Jesus Christ.
Is this deity compatible with the CrusFX 1000?
I'd say months to a few years most likely. But with the sort of passwords that most people choose, we're probably talking a couple hours. (but that's per password)
I recall talking to a MS rep about something and he indicated that all the backend MS services for things like MSN, Hotmail, and other MS sites is handled via passport. While MS may have decided not to push passport on others, they are heavily entrenched in it at this point, and I doubt they're going to change their infastructure either.