I didn't really know much about systemd being a ubuntu user, but found this giving more background on the story: https://wiki.debian.org/Debate.... The wiki does a good job detailing the technologies. Given the information, the choice of systemd is interesting.
Tell that to the dead of Korean Airlines KAL007. The wikipedia article has a few inaccuracies, but you still get the jist. The Russians thought it was an RC-135, but it ended up being a passenger airliner.
I've wanted to try out Max OS X for a while now, but due to the need for a different hardware architecture I haven't given much hope of it. Now with this change, does anyone think that they will try a demo/preview type download to wet the tastes of a potential new customer base?
"One problem with the services model is that it is based on the idea that you are giving customers crap--because if you give them software that works, what is the point of service?" McVoy says. "The other problem is that the services model doesn't generate enough revenue to support the creation of the next generation of innovative products. Red Hat has been around for a long time--for a decade now. Yet try to name one significant thing--one innovative product--that has come out of Red Hat."
What FUD...Everyone offers support services for software. Event BitKeeper does. As for RedHat not creating, it's sole business model is the support service field. Moving from business model to business model is not a model for staying in business.
This linksys print server has served me well at two locations. It can be a bit difficult to setup but supports netbios, ipx, and bsd spools for remote clients.
What ever happened to just parents setting down a set of rules and actually enforcing them? Devices like this might be the new 20th century way of being a parent, but they often tend to throw off the responsibilities of being a parent. Nothing beats being there for your kids. Take an active role for crying out loud, their only kids once.
I said nothing of capping links, only that worms can't really achieve the "Warhol Worm" status due in large part to the current infastructure. As links go fiber or the next generation technology, the likely likelyhood of a worm giong Warhol, becomes more likely.
One problem with saying that Slammer or any "flash worm" is that bandwidth and current infastructure isn't taken into account. Any worm taking on activity levels (as seen by how the whole Internet seemed to slow down) of this magnitude tend to self contain themselves at local router or node bottlenecks. As links go to fiber this won't hold, but atleast for now it does.
Perl's not a base requirement in most Linux distributions or other commercial Unix implementations. I would say it's a smart move for the FreeBSD team.
Part of the upgrade problems (7.2->8.0) were due to the major change of going to a new glibc revision. When upgrading from now on, I would suggest just using MandrakeUpdate. It uses urpmi (a nifty tool, some what similar to apt-get from the Debian world) to handle dependency issues.
I have a multi cd, dvd player..I bought it for that specific reason. I can't stand having to flip a dvd to continue a movie. I bought the directors cut of DasBoat and can't stand that it's been pressed on both sides. The simple fact is that you can buy a multi cd-dvd player, but no one manufactors a dvd player that will read a double sided dvd. Besides, the cost of the medium (the disk) and the stamping is most likely less than a dollar a disk.
I sent this in as an anonymous story, but it looks like this one got posted instead. According to www.incidents.org there is a new variant of Code Red (of which this would be the third version). This one installs a backdoor. As someone else posted here, the tell tell sign is that the buffer overwrite payload is now a string of 'X's and not 'N's as in the previous two versions of Code Red. The stakes have been raised folks.
Does this at all fix the problems when using the K7/Athlon optimziations on VIA boards like the IWILL? I've had to compile the entire 2.4.x series as K6 kernels due to the kernel panics caused by the K7 optimizations. I remember some kernel list traffic of trying to resolve this, but haven't scanned the list in several months.
I didn't really know much about systemd being a ubuntu user, but found this giving more background on the story: https://wiki.debian.org/Debate.... The wiki does a good job detailing the technologies. Given the information, the choice of systemd is interesting.
http://bigstory.ap.org/article/cockroaches-quickly-lose-sweet-tooth-survive
Tell that to the dead of Korean Airlines KAL007. The wikipedia article has a few inaccuracies, but you still get the jist. The Russians thought it was an RC-135, but it ended up being a passenger airliner.
I wouldn't say it's a dream. Microsoft is trying it now with the trial i64 version of XP Professional.
I've wanted to try out Max OS X for a while now, but due to the need for a different hardware architecture I haven't given much hope of it. Now with this change, does anyone think that they will try a demo/preview type download to wet the tastes of a potential new customer base?
What FUD...Everyone offers support services for software. Event BitKeeper does. As for RedHat not creating, it's sole business model is the support service field. Moving from business model to business model is not a model for staying in business.
Found these links when I was doing a websearch on monotone and other CMS systems.
Problems with BK's license
A critique of the license.
And a nastygram of BK to the subversion group.
Ya gotta breathe somewhere..
This linksys print server has served me well at two locations. It can be a bit difficult to setup but supports netbios, ipx, and bsd spools for remote clients.
Load Slashdot...
What ever happened to just parents setting down a set of rules and actually enforcing them? Devices like this might be the new 20th century way of being a parent, but they often tend to throw off the responsibilities of being a parent. Nothing beats being there for your kids. Take an active role for crying out loud, their only kids once.
I said nothing of capping links, only that worms can't really achieve the "Warhol Worm" status due in large part to the current infastructure. As links go fiber or the next generation technology, the likely likelyhood of a worm giong Warhol, becomes more likely.
One problem with saying that Slammer or any "flash worm" is that bandwidth and current infastructure isn't taken into account. Any worm taking on activity levels (as seen by how the whole Internet seemed to slow down) of this magnitude tend to self contain themselves at local router or node bottlenecks. As links go to fiber this won't hold, but atleast for now it does.
I am not in any affiliated with connected.com.
Perl's not a base requirement in most Linux distributions or other commercial Unix implementations. I would say it's a smart move for the FreeBSD team.
I'm just glad mine came in via fedex today.
I've dug through MSDN a while back and found this to work..
//Work around for broken for-scoping in VC++ 6
#pragma warning(disable:4127)
Part of the upgrade problems (7.2->8.0) were due to the major change of going to a new glibc revision. When upgrading from now on, I would suggest just using MandrakeUpdate. It uses urpmi (a nifty tool, some what similar to apt-get from the Debian world) to handle dependency issues.
I have a multi cd, dvd player..I bought it for that specific reason. I can't stand having to flip a dvd to continue a movie. I bought the directors cut of DasBoat and can't stand that it's been pressed on both sides. The simple fact is that you can buy a multi cd-dvd player, but no one manufactors a dvd player that will read a double sided dvd. Besides, the cost of the medium (the disk) and the stamping is most likely less than a dollar a disk.
I sent this in as an anonymous story, but it looks like this one got posted instead. According to www.incidents.org there is a new variant of Code Red (of which this would be the third version). This one installs a backdoor. As someone else posted here, the tell tell sign is that the buffer overwrite payload is now a string of 'X's and not 'N's as in the previous two versions of Code Red. The stakes have been raised folks.
I would like to see a corelation study of this information against postings to BugTraq. Information can be a two edge sword.
Until I see a link to Alan's site, this is very unreliable information. However much I might agree with it.
Does this at all fix the problems when using the K7/Athlon optimziations on VIA boards like the IWILL? I've had to compile the entire 2.4.x series as K6 kernels due to the kernel panics caused by the K7 optimizations. I remember some kernel list traffic of trying to resolve this, but haven't scanned the list in several months.
I would but most, like me, are scared of the goatse.cx link...I'll let the user beware...
Here is a URL for a story on this topic from back in January. http://linuxtoday.com/stories/15158.html