[02:29] <_ion> ^X^C? He must surely mean :q
[04:10] <kung> hi
[04:10] <kung> I just noticed, that my distro uses upstart instead of sysvinit
[04:11] <kung> nevertheless I'd like to run some of my old scripts...is there a way just to place them somewhere or do I have to rewrite them?
[04:12] <AlexExtreme> which distro?
[04:12] <AlexExtreme> Ubuntu?
[04:16] <kung> yea, edgy
[04:16] <kung> kubuntu actually
[04:16] <AlexExtreme> well, currently edgy will just run the existing sysvinit scripts, so you won't need to do anything to them
[04:17] <AlexExtreme> at least, until feisty is released.
[04:18] <kung> okay..then it must be another problem, why my scripts are no more executed..;)
[04:18] <kung> they worked for dapper, though.
[04:18] <kung> thx anyways
[04:18] <kung> :)
[04:19] <AlexExtreme> incorrect permissions, maybe?
[04:19] <AlexExtreme> what runlevel are they in? /etc/rc2.d?
[04:20] <kung> /etc/rc3.d
[04:20] <coNP> kung: do you ever switch to runlevel 3?
[04:20] <AlexExtreme> add them to rc2.d
[04:20] <AlexExtreme> then it should work
[04:21] <kung> hmm okay, it worked there in dapper...
[04:21] <kung> well and in hoary...
[04:21] <kung> ;)
[04:21] <kung> I'll move then to rc2..
[04:22] <kung> maybe I changed something to the runlevels back then..dunno
[08:57] <DarkWizzard> hello all
[08:57] <DarkWizzard> need help
[08:57] <DarkWizzard> I can't start my system
[08:57] <DarkWizzard> I'm under windows right now
[08:57] <DarkWizzard> it says rcS killed by signal 11
[08:57] <DarkWizzard> and rc-default killed by signal 11
[08:57] <DarkWizzard> thats all
[08:57] <_ion> It's segmentation fault.
[08:58] <DarkWizzard> before that suddenly it started segfaulting
[08:58] <_ion> Faulty RAM? Overclocked, overheating system?
[08:58] <DarkWizzard> I went to recovery mode
[08:58] <DarkWizzard> dont think so
[08:58] <DarkWizzard> windows works fine
[08:58] <DarkWizzard> Kubuntu edgy
[08:59] <DarkWizzard> this is strange
[08:59] <DarkWizzard> edgy is getting stranger by time
[08:59] <_ion> The first thing i'd run when programs start to segfault randomly is memtest86. You have it already installed, just select it from the grub menu.
[08:59] <DarkWizzard> ok
[08:59] <DarkWizzard> what does it do ?
[08:59] <_ion> It tests the RAM.
[09:00] <DarkWizzard> thats logical
[09:00] <DarkWizzard> ok I'll run it and come back
[09:00] <DarkWizzard> brb
[09:19] <DarkWizzard> back
[09:19] <DarkWizzard> my RAM is ok
[09:20] <DarkWizzard> I'm from a live cd
[09:20] <DarkWizzard> right now
[09:20] <DarkWizzard> I have no ideea what is causing that problem
[09:20] <DarkWizzard> maybe a reinstall of my init scripts would do the job
[09:20] <_ion> It completed all the tests in... 19 minutes?
[09:20] <DarkWizzard> not all
[09:20] <DarkWizzard> but I dont have that time
[09:21] <DarkWizzard> besides the live cd boots
[09:21] <thom> 19 minutes is useless for memtest in general
[09:22] <DarkWizzard> its not a hardware problem
[09:22] <DarkWizzard> I'm sure of that
[09:23] <DarkWizzard> E: Sub-process /usr/sbin/dpkg-preconfigure --apt || true received a segmentation fault.
[09:23] <DarkWizzard> I chrooted to the installed system
[09:23] <_ion> You could run debsums from the Live-CD to check for corrupted libraries.
[09:24] <DarkWizzard> how ?
[09:24] <DarkWizzard> I'm thinking about a clean install but first I have to revive my system and save the data
[09:24] <DarkWizzard> to bad this live cd can't write to ntfs partitions
[09:25] <DarkWizzard> *too
[09:25] <johnnybuoy> ntfs is proprietary
[09:25] <johnnybuoy> ...
[09:26] <DarkWizzard> what do you mean ?
[09:26] <johnnybuoy> too bad you use ntfs...
[09:26] <DarkWizzard> well yeah
[09:26] <johnnybuoy> well, you can't write in a language you don't know, can you..
[09:26] <DarkWizzard> its from the windows times
[09:26] <DarkWizzard> ntfs is writable
[09:26] <DarkWizzard> with ntfs-3g
[09:26] <_ion> Copy etc/apt/sources.list from your HDD to /etc/apt on the Live-CD, apt-get update, apt-get install debsums, debsums -s -r /your_hdd_mountpoint
[09:27] <_ion> (Any of those shouldn't be run inside the chroot)
[09:27] <johnnybuoy> DarkWizzard<> what is ntfs-3g?
[09:27] <DarkWizzard> a nice little program to handle ntfs filesystems under linux
[09:27] <_ion> johnnybuoy: apt-cache show
[09:27] <DarkWizzard> it makes them writable
[09:28] <johnnybuoy> hmm
[09:28] <johnnybuoy> not bad...
[09:28] <johnnybuoy> (gentoo here...)
[09:28] <_ion> I guess you can install ntfs-3g in a Live-CD session as well.
[09:32] <Keybuk> DarkWizzard: if dpkg is also segfaulting, I'd say you have either a corrupted libc, dynamic link loader, or hardware problem, e.g hard drive or RAM
[09:33] <_ion> ...And corrupted libraries are likely caused by such a hardware problem. :-)
[09:34] <cortana> DarkWizzard: if i were you i'd install debsums and check the integrity of as much as you can
[09:34] <cortana> could be tricky on the dodgy system in question tho
[09:34] <cortana> doh!
[09:35] <_ion> Well, if he was able to start a Live-CD session and a Windows session, running debsums might not be a problem.
[09:40] <DarkWIzzard> back
[09:40] <DarkWIzzard> LiveCD gone wild
[09:40] <DarkWizzard> so I need to install debsums
[09:40] <DarkWizzard> man I had a hell of a day
[09:41] <DarkWizzard> and now this
[09:42] <_ion> Please define "gone wild".
[09:42] <DarkWizzard> well it stopped spinning
[09:42] <DarkWizzard> its an old rewritable cd
[09:42] <DarkWizzard> and the system was doing to much
[09:42] <DarkWizzard> and nothing responded
[09:42] <DarkWizzard> so I just rebooted manually
[09:43] <DarkWizzard> sorry I dont have logs on the live cd
[09:44] <DarkWizzard> how do I use debsums ?
[09:44] <_ion> Copy etc/apt/sources.list from your HDD to /etc/apt in the Live-CD session, apt-get update, apt-get install debsums, debsums -s -r /your_hdd_mountpoint
[09:45] <DarkWizzard> ok
[09:45] <DarkWizzard> in progress
[09:45] <_ion> Run all of that outside any chroot.
[09:45] <DarkWizzard> ok
[09:45] <DarkWizzard> so it searches for corrupted libraryes ?
[09:46] <_ion> Well, yes.
[09:47] <DarkWizzard> I always liked kubuntu
[09:47] <DarkWizzard> but this release caused far to many problems
[09:47] <DarkWizzard> the upgrade was hell
[09:47] <DarkWizzard> tomorow I'm going to do a fresh install
[09:48] <DarkWizzard> debsums has a lot of output
[09:48] <DarkWizzard> debsums: checksum mismatch coreutils file /media/hda3/bin/mv
[09:48] <DarkWizzard> and a big list of it
[09:48] <DarkWizzard> but I know whats causing it
[09:48] <DarkWizzard> I had problem with coreutils
[09:49] <DarkWizzard> back in dapper
[09:49] <DarkWizzard> mkdir suddenly segfaultedd
[09:49] <DarkWizzard> and stty and sleep
[09:49] <DarkWizzard> so I built it from source
[09:49] <DarkWizzard> and after that it worked
[09:49] <_ion> Seems like you've had a hardware problem for a long time, and it's causing more and more visible problems.
[09:49] <DarkWizzard> I have the strangest problems
[09:50] <DarkWizzard> hmmm
[09:50] <DarkWizzard> well this was long ago
[09:50] <DarkWizzard> after that everything worked fine
[09:50] <DarkWizzard> my pc isn't the best one
[09:51] <_ion> (Btw, *never* just install stuff all around the filesystem without the package manager knowing about it.)
[09:51] <DarkWizzard> how can I tell the package manager that I installed something from source ?
[09:51] <DarkWizzard> debsums: no md5sums for initscripts
[09:52] <_ion> Well, for starters, instead of installing coreutils from source you should have identified the faulty piece of hardware and replaced it, and reinstalled the coreutils binary package.
[09:53] <DarkWizzard> how do you explain that after installing from source it worked
[09:53] <DarkWizzard> if I have faulty hardware ?
[09:53] <_ion> It's not like faulty hardware corrupts every single file a program write to the hard disk.
[09:54] <_ion> writes
[09:55] <DarkWizzard> We'll see if I keep on getting segfaults after a clean install
[09:55] <DarkWizzard> I just need to somehow install ntfs-3g on the live cd
[09:55] <_ion> Perhaps not immediately, but the system will keep getting more and more unstable, until it's unusable again.
[09:55] <DarkWizzard> well this is strange
[09:56] <_ion> Install smartmontools, run smartctl -a /dev/hda, watch for errors. Perhaps run a long self-test (smartctl -t long /dev/hda, wait, smartctl -a /dev/hda). Leave memtest running overnight.
[09:56] <DarkWizzard> what does smartctl do ?/
[09:57] <_ion> (SMART isn't guaranteed to find a fault even if your HDD, the ATA controller or the cable has one, but it might.)
[09:57] <_ion> apt-cache show smartmontools
[09:57] <DarkWizzard> but how could I temporary revive my system  ?
[09:58] <DarkWizzard> does debsums repair anything or only search ?
[09:58] <_ion> You might get a temporarily working system by reinstalling packages that debsums complains about.
[09:59] <thom> it just tells you what doesn't match
[09:59] <DarkWizzard> well
[09:59] <DarkWizzard> I cant reinstall from chroot
[09:59] <DarkWizzard> you must have guessed why
[09:59] <DarkWizzard> dpkg segfaults
[10:00] <_ion> Outside chroot: dpkg --root /mountpoint -i package.deb
[10:01] <thom> if dpkg segfaults you _definitely_ have flaky hardware
[10:01] <_ion> Begin by reinstalling libc6
[10:03] <DarkWizzard> ok
[10:03] <DarkWizzard> I just need to get some sleep
[10:03] <DarkWizzard> thanks for your help
[10:04] <DarkWizzard> good night all (even if its daytime there)
[10:04] <_ion> I'd like to emphasize again: you really need to replace the faulty piece of hardware. Otherwise you'll be running to the same  perhaps bigger  problems again and again.
[10:05] <DarkWizzard> ok I'll replace it if I'll have the buget
[10:05] <DarkWizzard> you know :)
[10:05] <_ion> You've had the problem since the first segfaults you got from the coreutils programs.
[10:05] <DarkWizzard> thats the biggest problem
[10:05] <DarkWizzard> maybe the os was buggy
[10:05] <DarkWizzard> windows never complained about hardware
[10:05] <_ion> Sigh.
[10:06] <DarkWizzard> and I spend much time under it
[10:06] <DarkWizzard> ok ok I understand
[10:06] <DarkWizzard> thanks for your help
[10:06] <DarkWizzard> bye all
[10:06] <_ion> At least leave memtest running overnight.
[11:23] <theCore> I think I found a bug/annoyance in upstart
[11:24] <theCore> if you login in GDM really fast
[11:24] <theCore> HAL doesn't have the time to start, therefore GNOME complains that HAL isn't initialized
[11:25] <Keybuk> that's not a bug in upstart
[11:25] <_ion> That doesn't have to do anything to do... keybuk was faster. :-)
[11:25] <Keybuk> that's just a bug in the ubuntu init script ordering
[11:25] <_ion> s/to do/with/
[11:25] <_ion> Argh, wrong again. :-)
[11:25] <theCore> ah, that's right
[11:26] <theCore> I always forget
[11:26] <Md> Keybuk: I need help with #397002
[11:27] <theCore> ok, then I fill that for Ubuntu package
[11:27] <Keybuk> Md: that's kinda interesting ... you check for /dev/console ?
[11:27] <Keybuk> uh, I mean assume stdin==/dev/console
[11:28] <Keybuk> RUNLEVEL and PREVLEVEL will be set
[11:28] <Md> warn_if_interactive() {
[11:28] <Md>   if [ "$RUNLEVEL" = "S" -a "$PREVLEVEL" = "N" ] ; then
[11:28] <Md>     return
[11:28] <Md>   fi
[11:28] <Md>   TTY=$(my_tty)
[11:28] <Md>   if [ -z "$TTY" -o "$TTY" = "/dev/console" ] ; then
[11:28] <Md>     return
[11:28] <Md>   fi
[11:28] <Md> where my_tty is just like tty(1)
[11:28] <Keybuk> ahh, that TTY thing will break, yes
[11:28] <Keybuk> it's arguably a bug in the Debian upstart-compat-sysv
[11:28] <Keybuk> they should have "console owner" in there for Debian, as Debian lacks Ubuntu's "no boot messages" policy
[11:29] <Keybuk> the RUNLEVEL and PREVLEVEL checks should work
[11:29] <Keybuk> oh, hmm, bet they don't
[11:29] <Keybuk> /etc/event.d/rcS doesn't set RUNLEVEL or PREVLEVEL, because rcS doesn't use them
[11:29] <Md> the submitter says that they do not
[11:29] <Keybuk> again, but in upstart-compat-sysv
[11:29] <Keybuk> s/but/bug/
[11:30] <Md> ok, I will reassign the bug and add this chat to the thread
[11:30] <Keybuk> *ndos*
[11:30] <Keybuk> *nods* even
[11:32] <theCore> I think it is too easy blame upstart, for bugs in the initscript package. It seems people really like to find bug in new software :)
[11:38] <Keybuk> I had a bug once blaming upstart for their fonts looking funny
[11:38] <_ion> Hehe.
[11:39] <theCore> their fonts?
[11:39] <theCore> whoa, that's going far ...
[11:40] <Md> theCore: people blame udev for everything, maybe next year we will have another scapegoat...
[11:41] <theCore> ah, gotta love the clueless newbie
[11:42] <Keybuk> Md: people stopped blaming udev in ubuntu
[11:42] <Keybuk> it works too well
[11:42] <theCore> personally, I never used a Linux system without udev, so I can't judge it
[11:43] <Md> it works well in debian too, they just to pretend they know how it works better than I do...
[11:43] <theCore> even the LFS I built had udev
[11:45] <theCore> so, does dbus support is still planned in upstart?
[11:55] <Keybuk> yes
[11:55] <Keybuk> either a dbus proxy, or use dbus for upstart's own IPC