[12:26] <leonel> How about  an  Enterprise support for Motu-server  :)
[12:27] <ftoo_on_gutsy> how about enterprise support for ipv6-only-ubuntu-server
[12:28] <ftoo_on_gutsy> or even enterprise support for my nackered old back .... :)
[06:42] <mikubuntu> am i connected here, or is there just no chatter tonite
[06:42] <jbrouhard> virtually no chatter
[06:42] <jbrouhard> hey PanzerMKZ
[06:43] <mikubuntu> jbrouhard: i wondered
[06:45] <mikubuntu> can anyone suggest the easiest approach to setting up the server packages i need to be able to start building ecommerce product pages?  oh, ya, very newb question.
[06:47] <mikubuntu> alternatively, can anyone be my b*#%&, and just handle the difficult parts for me? (i learned that on the linuxhelpask page, where they recommend the approach)
[06:48] <mikubuntu> lol
[07:20] <monsterb> hi all
[07:21] <monsterb> !bind
[07:21] <ubotu> Sorry, I don't know anything about bind - try searching on http://ubotu.ubuntu-nl.org/factoids.cgi
[08:40] <soren> mikubuntu: Depends. Do you already have the e-commerce software?
[09:06] <kraut> moin
[09:41] <pteague> is there a reason my ubuntu server is doing everything in uppercase?
[04:13] <mralphabet> pteague: define "everything"
[05:15] <raky> is this true?  "GRUB has built-in support for basic networking; this makes network booting extremely easy. Unfortunately the pre-built binaries don't have this support compiled in; you will need to compile GRUB for your specific network card."
[05:16] <mathiaz> raky: yes.
[06:17] <dholbach> hey folks
[06:18] <dholbach> I'm just triaging the sponsoring bug queue at the moment
[06:18] <dholbach> could somebody check out the patch on bug 91607?
[06:18] <ubotu> Launchpad bug 91607 in postfix-policyd "postfix-policyd init script doesn't behave" [Undecided,Fix released]  https://launchpad.net/bugs/91607
[06:19] <dholbach> oops sorry that's fixed already
[06:22] <CharlieSu> How do you tell what status code a program exited with?
[06:26] <soren> CharlieSu: Depends... If you just ran it from the command line, "echo $?" immediately after it will show you the exit code.
[06:58] <CharlieSu> soren: thanks dude..  that worked.. what other ways are there?
[06:58] <mralphabet> strace
[06:59] <soren> CharlieSu: It depends on how you're calling the program.
[07:00] <soren> CharlieSu: If you're calling it from a C program, it's part of the return code from the wait() system call.
[08:49] <m11> evening all
[09:30] <pteague> mralphabet> nope, i mean all the characters are showing up as uppercase...  caps lock off ls shows up as LS, but it does the ls command... if i use shift or caps lock it shows up as LS, but says command not found...  ls / shows stuff like BOOT, ETC, DEV, etc - rebooting fixed it i think
[09:44] <mralphabet> pteague: o0 that's odd to say the least
[09:59] <soren> pteague: What's your username on the machine?
[10:00] <soren> pteague: Does it begin with an uppercase letter, perhaps?
[10:00] <pteague> nope
[10:01] <pteague> i've been using linux a while... just the first time i set up ubuntu server
[10:02] <soren> It's pretty easy to reproduce.
[10:02] <soren> In a console (when logging in) type the username in uppercase letters.
[10:02] <mralphabet> o0
[10:04] <soren> mralphabet: You need to think back to the day when not all terminals supported both upper and lower case letters.
[10:04] <mralphabet> soren: it is possible that predates my experience
[10:04] <soren> mralphabet: Quite possibly. Do you have a long grey beard?
[10:05] <mralphabet> soren: no, I shave ;)
[10:05] <soren> Then you're not old enough. :)
[10:05] <mralphabet> hah
[10:08] <pteague> it looks like my mdadm.conf file is messed up... it doesn't list any of the drives that are a part of the raid array
[10:11] <pteague> ah, i see it's using /proc/partitions ... any idea how i can figure out the UUIDs of certain devices? such as /dev/sda1, etc?
[10:13] <soren> /lib/udev/vol_id
[10:13] <mralphabet> pteague: /dev/disk/by-uuid/
[10:14] <mralphabet> ls -al /dev/disk/by-uuid/ specifically
[10:16] <soren> Or just "sudo /lib/udev/vol_id /dev/sda1", for instance.
[10:17] <pteague> ok, now i'm confused as to why UUIDs are being used in /etc/fstab instead of just /dev/hda1 for example
[10:18] <pteague> does ubuntu automatically rebuild the soft links on boot based on the serial # or something from the devices to keep the UUIDs the same?
[10:19] <pteague> or maybe the person who told me the switch to UUIDs in /etc/fstab because /dev/hda1 may never point to the same device didn't know what they were talking about?
[10:20] <ScottK> pteague: What release are you running?
[10:20] <pteague> 7.04
[10:21] <ScottK> UUID is generally the way to go then.  "the person" was on target for machines with more than one drive (or array in the RAID case).
[10:22] <ScottK> Looking where mralphabet said is the right place to look.
[10:28] <pteague> yeah, but the 3 drives i'm using in my raid array do not have UUIDs assigned to them...  I'm trying to figure out how to make the raid array be more stable or something... everytime i reboot it states that none of the devices in the array were detected & that there was no raid superblock on sda (or maybe sda1?) & then it looks like it attempts to reimage the raid array
[10:31] <pteague> http://pastebin.com/m7c438d46
[10:32] <ScottK> If you are doing it by device name, shouldn't it be md0?
[10:35] <pteague> yes, md0 is made up of 3 drives - /dev/sda1, /dev/sdb1, & /dev/sdc1 - after booting it has to put the raid back together again & it's saying the /dev/sda1 does not have a valid raid superblock
[10:35] <mralphabet> pteague: grub doesn't like to boot to raid 5
[10:36] <pteague> /dev/hda1 is mounted as /, /dev/hda2 is swap, & md0 is mounted as /home
[10:38] <pteague> /dev/hda is an 5.8g pata hd & /dev/sda-sdc are 400g sata hds
[10:44] <pteague> mralphabet> or is the 'error' being reported because it's initially trying to attach it when linux is booting up & fails, but then puts it together & mounts it later?
[10:54] <mralphabet> pteague: if you look at /boot/grub/menu.lst, what is the partition it is trying to boot?
[10:54] <mralphabet> ie for mine it says: kernel          /boot/vmlinuz-2.6.20-15-server root=/dev/md0 ro quiet splash
[10:55] <mralphabet> in my case, md0 is mirrored pata 80's
[11:15] <pteague> it boots off the UUID that i believe is the UUID for /dev/hda1
[11:17] <pteague> dang, i moved the box to where it needs to go & now it's giving me fsck failed & dumping me into admin mode... apparently my md0 is failing - it has an invalid ext2 partition
[11:20] <mralphabet> ouch
[11:22] <pteague> at least it's /home & i hadn't completely rsynced it yet
[11:25] <m11> hey guys
[11:25] <m11> i am planing to get dell poweredge 2900 , did any of you tested that server with ubuntu ?
[11:26] <m11> http://www.dell.com/content/products/productdetails.aspx/pedge_2900?c=us&cs=04&l=en&s=bsd&~section=specs#tabtop
[11:27] <pteague> ah, it's saying /dev/sda1 appears to contain an ext2 filesystem & also appears to be part of a raid array, /dev/sdb1 appears to be a part of a raid array, & cannot open /dev/sdc1: device or resource busy
[11:28] <pteague> i may just reinstall stuff & see if i can get it to work correctly again