[12:03] <Drac[Server] > Is "0" unlimited?
[12:04] <Pygi> depends where
[12:04] <Pygi> but probably yes
[12:09] <Drac[Server] > Um... What do I do with "user www-date" and "group www-data" ?
[12:09] <Drac[Server] > data*
[12:09] <Pygi> just make sure you set right permissions on files
[12:09] <Drac[Server] > Eheh... um... which files would those be? ._.
[12:10] <Pygi> bah
[12:10] <Pygi> /var/www I guess
[12:10] <Drac[Server] > I told you I'm new at this...
[12:11] <Drac[Server] > What would those files do?
[12:11] <Pygi> buh, that is where you put files to host
[12:11] <Pygi> for your web server
[12:11] <Drac[Server] > Oh! Okay. Now I get it.
[12:11] <Drac[Server] > /var/www/(user)/filesgohere  right?
[12:13] <Pygi> huh, you want a multi-user enviroment?
[12:14] <Pygi> this can probably help
[12:14] <Pygi> read this
[12:14] <Drac[Server] > Well... I don't see how else I'd have multiple accounts with FTP access and stuff...
[12:14] <Pygi> t see how else I'd have multiple accounts with FTP acce
[12:14] <Pygi> bah, sec
[12:14] <Pygi> https://wiki.ubuntu.com/ApacheMySQLPHP?action=show&redirect=LAMPForHoary
[12:27] <fmasi> can some one help me seting up my vsftpd i am a bit rusty and i trying to make anonymous aces to be able to upload but after some configuration i got this error http://paste.ubuntu-nl.org/8221
[12:29] <fmasi> please help me i nead to get unrusted
[12:29] <Drac[Server] > When the mysql documents refer to the "hostname" do they mean what can be printed by the command that I can't remember at the moment?
[12:49] <fmasi> some one home ???
[09:49] <Pygi> o, welcome fabbione
[09:50] <fabbione> hey Pygi
[09:50] <Pygi> long time no see
[09:50] <fabbione> how are you?
[09:51] <Pygi> tired :-/ too much non-sleep due to coding :-/
[09:51] <fabbione> ehe
[09:52] <Pygi> :)
[09:52] <Pygi> how's server comin' along?
[09:53] <fabbione> working on it :)
[09:53] <Pygi> great :-P
[09:54] <Pygi> anything that I can help on?
[09:55] <fabbione> Pygi: test install from daily cd would be great
[09:55] <Pygi> k, will do...now tell me where to get it :)
[09:56] <fabbione> http://cdimage.ubuntu.com/ubuntu-server/
[09:57] <Pygi> k, I'll make it download now
[09:59] <Pygi> Once I install it *these days I hope* you'll get reports
[09:59] <fabbione> Pygi: keep in mind one thing
[09:59] <fabbione> the reason why we need testing is because we did switch the archive managment software
[09:59] <fabbione> iso's might be borked to death
[09:59] <fabbione> or not working at all
[09:59] <Pygi> k, no problem
[10:00] <fabbione> that's the whole point of testing them :)
[10:00] <Pygi> :)
[10:03] <Pygi> also, are we going to provide more detailed /etc files? meaning *every* option in most crucial files explained?
[10:03] <fabbione> i don't have time to do stuff like that
[10:03] <fabbione> and i won't
[10:04] <fabbione> if somebody wants to work on it, welcome to push me patches and i will apply them
[10:04] <Pygi> ah,kk
[12:21] <lapo> hi
[12:22] <fabbione> hi
[12:23] <lapo> ubuntu kernel should run update-initramfs in postinst
[12:24] <fabbione> it does
[12:24] <lapo> I have machines with mpt hw and the actual initramfs doesn't contain the needed modules (bug?), so w/o updating the initramfs on kernel upgrade the machines won't boot anymore
[12:25] <fabbione> lapo: file a bug in malone, but the kernel does update-initramfs
[12:25] <lapo> fabbione, are you sure?
[12:25] <fabbione> yes i am
[12:26] <lapo> fabbione, the kernel update of 2 or 3 days ago, leave my test server unbootable
[12:26] <lapo> fabbione, can it be lilo? does update-initramfs run lilo after updating the initrafs?
[12:26] <fabbione> lapo: file a bug on malone. component: linux-source-2.6.15
[12:27] <fabbione> that's a completely different hook
[12:27] <lapo> K, I'll do it
[12:27] <lapo> fabbione, yes it is, but the result is the same :-)
[12:30] <lapo> fabbione, should I file a bug against update-initramfs?
[12:30] <fabbione> lapo: yes.
[12:30] <fabbione> i don't think lilo is at fault here at all
[12:31] <fabbione> since the hook that calls the update bootloader has been untouched for ages
[12:31] <fabbione> and i would have noticed the breakage
[12:32] <lapo> fabbione, I think the problem is that update-lilo is run before update-initramfs
[12:33] <lapo> so I get a panic on boot cause it cannot find the initrafs image (since it's changed)
[12:34] <fabbione> nope
[12:35] <fabbione> lilo is executed way later than that
[12:35] <fabbione> open a bug on update-initramfs or lilo
[12:35] <fabbione> also check that initramfs is of a reasonable size compared to the old one
[12:36] <lapo> I think it's about 200k bigger, not that much
[12:36] <fabbione> try to boot with the old kernel and run lilo manually and see if it helps
[12:36] <fabbione> start excluding one bit at a time will help
[12:37] <lapo> fabbione, no problem doing things manually, there's some automation which haven't worked
[12:37] <lapo> I'll try reinstalling that kernel to see what happen
[12:38] <fabbione> lapo: do one thing at a time
[12:38] <fabbione> the kernel is installed, try to check if lilo config is right
[12:38] <fabbione> and rerun lilo manually
[12:38] <fabbione> see if that fix the problem
[12:38] <lapo> I know the drill, I did it several times these days :-)
[12:38] <fabbione> if it doesn't compare the differences between the initramfs?
[12:38] <lapo> doing things manually works
[12:40] <lapo> donig an apt-get install --reinstall linux-image-2.6.15-14-amd64-xeon
[12:44] <lapo> update-initramfs and update-lilo are in the correct order, lets reboot
[12:46] <lapo> something wicked happend :-/
[12:49] <lapo> found out, my boot partion fs was corrupted, so it was not kernel nor lilo fault, sorry for the noise
[12:50] <fabbione> lapo: anyway.. your nick says it all :D
[12:51] <lapo> fabbione, my nick is actually my name (purtroppo) :-)
[12:51] <fabbione> sucks to be you
[12:51] <lapo> but I'm no way involved with fiat, elkan or so :-)
[12:51] <lapo> eheh
[12:51] <fabbione> ejje
[12:51] <fabbione> ehe
[12:54] <lapo> since you did that joke about my name, I'going to bug you about grub :-)
[12:55] <fabbione> tsk :O)
[12:55] <lapo> lilo is the only option for a sw raid1 + lvm setup (read no /boot partition), since lilo is a PITA and there are patches around for grub to support raid1+lvm setups, any caches to have them in?
[12:56] <lapo> I think sw raid1+lvm is a common setup on servers, no?
[12:56] <fabbione> lilo does not support /boot on LVM
[12:57] <fabbione> you must keep /boot separate
[12:57] <lapo> fabbione, are you sure?
[12:57] <fabbione> lilo manages to install once
[12:57] <fabbione> it will kill you at the first kernel upgrade in certain conditions
[12:57] <fabbione> lapo: yes i am sure.. don't ask me if i am all the time :)
[12:57] <lapo> lapo@posta:~$ sudo sfdisk -d /dev/sda
[12:57] <lapo> Password:
[12:57] <lapo> # tabella delle partizioni di /dev/sda
[12:57] <lapo> unit: sectors
[12:57] <lapo> /dev/sda1 : start=       63, size=143363997, Id=fd, bootable
[12:57] <lapo> /dev/sda2 : start=        0, size=        0, Id= 0
[12:57] <lapo> /dev/sda3 : start=        0, size=        0, Id= 0
[12:57] <lapo> /dev/sda4 : start=        0, size=        0, Id= 0
[12:57] <lapo> so how can you explain this? :-)
[12:57] <fabbione> please do NOT flood the channel
[12:57] <lapo> sorry
[12:58] <fabbione> lapo: because i read lilo code? and we had bugs for it that forced me to do it
[12:58] <lapo> lilo does support booting from lvm, I'm currently using it
[12:58] <fabbione> lvm1, not 2
[12:58] <fabbione> and only if certain conditions are met
[12:59] <fabbione> the first time you will upgrade the kernel and the file will be fragmented across more than one PV you lose
[01:00] <lapo> fabbione, yep but if the boot vg is only on one pv there are no problems using such a setup
[01:01] <fabbione> right
[01:01] <fabbione> it also depends how you set the lv but that's a more uncommon case
[01:02] <fabbione> anyway grub supports boot from raid1, but not from lvm (in our case)
[01:02] <fabbione> and i doubt we will pull in anything new and fancy for grub
[01:02] <fabbione> we will probably get grub2 in dapper+1
[01:03] <lapo> grub2 is a myth :-)
[01:04] <lapo> btw, the installer get confused in my case using preexisting partitions and vgs, it installs grub
[01:04] <lapo> so a smarter grub can solve this problem too