[00:00] <NCommander> garrettkajmowicz, ping?
[00:04] <garrettkajmowicz> NCommander: Anything more recent would be good.
[00:04] <garrettkajmowicz> Sorry - phone call with relatives.
[00:04] <NCommander> first try do-release-upgrade -p
[00:04] <garrettkajmowicz> I c an always do a multistage upgrade.
[00:04] <NCommander> If that doesn't work, I'll talk you through doing a direct dapper->hardy upgrade via editing sources.list
[00:04] <garrettkajmowicz> Trying...
[00:06] <mathiaz> NCommander: considering that he's running edgy, I wouldn't recommend to upgrade to hardy directly.
[00:06] <NCommander> No, he's running dapper
[00:06] <mathiaz> This upgrade path (edgy -> hardy) has never been tested.
[00:06] <NCommander> The do-release-upgrade tried to upgrade him to edgy which doesn't exist anymore
[00:07] <mathiaz> NCommander:  My server is running 6.10
[00:07] <NCommander> garrettkajmowicz, you are running dapper, or did I misunderstand you
[00:07] <mathiaz>                           and I want to upgrade
[00:07] <NCommander> Er
[00:07]  * NCommander shoots his foot :-)
[00:07] <NCommander> Ok
[00:07] <NCommander> My mistake
[00:07] <NCommander> I thought he was running dapper, not edgy (I thought dapper = 6.10)
[00:07] <garrettkajmowicz> NCommander: Currently 6.10 - edgy
[00:07] <NCommander> garrettkajmowicz, it will require multiple upgrades to get you to the current release
[00:08] <garrettkajmowicz> That's fine - the first one's going to be hard.  -p gave me the same problem as before.
[00:08] <NCommander> (it might be possible to go straight to hardy, but it might also break your system, this is the only sane way)
[00:08] <NCommander> Yeah
[00:08] <NCommander> No problem
[00:08] <NCommander> do sudo nano /etc/apt/sources.list
[00:09] <mathiaz> garrettkajmowicz: if do-release-upgrade doesn't work, you can try apt-get dist-upgrade
[00:09] <garrettkajmowicz> NCommander: Opened for edit.
[00:09] <mathiaz> garrettkajmowicz: it's not really supported, but for servers there is good change it will work.
[00:09] <NCommander> mathiaz, the problem is do-release-upgrade trying to get its updated core from the repos, but edgy been removed from the mirrors
[00:09] <NCommander> And then do a search and replace for edgy, and replace with feisty
[00:09] <NCommander> ^- garrettkajmowicz
[00:09] <uvirtbot`> NCommander: Error: "-" is not a valid command.
[00:10] <NCommander> -_-;
[00:10] <NCommander> stupid bot
[00:11] <garrettkajmowicz> Should I convert old-releases.ubuntu.com to archive.ubuntu.com as well?
[00:11] <NCommander> Yes
[00:12] <NCommander> garrettkajmowicz, yeah. We're going to upgrade you to feisty by hand, then you can do do-release-upgrade to go from feisty to gutsy to hardy
[00:13] <garrettkajmowicz> OK - edit complete.
[00:13] <NCommander> Save and close
[00:14] <NCommander> type: sudo aptitude update
[00:14] <NCommander> (this will prepare aptitude to do the actual upgrade, the next command will update your system)
[00:15] <garrettkajmowicz> Oops - missed a case of old-releases.
[00:15] <garrettkajmowicz> I assume I should shut down unneeded processes like the web server...
[00:15] <NCommander> garrettkajmowicz, nope, aptitude will take care of that as needed
[00:15] <garrettkajmowicz> Update complete
[00:16] <NCommander> Ok
[00:16] <NCommander> sudo aptitude dist-upgrade
[00:17] <NCommander> This will take a LONG time depending on how many packages you need to update, but once its done, you'll be running Feisty Fawn
[00:17] <garrettkajmowicz> Cool.  Now fetching package 2/351.  This should take about 2 hours to download.  Hopefully you'll be around in the unlikely event that something goes wrong then.
[00:17] <NCommander> Once thats done
[00:18] <NCommander> Run do-release-upgrade to go from feisty to gutsy, and again to go to hardy, which is the current LTS
[00:18] <NCommander> (what we just did was what do-release-upgrade pretty much does internally)
[00:19] <garrettkajmowicz> Cool.  I've done that before and it's really quite nice.  I ran into the same problem with my desktop, but I kludged a different solution.  I created a local merged repository on my desktop containing both edgy and feisty, which allowed the dist upgrade to work.  That took 2 days to do, and I knew there had to be a better way!
[00:19] <NCommander> Ew
[00:19] <NCommander> Yeah
[00:19] <NCommander> This is the easier way ;-)
[00:19] <garrettkajmowicz> Thank you so much.
[00:20] <NCommander> Just remember to keep your system more up to date next time if possible ;-)
[00:21] <garrettkajmowicz> Well, until about 3 months ago I didn't know about/trust the upgrade tools.  My main experience with that had been Mandrake (ick), or Windows (they have 20k engineers - how can upgrade NOT work?).  So I had planned to wait until I couldn't take it any longer and do a complete upgrade.
[00:21] <garrettkajmowicz> Ie re-install.
[00:21] <NCommander> Heh
[00:22] <NCommander> Upgrades on Ubuntu pretty rarely break
[00:22] <NCommander> Its a fairly well tested process as long as you don't attempt to jump releases
[00:22] <garrettkajmowicz> Hmm.  Since We're on the subject - my laptop has the same problem.  What scares me it that it uses LUCKS (encryption) for everything but a 200M boot partition, and I'm nervous that things might go boom.
[00:24] <NCommander> I can help you upgrade
[00:24] <NCommander> But I recommend that you hug your backup first
[00:27] <garrettkajmowicz> Yeah.  My laptop doesn't actually have much on it.  It does mail by IMAP and most everything is dumb internet videos or dupliucate copies of documents which are out of date by 8 months.  I guess there's my freecell stats, but I'm not too worried.  I'm going to wait until my server works before I try something a little more risky, though.   :-)
[00:27] <NCommander> heh
[00:28] <NCommander> normally after each upgrade you should reboot, however, given that your simply going from release to release, its not necessary to reboot until after hardy is install
[00:28] <garrettkajmowicz> I *expect* to loose my laptop.  People think it's valuable (I bought it used for $200 3 years ago), and it's likely to be dropped.
[00:29] <garrettkajmowicz> OK - once download is done (198/351) we can start all over again
[00:29] <garrettkajmowicz> ! :-)
[00:31] <NCommander> Yeah
[00:31] <NCommander> Well, this is what you get for not upgrading ;-)
[00:31]  * NCommander is shot
[00:32] <garrettkajmowicz> Long day, or perforated?
[00:33] <NCommander> Huh?
[00:34] <garrettkajmowicz> Err - you are shot.  That either implies fatigue (you've had a long day), or that you've been shot with a projectile (thus having hole(s) in you, thus perforation).
[00:35] <garrettkajmowicz> It sounded funnier in my head...   :-)
[00:36] <NCommander> -_-;
[00:36] <NCommander> how goes the upgrade?
[00:37] <garrettkajmowicz> Downloading 386/351
[00:38] <garrettkajmowicz> OK - done fetching.  Now extracting.
[00:43] <garrettkajmowicz> Some problems with Apache - but I can deal with those later.  Regenerating the initramfs
[00:48] <NCommander> 386/351 O_o;
[00:48] <NCommander> Errr
[01:06] <garrettkajmowicz> OK - I ran into a problem with configuration.
[01:07] <garrettkajmowicz> NM - diff just took 3 minutes
[01:23] <garrettkajmowicz> Unpacking more stuff while I manually update the mdadm config files...
[01:30] <garrettkajmowicz> OK - upgrade is done (though Wordpress isn't working correctly at the moment...)
[01:30] <garrettkajmowicz> Should I try another update, reboot, or try to get current applications working correctly?
[01:43] <garrettkajmowicz> OK - let's go for a reboot!
[01:48] <garrettkajmowicz> See you on the flip side (loosing network connectivity momentarily)
[01:58] <garrettkajmowicz> Awesome.  A reboot and wordpress is working again.  Now to check mail services...
[01:59] <garrettkajmowicz> Looks good, too.  I guess I'll move forward to the next version and see how that works.  Thanks for all your help!
[02:00] <NCommander> no problem garrettkajmowicz
[08:09] <frewsxcv> how many gigabytes are in one U?
[08:26] <hads> Huh?
[08:31] <frewsxcv> hads: how much storage do you get with this? https://serverpronto.infolink.com/colopronto/order.php
[08:32] <hads> No idea, ask them.
[08:32] <hads> http://en.wikipedia.org/wiki/Rack_unit
[13:10] <MythbuntuGuest38> 54
[13:39] <ghaleb_> hello, I get this error when I start my freeradius server: Error: rlm_eap: Unable to load EAP-Type/peap, as EAP-Type/TLS is required first.
[15:24] <randomlogic78> I just installed Ubuntu 8.04 LTS Server Edition and I want to put the server on my wireless network with a D-Link AR5212.  Do I need to install everything from scratch, or is madwifi support built into the server edition?
[15:58] <tacone> hello, I need a lightweight smtp for local website testing. any suggestion ?
[16:24] <sommer> tacone: ssmtp works well for that type of situation
[16:24] <tacone> nice, thanks
[16:25] <sommer> welcome
[16:38] <mib_h5z0mp66> how to Installing Ubuntu 8.04 server in Virtual PC 2007
[19:06] <randomlogic78> I followed the directions on this site -> http://madwifi.org/wiki/UserDocs/802.11i to set up my wifi card on Hardy-server and I'm not getting connected to my network.  When I try to ping the router, the network is unreachable, and the link light blinking slowly on my nic
[19:07] <randomlogic78> sudo wpa_supplicant -w -Dwext -i ath0 -c/etc/wpa)supplicant.conf repeats the error "No such device" and "Could not set interface 'ath0' UP
[20:02] <Crewsr3> Can I set up a server that everyone can get to but lock down the content filtering part of just one user.  Is it as simple as user rights?  I'm installing Dansguardian and I want to be the only person that can access those settings
[20:02] <Crewsr3> I also have webadmin set so so would I have the same setting for web admin access
[20:34] <randomlogic78> On bootup my server gives the error that apache can not determine my domain name and it uses 127.0.0.1 instead... how do I set the domain name?
[20:41] <blue-frog> just a warning, not an error
[20:41] <blue-frog> give a FQDN in /etc/hosts
[20:42] <randomlogic78> thanks... just added the FQDN to hosts and rebooting now
[20:42] <blue-frog> reboot?
[20:42] <randomlogic78> I'm still annoyed that I have to run two commands to connect to my wireless network though, I wish this would happen at boot.
[20:43] <randomlogic78> I suppose I could have restarted apache, but don't know how yet
[20:43] <blue-frog> server? on wireless?
[20:43] <randomlogic78> yea
[20:44] <randomlogic78> I know, everyone thinks it's strange... but it's the best solution for me
[22:21] <lukehasnoname> am I crazy or does visudo use nano in ibex
[22:31] <jac> hi
[23:54] <D3RGPS31> under LAMP, my virtualhosts arn't responding to .htaccess files, any suggestions?