Re: fresh install of OpenBSD 5.4 on an old Sparc server fails to install wget

dev <[email protected]>
Newsgroups gmane.os.openbsd.sparc
Message-ID <254420362.7263.1391934372437.JavaMail.vpopmail@webmail2.networksolutionsemail.com>
On February 9, 2014 at 3:05 AM Cory Smelosky <[email protected]> wrote:
> On Sun, 9 Feb 2014, dev wrote:
>
> <trimmed>
> >
> > Very cool .. however I don't know what it installed into /usr/local
> > but
> > I guess I can learn to live with that being a "do not touch" vendor
> > area as opposed to a "user may modify" area.
> >
>
> It seems to generally be up to the site to determine what /should/ and
> /shouldn't/ be the "user may modify" areas. `man hier` provides a
> guideline that I think at least a few people follow.  I know Solaris
> loves
> to shove things in /opt. ;)

Actually the specification states that all vendor software lives in
the /usr area and things that are from elsewhere must go to /opt/foo
where "foo" is the vendor name.  Therefore we see MySQL gets installed
into /opt/mysql for example. Logging must go to /var/opt/foo and config
must go to /etc/opt/foo area. Those are just very old rules that protect
the operating system from being mucked with and also to ensure that no
one drops a lib into someplace  searched by the runtime linker. Kaboom
is never a nice thing.

>
> Using /usr/local for this seems to date to Net/2 from the CSRG BSDs.
>  I
> can't track down SysV man pages to see if coming from Solaris had
> different conventions for stuffing files. ( I wonder where /usr/local
> and
> /opt became different things over the years...You then get the
> crazy /opt/local and stuff. ;) )
>
> Can anyone else chime in with the history of hier? ;)
>


I have to look around and get familiar with this new land. Thus far I
really like what I see. It is darn easy to install. I mean trivial. You
gotta love that. After install there are some setup thingies that I
need to look into. I don't quite get what is going on with ntpd.conf
and I need to figure out how to lock down the server to listen for
ssh connections and not much else. In fact, I like to set ssh to listen
on port 443 unless I have Apache running, which I don't yet. I find
that running ssh server to listen on 443 gets rid of the ba-zillion
silly login attempts by folks trying to use a password for root and
other common account names. I mean really, people still use passwords
out there?

Anyways, I really like what I see and with luck I will get to a point
where I can bootstrap GCC without too much magic.

dc
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.