From maintainer at lunar-linux.org Fri Aug 1 12:35:31 2008 From: maintainer at lunar-linux.org (maintainer@lunar-linux.org) Date: Fri, 1 Aug 2008 12:35:31 +0200 (CEST) Subject: weekly news - 20080801 Message-ID: <20080801103531.CCFFAF29F6@doppio.foo-projects.org> Hi! Here's the latest weekly news edition! ===================================================================== ===================================================================== New modules: (2) librelp-0.1.1: A reliable logging library rsyslog-3.18.1: An enhanced multi-threaded syslogd with a focus on security and r Removed modules: (1) links2 New versions: (44) GraphicsMagick : 1.2.4 -> 1.2.5 NVIDIA : 173.14.09 -> 173.14.12 airconfig-svn : svn-29 -> svn-30 akonadi : svn-29 -> svn-30 automoc : svn-29 -> svn-30 avidemux : 2.4.1 -> 2.4.3 cronie : 1.1 -> 1.2 discover-data : 2.2008.07.01 -> 2.2008.08.01 ferm : 2.0 -> 2.0.2 fox : 1.6.33 -> 1.6.34 fuse : 2.7.3 -> 2.7.4 ghal-svn : svn-29 -> svn-30 gitosis-git : git-29 -> git-30 heirloom-mailx : 12.3 -> 12.4 inputproto : 1.4.3 -> 1.4.4 libzip : 0.8 -> 0.9 links : 0.98 -> 2.2 linux-2.4 : 2.4.36.1 -> 2.4.36.6 linux-2.4-agr : 2.4.36.1 -> 2.4.36.6 linux-2.4-grsec : 2.4.36.1 -> 2.4.36.6 linux-2.4-om : 2.4.36.1 -> 2.4.36.6 linux-2.4-stable : 2.4.36.1 -> 2.4.36.6 linux-2.4-vanilla : 2.4.36.1 -> 2.4.36.6 linux-2.6-mm : 2.6.26-rc8-mm1 -> 2.6.27-rc1-mm1 lyx : 1.5.5 -> 1.5.6 phpMyAdmin : 2.11.7.1 -> 2.11.8.1 pixman : 0.11.4 -> 0.11.8 poppler : 0.8.3 -> 0.8.4 postfix : 2.5.2 -> 2.5.3 pygame : 1.8.0release -> 1.8.1release qt4 : 4.4.0 -> 4.4.1 raptor : 1.4.16 -> 1.4.18 soprano : 2.0.98 -> 2.1 swfdec : 0.6.6 -> 0.6.8 syslinux : 3.63 -> 3.71 thunderbird : 2.0.0.14 -> 2.0.0.16 transcode : 1.0.5 -> 1.0.6 uade : 2.09 -> 2.11 vsftpd : 2.0.6 -> 2.0.7 wavpack : 4.41.0 -> 4.50.1 webkitkde : svn-29 -> svn-30 wesnoth : 1.4.3 -> 1.4.4 xf86-video-intel : 2.3.1 -> 2.4.0 xf86-video-vmware : 10.16.2 -> 10.16.3 Moved modules: cronie : zbeta -> utils lyx : x11-apps -> qt4-apps raptor : audio -> libs ===================================================================== The Lunar-Linux team From maintainer at lunar-linux.org Fri Aug 8 12:35:31 2008 From: maintainer at lunar-linux.org (maintainer@lunar-linux.org) Date: Fri, 8 Aug 2008 12:35:31 +0200 (CEST) Subject: weekly news - 20080808 Message-ID: <20080808103531.ED290F29F0@doppio.foo-projects.org> Hi! Here's the latest weekly news edition! ===================================================================== ===================================================================== New modules: (3) consonance-0.3: lightweight music manager laptop-mode-tools-1.45: A laptop power saving package for Linux systems mbr-1.1.10: A Master Boot Record partition manager New versions: (31) airconfig-svn : svn-30 -> svn-31 akonadi : svn-30 -> svn-31 automoc : svn-30 -> svn-31 bind : 9.5.0-P1 -> 9.5.0-P2 dejavu-ttf : 2.20 -> 2.26 foo2zjs : 20080605 -> 20080730 ghal-svn : svn-30 -> svn-31 ghostscript : 8.62 -> 8.63 git : 1.5.6.4 -> 1.5.6.5 gitosis-git : git-30 -> git-31 gnome-pilot : 2.0.10 -> 2.0.16 gnucash : 2.2.5 -> 2.2.6 gnutls : 2.3.2 -> 2.4.1 hplip : 2.8.6 -> 2.8.7 intltool : 0.40.0 -> 0.40.3 konversation : 1.0.1 -> 1.1 ktorrent4 : 3.1.1 -> 3.1.2 lftp : 3.7.3 -> 3.7.4 libkdcraw : 0.1.3 -> 0.1.4 liferea : 1.4.16b -> 1.4.17 linux-2.6 : 2.6.26 -> 2.6.26.2 man-pages : 3.05 -> 3.06 mpg123 : 1.4.3 -> 1.5.0 samba : 3.2.0 -> 3.2.1 snort : 2.8.2.1 -> 2.8.2.2 sox : 14.0.1 -> 14.1.0 sqlite : 3.5.9 -> 3.6.1 subversion : 1.5.0 -> 1.5.1 transmission : 1.22 -> 1.31 webkitkde : svn-30 -> svn-31 zile : 2.2.59 -> 2.2.61 ===================================================================== The Lunar-Linux team From cjhandrew at gmail.com Sun Aug 10 11:51:51 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Sun, 10 Aug 2008 10:51:51 +0100 Subject: USB missing in connect.lunar Message-ID: <307203ff0808100251i6be37e29r3b6bab5e82aeb182@mail.gmail.com> Hi, everyone. I'm new to Lunar and the list and am just doing my first install. The spare box I am using, connects to my router via a USB port, not eth0. I managed to get networking set-up with the help of 'dagbrown' (many thanks). I noticed that /var/lib/lunar/functions/connect.lunar tries different network options, but seems to be missing USB[1-9]. I placed this in the file manually, and my USB network connection worked perfectly. Unfortuantely, when I ran lin moonbase (http://www.lunar-linux.org/index.php?option=com_content&task=view&id=58&Itemid=1), my USB option was removed. I guess the file was updated/ replaced. Does anyone know whether it is possible to make the USB addition persistent, so that when I do future updates, I won't lose my network connection? Should this be filed as a bug (improvement)? Anyway, looks like a great distro. Many thanks, Chris. -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From cjhandrew at gmail.com Sun Aug 10 11:53:38 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Sun, 10 Aug 2008 10:53:38 +0100 Subject: Sparc (32-bit) support? Message-ID: <307203ff0808100253i3f1b668bn5f5ef08fac160fb3@mail.gmail.com> Hi, all. As per previous message, I am new to Lunar. I read on Wikipedia that Lunar may support sparc (32-bit). I have a Sparcstation20 that would love to run Lunar. Has anyone managed to get it running on sparc, before? Many thanks, Chris. -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From sofar at foo-projects.org Mon Aug 11 18:53:51 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Mon, 11 Aug 2008 09:53:51 -0700 Subject: USB missing in connect.lunar In-Reply-To: <307203ff0808100251i6be37e29r3b6bab5e82aeb182@mail.gmail.com> References: <307203ff0808100251i6be37e29r3b6bab5e82aeb182@mail.gmail.com> Message-ID: <48A06E9F.2060502@foo-projects.org> Chris Andrew wrote: > Hi, everyone. > > I'm new to Lunar and the list and am just doing my first install. > > The spare box I am using, connects to my router via a USB port, not > eth0. I managed to get networking set-up with the help of 'dagbrown' > (many thanks). > > I noticed that /var/lib/lunar/functions/connect.lunar tries different > network options, but seems to be missing USB[1-9]. I placed this in > the file manually, and my USB network connection worked perfectly. rename your usb0 device to eth0 using `ifrename` and it all should work just fine. Auke From dagbrown at lart.ca Mon Aug 11 19:52:24 2008 From: dagbrown at lart.ca (Dave Brown) Date: Tue, 12 Aug 2008 02:52:24 +0900 Subject: USB missing in connect.lunar In-Reply-To: <48A06E9F.2060502@foo-projects.org> References: <307203ff0808100251i6be37e29r3b6bab5e82aeb182@mail.gmail.com> <48A06E9F.2060502@foo-projects.org> Message-ID: <20080811175224.GA31253@phb> On Mon, Aug 11, 2008 at 09:53:51AM -0700, Kok, Auke wrote: > Chris Andrew wrote: > > Hi, everyone. > > > > I'm new to Lunar and the list and am just doing my first install. > > > > The spare box I am using, connects to my router via a USB port, not > > eth0. I managed to get networking set-up with the help of 'dagbrown' > > (many thanks). > > > > I noticed that /var/lib/lunar/functions/connect.lunar tries different > > network options, but seems to be missing USB[1-9]. I placed this in > > the file manually, and my USB network connection worked perfectly. > > rename your usb0 device to eth0 using `ifrename` and it all should work just fine. That doesn't seem like an acceptable answer. Is wireless-tools preinstalled on the ISO? That's the package which contains ifrename, and if you don't have that, you need to install it, which involves manually patching connect.lunar (this is a TRIVIAL patch by the way, it took me ten seconds to figure it out when I was helping Chris on #lunar) to find the usb[0-9] network interface. For another thing, network configuration should happen in the installer, and that should be aware of such things as USB network interfaces. The lnet utility exists for a reason--to get things like that right so the user doesn't have to waste time manually changing things on their system. --Dave From dennisveatch at bellsouth.net Mon Aug 11 20:46:02 2008 From: dennisveatch at bellsouth.net (Dennis Veatch) Date: Mon, 11 Aug 2008 14:46:02 -0400 Subject: USB missing in connect.lunar In-Reply-To: <20080811175224.GA31253@phb> References: <307203ff0808100251i6be37e29r3b6bab5e82aeb182@mail.gmail.com> <48A06E9F.2060502@foo-projects.org> <20080811175224.GA31253@phb> Message-ID: <200808111446.02320.dennisveatch@bellsouth.net> On Monday 11 August 2008 13:52:24 Dave Brown wrote: > On Mon, Aug 11, 2008 at 09:53:51AM -0700, Kok, Auke wrote: > > Chris Andrew wrote: > > > Hi, everyone. > > > > > > I'm new to Lunar and the list and am just doing my first install. > > > > > > The spare box I am using, connects to my router via a USB port, not > > > eth0. I managed to get networking set-up with the help of 'dagbrown' > > > (many thanks). > > > > > > I noticed that /var/lib/lunar/functions/connect.lunar tries different > > > network options, but seems to be missing USB[1-9]. I placed this in > > > the file manually, and my USB network connection worked perfectly. > > > > rename your usb0 device to eth0 using `ifrename` and it all should work > > just fine. > > That doesn't seem like an acceptable answer. > > Is wireless-tools preinstalled on the ISO? That's the package which > contains ifrename, and if you don't have that, you need to install it, > which involves manually patching connect.lunar (this is a TRIVIAL patch > by the way, it took me ten seconds to figure it out when I was helping > Chris on #lunar) to find the usb[0-9] network interface. > > For another thing, network configuration should happen in the installer, > and that should be aware of such things as USB network interfaces. The > lnet utility exists for a reason--to get things like that right so the > user doesn't have to waste time manually changing things on their > system. > > --Dave Looking at the wireless_tools BUILD, is appears, iwevent and ifrename do not get copied to /sbin. -- You can tuna piano but you can't tune a fish. http://www.lunar-linux.org/ It's worth the spin. From cjhandrew at gmail.com Tue Aug 12 13:04:56 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Tue, 12 Aug 2008 12:04:56 +0100 Subject: Grub broken. Message-ID: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> Hi, I did my first update to Lunar yesterday, and it seems like Lunar is now broken. When I boot the machine, Grub arrives at a prompt, and won't let me boot. Can anyone help me point Grub to the correct kernel image, or whatever else I need to do? Many thanks, Chris. -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From dagbrown at lart.ca Tue Aug 12 13:21:01 2008 From: dagbrown at lart.ca (Dave Brown) Date: Tue, 12 Aug 2008 20:21:01 +0900 Subject: Grub broken. In-Reply-To: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> Message-ID: <20080812112101.GA20027@phb> On Tue, Aug 12, 2008 at 12:04:56PM +0100, Chris Andrew wrote: > Hi, > > I did my first update to Lunar yesterday, and it seems like Lunar is now broken. > > When I boot the machine, Grub arrives at a prompt, and won't let me boot. > > Can anyone help me point Grub to the correct kernel image, or whatever > else I need to do? Looks like you might have to create a menu.lst file by hand. You put it in /boot/grub (assuming /boot is a separate filesystem for you) and list your kernel options in it. I'd offer mine as an example, but it has crazy in it to deal with my all-RAID-all-the-time system. --Dave From samuel.verstraete at gmail.com Tue Aug 12 13:23:01 2008 From: samuel.verstraete at gmail.com (samuel) Date: Tue, 12 Aug 2008 13:23:01 +0200 Subject: Grub broken. In-Reply-To: <20080812112101.GA20027@phb> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> Message-ID: afaik it has nothing to do with menu.lst... just a borked grub install routine in lunar :) On Tue, Aug 12, 2008 at 1:21 PM, Dave Brown wrote: > On Tue, Aug 12, 2008 at 12:04:56PM +0100, Chris Andrew wrote: >> Hi, >> >> I did my first update to Lunar yesterday, and it seems like Lunar is now broken. >> >> When I boot the machine, Grub arrives at a prompt, and won't let me boot. >> >> Can anyone help me point Grub to the correct kernel image, or whatever >> else I need to do? > > Looks like you might have to create a menu.lst file by hand. You put it > in /boot/grub (assuming /boot is a separate filesystem for you) and list > your kernel options in it. > > I'd offer mine as an example, but it has crazy in it to deal with my > all-RAID-all-the-time system. > > --Dave > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > From cjhandrew at gmail.com Tue Aug 12 17:06:13 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Tue, 12 Aug 2008 16:06:13 +0100 Subject: Grub broken. In-Reply-To: <20080812112101.GA20027@phb> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> Message-ID: <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> Can anyone tell me what I should type at the Grub > prompt to see what my menu.1st looks like? Cheers, Chris. 2008/8/12 Dave Brown : > On Tue, Aug 12, 2008 at 12:04:56PM +0100, Chris Andrew wrote: >> Hi, >> >> I did my first update to Lunar yesterday, and it seems like Lunar is now broken. >> >> When I boot the machine, Grub arrives at a prompt, and won't let me boot. >> >> Can anyone help me point Grub to the correct kernel image, or whatever >> else I need to do? > > Looks like you might have to create a menu.lst file by hand. You put it > in /boot/grub (assuming /boot is a separate filesystem for you) and list > your kernel options in it. > > I'd offer mine as an example, but it has crazy in it to deal with my > all-RAID-all-the-time system. > > --Dave > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From sofar at foo-projects.org Tue Aug 12 18:35:33 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Tue, 12 Aug 2008 09:35:33 -0700 Subject: Grub broken. In-Reply-To: <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> Message-ID: <48A1BBD5.5060401@foo-projects.org> Chris Andrew wrote: > Can anyone tell me what I should type at the Grub > prompt to see what > my menu.1st looks like? Ive seen this bug and it's sometimes not even needed to fix a menu.lst file. At the failed boot prompt you can `reinstall` grub on the fly: > root (hd0,0) > setup (hd0) > reboot this will work if your /boot partition is /dev/sda and you had/want grub in the mbr. if the above `setup` command works then grub will find your menu.lst file again and hopefully it'll work if not then you can boot as follows: > root (hd0,0) > kernel 2.6.2x root=/dev/sda2 > boot and then try to use lunar to fix it (lin -c grub, lin -c linux-2.6) Auke From cjhandrew at gmail.com Tue Aug 12 19:32:29 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Tue, 12 Aug 2008 18:32:29 +0100 Subject: Grub broken. In-Reply-To: <48A1BBD5.5060401@foo-projects.org> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> Message-ID: <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> Hi, all. Thanks, Auke, > root (hd0,0) > setup (hd0) > reboot did the job and it now boots. For some strange reason I am now getting an fcsk error 8 on /dev/hda2. I tried /sbin/fsck -y /dev/hda2, boot it says that my superblock is missing or corrupt. Before I installed Lunar, I did an exhaustive HDD check, so I'm sure my HDD is ok. Can anyone help me get past this? Failing that, I will try 1 fresh install. Many thanks, Chris. 2008/8/12 Kok, Auke : > Chris Andrew wrote: >> Can anyone tell me what I should type at the Grub > prompt to see what >> my menu.1st looks like? > > Ive seen this bug and it's sometimes not even needed to fix a menu.lst file. At > the failed boot prompt you can `reinstall` grub on the fly: > >> root (hd0,0) >> setup (hd0) >> reboot > > this will work if your /boot partition is /dev/sda and you had/want grub in the > mbr. if the above `setup` command works then grub will find your menu.lst file > again and hopefully it'll work > > if not then you can boot as follows: > >> root (hd0,0) >> kernel 2.6.2x root=/dev/sda2 >> boot > > and then try to use lunar to fix it (lin -c grub, lin -c linux-2.6) > > Auke > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From sofar at foo-projects.org Tue Aug 12 20:24:08 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Tue, 12 Aug 2008 11:24:08 -0700 Subject: Grub broken. In-Reply-To: <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> Message-ID: <48A1D548.9080603@foo-projects.org> Chris Andrew wrote: > Hi, all. > > Thanks, Auke, > >> root (hd0,0) >> setup (hd0) >> reboot > > did the job and it now boots. For some strange reason I am now > getting an fcsk error 8 on /dev/hda2. > > I tried /sbin/fsck -y /dev/hda2, boot it says that my superblock is > missing or corrupt. Before I installed Lunar, I did an exhaustive HDD > check, so I'm sure my HDD is ok. ew. fortunately there are backup superblocks. To find out where they are, run `mkfs.ext3` with the -n option so that it displays their location (but doesn't actually format the filesystem): # mkfs.ext3 -n /dev/hda2 then use fsck.ext3 with one of those numbers to see if it can be recovered: # fsck.ext3 -b $BLOCKNUMBER /dev/hda2 warning: if the superblock is bad it's quite likely something trashed the filesystem alltogether (like installing grub in the wrong location). Auke > > Can anyone help me get past this? Failing that, I will try 1 fresh install. > > Many thanks, > > Chris. > > 2008/8/12 Kok, Auke : >> Chris Andrew wrote: >>> Can anyone tell me what I should type at the Grub > prompt to see what >>> my menu.1st looks like? >> Ive seen this bug and it's sometimes not even needed to fix a menu.lst file. At >> the failed boot prompt you can `reinstall` grub on the fly: >> >>> root (hd0,0) >>> setup (hd0) >>> reboot >> this will work if your /boot partition is /dev/sda and you had/want grub in the >> mbr. if the above `setup` command works then grub will find your menu.lst file >> again and hopefully it'll work >> >> if not then you can boot as follows: >> >>> root (hd0,0) >>> kernel 2.6.2x root=/dev/sda2 >>> boot >> and then try to use lunar to fix it (lin -c grub, lin -c linux-2.6) >> >> Auke >> _______________________________________________ >> Lunar mailing list >> Lunar at lunar-linux.org >> http://foo-projects.org/mailman/listinfo/lunar >> > > > From cjhandrew at gmail.com Tue Aug 12 20:31:24 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Tue, 12 Aug 2008 19:31:24 +0100 Subject: Grub broken. In-Reply-To: <48A1D548.9080603@foo-projects.org> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> Message-ID: <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> "This device apparently does not exist". Does anyone know why this has happened? I'm reluctant to do a long install just to replicate the error. Thanks again, Auke. Cheers, Chris. 2008/8/12 Kok, Auke : > Chris Andrew wrote: >> Hi, all. >> >> Thanks, Auke, >> >>> root (hd0,0) >>> setup (hd0) >>> reboot >> >> did the job and it now boots. For some strange reason I am now >> getting an fcsk error 8 on /dev/hda2. >> >> I tried /sbin/fsck -y /dev/hda2, boot it says that my superblock is >> missing or corrupt. Before I installed Lunar, I did an exhaustive HDD >> check, so I'm sure my HDD is ok. > > ew. fortunately there are backup superblocks. To find out where they are, run > `mkfs.ext3` with the -n option so that it displays their location (but doesn't > actually format the filesystem): > > # mkfs.ext3 -n /dev/hda2 > > then use fsck.ext3 with one of those numbers to see if it can be recovered: > > # fsck.ext3 -b $BLOCKNUMBER /dev/hda2 > > > warning: if the superblock is bad it's quite likely something trashed the > filesystem alltogether (like installing grub in the wrong location). > > Auke > > >> >> Can anyone help me get past this? Failing that, I will try 1 fresh install. >> >> Many thanks, >> >> Chris. >> >> 2008/8/12 Kok, Auke : >>> Chris Andrew wrote: >>>> Can anyone tell me what I should type at the Grub > prompt to see what >>>> my menu.1st looks like? >>> Ive seen this bug and it's sometimes not even needed to fix a menu.lst file. At >>> the failed boot prompt you can `reinstall` grub on the fly: >>> >>>> root (hd0,0) >>>> setup (hd0) >>>> reboot >>> this will work if your /boot partition is /dev/sda and you had/want grub in the >>> mbr. if the above `setup` command works then grub will find your menu.lst file >>> again and hopefully it'll work >>> >>> if not then you can boot as follows: >>> >>>> root (hd0,0) >>>> kernel 2.6.2x root=/dev/sda2 >>>> boot >>> and then try to use lunar to fix it (lin -c grub, lin -c linux-2.6) >>> >>> Auke >>> _______________________________________________ >>> Lunar mailing list >>> Lunar at lunar-linux.org >>> http://foo-projects.org/mailman/listinfo/lunar >>> >> >> >> > > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From samuel.verstraete at gmail.com Tue Aug 12 20:37:42 2008 From: samuel.verstraete at gmail.com (samuel) Date: Tue, 12 Aug 2008 20:37:42 +0200 Subject: Grub broken. In-Reply-To: <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> Message-ID: that's interesting... i got the same with my last lunar install... installed already 4 times again.. and everytime the same all i updated is theedge... maybe lunar-init is borking something??? cause mounting the device from the iso says it'"s perfectly clean... On Tue, Aug 12, 2008 at 8:31 PM, Chris Andrew wrote: > "This device apparently does not exist". > > Does anyone know why this has happened? I'm reluctant to do a long > install just to replicate the error. > > Thanks again, Auke. > > Cheers, > > Chris. > > 2008/8/12 Kok, Auke : >> Chris Andrew wrote: >>> Hi, all. >>> >>> Thanks, Auke, >>> >>>> root (hd0,0) >>>> setup (hd0) >>>> reboot >>> >>> did the job and it now boots. For some strange reason I am now >>> getting an fcsk error 8 on /dev/hda2. >>> >>> I tried /sbin/fsck -y /dev/hda2, boot it says that my superblock is >>> missing or corrupt. Before I installed Lunar, I did an exhaustive HDD >>> check, so I'm sure my HDD is ok. >> >> ew. fortunately there are backup superblocks. To find out where they are, run >> `mkfs.ext3` with the -n option so that it displays their location (but doesn't >> actually format the filesystem): >> >> # mkfs.ext3 -n /dev/hda2 >> >> then use fsck.ext3 with one of those numbers to see if it can be recovered: >> >> # fsck.ext3 -b $BLOCKNUMBER /dev/hda2 >> >> >> warning: if the superblock is bad it's quite likely something trashed the >> filesystem alltogether (like installing grub in the wrong location). >> >> Auke >> >> >>> >>> Can anyone help me get past this? Failing that, I will try 1 fresh install. >>> >>> Many thanks, >>> >>> Chris. >>> >>> 2008/8/12 Kok, Auke : >>>> Chris Andrew wrote: >>>>> Can anyone tell me what I should type at the Grub > prompt to see what >>>>> my menu.1st looks like? >>>> Ive seen this bug and it's sometimes not even needed to fix a menu.lst file. At >>>> the failed boot prompt you can `reinstall` grub on the fly: >>>> >>>>> root (hd0,0) >>>>> setup (hd0) >>>>> reboot >>>> this will work if your /boot partition is /dev/sda and you had/want grub in the >>>> mbr. if the above `setup` command works then grub will find your menu.lst file >>>> again and hopefully it'll work >>>> >>>> if not then you can boot as follows: >>>> >>>>> root (hd0,0) >>>>> kernel 2.6.2x root=/dev/sda2 >>>>> boot >>>> and then try to use lunar to fix it (lin -c grub, lin -c linux-2.6) >>>> >>>> Auke >>>> _______________________________________________ >>>> Lunar mailing list >>>> Lunar at lunar-linux.org >>>> http://foo-projects.org/mailman/listinfo/lunar >>>> >>> >>> >>> >> >> _______________________________________________ >> Lunar mailing list >> Lunar at lunar-linux.org >> http://foo-projects.org/mailman/listinfo/lunar >> > > > > -- > Reasons why you may want to try GNU/Linux: > > http://www.getgnulinux.org/ > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > From sofar at foo-projects.org Tue Aug 12 20:38:24 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Tue, 12 Aug 2008 11:38:24 -0700 Subject: Grub broken. In-Reply-To: <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> Message-ID: <48A1D8A0.8030408@foo-projects.org> Chris Andrew wrote: > "This device apparently does not exist". > > Does anyone know why this has happened? I'm reluctant to do a long > install just to replicate the error. cat /proc/partitions ? From cjhandrew at gmail.com Tue Aug 12 21:59:18 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Tue, 12 Aug 2008 20:59:18 +0100 Subject: Grub broken. In-Reply-To: <48A1D8A0.8030408@foo-projects.org> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> <48A1D8A0.8030408@foo-projects.org> Message-ID: <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> Looks something like this: 3 0 19931184 hda 3 1 104391 hda1 (should be /boot) 3 2 19824210 hda2 (should be /) 3 64 4124736 hdb 3 65 987966 hdb1 (should be /home) 3 66 3132675 hdb2 (should be swap) Thanks, Chris. 2008/8/12 Kok, Auke : > Chris Andrew wrote: >> "This device apparently does not exist". >> >> Does anyone know why this has happened? I'm reluctant to do a long >> install just to replicate the error. > > cat /proc/partitions ? > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From samuel.verstraete at gmail.com Tue Aug 12 22:05:52 2008 From: samuel.verstraete at gmail.com (samuel) Date: Tue, 12 Aug 2008 22:05:52 +0200 Subject: Grub broken. In-Reply-To: <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> <48A1D8A0.8030408@foo-projects.org> <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> Message-ID: did you update theedge (which installed lunar-init) ? and then a reboot? On Tue, Aug 12, 2008 at 9:59 PM, Chris Andrew wrote: > Looks something like this: > > 3 0 19931184 hda > 3 1 104391 hda1 (should be /boot) > 3 2 19824210 hda2 (should be /) > 3 64 4124736 hdb > 3 65 987966 hdb1 (should be /home) > 3 66 3132675 hdb2 (should be swap) > > Thanks, > > Chris. > > > 2008/8/12 Kok, Auke : >> Chris Andrew wrote: >>> "This device apparently does not exist". >>> >>> Does anyone know why this has happened? I'm reluctant to do a long >>> install just to replicate the error. >> >> cat /proc/partitions ? >> _______________________________________________ >> Lunar mailing list >> Lunar at lunar-linux.org >> http://foo-projects.org/mailman/listinfo/lunar >> > > > > -- > Reasons why you may want to try GNU/Linux: > > http://www.getgnulinux.org/ > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > From sofar at foo-projects.org Tue Aug 12 22:16:57 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Tue, 12 Aug 2008 13:16:57 -0700 Subject: Grub broken. In-Reply-To: <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> <48A1D8A0.8030408@foo-projects.org> <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> Message-ID: <48A1EFB9.3040706@foo-projects.org> Chris Andrew wrote: > Looks something like this: > > 3 0 19931184 hda > 3 1 104391 hda1 (should be /boot) > 3 2 19824210 hda2 (should be /) > 3 64 4124736 hdb > 3 65 987966 hdb1 (should be /home) > 3 66 3132675 hdb2 (should be swap) > > Thanks, > > Chris. > > > 2008/8/12 Kok, Auke : >> Chris Andrew wrote: >>> "This device apparently does not exist". >>> >>> Does anyone know why this has happened? I'm reluctant to do a long >>> install just to replicate the error. >> cat /proc/partitions ? please, top-quote - I have totally lost my train of thought. you completely mess up the history this way, which is frankly making it unpleasant for me to help you. you said before that fsck.ext3 -n /dev/hda2 fails with "does not exist", which seems weird. Is /dev/ filled with device nodes and does /dev/hda2 in place? Auke From cjhandrew at gmail.com Tue Aug 12 22:25:26 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Tue, 12 Aug 2008 21:25:26 +0100 Subject: Grub broken. In-Reply-To: References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> <48A1D8A0.8030408@foo-projects.org> <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> Message-ID: <307203ff0808121325t448d9623h26f825e81d0a41c6@mail.gmail.com> Not sure about updating theedge. I think if the update is buggy enough for this to happen, I probably need to stick with a more stable distro. The Lunar community seems really helpful, and the distro looks promising. # Auke, thanks for your help. Sorry the output of cat /proc/partitions got confusing. Cheers, Chris. 2008/8/12 samuel : > did you update theedge (which installed lunar-init) ? and then a reboot? > > On Tue, Aug 12, 2008 at 9:59 PM, Chris Andrew wrote: >> Looks something like this: >> >> 3 0 19931184 hda >> 3 1 104391 hda1 (should be /boot) >> 3 2 19824210 hda2 (should be /) >> 3 64 4124736 hdb >> 3 65 987966 hdb1 (should be /home) >> 3 66 3132675 hdb2 (should be swap) >> >> Thanks, >> >> Chris. >> >> >> 2008/8/12 Kok, Auke : >>> Chris Andrew wrote: >>>> "This device apparently does not exist". >>>> >>>> Does anyone know why this has happened? I'm reluctant to do a long >>>> install just to replicate the error. >>> >>> cat /proc/partitions ? >>> _______________________________________________ >>> Lunar mailing list >>> Lunar at lunar-linux.org >>> http://foo-projects.org/mailman/listinfo/lunar >>> >> >> >> >> -- >> Reasons why you may want to try GNU/Linux: >> >> http://www.getgnulinux.org/ >> _______________________________________________ >> Lunar mailing list >> Lunar at lunar-linux.org >> http://foo-projects.org/mailman/listinfo/lunar >> > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From sofar at foo-projects.org Tue Aug 12 22:42:38 2008 From: sofar at foo-projects.org (Kok, Auke) Date: Tue, 12 Aug 2008 13:42:38 -0700 Subject: Grub broken. In-Reply-To: <307203ff0808121325t448d9623h26f825e81d0a41c6@mail.gmail.com> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <20080812112101.GA20027@phb> <307203ff0808120806j50a15f0eo7134d80222f6144f@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> <48A1D8A0.8030408@foo-projects.org> <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> <307203ff0808121325t448d9623h26f825e81d0a41c6@mail.gmail.com> Message-ID: <48A1F5BE.2090901@foo-projects.org> Chris Andrew wrote: > Not sure about updating theedge. > > I think if the update is buggy enough for this to happen, I probably > need to stick with a more stable distro. > > The Lunar community seems really helpful, and the distro looks promising. > > # Auke, thanks for your help. Sorry the output of cat > /proc/partitions got confusing. > > Cheers, > > Chris. > > 2008/8/12 samuel : >> did you update theedge (which installed lunar-init) ? and then a reboot? >> >> On Tue, Aug 12, 2008 at 9:59 PM, Chris Andrew wrote: >>> Looks something like this: >>> >>> 3 0 19931184 hda >>> 3 1 104391 hda1 (should be /boot) >>> 3 2 19824210 hda2 (should be /) >>> 3 64 4124736 hdb >>> 3 65 987966 hdb1 (should be /home) >>> 3 66 3132675 hdb2 (should be swap) >>> >>> Thanks, >>> >>> Chris. >>> >>> >>> 2008/8/12 Kok, Auke : >>>> Chris Andrew wrote: >>>>> "This device apparently does not exist". >>>>> >>>>> Does anyone know why this has happened? I'm reluctant to do a long >>>>> install just to replicate the error. >>>> cat /proc/partitions ? > PLEASE, stop and READ the following webpage first: http://en.wikipedia.org/wiki/Posting_style we prefer top-quoting aka bottom-posting or inline replying. I'm going to ignore top-posted comments from you from now on as they waste my time trying to figure out what the hell is relevant in your post to what you are replying to. Auke From cjhandrew at gmail.com Tue Aug 12 23:07:44 2008 From: cjhandrew at gmail.com (Chris Andrew) Date: Tue, 12 Aug 2008 22:07:44 +0100 Subject: Grub broken. In-Reply-To: <48A1F5BE.2090901@foo-projects.org> References: <307203ff0808120404y671d59fej143a2db35700086e@mail.gmail.com> <48A1BBD5.5060401@foo-projects.org> <307203ff0808121032n76d205d6s4a568f84ec51a165@mail.gmail.com> <48A1D548.9080603@foo-projects.org> <307203ff0808121131x6d53fcb5w2a4035b4504133d8@mail.gmail.com> <48A1D8A0.8030408@foo-projects.org> <307203ff0808121259k126755dema3b604958da4e2ee@mail.gmail.com> <307203ff0808121325t448d9623h26f825e81d0a41c6@mail.gmail.com> <48A1F5BE.2090901@foo-projects.org> Message-ID: <307203ff0808121407p53ccc5b8u776aa37bd4b265f1@mail.gmail.com> Thanks! 2008/8/12 Kok, Auke : > Chris Andrew wrote: >> Not sure about updating theedge. >> >> I think if the update is buggy enough for this to happen, I probably >> need to stick with a more stable distro. >> >> The Lunar community seems really helpful, and the distro looks promising. >> >> # Auke, thanks for your help. Sorry the output of cat >> /proc/partitions got confusing. >> >> Cheers, >> >> Chris. >> >> 2008/8/12 samuel : >>> did you update theedge (which installed lunar-init) ? and then a reboot? >>> >>> On Tue, Aug 12, 2008 at 9:59 PM, Chris Andrew wrote: >>>> Looks something like this: >>>> >>>> 3 0 19931184 hda >>>> 3 1 104391 hda1 (should be /boot) >>>> 3 2 19824210 hda2 (should be /) >>>> 3 64 4124736 hdb >>>> 3 65 987966 hdb1 (should be /home) >>>> 3 66 3132675 hdb2 (should be swap) >>>> >>>> Thanks, >>>> >>>> Chris. >>>> >>>> >>>> 2008/8/12 Kok, Auke : >>>>> Chris Andrew wrote: >>>>>> "This device apparently does not exist". >>>>>> >>>>>> Does anyone know why this has happened? I'm reluctant to do a long >>>>>> install just to replicate the error. >>>>> cat /proc/partitions ? >> > > PLEASE, stop and READ the following webpage first: > > http://en.wikipedia.org/wiki/Posting_style > > we prefer top-quoting aka bottom-posting or inline replying. > > I'm going to ignore top-posted comments from you from now on as they waste my time > trying to figure out what the hell is relevant in your post to what you are > replying to. > > Auke > > > _______________________________________________ > Lunar mailing list > Lunar at lunar-linux.org > http://foo-projects.org/mailman/listinfo/lunar > -- Reasons why you may want to try GNU/Linux: http://www.getgnulinux.org/ From maintainer at lunar-linux.org Fri Aug 15 12:35:33 2008 From: maintainer at lunar-linux.org (maintainer@lunar-linux.org) Date: Fri, 15 Aug 2008 12:35:33 +0200 (CEST) Subject: weekly news - 20080815 Message-ID: <20080815103533.CE60AF29F2@doppio.foo-projects.org> Hi! Here's the latest weekly news edition! ===================================================================== ===================================================================== New modules: (13) guidance-power-manager-4.1.0: A frontend to HAL's power features for KDE kde-l10n-ku-4.1.0: contains translated KDE messages kde-l10n-lt-4.1.0: contains translated KDE messages kde-l10n-ml-4.1.0: contains translated KDE messages kde-l10n-sr-4.1.0: contains translated KDE messages kde-l10n-ta-4.1.0: contains translated KDE messages kdepim4-4.1.0: libraries central to KDE PIM application kdeplasma4-addons-4.1.0: mandatory package for KDE konq-plugins-4.1.0: additional plugins for konqueror file manager and web browser kopete-cryptography-4.1.0: send and recieve encrypted and/or signed messages phonon-4.2.0: skanlite-4.1.0: simple image scanning application valknut-qt3-0.3.19: Direct Connect (DC++) client for Qt Removed modules: (13) extragear-plasma kaider kbudget kde-l10n-ar kde-l10n-be kde-l10n-eu kde-l10n-fa kde-l10n-is kde-l10n-ne kde-l10n-se knetmap ksubeditor showimg New versions: (124) DirectFB : 1.0.1 -> 1.2.1 airconfig-svn : svn-31 -> svn-32 akonadi : svn-31 -> 1.0.0 amarok : 1.4.9.1 -> 1.4.10 amarok4 : 1.80 -> 1.83 amsn : 0.97RC1 -> 0.97.1 angband : 3.0.6 -> 3.0.9b aria2 : 0.13.1+1 -> 0.15.1+2 automoc : svn-31 -> svn-32 svn-32 bluez-libs : 3.35 -> 3.36 bluez-utils : 3.35 -> 3.36 dclib : 0.3.13 -> 0.3.19 dirmngr : 1.0.1 -> 1.0.2 eet : 0.9.9 -> 1.0.0 elfutils : 0.127 -> 0.135 enlightenment : 0.16.8.13 -> 0.16.8.14 flash-plugin-10 : 070208 -> 081108 freeciv : 2.1.5 -> 2.1.6 freetds : 0.64 -> 0.82 ghal-svn : svn-31 -> svn-32 gitosis-git : git-31 -> git-32 hylafax : 5.2.6 -> 5.2.7 imlib2 : 1.4.0 -> 1.4.1 kcoloredit : 4.0.3 -> 4.1.0 kde-l10n-bg : 4.0.4 -> 4.1.0 kde-l10n-ca : 4.0.4 -> 4.1.0 kde-l10n-cs : 4.0.4 -> 4.1.0 kde-l10n-csb : 4.0.4 -> 4.1.0 kde-l10n-da : 4.0.4 -> 4.1.0 kde-l10n-de : 4.0.4 -> 4.1.0 kde-l10n-e0 : 4.0.4 -> 4.1.0 kde-l10n-el : 4.0.4 -> 4.1.0 kde-l10n-en_GB : 4.0.4 -> 4.1.0 kde-l10n-es : 4.0.4 -> 4.1.0 kde-l10n-et : 4.0.4 -> 4.1.0 kde-l10n-fi : 4.0.4 -> 4.1.0 kde-l10n-fr : 4.0.4 -> 4.1.0 kde-l10n-fy : 4.0.4 -> 4.1.0 kde-l10n-ga : 4.0.4 -> 4.1.0 kde-l10n-gl : 4.0.4 -> 4.1.0 kde-l10n-hi : 4.0.4 -> 4.1.0 kde-l10n-hu : 4.0.4 -> 4.1.0 kde-l10n-it : 4.0.4 -> 4.1.0 kde-l10n-ja : 4.0.4 -> 4.1.0 kde-l10n-kk : 4.0.4 -> 4.1.0 kde-l10n-km : 4.0.4 -> 4.1.0 kde-l10n-ko : 4.0.4 -> 4.1.0 kde-l10n-lv : 4.0.4 -> 4.1.0 kde-l10n-mk : 4.0.4 -> 4.1.0 kde-l10n-nb : 4.0.4 -> 4.1. kde-l10n-nds : 4.0.4 -> 4.1.0 kde-l10n-nl : 4.0.4 -> 4.1.0 kde-l10n-nn : 4.0.4 -> 4.1.0 kde-l10n-pa : 4.0.4 -> 4.1.0 kde-l10n-pl : 4.0.4 -> 4.1.0 kde-l10n-pt : 4.0.4 -> 4.1.0 kde-l10n-pt_BR : 4.0.4 -> 4.1.0 kde-l10n-ru : 4.0.4 -> 4.1.0 kde-l10n-sl : 4.0.4 -> 4.1.0 kde-l10n-sv : 4.0.4 -> 4.1.0 kde-l10n-th : 4.0.4 -> 4.1.0 kde-l10n-tr : 4.0.4 -> 4.1.0 kde-l10n-uk : 4.0.4 -> 4.1.0 kde-l10n-wa : 4.0.4 -> 4.1.0 kde-l10n-zh_CN : 4.0.4 -> 4.1.0 kde-l10n-zh_TW : 4.0.4 -> 4.1.0 kde4 : 4.0.5 -> 4.1.0 kdeaccessibility4 : 4.0.5 -> 4.1.0 kdeadmin4 : 4.0.5 -> 4.1.0 kdeartwork4 : 4.0.5 -> 4.1.0 kdebase4 : 4.0.5 -> 4.1.0 kdebase4-runtime : 4.0.5 -> 4.1.0 kdebase4-workspace : 4.0.5 -> 4.1.0 kdebindings4 : 4.0.5 -> 4.1.0 kdeedu4 : 4.0.5 -> 4.1.0 kdegames4 : 4.0.5 -> 4.1.0 kdegraphics4 : 4.0.5 -> 4.1.0 kdelibs4 : 4.0.5 -> 4.1.0 kdemultimedia4 : 4.0.5 -> 4.1.0 kdenetwork4 : 4.0.5 -> 4.1.0 kdepimlibs4 : 4.0.5 -> 4.1.0 kdesdk4 : 4.0.5 -> 4.1.0 kdesvn : 0.14.6 -> 1.0.0 kdetoys4 : 4.0.5 -> 4.1.0 kdeutils4 : 4.0.5 -> 4.1.0 kdewebdev4 : 4.0.5 -> 4.1.0 kfax : 4.0.3 -> 4.1.0 kgrab : 4.0.3 -> 4.1.0 kgraphviewer : 4.0.3 -> 4.1.0 kiconedit : 4.0.3 -> 4.1.0 kio_gopher : 4.0.3 -> 4.1.0 kmldonkey4 : 4.0.3 -> 4.1.0 kover : 2.9.6 -> 3 kpovmodeler : 4.0.3 -> 4.1.0 ksubtile : 1.2 -> 1.3 man-pages : 3.06 -> 3.07 motion : 3.2.9 -> 3.2.10.1 mpeg2dec : 0.4.1 -> 0.5.1 mysql : 5.0.51b -> 5.0.67 ncftp : 3.2.1 -> 3.2.2 nss : 3.11.7 -> 3.12 openvrml : 0.17.6 -> 0.17.7 php : 4.4.8 -> 4.4.9 php5-suhosin : 5.2.3-0.9.20 -> 5.2.6-0.9.25 poppler : 0.8.4 -> 0.8.5 postfix : 2.5.3 -> 2.5.4 rpm : 5.1.1 -> 5.1.4 rpm-old : 4.4.2.2 -> 4.4.2.3 rsyslog : 3.18.1 -> 3.18.2 setuptools : 0.6c7 -> 0.6c8 spcaview : 20061208 -> 20071224 timezone-data : 2008b -> 2008e transmission : 1.31 -> 1.32 usermin : 1.350 -> 1.360 valknut : 0.3.13 -> 0.4.5 vim : 7.1 -> 7.2 virtualbox : 1.6.2 -> 1.6.4 webkitkde : svn-31 -> svn-32 webmin : 1.420 -> 1.430 xawtv-fonts : 1.0 -> 1.1 xf86-input-evdev : 2.0.2 -> 2.0.3 xine-lib : 1.1.14 -> 1.1.15 xine-plugin : 1.0.1 -> 1.0.2 xscreensaver : 5.06 -> 5.07 Moved modules: akonadi : zbeta -> kde4/utils automoc : zbeta -> kde4/utils zbeta koffice4 : kde4/base -> kde4/apps valknut : qt-apps -> qt4-apps webkitkde : zbeta -> kde4/apps ===================================================================== The Lunar-Linux team From zbiggy at o2.pl Sat Aug 16 14:14:05 2008 From: zbiggy at o2.pl (Zbigniew Luszpinski) Date: Sat, 16 Aug 2008 14:14:05 +0200 Subject: Error: org.freedesktop.hal.storage.mount-removable no <-- (action, result) [Resolved] Message-ID: <200808161414.05985.zbiggy@o2.pl> Hello, if you use kde3 (or other DM) in Lunar and insert pendrive or any other hot plugable device the kde will show you option to mount it. If an user will agree to mount it the error will appear: "org.freedesktop.hal.storage.mount-removable no <-- (action, result)" There is easy fix for this error. Just define security rules in /etc/PolicyKit/PolicyKit.conf like these: First rule allows automounting pendrives, the second one is for fixed disks like hard drives. have a nice day, Zbigniew 'zbiggy' Luszpinski From maintainer at lunar-linux.org Fri Aug 22 12:35:32 2008 From: maintainer at lunar-linux.org (maintainer@lunar-linux.org) Date: Fri, 22 Aug 2008 12:35:32 +0200 (CEST) Subject: weekly news - 20080822 Message-ID: <20080822103532.CB2DBF29F2@doppio.foo-projects.org> Hi! Here's the latest weekly news edition! ===================================================================== ===================================================================== New modules: (4) camstream-0.27: collection of tools for webcams and other video-devices cheese-2.22.3: webcam picture taker kdebluetooth4-0.1: KDE4 bluetooth GUI xf86-input-synaptics-0.15.0: A Synaptics touchpad driver Removed modules: (1) espgs New versions: (32) ImageMagick : 6.4.0-11 -> 6.4.2-10 NVIDIA-beta : 177.13 -> 177.67 PolicyKit : 0.8 -> 0.9 airconfig-svn : svn-32 -> svn-33 alsa-lib : 1.0.17 -> 1.0.17a amsn : 0.97.1 -> 0.97.2 automoc : svn-32 svn-32 -> svn-33 svn-33 claws_pdf_viewer : 0.6 -> 0.9.1 dbus : 1.2.1 -> 1.2.3 dcraw : 8.86 -> 8.87 gambas2 : 2.7.0 -> 2.8.1 ghal-svn : svn-32 -> svn-33 gitosis-git : git-32 -> git-33 gtkpod : 0.99.10 -> 0.99.12 hunspell : 1.2.4 -> 1.2.7 kipi-plugins : 0.1.4 -> 0.1.5 libgpod : 0.5.2 -> 0.6.0 libkexiv2 : 0.1.6 -> 0.1.7 libkipi : 0.1.5 -> 0.1.6 libspectre : 0.2.0 -> 0.2.1 linux-2.6 : 2.6.26.2 -> 2.6.26.3 ntfs-3g : 1.2712 -> 1.2812 ntop : 3.2 -> 3.3.7 ntp : 4.2.4p4 -> 4.2.4p5 opera : 9.51 -> 9.52 opera-static : 9.51 -> 9.52 pidgin : 2.4.3 -> 2.5.0 samba : 3.2.1 -> 3.2.2 tcl : 8.5.3 -> 8.5.4 tk : 8.5.3 -> 8.5.4 webkitkde : svn-32 -> svn-33 ===================================================================== The Lunar-Linux team From maintainer at lunar-linux.org Fri Aug 29 12:35:29 2008 From: maintainer at lunar-linux.org (maintainer@lunar-linux.org) Date: Fri, 29 Aug 2008 12:35:29 +0200 (CEST) Subject: weekly news - 20080829 Message-ID: <20080829103529.B51A99B1BD@doppio.foo-projects.org> Hi! Here's the latest weekly news edition! ===================================================================== ===================================================================== New versions: (6) airconfig-svn : svn-33 -> svn-34 automoc : svn-33 svn-33 -> svn-34 svn-34 ghal-svn : svn-33 -> svn-34 gitosis-git : git-33 -> git-34 webkitkde : svn-33 -> svn-34 ===================================================================== The Lunar-Linux team