[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Anyway to use chroot apache on /home instead of /var?
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: Anyway to use chroot apache on /home instead of /var?
- From: jared r r spiegel <jrrs_(_at_)_ice-nine_(_dot_)_org>
- Date: Sat, 15 May 2004 02:34:30 -0600
- Mail-followup-to: jared r r spiegel <jrrs_(_at_)_ice-nine_(_dot_)_org>, misc_(_at_)_openbsd_(_dot_)_org
On Fri, May 14, 2004 at 11:19:56PM -0500, Sean and Nina wrote:
> I have more space on my /home partition and wanted to use /home for
> apache but I don't want to turn off chroot.
do not be afraid of learning from unforseeable partitioning
mistakes. the first time i installed openbsd, i made /var
*waaaaaaaaay* too small, next time i made it way too big,
time goes on, you get better ideas about how to do it nextime.
installing openbsd is hysterically simple, don't cling to a
fear of not (re)installing again just for the sake of not
another poster mentioned reading the manpage about the '-d',
seeing as how:
> With Gentoo I was used to using /home for apache.
we could give you the benefit of the doubt and assume that since
you've used gentoo before, you may never have even been instructed
by any of their documentation to read a manpage. or maybe the since the
system had compiled *roff to be specifically for *your* computer, the
manpages had too high of a framerate for your monitor and they could
not be displayed?
but all that aside; what you might find to be a helpful aside is
what i end up doing now -- i mount a partition on /var/www; works out
nicely for convenience's sake if i ever need to treat *it* and the
stock /var/www differently.; also, what would matter most in your
situation, wouldn't matter for squat how big /var was.
what would likely serve you best is DON'T try to make openbsd an
iota like gentoo, leave it like openbsd. any time you do a snapshot
upgrade, or make build, mergemaster, etc, you're going to run into having
to maintain(ence) the fact that apache is not where everything which was
created to automate the process for you and make your job of administering
the system easier and more hassle free.
i don't know offhand if you could symlink /var/www to point to /home/apache
or whatever you had in mind, but using anything other than /var/www for
it is going to be a pain in your own ass for anything beyond perhaps
migrating configuration whatnot you might be pulling from gentoo.
it could be said that for anyone who would not have a pain in the ass
managing that, they likely wouldn't have reason to ask a peep about anything
to do with it...
and to head this one off at the pass, since gentoo was mentioned, you may
be attracted to the idea of putting all types of fancy CFLAGS into /etc/mk.conf
in order to make things "faster". besides being able to search the archives
and find hundreds of well thought-out posts by nick@ and others about why it's
a total waste of your lifetime to do that; i'll offer this reason:
i have two machines, a pIII/450 and a k6-2/500. i usually have each of them
running -current, but rarely the same day's current. obviously the pIII
will make build /usr/src in much less time than the k6. upgrading from
snapshot is just amazingly simple to do, but in despite of that i have
frequently and nearly always upgraded from source. it makes sense to do when
one has much learning about the system yet to do, but has made it far enough
to be able to do it successfully ( but if you try, don't post to misc@ with
trouble until you've perhaps wiped and refetched /usr/src and followed the
upgrade mini-faq *to the letter* several times, otherwise ppl will hate you ).,
but anyway; i realized just last night that i could be doing a make build on
the pIII ( which takes about 2.5h all told ), and then *make release* on it,
and then use the install sets that created to drop onto the k6; saving me about
8 hours of time even without having done an upgrade via snapshot initially
on both ( which would probably take 45m, download time non-withstanding ).
this would likely be confounded and made perhaps impossible if i was CFLAGSing
-march=i686 on the pIII just because i could; as then the k6 might run into
some brick wall somewhere. in other words, you *WILL* lose more minutes/hours
of your life making wild and crazy or even simple unneeded CFLAGS to everything
just to suit your fancy than if you just left it be. somethings might run
1% slower, but when you look at the hole picture, you will be saving time; it
just may take a long time to realize this.
( note: most of that is not directed straight at OP, but hopefully anyone
from a gentoo mindset experimenting with openbsd. )
[ openbsd 3.5 GENERIC ( may 10 ) // i386 ]
Visit your host, monkey.org