On 2/4/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> On 2/5/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> > On 2/4/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> > > Hello all,
> > >
> > > Everything is fine, until the installer tries to perform some
> > > operation with symlinks, such
On 2/4/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> On 2/5/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> > Wireless-Tools makes sense. I'm thinking it should be called
> > WirelessConfig. It'll only deal with iwconfig settings. Everything
> > else (ifconfig, dhcpcd) should be handled by
On 2/5/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> On 2/4/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> > Hello all,
> >
> > Everything is fine, until the installer tries to perform some
> > operation with symlinks, such as 'ln -s libc.so.6 libc.so'. Since
> > libc.so already exists in /Sy
On 2/5/07, Carlo Calica <[EMAIL PROTECTED]> wrote:
> Wireless-Tools makes sense. I'm thinking it should be called
> WirelessConfig. It'll only deal with iwconfig settings. Everything
> else (ifconfig, dhcpcd) should be handled by NetworkInterface. Then
> changes won't need to be synced.
[...]
>
On 2/4/07, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> Everything is fine, until the installer tries to perform some
> operation with symlinks, such as 'ln -s libc.so.6 libc.so'. Since
> libc.so already exists in /System/Index/lib and no '--force' flag was
> passed to ln, the li
Hello all,
I spent a good time this weekend working on the /System/Index thing.
However, I found a great problem and I can't see how to overcome it.
Given that we have a system compiled against /System/Index, we'll have
things like /System/Index/lib/libc.so, /System/Index/bin/gcc, and so
on. Now
