If you are planning this for a server, you should consider stability as one of your primary factors. Going with Breezee preview would not fit this requirement, as there will be changes in the final release. I've also heard that Breezee preview does have some issues that are getting worked out before the final release. (consider that hearsay though - I'm not sure what the issues were and can't remember the source of the comment).
So, I would favor a distro that's slightly older over one that is still in beta. If you REALLY want stability for a server, you could take a look at Red Hat Enterprise Linux, or SuSe Linux Enterprise Server. These are both targeted at servers. The downside is that they tend to be a generation or two older - but that's not too big a deal when it comes to servers. I'm not sure what would be needed to get your NIC and sound running (do you need sound on a server?) with Kubuntu (well, through their methods at least). But, adding hardware, or tweaking settings after the install is pretty common. I wouldn't be surprised if it's as simple as opening the KDE control panel (or the equivalent if you choose a gnome interface), select the NIC and assign the IP data to it. It's the part where the NIC gets detected that can be a little troublesome... My thoughts. Shawn On Thursday 06 October 2005 11:41, D Bhardwaj wrote: > I have decided to go with Kubuntu. With the exception of the nic and sound, > 5.04 loads fine on the new hardware. Next step: I am planning on putting > another nic. What, if anything, do I have to do for the os to detect the > nic? > > What are the implications of installing breezee preview? What are the > pros/cons for me to start with 5.04 now or 5.10 beta, given my limited > knowledge? > > I am searching google.com/linux as well for info. > > Thanks, > > Dharam
pgpBH2TESqZqG.pgp
Description: PGP signature
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
