On 03/07/07, Daniel Griffith <[EMAIL PROTECTED]> wrote: > The Nforce networking driver and 3114 driver not working on the first > generation of the hardware without a recent bios (which isn't > available) is a major issue, for most people it is a showstopper, > people will be installing Solaris for the first time on "old" > available hardware, not buying new hardware to test an new > distribution.
Sometimes hardware has bugs that need to be fixed, that's what hardware updates are for. GNU/Linux distributions work around many bugs that probably shouldn't be. Many of the Linux kernel maintainers have some very choice words for some hardware, read through the comments :) While I agree that sometimes it may be for the greater good to workaround certain issues, sometimes, quite frankly, it is better that people update -- they're going to have a better experience with their system in the long run. > On 7/3/07, Doug Scott <[EMAIL PROTECTED]> wrote: > > Solaris is installed such that root access is denied via ssh. To get > > around this, login as root on the console and create a user account. You > > then can ssh into the user account and then su into root. > > I found the solution in seconds thanks to google, it's just an inane > situation if there is only a root account on the box. Inane, no. Inconvenient, yes. Very secure by default, most definitely. Subjective again. > > A normal user account 'should' be created as part of the installation > > process. This is coming as part of the project to rewrite the installer. > > Yeah, I assumed it wasn't deliberate, it didn't make me any happier > though as I wrestled a big heavy server full of hard disks back out of > a rack so I could attach a screen... I'm guessing that's partly because people that buy Sun hardware would have LOM (lights out management?) so this wouldn't be an issue for them. > > Init.d scripts are deprecated on Solaris nowdays. I think there are some > > SMF manifest files for samba on the net. Just try a search for "smf" and > > "samba". (SMF leaves Linux/Solaris/whoever init.d for dead) > > I think that's a matter of opinion:) I don't know anything about SMF > but I've just had a look at > http://www.cuddletech.com/blog/pivot/entry.php?id=182 and it looks > total overkill for Indiana. Maybe if I was running a 32 cpu multiuser > box SMF would be great, but thats a job for Solaris not Indiana - XML > manifests? Shudder. Matter of opinion; SMF is a far more comprehensive solution than what most Linux distributions provide. While it may seem like overkill, it really isn't. SMF is the future, and it is part of the self-healing functionality that Solaris provides. Spend some time with SMF and you'll understand why it is preferred over the legacy methods most UNIX/Linux OS' use. > I've spent three weeks with Solaris, I think it would be very > productive for people here to spend 3 weeks with Gentoo:) Someone here > yesterday was writing about his attitude towards Linux, and then said > he was a Slackware user - people here need to spend some decent time > with a _modern_ linux distribution and then ask themselves what > Indiana can offer that would be preferable - becouse at the moment you > seem to be shooting for what Linux was like 5 years ago, rather than > where it is today. Actually, many of us have used "modern linux boxes." I use Ubuntu for some ports I maintain, and RedHat Enterprise Linux all day at work. I've used Gentoo, Fedora, RedHat since the very early days, Slackware, and many others. Please don't assume that folks around here that don't care for certain suggestions don't have experience with a lot of GNU/Linux distributions and/or other operating systems. -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
