Linked by Dedoimedo on Thu 17th Mar 2011 23:17 UTC
Debian and its clones Writing about Debian is not a simple thing. You know it's the giant that has spawned pretty much every other distro out there. It's almost like a Roman Empire, almost a taboo. Furthermore, it's not a desktop distro per se. It's more sort of a template you use to build your platform. It's also a SOHO server distro, therefore it more fits into the business category, comparable to CentOS and similar.
Thread beginning with comment 466910
To view parent comment, click here.
To read all comments associated with this story, please click here.
Anonymous Penguin
Member since:

Ubuntu seems to be more focused on setting up the desktop in such a way that everything is where a user probably expects it to be. And the software is and needs to be more up to date than on the server.

With Debian the desktop users are more of a second-class citizen I think or atleast should be familiar with Debian.

On average it takes me 2 or 3 hours to install Debian from scratch, including all necessary software, proprietary drivers and plugins and some customization.

Once done it can be used for years by users without too many pretences such as "parents". All that is needed is the security updates.

After all so many people are still using a 10 years old OS, Windows XP.

Reply Parent Score: 3

jabbotts Member since:

If you haven't already, you can probably shave much off that install time by using some basic bash scripts.

one to copy a modified source.list, retrieve repository keyrings and any other "repo setup" stuff.

one to install your choice of packages

aptitude install \
vim less \
openssh-server \

and so on. I use rows to group similar categories of packages but the "\" lets me wrap the lines so I can read wtihout panning right and left.

one to generate your certificates and copy them in place since they should exist before heavy config happens.

one to do the heavy config once certificates are in place. This can easily be a combination of pre-modified config files copied into place, sed replacements or whatever other scripting tricks you can use to edit config files and reduce what must be pre-modified and copied over.

after all that

one to run regularily to do package updates and maintenance.

Granted, this isn't how I setup a new user but this is how I build out there system for them along with any of my own systems or servers. Makes dev systems easily repeatable and production systems quick to rebuild. It's actually faster to rerun my build scripts than to fetch the drive image from the backup locker.

Reply Parent Score: 2