slashcode-development

[Slashcode-development] Bender: clearing 1.0.9 install, and bender install locations

[Steve L. <st...@si...>]

(BTW: I'm mot sure I'm totally clear where these kinds of questions should
go: the dev list or the regular slash list.  Since this one is primarily a
coding question I figure it's here, but shout if I'm wrong and I'll scoot
over to the other one.)

I have made zero progress in diagnosing the Bender-Apache 1.3.14/17
startup segfaults I'm having, so I figure it's time for the 
screw-it-scorch-and-burn rebuild.

Part of this is rebuilding apache, part is rebuilding slash 1.1.3.  I do
still have my 1.0.9 install on my box, which I'm assuming I should remove
in case conflicts are part of the problem.  I'll tgz the /home/slash
directory and delete it.  Question #1: is there anything else I should do
to make sure the 1.0.9 install is completely gone before I reinstall
1.1.3?

Question #2: My inclination is to put the install in /home/slash rather
than the default of /usr/local, because I want my hosted sites on
/home.  I did run into problems during the 1.1.3 install about alternate
install prefixes not being fully propagated, which I tried to correct by
hand, but I'm not sure I got them all.  Can I accept the /usr/local
install for the modules and plugins and themes but still put the sites
themselves on /home without too much contortion?  How are the folks
currently using Bender doing it?

Cheers,

Steve

-- 
Steve Linberg, Chief Goblin 
Silicon Goblin Technologies 
http://silicongoblin.com 
Be kind.  Remember, everyone you meet is fighting a hard battle. 

Re: [Slashcode-development] Bender: clearing 1.0.9 install, and bender install locations

[Chris N. <pu...@po...>]

At 09:47 -0500 02.14.2001, Steve Linberg wrote:
>Part of this is rebuilding apache, part is rebuilding slash 1.1.3.  I do
>still have my 1.0.9 install on my box, which I'm assuming I should remove
>in case conflicts are part of the problem.  I'll tgz the /home/slash
>directory and delete it.  Question #1: is there anything else I should do
>to make sure the 1.0.9 install is completely gone before I reinstall
>1.1.3?

Almost everything in 1.0.x is under /home/slash/, unless you moved things
elsewhere by hand.  Exceptions: /etc/rc.d/slashd, Apache configs, MySQL
data.  I think that is about it.


>Question #2: My inclination is to put the install in /home/slash rather
>than the default of /usr/local, because I want my hosted sites on
>/home.  I did run into problems during the 1.1.3 install about alternate
>install prefixes not being fully propagated, which I tried to correct by
>hand, but I'm not sure I got them all.  Can I accept the /usr/local
>install for the modules and plugins and themes but still put the sites
>themselves on /home without too much contortion?  How are the folks
>currently using Bender doing it?

If there are broken paths using PREFIX=/home/slash, let us know so we can
fix them.  However, I would recommend just installing in /usr/local/slash
and then just moving the contents of the site directory manually (editing
appropriate httpd configs), and editing slashd appropriately to deal with
the new locations.  That should take care of it for you, I think.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Bender: clearing 1.0.9 install, and bender install locations

[Steve L. <st...@si...>]

On Wed, 14 Feb 2001, Chris Nandor wrote:

> If there are broken paths using PREFIX=/home/slash, let us know so we can
> fix them.

In my install, the Makefile didn't get the INIT and PREFIX arguments.  I
specified:

make INIT=/etc/rc.d PREFIX=/home/slash

Makefile contained:

PREFIX = /usr/local/slash
INIT = /etc

I edited these by hand to read:

PREFIX = /home/slash
INIT = /etc/rc.d

before continuing with the process.

> However, I would recommend just installing in /usr/local/slash
> and then just moving the contents of the site directory manually (editing
> appropriate httpd configs), and editing slashd appropriately to deal with
> the new locations.  That should take care of it for you, I think.

Will do!  Thanks (Brian too) for the tips.

Steve

-- 
Steve Linberg, Chief Goblin 
Silicon Goblin Technologies 
http://silicongoblin.com 
Be kind.  Remember, everyone you meet is fighting a hard battle. 

Re: [Slashcode-development] Bender: clearing 1.0.9 install, andbender install locations

[Brian A. <br...@ta...>]

Chris Nandor wrote:
> >Question #2: My inclination is to put the install in /home/slash rather
> >than the default of /usr/local, because I want my hosted sites on
> >/home.  I did run into problems during the 1.1.3 install about alternate
> >install prefixes not being fully propagated, which I tried to correct by
> >hand, but I'm not sure I got them all.  Can I accept the /usr/local
> >install for the modules and plugins and themes but still put the sites
> >themselves on /home without too much contortion?  How are the folks
> >currently using Bender doing it?
> 
> If there are broken paths using PREFIX=/home/slash, let us know so we can
> fix them.  However, I would recommend just installing in /usr/local/slash
> and then just moving the contents of the site directory manually (editing
> appropriate httpd configs), and editing slashd appropriately to deal with
> the new locations.  That should take care of it for you, I think.
You could also create links from the /usr/local/slash/sites directory
to the users home directory. During the install process you can say
who owns what.

	-Brian

Re: [Slashcode-development] Bender: clearing 1.0.9 install, andbender install locations

[Chris N. <pu...@po...>]

At 10:16 -0800 02.14.2001, Brian Aker wrote:
>Chris Nandor wrote:
>> >Question #2: My inclination is to put the install in /home/slash rather
>> >than the default of /usr/local, because I want my hosted sites on
>> >/home.  I did run into problems during the 1.1.3 install about alternate
>> >install prefixes not being fully propagated, which I tried to correct by
>> >hand, but I'm not sure I got them all.  Can I accept the /usr/local
>> >install for the modules and plugins and themes but still put the sites
>> >themselves on /home without too much contortion?  How are the folks
>> >currently using Bender doing it?
>>
>> If there are broken paths using PREFIX=/home/slash, let us know so we can
>> fix them.  However, I would recommend just installing in /usr/local/slash
>> and then just moving the contents of the site directory manually (editing
>> appropriate httpd configs), and editing slashd appropriately to deal with
>> the new locations.  That should take care of it for you, I think.
>You could also create links from the /usr/local/slash/sites directory
>to the users home directory. During the install process you can say
>who owns what.

Yeah, I should have added that ... I was thinking he wanted the actual
files in /home, though.  I think symlinks is the easiest way to go, though.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-development] Bender: clearing 1.0.9 install, andbender install locations

[Steve L. <st...@si...>]

On Wed, 14 Feb 2001, Chris Nandor wrote:

> At 10:16 -0800 02.14.2001, Brian Aker wrote:
> >You could also create links from the /usr/local/slash/sites directory
> >to the users home directory. During the install process you can say
> >who owns what.
> 
> Yeah, I should have added that ... I was thinking he wanted the actual
> files in /home, though.  I think symlinks is the easiest way to go, though.

Yes, I'm fine with having the core slash code in /usr/local, but I'd like
the actual content of the sites in /home so it can easily count against
user quotas.  Symlinks from /usr/local/slash/sites to /home/foo seems like
the best way to handle it.

-- 
Steve Linberg, Chief Goblin 
Silicon Goblin Technologies 
http://silicongoblin.com 
Be kind.  Remember, everyone you meet is fighting a hard battle. 

Re: [Slashcode-development] Bender: clearing 1.0.9 install, andbender install locations

[Chris N. <pu...@po...>]

At 14:13 -0500 02.14.2001, Steve Linberg wrote:
>Yes, I'm fine with having the core slash code in /usr/local, but I'd like
>the actual content of the sites in /home so it can easily count against
>user quotas.  Symlinks from /usr/local/slash/sites to /home/foo seems like
>the best way to handle it.

Yeah, as long as you remember to "dereference" symbolic links, like with du
-D, when you count up sizes.  Also, if you don't count those directories
separate from the rest, then warn users that any symbolic links in their
user directories could mess up their quotas.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/