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
