[12:34] <allee> mhmmm, my laptop does not know pkgsel/install-pattern but uses: base-config/package-selection ... let's try ...
[12:50] <allee> yeah, that was it!
[06:44] <Psi-Jack> Hey
[06:45] <Psi-Jack> Anyone here know where apache's suexec docroot is set to?
[06:49] <infinity>  /var/www
[06:52] <Psi-Jack> Hmm..
[06:52] <Psi-Jack> You SURE?
[06:52] <infinity> Last time I checked.
[06:53] <infinity> --with-suexec-docroot=/var/www  <--- apache2
[06:53] <infinity> --suexec-docroot=/var/www       <--- apache1.3
[06:53] <Psi-Jack> Hmmm.
[06:54] <infinity> (PS: I'm the apache maintainer)
[06:54] <Psi-Jack> Odd. I tried using it in /var/www, and I got 500 errors.
[06:55] <Psi-Jack> Hmmm.
[06:55] <Psi-Jack> I see.. Odd.. heh.
[06:56] <Psi-Jack> [2006-03-09 00:02:49] : target uid/gid (2000/2000) mismatch with directory (0/0) or program (0/0)
[06:56] <Psi-Jack> Heh
[06:56] <Psi-Jack> Least it's progress somewhere.
[06:56] <infinity> suEXEC is a bit picky about only changing id/gid to the owner if the script being run, etc.
[06:56] <infinity> s/if the/of the/
[06:57] <Psi-Jack> Well, this, is complaining about the directory itself.
[06:57] <Psi-Jack> Because the directory is root:root owned. heh
[06:58] <infinity> Well, generally you'd want to set up subdirectories to do this from. :)
[06:58] <Psi-Jack> Well, yeah. That's what I'm doing.
[06:59] <infinity>  /var/www/www.site1.com/suexec, /var/www/www.site2.org/suexec
[06:59] <infinity> And set owenership on those directories to the users who are being suEXECed.
[07:00] <Psi-Jack> Heh, yeah.
[07:00] <maswan> Actually suEXEC is very picky, about alot of things. :)
[07:00] <Psi-Jack> I'm trying to find the most /logical/ means to run a community-hosted site, where people can have their own websites.
[07:01] <Psi-Jack> I don't think suexecusergroup works in <directory> entries, does it? heh
[07:02] <Psi-Jack> Nope, it doesn't/
[07:02] <Psi-Jack> Hmm.
[07:03] <Psi-Jack> Seems like the only truely "secure" way I'd be able to do it, is by using username.members.domain.tld, for each user. That's just.. Ouch. :)
[07:03] <infinity> What's wrong with that?
[07:04] <infinity> mod_vhost will do it automatically for you, so you don't have to do an entry for each user.
[07:04] <Psi-Jack> Well, there's no automagic way to handle that, really.
[07:04] <Psi-Jack> Hmm...
[07:04] <infinity> And a wildcard DNS entry takes care of the DNS problem.
[07:04] <infinity> Then you're done.
[07:05] <Psi-Jack> How would mod_vhost determine the username to suexec to?
[07:06] <infinity> mod_vhost does vhost templating, so you can extract the username from the Host request, and use that to define the DocumentRoot and suEXEC paramaters, logfiles, etc.
[07:06] <Psi-Jack> Ahhh. i see.. Makes sense. That is usable.
[07:07] <infinity> And was pretty much specifically designed for this use case. :)
[07:07] <Psi-Jack> Heh he.
[07:07] <Psi-Jack> Well, it's going to be quite useful for me. :)
[07:07] <infinity> (For ISPs with massive numbers of "hosted users", to be precise)
[07:08] <Psi-Jack> And I got the idea, now, to use nss-mysql to help with it all, too.
[07:09] <Psi-Jack> But, yeah, definately much better than my alternative thoughts on how to do it. LOL
[07:15] <Psi-Jack> Wee@
[07:26] <Psi-Jack> Anyone know the difference between libnss-mysql and libnss-mysql-bg?
[09:42] <Psi-Jack> Hey, anyone know if 16 chars is the /max/ username/groupname Linux can actually properly support or could it go up to 25?
[05:21] <allee> Sun Galaxy X4100: mpt* drivers in dapper.  Two (or one) simple disk are detected during installation. When 2 disk configured as RAID1 in the LSI controller, kernel fails to detect the disk
[05:22] <allee> scsi0 : ioc0: LSISAS1064, FwRev=01040000h, Ports=1, MaxQ=511, IRQ=169
[05:22] <allee> Is this a limitation of the driver or a bug?
[05:23] <allee> SLES9 has no problem with the RAID1 of the LSI controler.  And uses it as sda.
[05:28] <allee> SLES9 uses: Fusion MPT SAS Host driver 3.02.62sus
[05:28] <allee> ubuntu uses:
[05:28] <allee> Fusion MPT SAS Host driver 3.03.04
[05:32] <fabbione> allee: you are on the wrong channel
[05:32] <fabbione> either open a bug on malone or talk with kernel maintainer on #ubuntu-kernel
[05:34] <allee> fabbione: 'k I'll do both