Ajai Khattri wrote:
On Sun, 5 Jul 2009, Matt Juszczak wrote:
I see FreeBSD do this (separate user-installed packages into /usr/local),
but Linux always seems to install extra packages and user-generated
content in /usr as the root. IE: mysql & apache. Always wondered why the
separation was
On Sun, Jul 5, 2009 at 5:41 PM, Adrian Noland wrote:
>
>
> On Wed, Jul 1, 2009 at 9:48 AM, David Mintz wrote:
>
>> Perhaps this is one of those things that doesn't matter a helluva lot,
>> but: when you have a freshly installed Debian-style LAMP (actually Ubuntu
>> server 9.04) and you are look
On Sun, 5 Jul 2009, Matt Juszczak wrote:
> I see FreeBSD do this (separate user-installed packages into /usr/local),
> but Linux always seems to install extra packages and user-generated
> content in /usr as the root. IE: mysql & apache. Always wondered why the
> separation was never there.
On Wed, Jul 1, 2009 at 9:48 AM, David Mintz wrote:
> Perhaps this is one of those things that doesn't matter a helluva lot,
> but: when you have a freshly installed Debian-style LAMP (actually Ubuntu
> server 9.04) and you are looking for a place in the filesystem to install
> your PHP applicati
Also, for those who work in mixed environments; /opt is a Unix-ism.
/usr/local is a Linux-ism.
I see FreeBSD do this (separate user-installed packages into /usr/local),
but Linux always seems to install extra packages and user-generated
content in /usr as the root. IE: mysql & apache. Always
David Mintz wrote:
Perhaps this is one of those things that doesn't matter a helluva lot, but:
when you have a freshly installed Debian-style LAMP (actually Ubuntu server
9.04) and you are looking for a place in the filesystem to install your PHP
application files -- where do you like to put them
This has been quite enlightening, thanks.
I ended up deciding on opt/www for web apps, and /usr/share/php will house
the system-wide libs like Zend Framework. Yes it could be
/usr/local/whatever but... wtf.
--
David Mintz
http://davidmintz.org/
The subtle source is clear and bright
The tribu
If you're installing linux packages/apps into /usr/local, which is
most common, it's highly recommended to use gnu stow to manage them.
I create /usr/local/stow dirinstall all my linux packages there
(apache, php, mysql, etc)...and then do a simple `stow -v
package_dir/` from /usr/local/stow.
On Wed, 1 Jul 2009, Eddie Drapkin wrote:
> Every application that I run is a new user that doesn't have
> permission to r/w out of its /home/ so that collaboration with people
> on several projects means no one's snooping anyone else's sourcecode.
> The apache user is in all of their groups, for o
On Wed, Jul 1, 2009 at 12:01 PM, Michael Hernandez wrote:
> On Wed, 2009-07-01 at 11:54 -0400, Ajai Khattri wrote:
>> On Wed, 1 Jul 2009, Michael Hernandez wrote:
>>
>> > I worry that using /usr/local for stuff might
>> > end up with an accidental delete or overwrite by the package manager.
>>
>> W
On Wed, 1 Jul 2009, Michael Hernandez wrote:
> I only say that because there is stuff in /usr/local on my ubuntu system
> that I didn't put there (at least not manually)
Yes, the FHS standard mandates that certain directories should exist
there (they are mostly empty) which is why most distros c
On Wed, 2009-07-01 at 11:54 -0400, Ajai Khattri wrote:
> On Wed, 1 Jul 2009, Michael Hernandez wrote:
>
> > I worry that using /usr/local for stuff might
> > end up with an accidental delete or overwrite by the package manager.
>
> Why? System packages never install into /usr/local. Traditionally
On Wed, Jul 1, 2009 at 10:48 AM, David Mintz wrote:
> Perhaps this is one of those things that doesn't matter a helluva lot, but:
> when you have a freshly installed Debian-style LAMP (actually Ubuntu server
> 9.04) and you are looking for a place in the filesystem to install your PHP
> application
On Wed, 1 Jul 2009, Michael Hernandez wrote:
> I worry that using /usr/local for stuff might
> end up with an accidental delete or overwrite by the package manager.
Why? System packages never install into /usr/local. Traditionally,
/usr/local has always been for "local" stuff. When I build stuff
I myself have used the "/var/www/www.domainname.com" method myself. Another
scheme I find worthwhile is to do "/var/www/apps/applciation_name" so I
don't need clog the doc root with URL's depending on the client.
-Anthony
On Wed, Jul 1, 2009 at 11:04 AM, Hans Zaunere wrote:
> > Perhaps this is
> Perhaps this is one of those things that doesn't matter a helluva lot,
> but: when you have a freshly installed Debian-style LAMP (actually
> Ubuntu server 9.04) and you are looking for a place in the filesystem
> to install your PHP application files -- where do you like to put them?
> /usr/loc
On Wed, 2009-07-01 at 10:48 -0400, David Mintz wrote:
> Perhaps this is one of those things that doesn't matter a helluva lot,
> but: when you have a freshly installed Debian-style LAMP (actually
> Ubuntu server 9.04) and you are looking for a place in the filesystem
> to install your PHP applicat
On Wed, Jul 1, 2009 at 10:48 AM, David Mintz wrote:
> Perhaps this is one of those things that doesn't matter a helluva lot, but:
> when you have a freshly installed Debian-style LAMP (actually Ubuntu server
> 9.04) and you are looking for a place in the filesystem to install your PHP
> application
Perhaps this is one of those things that doesn't matter a helluva lot, but:
when you have a freshly installed Debian-style LAMP (actually Ubuntu server
9.04) and you are looking for a place in the filesystem to install your PHP
application files -- where do you like to put them? /usr/local/share/..
19 matches
Mail list logo
