[juneau-lug] Re: test
- From: "Kevin Miller" <Kevin_Miller@xxxxxxxxxxxxxxx>
- To: <juneau-lug@xxxxxxxxxxxxx>
- Date: Fri, 21 Apr 2006 09:28:13 -0800
East Wind wrote:
> Hello Kevin,
>=20
> Wednesday, April 19, 2006, 7:33:32 AM, you wrote:
>=20
>> East Wind wrote:
>>> It's back to Fedora for this me - SUSE just didn't
>>> work out for me.
>=20
>> In what respect? I've been pretty happy with it...
>=20
> Like that woodwork I see on your page!
Thanks - that's how I stay sane. (Sane being a relative term <g>)
=20
> There must be an awful lot I don't know about SUSE.
> But here's some of my frustrations:
>=20
> Failed to detect a dual processor mobo.
> When named starts it says "using 1 CPU".
> Hogwash. Get it strait, get the very basics
> right the 1st time 'cause I'm not gonna fool around
> with tweakin' make files just to get a basic install.
> I'll tweak the heck out of them files later, but not
> when I'm totally down and need a box.
If you cat /proc/version does it show you're running the default, or the
SMP kernel. I think detects it at install time, but gives you the
option to not run the SMP kernel if you don't want. But that's just
from vague memory - I could be wrong. I have named running on an SMP
box, but it's a really old version (soon to be updated).
Whether there's a SMP aware version of named (or compile time options) I
don't know. Haven't given that any thought before. I'll have to check
when we rebuild the server.
> Yast is a total slug. Come on. Get real, yast.
> When I go into my DNS server config, yast takes 30 seconds
> to read 1 stinkin' config file! I think this may
> have been due to not detecting the other CPU perhaps.
> I much prefer webmin anyways.
Yeah, it is a bit of a pig out of the gate. Not sure what it's doing,
but I suspect it's more than one config file. I'd expect that it's
walking the sysconfig directory and grabbing all the config files. But
that's just a guess. You can still use webmin. I've never managed DNS
via YaST. When I set it up (originally on 8.0) I set it up in a chroot
jail, and do all the edits by hand. Couple of minor tweaks to the
/etc/init.d/named script and it works just fine. When I need to change
it, I make my edits, change the serial number, and run "rndc reload" and
I'm golden.
YaST is a jiffy tool for managing the box, but I generally manage the
applications individually. It's just another tool - no reason it has to
be used.
=20
> There's alot more sample config files for fedora
> out on the web. I can go to the apache web site and read
> all about apache....and the files will be in the same
> place on my box. SUSE does too many includes, and fedora does too.
That can be confusing. I like to edit small files that contain related
commands so the module/includes make sense to me although it's helps a
lot to print out the top level file so I can refer to it when trying to
find what I need to edit. =20
On the other hand, it's not the stock apache approach, so it is a
distraction when looking for examples on the net and they're laid out in
a completely different way. Was just reading on /. or somewhere that
Redhat, Novell, IBM, etc and collaborating on application consistancy
sort of along the lines of the LSB project. Be nice if there was more
uniformity. Someday...
> The SUSE folks stated that their startup scripts
> and what not are alot different due to their idea
> of what a startup situation should look like.
> Nowhere did I find a clear description of their
> thinking and why they thought their startup
> situation was better. Perhaps it really is.
I don't recall what RH is doing there, but the SUSE startup scripts are
pretty stock. They live in /etc/init.d, and you have rcX.d where "X" is
0 through 5 corresponding to the different runlevels. Links to the
scripts in init.d live in there to start or kill whatever daemon is
wanted. There's a link for rc.d which points to init.d so if a program
is pointing to /etc/rc.d/ it will still work.
One thing that SUSE does with their scripts is to create a link in
/usr/sbin called rcSCRIPT where SCRIPT is the init script for some
program. For instance, if I want to stop named I just type "rcnamed
stop" instead of "/etc/init.d/named stop". Similar to the "service
named stop" with RH. No real difference beyond that that I'm aware of.
> However, with no explanation to the method to the
> madness I was lost. And I didn't search really hard
> either so perhaps that's my failing too.
Yeah, it can be annoying until you have that "Oh, that's all they're
doing" moment. Then you just roll w/the punches. =20
> As for Debian......
> Being KDE free is not an advantage!
> Perhaps I just accepted the default which was not
> to install KDE? Even fedora doesn't install KDE
> by default.
I need to try a Debian install one of these days. Played on it a little
on a box that James set up here at work, but haven't gotten into the
nuts and bolts of it yet. One nice thing about it is that it'll upgrade
packages instead of just patching them. Patching is good, but w/a two
year cycle it makes rebuilds a lot more mandatory than I like. I guess
I could pay Novell four figures to get the enterprise editions which
they support for five years, but with Debian we can just keep pulling in
the latest/greatest as needed for a longer time so I'm willing to give
it a try. Of course, all the apps, like apache, will be in the wrong
directories but I guess I can get used to that.
> Somebody....pour lighter fluid on my soapbox
> and light it up!
It's almost the weekend - will that help? :-)
S'later...
...Kevin
--=20
Kevin Miller Registered Linux User No: 307357
CBJ MIS Dept. Network Systems Admin., Mail Admin.
155 South Seward Street ph: (907) 586-0242
Juneau, Alaska 99801 fax: (907 586-4500
------------------------------------
The Juneau Linux Users Group -- http://www.juneau-lug.org
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the
word unsubscribe in the subject header.
Other related posts: