Originally Posted by enorbet2
@mushroomboy There is no way an update can break a Slackware system because it does not resolve dependencies and because it doesn't it is considerably simpler and cleaner. That's the admin's job.
That says it all. I'm not saying it will not work, but to minimize downtime for a major upgrade it is nice to have something do the dependencies. If it worked so well and easy you would think it would have a high market share for servers? Not to mention major known companies would use it. I'm not saying it's inferior as a distro, but it's not automatic enough to be used as a mainstream server. When something goes down you need it back up and running now, fast and clean. Now you could do disc images, and that will work, I'm pretty sure upgrading the entire network when the new version comes out will be a bit more of a hastle. No offense but configuring and maintaining something like Fedora/Debian vs Slackware is a completely different ballgame.
I mean you could use slackware, but then the problem becomes this: You will need to pay your admins more money, because they require more learning/experience. That will cost the company time and money now, which makes it even that much worse. So what do you do? You cut things in half and use something that can be set up in minutes as a server. That's the realistic view, it's not a distro war but corporate politics.
OP: lol I was under the impression for some reason you had two completely different computers and needed to set up the sever from scratch. Idk why I thought that, you also shouldn't have to dump the DB to a backup. Though dumping the DB is always a good idea from time to time. =P It's probably that the mac addresses were manually set up.
One of those solutions might help, I'm not sure.
 I also forgot to mention major upgrades without doing a full distro upgrade. That could be a problem too as I'm sure an admin doesn't want to spend the time working on a cluster of servers updating the machines. Again you could just do one, make an image, and image the rest. You can do a build server, and run packages to the rest of them, but you still waste time on that build server. That's the advantage, updates are clean and easy. Especially when security is the #1 goal.Edited by mushroomboy - 1/11/11 at 1:08pm