Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

fedora 7



> On 6/3/07, David Kramer <david-8uUts6sDVDvs2Lz0fTdYFQ at public.gmane.org> wrote:
>> That's just the thing.  There is no such thing as "standard command line
>> admin tools".  Unless you call vi/emacs "standard command line admin
>> tools".  Every distro has their own thing.  Fedora has system-config-*.
>>    SUSE has YaST.  To this day, we still have different locations for
>
> adding users, configuring interfaces, configuring nfs or samba can all
> be done with the standard tools adduser/useradd, ifconfig, etc on any
> distro.  And yes, you can also hack the configs manually, because
> that's all those tools are really doing.

I think you're proving my point here.
Some systems have adduser, some have useradd, some have neither.  ifconfig
can manipulate the current state of the network, but it doesn't modify the
config files so if you reboot the system that configuration is saved.

>> major package's files between distros, and that's just silly and
>> counterproductive.  Does your apache put the DocumentRoots in /srv or
>> /var?  Is it called httpd, apache, or apache2?
>
> It takes running a few different distros to realize where things go.
> In RHEL/Fedora it would be /var/www/html whereas Debian/Ubuntu is it
> just /var/www.

... And SUSE uses /srv/www.  That's my point.  I'm not saying it's hard to
figure out, I'm just saying it's not consistent.  All those efforts to
unify it are not working, because some of the decisions are hard, but this
is an example of a REALLY STUPID thing to not be agreed upon.

> Samba is not that difficult.  And even so, Ubuntu offers a nice
> template file so that you can just uncomment the values you want or
> crib your own.  Then just do smbpasswd -a user, followed by
> /etc/init.d/samba restart.

I have not found that to be the case, but that's partly because I am
supporting multiple versions of Windows at home.  I have yet to stumble
upon an authentication setup that works for all of Linux and Windows XP
and Windows 2000 connecting to my Linux box.  Maybe I haven't stumbled
upon the right HOWTO, but "Just do these three tweaks" hasn't worked for
me yet.

>  X is difficult by hand, but you can always
> use Xorg -configure to auto-generate a base config for you.  In
> Debian/Ubuntu, you can use dpkg-reconfigure xserver-xorg and go
> through the curses dialog.  iptables is also not difficult, if you
> have some experience, like anything.  And you can always read the man
> page or /usr/share/doc.

Basic iptables isn't that hard, but getting it to a point that I would be
confident my always-on server is as as secure as it could be is not.  Yes,
I could learn it better, but I found the tool "Firestarter" and fell in
love with it.  It's awesome.

> vintage?  You mean out of date?  This is certainly not true of
> Debian/Ubuntu, as the server and desktop packages utilize the same.
> You can always search packages.ubuntu.com for more info...

You asked me what I heard and I told you.  The Ubuntu website doesn't even
tell you what packages are included in each version, let alone what
version.  I can look at the above URL, but that was the first I saw it.

> Try Xubuntu instead,  It has fewer requirements since it runs Xfce as
> the default desktop.  Or you could install Ubuntu and replace Gnome
> with fluxbox or blackbox...

That may work, but it wouldn't be a fair test of what Ubuntu feels like on
a full install, which is the whole point.  I'll wait till I get better
spare hardware.



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.







BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org