Re: [gobolinux-devel] Upgrading Glibc
2007/3/6, Lucas C. Villa Real <[EMAIL PROTECTED]>: > On 3/5/07, Michael Homer <[EMAIL PROTECTED]> wrote: > > > Were you running an updated version of Scripts? The current version > > > should handle Glibc installation fine. > > michael@ ~]ls -l /Programs/Scripts/Current > > lrwxrwxrwx 1 gobo gobo 5 Mar 1 22:35 /Programs/Scripts/Current -> 2.6.2 > > I can't find a newer version in the repository, at least. Also: > > michael@ ~]uname -r > > 2.6.17.11-Gobo > > michael@ ~]ls -l /Programs/Glibc/Current > > lrwxrwxrwx 1 gobo gobo 3 Mar 5 22:23 /Programs/Glibc/Current -> 2.4 > > > > Everything other than Scripts, BootScripts, Firefox, and Freshen is > > the out-of-the-box version from 013. The InstallPackage command was > > `InstallPackage -b -D -u keep Glibc 2.5`; would a different version be > > better? > > It shouldn't make difference. Detsch tested the upgrade on a 2.3 > system moving to a 2.4. I have never tried myself to upgrade Glibc. > Can anyone take a look into this? Maybe by running gobo inside qemu or > other emulator.. I don't have the time to test that right now, > unfortunately. > I've upgraded Glibc somewhat succesfully. It did symlink fine and the system did not crash. However some applications, like Xorg, have problems since the upgrade, but I cannot seem to ppin down if that's because some lib it's using is compiled against the old version of Glibc or if the error's somewhere else. Not without recompiling the complete dependency chain of Xorg and Window Maker. -- /Jonas ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > It shouldn't make difference. Detsch tested the upgrade on a 2.3 > system moving to a 2.4. I have never tried myself to upgrade Glibc. > Can anyone take a look into this? Maybe by running gobo inside qemu or > other emulator.. I don't have the time to test that right now, > unfortunately. > I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage Scripts and Compile. Compile DHCPCD (we need a new bin package). InstallPackage Glibc. D/L and sig check fine. During SyminkProgram, fine until ldconfig, then get "FATAL: kernel too old" error messages. Now nothing works. On reboot, init dies with "FATAL: kernel too old". I'll upgrade kernels and check again. -- Carlo J. Calica ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > > > It shouldn't make difference. Detsch tested the upgrade on a 2.3 > > system moving to a 2.4. I have never tried myself to upgrade Glibc. > > Can anyone take a look into this? Maybe by running gobo inside qemu or > > other emulator.. I don't have the time to test that right now, > > unfortunately. > > > > I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage > Scripts and Compile. Compile DHCPCD (we need a new bin package). > InstallPackage Glibc. D/L and sig check fine. During SyminkProgram, > fine until ldconfig, then get "FATAL: kernel too old" error messages. > Now nothing works. On reboot, init dies with "FATAL: kernel too old". > I'll upgrade kernels and check again. That's exactly what happened for me. For the record, for anybody else who runs into this problem, here's how I fixed it: 1) Boot into another distro - I used Gentoo, but it shouldn't matter what. Mount the Gobo partition on /mnt/gobo. 2) cd /mnt/gobo/Programs/Glibc 3) rm -r 2.5 4) rm Current 5) ln -s 2.4 Current 6) cd /mnt/gobo/System/Links/Libraries 7) ln -sf ../../Programs/Glibc/2.4/lib/* . 8) cd ../Executables 9) ln -sf ../../Programs/Glibc/2.4/bin/* . 10) rm -f /mnt/gobo/System/Settings/ld.so.conf (it's a symlink) 11) echo /System/Links/Libraries > /mnt/gobo/System/Settings/ld.so.conf 12) ldconfig -r /mnt/gobo -f /System/Settings/ld.so.conf -C /System/Settings/ld.so.cache 13) cp /mnt/gobo/System/Settings/ld.so.cache /mnt/gobo/Programs/Glibc/Settings 14) chroot /mnt/gobo (this should work _at this point, and no sooner_) 15) SymlinkProgram Glibc 2.4 16) Reboot into Gobo All those commands need to be run as root - under sudo is fine. It's also possible that some of those commands aren't actually necessary, I didn't perform rigorous elimination testing on them. It might be worthwhile making up a statically-linked binary to perform those steps in an emergency and including it in Scripts, if there's no way to avoid it. -Michael ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
2007/3/6, Michael Homer <[EMAIL PROTECTED]>: > On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > > > > > It shouldn't make difference. Detsch tested the upgrade on a 2.3 > > > system moving to a 2.4. I have never tried myself to upgrade Glibc. > > > Can anyone take a look into this? Maybe by running gobo inside qemu or > > > other emulator.. I don't have the time to test that right now, > > > unfortunately. > > > > > > > I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage > > Scripts and Compile. Compile DHCPCD (we need a new bin package). > > InstallPackage Glibc. D/L and sig check fine. During SyminkProgram, > > fine until ldconfig, then get "FATAL: kernel too old" error messages. > > Now nothing works. On reboot, init dies with "FATAL: kernel too old". > > I'll upgrade kernels and check again. > That's exactly what happened for me. For the record, for anybody else > who runs into this problem, here's how I fixed it: > 1) Boot into another distro - I used Gentoo, but it shouldn't matter > what. Mount the Gobo partition on /mnt/gobo. > 2) cd /mnt/gobo/Programs/Glibc > 3) rm -r 2.5 > 4) rm Current > 5) ln -s 2.4 Current > 6) cd /mnt/gobo/System/Links/Libraries > 7) ln -sf ../../Programs/Glibc/2.4/lib/* . > 8) cd ../Executables > 9) ln -sf ../../Programs/Glibc/2.4/bin/* . > 10) rm -f /mnt/gobo/System/Settings/ld.so.conf (it's a symlink) > 11) echo /System/Links/Libraries > /mnt/gobo/System/Settings/ld.so.conf > 12) ldconfig -r /mnt/gobo -f /System/Settings/ld.so.conf -C > /System/Settings/ld.so.cache > 13) cp /mnt/gobo/System/Settings/ld.so.cache /mnt/gobo/Programs/Glibc/Settings > 14) chroot /mnt/gobo (this should work _at this point, and no sooner_) > 15) SymlinkProgram Glibc 2.4 > 16) Reboot into Gobo > All those commands need to be run as root - under sudo is fine. It's > also possible that some of those commands aren't actually necessary, I > didn't perform rigorous elimination testing on them. It might be > worthwhile making up a statically-linked binary to perform those steps > in an emergency and including it in Scripts, if there's no way to > avoid it. > -Michael Steps 2-9 can be skipped by using RescueSymlinkprogram, which is a static binary included in Scripts, instead. That should probably also take care of reseting your ld.* files as well. And you can use the GoboLinux install CD (one does most probably have one lying around). -- /Jonas ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > 2007/3/6, Michael Homer <[EMAIL PROTECTED]>: > > On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > > On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > > > > > > > It shouldn't make difference. Detsch tested the upgrade on a 2.3 > > > > system moving to a 2.4. I have never tried myself to upgrade Glibc. > > > > Can anyone take a look into this? Maybe by running gobo inside qemu or > > > > other emulator.. I don't have the time to test that right now, > > > > unfortunately. > > > > > > > > > > I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage > > > Scripts and Compile. Compile DHCPCD (we need a new bin package). > > > InstallPackage Glibc. D/L and sig check fine. During SyminkProgram, > > > fine until ldconfig, then get "FATAL: kernel too old" error messages. > > > Now nothing works. On reboot, init dies with "FATAL: kernel too old". > > > I'll upgrade kernels and check again. > > That's exactly what happened for me. For the record, for anybody else > > who runs into this problem, here's how I fixed it: > > 1) Boot into another distro - I used Gentoo, but it shouldn't matter > > what. Mount the Gobo partition on /mnt/gobo. > > 2) cd /mnt/gobo/Programs/Glibc > > 3) rm -r 2.5 > > 4) rm Current > > 5) ln -s 2.4 Current > > 6) cd /mnt/gobo/System/Links/Libraries > > 7) ln -sf ../../Programs/Glibc/2.4/lib/* . > > 8) cd ../Executables > > 9) ln -sf ../../Programs/Glibc/2.4/bin/* . > > 10) rm -f /mnt/gobo/System/Settings/ld.so.conf (it's a symlink) > > 11) echo /System/Links/Libraries > /mnt/gobo/System/Settings/ld.so.conf > > 12) ldconfig -r /mnt/gobo -f /System/Settings/ld.so.conf -C > > /System/Settings/ld.so.cache > > 13) cp /mnt/gobo/System/Settings/ld.so.cache > > /mnt/gobo/Programs/Glibc/Settings > > 14) chroot /mnt/gobo (this should work _at this point, and no sooner_) > > 15) SymlinkProgram Glibc 2.4 > > 16) Reboot into Gobo > > All those commands need to be run as root - under sudo is fine. It's > > also possible that some of those commands aren't actually necessary, I > > didn't perform rigorous elimination testing on them. It might be > > worthwhile making up a statically-linked binary to perform those steps > > in an emergency and including it in Scripts, if there's no way to > > avoid it. > > -Michael > Steps 2-9 can be skipped by using RescueSymlinkprogram, which is a > static binary included in Scripts, instead. That should probably also > take care of reseting your ld.* files as well. I tried it; it didn't actually seem to do anything. At least, running it didn't make things work, and the Current symlink still pointed to 2.5 when I examined it from Gentoo. I also don't think it would have been able to run ldconfig - it was one of the binaries that didn't work. That's why I had to use the Gentoo one with the -r /mnt/gobo (change to and use new root directory) option. Actually, I guess that same problem with ldconfig would scupper making a "RescueGlibc" binary. I don't know what's involved in generating ld.so.cache, but I doubt it's simple. > And you can use the GoboLinux install CD (one does most probably have > one lying around). Yeah, a live CD should be fine. I couldn't use the Gobo one because of the dodgy CD drive I mentioned before, possibly combined with some bug on the CD (Ubuntu CDs work fine, but the Gobo one will die at random at one of several points before the prompt appears). For anybody else, though, a Gobo CD could even be better - you might be able to use the SymlinkProgram on the CD by changing the $goboRoot variable, which would avoid the manual linking in the middle. -Michael ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> >
> > It shouldn't make difference. Detsch tested the upgrade on a 2.3
> > system moving to a 2.4. I have never tried myself to upgrade Glibc.
> > Can anyone take a look into this? Maybe by running gobo inside qemu or
> > other emulator.. I don't have the time to test that right now,
> > unfortunately.
> >
>
> I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage
> Scripts and Compile. Compile DHCPCD (we need a new bin package).
> InstallPackage Glibc. D/L and sig check fine. During SyminkProgram,
> fine until ldconfig, then get "FATAL: kernel too old" error messages.
> Now nothing works. On reboot, init dies with "FATAL: kernel too old".
> I'll upgrade kernels and check again.
I think this can have something to do with glibc's --with-kernel
parameter. We used a very recent release, so this can be a problem.
Should be the case of adding Linux 2.6.x to Glibc's dependencies and
then creating a Linux package that presents
/System/Kernel/{Boot,Modules} + /Files/Compile/Sources/linux-2.6.x
(sanitized) inside Unmanaged? Seems to be a better way to handle the
kernel package and fix the Glibc issue, right?
--
Lucas
powered by /dev/dsp
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
2007/3/6, Lucas C. Villa Real <[EMAIL PROTECTED]>:
> On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> > On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> > >
> > > It shouldn't make difference. Detsch tested the upgrade on a 2.3
> > > system moving to a 2.4. I have never tried myself to upgrade Glibc.
> > > Can anyone take a look into this? Maybe by running gobo inside qemu or
> > > other emulator.. I don't have the time to test that right now,
> > > unfortunately.
> > >
> >
> > I tested a Glibc upgrade in qemu. Fresh 013 install. InstallPackage
> > Scripts and Compile. Compile DHCPCD (we need a new bin package).
> > InstallPackage Glibc. D/L and sig check fine. During SyminkProgram,
> > fine until ldconfig, then get "FATAL: kernel too old" error messages.
> > Now nothing works. On reboot, init dies with "FATAL: kernel too old".
> > I'll upgrade kernels and check again.
>
> I think this can have something to do with glibc's --with-kernel
> parameter. We used a very recent release, so this can be a problem.
> Should be the case of adding Linux 2.6.x to Glibc's dependencies and
> then creating a Linux package that presents
> /System/Kernel/{Boot,Modules} + /Files/Compile/Sources/linux-2.6.x
> (sanitized) inside Unmanaged? Seems to be a better way to handle the
> kernel package and fix the Glibc issue, right?
>
I have thought about this but I don't like the idea of having
everything for the kernel doubled, once in /Programs/Linux and the
other at the "correct" places. I'm still trying to find a good way for
this.
And I still think that the image and the source should be in separate
packages anyway.
--
/Jonas
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> 2007/3/6, Lucas C. Villa Real <[EMAIL PROTECTED]>:
> >
> > I think this can have something to do with glibc's --with-kernel
> > parameter. We used a very recent release, so this can be a problem.
> > Should be the case of adding Linux 2.6.x to Glibc's dependencies and
> > then creating a Linux package that presents
> > /System/Kernel/{Boot,Modules} + /Files/Compile/Sources/linux-2.6.x
> > (sanitized) inside Unmanaged? Seems to be a better way to handle the
> > kernel package and fix the Glibc issue, right?
> >
With a 2.6.20 kernel everything is fine. It was actually VERY smooth.
Nice job.
> I have thought about this but I don't like the idea of having
> everything for the kernel doubled, once in /Programs/Linux and the
> other at the "correct" places. I'm still trying to find a good way for
> this.
>
> And I still think that the image and the source should be in separate
> packages anyway.
>
Disk space is cheap. I guess we could have a config file somewhere to
prune Unmanaged. It would we worthwhile for packages other than the
kernel if the user really cares. Kernel sources as a sep package
makes sense but should be included on the ISO. Should also be in the
Typical profile as well. This is linux and compiling out of tree
kernel modules isn't that odd.
--
Carlo J. Calica
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > With a 2.6.20 kernel everything is fine. It was actually VERY smooth. > Nice job. Ah, good to know it worked! > Disk space is cheap. I guess we could have a config file somewhere to > prune Unmanaged. It would we worthwhile for packages other than the > kernel if the user really cares. Kernel sources as a sep package > makes sense but should be included on the ISO. Should also be in the > Typical profile as well. This is linux and compiling out of tree > kernel modules isn't that odd. Can't we 'rm -rf Unmanaged' on PostInstall? -- Lucas powered by /dev/dsp ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > With a 2.6.20 kernel everything is fine. It was actually VERY smooth. > > Nice job. > > Ah, good to know it worked! > > > Disk space is cheap. I guess we could have a config file somewhere to > > prune Unmanaged. It would we worthwhile for packages other than the > > kernel if the user really cares. Kernel sources as a sep package > > makes sense but should be included on the ISO. Should also be in the > > Typical profile as well. This is linux and compiling out of tree > > kernel modules isn't that odd. > > Can't we 'rm -rf Unmanaged' on PostInstall? On the Linux package, I mean. -- Lucas powered by /dev/dsp ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> On 3/6/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote:
> > 2007/3/6, Lucas C. Villa Real <[EMAIL PROTECTED]>:
> > >
> > > I think this can have something to do with glibc's --with-kernel
> > > parameter. We used a very recent release, so this can be a problem.
> > > Should be the case of adding Linux 2.6.x to Glibc's dependencies and
> > > then creating a Linux package that presents
> > > /System/Kernel/{Boot,Modules} + /Files/Compile/Sources/linux-2.6.x
> > > (sanitized) inside Unmanaged? Seems to be a better way to handle the
> > > kernel package and fix the Glibc issue, right?
> > >
>
> With a 2.6.20 kernel everything is fine. It was actually VERY smooth.
> Nice job.
I will upgrade that now and make sure it also works within Freshen.
I'll also special-case installing glibc to check `uname -r` first
temporarily until there's a permanent solution sorted out. Ideally,
there'd be something like /Programs/Linux/2.6.20 for consistency,
although it could be empty after that or a symlink.
It occurred to me after sending my last message that the reason
RescueSymlinkProgram didn't work is that it had no way to elevate its
own permissions. Sudo was non-functioning, and I didn't have a root
terminal open at the time, so there was no way I could make it work.
RSP should at least check its effective UID and error out if it
doesn't have the permissions, or better, be setuid. That is a minor
security risk though. I have chmodded +s my copy.
-Michael
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] [gobolinux-users] configuration internet access
BTW, regarding wifi support at boot... Would it be possible to have it try wired ethernet first and wifi if it succeeds? Also, it would be lovely if it choosed the "best" essid (fastest, highest signal strength, and open), or prefer specific ones if the user has specified some in an array? As I have it now on my laptop, I always do these things manually since I use wired eth to my LAN and wifi when away. It would be cool if it "just worked". =) -- /Jonatan-=( http://kymatica.com )=- ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
Jonas Karlsson wrote:
> 2007/3/6, Lucas C. Villa Real <[EMAIL PROTECTED]>:
>> On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
>>> On 3/5/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
It shouldn't make difference. Detsch tested the upgrade on a
2.3 system moving to a 2.4. I have never tried myself to
upgrade Glibc. Can anyone take a look into this? Maybe by
running gobo inside qemu or other emulator.. I don't have the
time to test that right now, unfortunately.
>>> I tested a Glibc upgrade in qemu. Fresh 013 install.
>>> InstallPackage Scripts and Compile. Compile DHCPCD (we need a
>>> new bin package). InstallPackage Glibc. D/L and sig check fine.
>>> During SyminkProgram, fine until ldconfig, then get "FATAL:
>>> kernel too old" error messages. Now nothing works. On reboot,
>>> init dies with "FATAL: kernel too old". I'll upgrade kernels and
>>> check again.
>> I think this can have something to do with glibc's --with-kernel
>> parameter. We used a very recent release, so this can be a problem.
>> Should be the case of adding Linux 2.6.x to Glibc's dependencies
>> and then creating a Linux package that presents
>> /System/Kernel/{Boot,Modules} + /Files/Compile/Sources/linux-2.6.x
>> (sanitized) inside Unmanaged? Seems to be a better way to handle
>> the kernel package and fix the Glibc issue, right?
>>
> I have thought about this but I don't like the idea of having
> everything for the kernel doubled, once in /Programs/Linux and the
> other at the "correct" places. I'm still trying to find a good way
> for this.
Are you referring to /Programs/Linux-Headers? As I understand it, that's
only the kernel headers for which the current libc is compiled against,
and not the headers corresponding to the actually installed kernel. So,
we need both.
> And I still think that the image and the source should be in separate
> packages anyway.
I think the source in lucas Linux package is a minimized one, only
useful to compile modules against. I think this is very nice if one
doesn't want to download the whole kernel source.
--
/Jonatan-=( http://kymatica.com )=-
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > Are you referring to /Programs/Linux-Headers? As I understand it, that's > only the kernel headers for which the current libc is compiled against, > and not the headers corresponding to the actually installed kernel. So, > we need both. Is Linux-Libc-Headers obsolete? Deprecated? http://gobo.dreamhosters.com/recipes/?name=headers&search=Recipes Glibc does appear to depend on Linux-Headers and not Linux-Libc-Headers http://gobo.dreamhosters.com/recipes/?list=Glibc&ver=2.5-r3&file=Resources/Dependencies -mpb ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > On 3/6/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > On 3/6/07, Carlo Calica <[EMAIL PROTECTED]> wrote: > > > > > Disk space is cheap. I guess we could have a config file somewhere to > > > prune Unmanaged. It would we worthwhile for packages other than the > > > kernel if the user really cares. Kernel sources as a sep package > > > makes sense but should be included on the ISO. Should also be in the > > > Typical profile as well. This is linux and compiling out of tree > > > kernel modules isn't that odd. > > > > Can't we 'rm -rf Unmanaged' on PostInstall? > > On the Linux package, I mean. > I don't see why the Linux package would be a special case vs other packages with Unmanaged. I guess size. My modules dir is 40 megs. The kernel is probably 2-3 more. -- Carlo J. Calica ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
[gobolinux-devel] New Freshen
Hi, I've finished a pre-release new version of Freshen, that's had all the features updated so that they actually work as expected. As well as that, there are a couple of new features: - upgrade-system actually works now, and pretty much flawlessly. I've just used it to update mine. - Included in the above, the lists of updates are now in properly sorted dependency order (using the tsort topographic sort library from Ruby's standard library). It uses the recipe dependency files for preference, followed by the /packages/official/dependencies/* files in the package repositories. It seems to be reasonably accurate. The Glibc upgrade problems are cleared up by upgrading the kernel; I've added an explicit special case that checks `uname -r` and removes Glibc from the list if it isn't >=2.6.20. I'm posting this here rather than on -users because I'd like to have it go through a little bit of real-world testing, particularly the upgrade-system feature. I suggest limiting the number of programs it will update and making sure things are still as they should be after - the -l command-line option deals with this. I also have a couple of wishlist items for Compile and InstallPackage. It would be nice if there were a command line option to skip the UpdateSettings stage so that it could be batched at the end of a run. The other is that one of the ruby libraries it provides needs a small update to work with current configuration files. I've patched around it in Freshen by making it load its own libraries first and including an updated version of parseconfig.rb with a one-line change (line 28). This should go into the base Compile. I've uncovered a problem or two with some packages in the process. Qt 3.3.7 isn't properly signed, and verification fails with errors about ( characters in a couple of filenames. I believe the same thing happened on at least one other package, but I'll have to pass that along when I run into it again. I have attached the package because I can't get FTP out while some part of the system is in the process of upgrading itself. It's only 10kb, so I hope people won't mind. -Michael Freshen--2.0.9--i686.tar.bz2 Description: BZip2 compressed data ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] Upgrading Glibc
On 3/6/07, mpb <[EMAIL PROTECTED]> wrote: > On 3/6/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote: > > > Are you referring to /Programs/Linux-Headers? As I understand it, that's > > only the kernel headers for which the current libc is compiled against, > > and not the headers corresponding to the actually installed kernel. So, > > we need both. > > Is Linux-Libc-Headers obsolete? Deprecated? It's deprecated. It was another project which was discontinued. The new headers are now processed directly in the kernel with the Makefile target 'headers-install'. The new recipe is called Linux-Headers. > http://gobo.dreamhosters.com/recipes/?name=headers&search=Recipes > > Glibc does appear to depend on Linux-Headers and not Linux-Libc-Headers > > http://gobo.dreamhosters.com/recipes/?list=Glibc&ver=2.5-r3&file=Resources/Dependencies I'm removing Linux-Libc-Headers from the repository. Thanks. -- Lucas powered by /dev/dsp ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
Re: [gobolinux-devel] [gobolinux-commits] tools/ChrootCompile/bin ChrootCompile
On 3/6/07, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > CVSROOT:/sources/goboscripts > Module name:tools > Changes by: Jonas Karlsson 07/03/07 01:25:48 > > Modified files: > ChrootCompile/bin: ChrootCompile > > Log message: > Fixing that dependencies from recipe are respected and comments > allowed Good catch, thanks. -- Lucas powered by /dev/dsp ___ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
