[02:51] <leonel> is there a CD  version with  universe ?  I mean  if I need a Server in a Local LAN  with No internet access  how can I install universe Packages  ? 
[03:03] <malakhi> leonel: you could try https://help.ubuntu.com/community/PackageCDs
[03:04] <leonel> too easy  ... I overlooked the problem   thanks 
[03:04] <leonel> malakhi: :)
[03:05] <malakhi> np
[11:31] <[miles] > morning guys
[11:31] <[miles] > fuck, has anyone every seen a problem, that when you use sudo xxxx it gives a resolve error
[11:38] <Burgundavia> what sort of error?
[11:40] <[miles] > gethostbyname()
[11:40] <[miles] > Sudo: unable to lookup xxxxxxxx via gethostbyname()
[11:50] <shawarma> [miles] : Yes.
[11:58] <[miles] > shawarma: the hosts is correct...
[11:58] <[miles] > however..
[11:59] <[miles] > I notice when I do a hostname -f
[11:59] <[miles] > it errors
[12:00] <shawarma> With the same error, I suppose?
[12:01] <shawarma> [miles] : What does "grep `hostname` /etc/hosts" give?
[12:03] <[miles] > seems to be working now
[12:03] <shawarma> \o/
[12:03] <[miles] > I think the guy had spaces, or something in the file
[12:03] <[miles] > I did not set up the box
[12:03] <[miles] > bbias
[12:04] <ajmitch> usually that's when /etc/hostname isn't setup
[12:05] <shawarma> ajmitch: Yes, that's bound to cause trouble.
[12:05] <ajmitch> happened to me yesterday, fresh install on linode
[12:05] <[miles] > ah all sorted now
[12:05] <ajmitch> easily fixed
[12:05] <[miles] > the guy was sweating buckets
[12:05] <ajmitch> doesn't stop sudo working, usually
[12:06] <[miles] > trying to migrate him from ShitOS to Ubuntu Server
[12:06] <[miles] > sorry, CentOS
[12:06] <shawarma> Honest mistake. :)
[01:13] <Nafallo> hehe. I've heard something fun about CentOS yesterday that nearly killed me :-)
[01:19] <[miles] > tell
[01:25] <shawarma> Nafallo: Yeah, tell us. I've been holding my breath.
[01:26] <Nafallo> a friend discovered that the damn thing sets the tcp window-size through env WINDOW
[01:26] <Nafallo> and he set WINDOW=2 and wondered why things were slow... :-P
[01:35] <shawarma> O_O
[01:35] <shawarma> omg..
[01:37] <Nafallo> :-)
[01:37] <Nafallo> windowmaker probably uses env WINDOW ;-)
[01:38] <Nafallo> I really like that the networkthingies took the env from his account :-P
[01:45] <shawarma> Nafallo: I can't any mention of this anywhere.. How did he find out?
[01:45] <Nafallo> shawarma: debugging? :-)
[01:46] <Nafallo> shawarma: spent an hour on it :-P
[02:06] <ham1979> Hello
[02:07] <ham1979> I have just upgraded from breezy badger to dapper and my postfix/mailmain/amavis /clamav server has stopped delivering mail
[02:07] <ham1979> in the log there is postfix/qmgr delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1] :
[02:13] <shawarma> I can't believe I'm about to say this..
[02:13] <shawarma> ham1979: have you tried rebooting it?
[02:13] <shawarma> ham1979: Lots of stuff happens during upgrades and postfix/mailman/amavis/clamav is quite an involved setup..
[02:16] <ham1979> yep tried rebooting
[02:16] <ham1979> my amavis was renamed .conf.disabled i think
[02:17] <shawarma> I've got to go and get some lunch. I can't think properly anymore.
[02:27] <Tomasz_svk> hi, I have Ubuntu 7.04 Server. I have installed MySQL server there. But if i want to connect there throught PHPMyAdmin at another server, it write Error: #1130 - Host 'support11.cust.nextra.sk' is not allowed to connect to this MySQL server
[02:29] <mat1980> Tomasz_svk: did you gave access priviledge to the user you use from other host? maybe it has access only from localhost.
[02:30] <Tomasz_svk> i commented line #bind-address  ... but it nothing done
[02:30] <Tomasz_svk> If it was allowed, PhpMyAdmin wrote something as Server not respond
[02:32] <Tomasz_svk> But I don not want to install there Apache + PHP, because it is only game server, I need only MySQL
[02:38] <mat1980> Tomasz_svk: sorry... I'm not very experienced with mysql.
[02:39] <Tomasz_svk> is special only mysql support channel?
[02:39] <Tomasz_svk> thank you for your time
[02:39] <Tomasz_svk> is special only mysql support channel?
[02:39] <Tomasz_svk> thank you
[02:58] <ham1979> I am having trouble with amavis since upgrading from Breezy Badger to Dapper
[02:59] <ham1979> I realised that the config files are now separate I have copied some changes across but am getting same message delivery temporarily suspended
[03:09] <shawarma> ham1979: This is amavisd-new?
[03:24] <hansin321> I forget, but what is the 'standard/usual' location/path where to download and unpack source code to for compilation?  /usr/src?  Thanks.
[03:26] <ham1979> shawarma - yes amavisd-new 
[03:26] <ham1979> shouldn't have bothered upgrading!
[03:26] <malakhi> hansin321: depends on your environment. /usr/src would be where you would put deb sources. /usr/local/src would be raw sources, i think.
[03:26] <shawarma> hansin321: Your home directory, I suppose.
[03:27] <shawarma> malakhi: no.
[03:27] <malakhi> shawarma: oh?
[03:27] <shawarma> Why would you put source in /usr/src where noone can write?
[03:28] <hansin321> Thanks malakhi & shawarma.  I suppose either would do.  Good info on .deb vs. .tar.gz
[03:28] <malakhi> shawarma: root can. That's why I said it depends. If you're compiling for the entire system, then root is obviously doing the work.
[03:28] <shawarma> No.
[03:28] <shawarma> You should never log in as root.
[03:28] <shawarma> You should fiddle with the source as your normal user and when you want to install stuff, you "sudo make install" or whatever.
[03:29] <shawarma> There's no reason at all why root would be doing the compiling.
[03:29] <hansin321> shawarma: I have had the same issue.  If you compile from home directory that works, but I have also been told before that /usr/local/src is where a lot of people compile from.  But the root issue makes sense, especially since you only need to be root usually for 'make install'.
[03:30] <shawarma> hansin321: It used to be very normal for new Linux users to log in as root and do all their work that way. If you're doing that, you've lost already, but in that case it may *feel* right to be doing stuff in /usr/(local)/src, but it's really not.
[03:31] <malakhi> shawarma: I guess what I should say is that /usr/src, etc are where source code is supposed to be stored, with working occurring in /home
[03:31] <shawarma> hansin321: Yes, you should. Breezy is ancient and entirely unsupported.
[03:32] <shawarma> malakhi: In rare cases, yes.
[03:32] <malakhi> shawarma: that's the FHS standard
[03:32] <shawarma> hansin321: Sorry. That wasn't for you.
[03:32] <hansin321> shawarma: Ok, thanks.  So maybe making a ~/src or ~/.src directory for onself might not be a bad idea.
[03:32] <malakhi> hansin321: despite my debate, that's what I do.
[03:32] <shawarma> hansin321: I have a src/ directory in my homedir where I do all my work.
[03:33] <hansin321> Thanks all.  Learned a little more new today.
[03:33] <shawarma> malakhi: "Source code may be place placed in this subdirectory, only for reference purposes. [35] "
[03:33] <shawarma> malakhi: From fhs.
[03:33] <shawarma> malakhi: You can put a reference version of the linux kernel source there, for instance.
[03:34] <malakhi> shawarma: which is what I just said. You place the source there, and pull a local copy to /home for actual use.
[03:34] <shawarma> malakhi: You're not supposed to put all that tarballs of source you find everywhere in /usr/src and pull them from there when you need them.
[03:35] <shawarma> malakhi: That's not what it's for.
[03:35] <shawarma> ham1979: Yes, you should. Breezy is ancient and entirely unsupported.
[03:35] <shawarma> ham1979: Was it a very specialized amavisd setup?
[03:35] <malakhi> shawarma: Well, I'll just agree to disagree with you then.
[03:36] <shawarma> malakhi: Why, oh why, would you put all the  source code you find in random places in /usr/src ?
[03:37] <malakhi> shawarma: because multiple people need access to the same source. I know that revision control would be preferred, but sometimes that sort of overhead is unnecessary.
[03:37] <malakhi> shawarma: And I'm not talking about random source. I'm talking about a package that is frequently recompiled for use by the whole system, and all its users.
[03:38] <shawarma> malakhi: Right. those are the rare cases I mentioned. :)
[03:38] <ham1979> shawarma: Not especially - i used http://flurdy.com/docs/postfix/ which doesn't seem too tricky!
[03:38] <shawarma> malakhi: And even then, revision control is really the way to do it.
[03:38] <malakhi> shawarma: I guess the misunderstanding is that I use it that way pretty regularly, so it's not rare to me :)
[03:39] <shawarma> ham1979: I really don't remember what changed from breezy->dapper anymore.
[03:39] <shawarma> malakhi: Why on earth are you not using a vcs?
[03:40] <malakhi> shawarma: not worth the hastle. We're not actually altering the source code. Just recompiling against new deps, etc.
[03:40] <shawarma> ham1979: To be honest, I'd recommend just storing your current config for reference and starting over.
[03:40] <hansin321> Do any of you know, if I build/compile Asterisk if I need the package 'linux-source' or is 'linux-headers-server' probably enough?
[03:40] <shawarma> ham1979: I'm pretty sure it's going to be a less painful procedure.
[03:41] <shawarma> hansin321: neither
[03:41] <shawarma> hansin321: linux-libc-dev
[03:41] <hansin321> is that part of 'build-essential'?
[03:41] <shawarma> hansin321: I believe so, yes.
[03:41] <shawarma> hansin321: indirecly, yes.
[03:42] <shawarma> hansin321: It's a dependency of libc6-dev which is a dependency of build-essential.
[03:42] <hansin321> shawarma: When I compiled before, I think I got an error that was corrected by 'linux-headers-xxx', or at least that is what I remember. 
[03:42] <shawarma> hansin321: Possibly something about compiler.h?
[03:44] <hansin321> Well, some of the fine details of this stuff is a little over my head, so not sure why.  It may have been for compiling Zaptel which creates a kernel driver.  That mean a little more?
[03:45] <shawarma> hansin321: Yes, that's something entirely different. :)
[03:45] <shawarma> hansin321: In that case, you need the kernel headers.
[03:45] <shawarma> hansin321: Are the zaptel drivers in Ubuntu not sufficient?
[03:45] <hansin321> Thought so (once I thout about it).  But still don't need full kernel source, right?
[03:46] <shawarma> hansin321: Just the headers. linux-headers-`uname -r` probably.
[03:46] <hansin321> shawarma: Ubuntu stuff is 1.2.X series, and current is 1.4.x.  Asterisk compiles very nice and easy and I wan't to run 1.4.x series.
[03:47] <shawarma> hansin321: zaptel-source | 1:1.4.3~dfsg-2 | http://archive.ubuntu.com gutsy/universe Packages
[03:48] <shawarma> hansin321: You could grab that, do the module-assistant dance and be happy. :)
[03:51] <hansin321> shawarma: That is an option I suppose.  1.4.3 is the latest...  Not sure how to do the module-assistant dancce; Is it anything like the 'Twist' or the 'Hammer-Time' dance ;)
[03:51] <shawarma> hansin321: almost. :)
[03:52] <hansin321> I look it up.  Thanks for pointing it out for me...
[03:52] <shawarma> hansin321: You grab the zaptel-source package from gutsy, install it, run 'module-assistant build zapel' or something to that effect.
[03:52] <shawarma> hansin321: And then you dance.
[03:57] <hansin321> shawarma: Thanks.  I'll do the Geico 'Its my birthday, got my car fixed' thingy ;)
[03:58] <shawarma> hansin321: :)
[04:02] <hansin321> Thanks all for the help, off to work for me...
[04:38] <phil_> hello all, I'm having some problems with my LAMP server. keep getting buffer I/O errors on the /home partition and its affecting the servers ability to serve files to the network. anyone able to help?
[04:39] <dendrobates> phil_: what is the exact error
[04:42] <phil_> buffer I/O error on device sda2, logical block2129920, then ata1: command 0x25 timeout, stat 0x0d host_stat 0x21, then ata1 translated stat_err 0x0d0/00 to scsi SK/ASC?ASCQ 0xb/47/00
[04:42] <nictuku> phil_: check dmesg. may be faulty hardware
[04:42] <nictuku> hm
[04:42] <phil_> where 'then' is a line break
[04:43] <phil_> I can't really get to a prompt, when I change screens it just keep filling up with these errors and although I can type stuff, I can't type it at a prompt
[04:43] <phil_> does that make sense?
[04:45] <phil_> also, these errors don't show up when I access the box through slogin from another machine. I only see them when I plug a monitor into the server
[04:45] <dendrobates> phil_: timeout waiting on device sound lise a hardware error to me.  I've had similar problems when a fan nicked a SCSI cable.  
[04:46] <dendrobates> phil_: You see them when you plug a monitor in because they are being echoed to the console.
[04:47] <dendrobates> phil_: if you type 'dmesg' from a remote login you will see them as well.
[04:47] <phil_> ok. I just changed the cables today thinking it might be something like that. I wouldn't be surprised if it was a bust drive considering the bloody thing is only 6 months old!
[04:48] <dendrobates> phil_: unmount that filesystem and run do an fsck and check for bad blocks.
[04:48] <phil_> okay, I'll check through dmesg and see if that throws up anything else. Do you think it would be worth checking the drives SMART status? I already did a fsck check and it came out fine.
[04:50] <mathiaz> phil_: SMART status may be worth checking. It should give you some indication about errors reported by the drive.
[04:51] <phil_> ok, will do. thanks for the help dendrobates & mathiaz
[04:52] <dendrobates> phil_:  I forgot badblocks was decoupled from fsck.  you could also try 'badblocks -n /dev/sda2' 
[04:52] <phil_> ah, okay, I'll try that as well. thanks : )
[08:25] <bsdunix> anyone here?
[08:27] <mralphabet> nope
[09:43] <Triumph|TK> anyone alive?
[10:03] <shawarma> Triumph|TK: Just ask.
[10:07] <Triumph|TK> lol
[10:07] <Triumph|TK> i hate just asking it seems rude
[10:07] <Triumph|TK> i like to say hi first
[10:09] <Triumph|TK> my ssh server is giving me connection refused when i try to access it
[10:10] <Triumph|TK> i went through the config a few times
[10:10] <Triumph|TK> i have the ports forwarded
[10:15] <shawarma> It's ok to say hi first, but the asking to ask bit is more annoying than just plain rudeness :)
[10:15] <shawarma> Triumph|TK: brb
[10:18] <Triumph|TK> ok
[10:19] <TK2> lost connection there
[10:22] <shawarma> Triumph|TK: Can you connect from the machine itself?
[10:23] <TK2> i havn't tried but i have tried connecting from another computer inside my network using the network ip
[10:23] <TK2> and that does work
[10:25] <qhartman> Anyone here have experience with the Proliant DL360s?
[10:25] <qhartman> the new ones with the 6 SFF SAS drives
[10:35] <shawarma> TK2: Um... then what is it that doesn't work?
[10:35] <TK2> external ip
[10:35] <shawarma> I see. Well.. Does your router run Ubuntu?
[10:35] <TK2> does my router run ubuntu? sorry i dont understand
[10:36] <shawarma> TK2: I'm not sure I can ask any clearer.. Do you have a router?
[10:36] <TK2> yes
[10:36] <TK2> is my ubuntu server on my router?
[10:36] <TK2> yes
[10:37] <shawarma> What kind of router is it?
[10:37] <TK2> westell
[10:38] <TK2> when i try to connect externally it says connection refused not connection timed out
[10:38] <TK2> so its making a connection the server is just refusing it
[10:40] <shawarma> You router can reject connections as well.
[10:41] <TK2> i forwarded port 22
[10:43] <mralphabet> so dsl modem / router ---> ubuntu box --> network ?
[10:43] <mralphabet> or dsl modem / router ---> network --> ubuntu box ?
[10:43] <TK2> 2nd one
[10:44] <TK2> the ubuntu box is just on the switch
[10:44] <TK2> with the network
[10:44] <mralphabet> k
[10:44] <TK2> is that wrong?
[10:44] <mralphabet> so you are trying to connect from the outside to the ubuntu box?
[10:45] <TK2> im trying to make my web server and my ssh server accessable via my external ip outside my network , my ftp server for some reason DOES work from outsdie my network but the others don't
[10:45] <TK2> the apache server might be a whole different issue but im concentrating on 1 at a time
[10:46] <TK2> although i am testing the ssh server from inside my network using my external ip
[10:46] <TK2> trying to give as many details as possible
[10:47] <mralphabet> that's fine, I'm looking at 2 or 3 different things atm, so slow to respond ;)
[10:47] <TK2> not a problem
[10:47] <mralphabet> not wrong, by the way, that's a normal setup
[10:48] <mralphabet> it is also quite common for ISP's to block port 22 and port 80
[10:48] <TK2> really
[10:48] <TK2> hmm
[10:49] <TK2> maybe i should try changing the ports
[10:50] <mralphabet> to be honost, I'm surprised ftp works
[10:50] <mralphabet> my ISP used to block anything < 1024
[10:50] <TK2> im on verizon dsl =O
[10:50] <mralphabet> then they moved to selective ports, IE 21 80 53 88, others
[10:52] <TK2> im going to change my ssh port to 420 and try it
[10:55] <TK2> same error connection refused
[10:55] <TK2> oh wait forgot to forward new port
[10:58] <TK2> same error connection refused
[11:00] <TK2> i think it might be that i set up my hosts config wrong but then again my ftp works
[11:02] <TK2> mr.alphabet could i ask you some questions about my host config
[11:03] <TK2> please
[11:03] <skreet> exit
[11:05] <mralphabet> sure
[11:06] <TK2> ok in /etc/hosts
[11:06] <TK2> my 1st line should be 127.0.0.1 localhost
[11:06] <TK2> what should my 2nd line be
[11:10] <mralphabet> 127.0.1.1       Dominus.stp.wi.charter.com      Dominus
[11:10] <mralphabet> that's mine
[11:10] <TK2> ok mine is similar
[11:10] <mralphabet> IP    FQDN    Machine Name
[11:11] <TK2> 192.168.1.46 server.myhome.westell.com server
[11:11] <mralphabet> yeah
[11:11] <mralphabet> no
[11:11] <mralphabet> no
[11:11] <TK2> =O
[11:11] <mralphabet> the 127.0.1.1 is important
[11:12] <mralphabet> 127.0.0.1       localhost
[11:12] <mralphabet> 127.0.1.1       Dominus.stp.wi.charter.com      Dominus
[11:12] <TK2> ok
[11:12] <TK2> ill put the 127.0.1.1
[11:12] <mralphabet> the 192.168.1.46 server.myhome.westell.com server
[11:12] <mralphabet> is a third line
[11:13] <TK2> so my 2nd line should be 127.0.1.1 server.myhome.westll.com server
[11:13] <mralphabet> yes
[11:13] <TK2> gotcha
[11:13] <mralphabet> well, westell
[11:13] <mralphabet> with the e ;)
[11:15] <TK2> k restarting my network
[11:16] <TK2> still refused
[11:17] <mralphabet> try something above 10k
[11:17] <TK2> ok
[11:17] <mralphabet> you have a connection on the outside world you are trying from, right?
[11:17] <TK2> nop
[11:18] <TK2> is that a problem
[11:19] <mralphabet> usually you aren't able to use the external IP address to engage the port forwarding on the westell unless you are outside the network
[11:19] <mralphabet> can you ssh or http to the box from inside your network?
[11:20] <TK2> http no, ive had friends try
[11:20] <mralphabet> k
[11:20] <mralphabet> let's back up a step
[11:20] <TK2> all ears
[11:20] <TK2> your help is much appreciated
[11:21] <mralphabet> these services you are trying to reach on the ubuntu machine, can you connect to them at all from _inside_ your network, IE using the 192 address
[11:21] <TK2> yes
[11:23] <mralphabet> okay, so you have somebody outside your network trying to hit whatever.your.ip.address:port is and they are getting a connection refused
[11:23] <TK2> i have not had them try to connect via ssh but when trying to connect to the web server they are getting page cannot be displayed
[11:24] <mralphabet> and they are trying 123.456.789.123:450
[11:24] <mralphabet> *fill in your ip address and port here*
[11:25] <TK2> port is 80 i never added the port for them
[11:25] <TK2> but yes http://myip
[11:25] <mralphabet> k
[11:26] <TK2> and i have had them succesfully access the ftp server in the same way
[11:27] <mralphabet> If you are using port forwarding on the westell to get around the port 80 limitation, the outside world needs to refernce that port in the address bar
[11:27] <mralphabet> IE my http port is 8888
[11:27] <mralphabet> so to visit my home web server from outside, I need http://123.456.789.32:8888
[11:28] <mralphabet> my router translates 8888 on the outside to 80 on the inside and forwards it to my webserver
[11:29] <mralphabet> so 123.456.789.32:8888  -->  8888-router with NAT-80 --> 192.168.1.10:80
[11:29] <TK2> ok and that is all set up through the router
[11:30] <mralphabet> through my router, yes
[11:30] <mralphabet> I don't know if the westell can do that kind of translation
[11:30] <TK2> ok this information is very helpful
[11:31] <TK2> is that called trigger ports by any chance?
[11:31] <TK2> Forward a range of ports to an IP
[11:31] <TK2> address on the LAN only after
[11:31] <TK2> specific outbound traffic
[11:31] <mralphabet> if the westell *can't* do port to different port translation, you will need to get your apache to answer on the different port as well
[11:31] <mralphabet> IE 123.456.789.32:8888  -->  8888-router with NAT-8888 --> 192.168.1.10:8888
[11:32] <TK2> what is the service called in your router
[11:33] <mralphabet> port forwarding ;)
[11:33] <mralphabet> I don't run a westell
[11:34] <TK2> thank god for you
[11:34] <TK2> its a modem / router
[11:34] <TK2> i have another linksys i could use also
[11:34] <TK2> but this way is easier
[11:34] <mralphabet> http://www.google.com/search?q=westell+port+forwarding
[11:34] <mralphabet> putting a linksys in place would not solve your problem
[11:35] <mralphabet> that would only mean modem/westell(NAT) --> linksys(NAT) --> network
[11:35] <TK2> IE 123.456.789.32:80 --> 80-router with NAT-80 --> 192.168.1.10:80
[11:35] <mralphabet> level of complexity x2
[11:35] <TK2> i have this set up as of now, is this wrong?
[11:36] <mralphabet> that should be right, as long as verizon doesn't block port 80
[11:36] <TK2> ohhh i see what ur saying now
[11:36] <TK2> this is just to see if that port is being blocked
[11:36] <TK2> excuse my ignorance
[11:37] <mralphabet> It's really  Verizon Router serving IP to you --> modem/westel blah blah blah
[11:37] <mralphabet> in the Verizon Router they can block whatever they want and it will not reach you
[11:37] <TK2> in my port forwarding options i have global port range and base port range im thinking the 8888 should be the global and 80 should be the base
[11:38] <TK2> ok then ill just change the apache port to 8888 to test it
[11:39] <mralphabet> http://www.voip.com/help/Residential/Installation/Networking/westell_port_fwd.aspx
[11:39] <mralphabet> ^^ similar configuration
[11:40] <mralphabet> http://www.portforward.com/
[11:40] <TK2> i know how to port forward though
[11:41] <TK2> im gunna change the apache listen port to 8888 and forward 8888 on my router then ill let ya know what happens
[11:41] <TK2> again thanks for your time
[11:47] <mpathy> Hi there..
[11:48] <mpathy> Having problems with an dist-upgrade..
[11:48] <mpathy> From Dapper to Edgy worked
[11:49] <mpathy> Now after another reboot started dist-upgrade Edgy to Feisty, and now I got this: http://pastie.caboo.se/72487.txt
[11:51] <TK2> mralphabet
[11:51] <TK2> mralphabet
[11:51] <TK2> it works
[11:51] <TK2> it works
[11:52] <mralphabet> grats
[11:52] <TK2> :)
[11:52] <TK2> port 8888 did the trick
[11:52] <TK2> :) :_) :) :)
[11:53] <TK2> thank you so much
[11:53] <mpathy> I looks like Ubuntu only works good with Grub - isnt that some kind of bad?
[11:54] <mralphabet> TK2: no problem
[11:55] <mpathy> hmm
[11:57] <mralphabet> mpathy: dist-upgrade may not be the recommended path up to feisty
[11:58] <mralphabet> mpathy: sudo apt-get install update-manager-core
[11:58] <mralphabet> mpathy: sudo do-release-upgrade
[11:58] <mpathy> ?
[11:59] <mralphabet> that's the recommended upgrade method to feisty (from edgy)
[11:59] <mpathy> Why I didnt get at least one simple warning on that somewhere..? Which person think of that who works with debian based systems for years?
[12:00] <mpathy> can I do it yet altough?
[12:00] <mralphabet> well, it's listed on http://www.ubuntu.com/getubuntu/upgrading
[12:01] <mralphabet> it was listed in the documentation for months
[12:01] <ajmitch> mpathy: if you want to stick with lilo, check /etc/kernel-img.conf to see what bootloader it's trying to setup on kernel install
[12:01] <ajmitch> most likely it has postinst hooks there to run update-grub
[12:01] <mpathy> ajmitch: it works until I did dist-upgrade also with liko
[12:02] <mpathy> ajmitch: yes.. as lilo does never exist..
[12:02] <mpathy> do I have to edit the post-inst file now forever?
[12:02] <ajmitch> no
[12:03] <mpathy> but?
[12:04] <mpathy> I run lilo after every new kernel thats not the problem.. but if ubuntu tries every time to do update-grub, it would be really annoying
[12:04] <ajmitch> and I told you where it says what gets run
[12:07] <mpathy> ajmitch: I changed it and he puts out the help text on sudo apt-get -f install
[12:08] <mpathy> ajmitch: but there are no parameters, you update with only "lilo"
[12:09] <ajmitch> so what do you have for postinst_hook in /etc/kernel-img.conf now?