On Sun, Nov 27, 2005 at 09:59:37PM +0100, Blaisorblade wrote:
> The attached patch is a (hacky) proposal, alternative to Jeff's
> fix-stub-syscall6, to fix the SKAS0 compilation problem.
Bleah :-)
> In fact, Jeff's patch makes the problem appear on my system (where I never
> reproduced it).
Wh
On Sunday 27 November 2005 12:31, Nix wrote:
> > I personally symlink /bin, /sbin, and /lib to the
> > corresponding /usr directories and consolidate the whole mess, myself.
> > Yes, you have to patch gcc's paths (in collect2) to not search _both_
> > /lib and /usr/lib because if gnu's
Hi Paolo,
Please create an x86_64 binary so I can play with different 64 bit distros.
Thanks in advance (I know you have lots of spare time on your hands)
Cheers
Phill.
P.S. the 32 bit binary is wonderful! It does absolutely everything I need.
-
On Sunday 27 November 2005 12:35, Nix wrote:
> On Sun, 27 Nov 2005, [EMAIL PROTECTED] whispered secretively:
> > It's not a file, it's a AF_UNIX socket bound there - and bind() fails if
> > the file exists. So it's a different story (I was puzzled by a missing
> > bind(O_EXCL), but I learned with t
On Sunday 27 November 2005 12:49, Nix wrote:
> I'm using both matlab/octave *and*, when running backups, said French disk
> archiver. The source is gradually being Anglicised so that the developer
> base can rise a bit :)
>
> It has numerous advantages over tar and rsync if, like me, you're stuck
On Sunday 27 November 2005 13:20, Blaisorblade wrote:
> > Try "rdinit=/bin/sh", that affects what init gets run on the initramfs.
> > (Assuming the initramfs has a comand shell...)
>
> Missing from Documentation/filesystems/ramfs-rootfs-initramfs.txt.
I only dredged through the source and found it
The attached patch is a (hacky) proposal, alternative to Jeff's
fix-stub-syscall6, to fix the SKAS0 compilation problem.
In fact, Jeff's patch makes the problem appear on my system (where I never
reproduced it).
I'm going to stick this in -bs2, as it makes kernels compiled for me work
better.
On Sun, 27 Nov 2005, [EMAIL PROTECTED] whispered secretively:
> Plus, for deep troubleshooting (mainly for kernels) init=/bin/sh is useful.
init=/bin/busybox/sh is also useful for those cases when you've futzed
your libc. :)
>> > No - the kernel doesn't allow storing the full set of infos which a
On Sunday 27 November 2005 12:17, Nix wrote:
> [Sorry for response delay, steaming cold/flu]
>
> On Fri, 25 Nov 2005, Rob Landley worried:
> > On Friday 25 November 2005 15:04, Nix wrote:
> >> The ~/.kde directory doesn't contain temporary files, but persistent
> >> state:
> >
> > ~/.kde/share/apps
On Sunday 27 November 2005 19:59, Rob Landley wrote:
> On Sunday 27 November 2005 11:37, Blaisorblade wrote:
> > > Like "/tmp/uml.ctl" in arch/um/drivers/daemon_kern.c, line 70?
> Any user can create /tmp/uml.ctl and the sticky bit prevents anybody else
> from deleting it, so any user can block UM
On Sunday 27 November 2005 19:35, Nix wrote:
> On Sun, 27 Nov 2005, [EMAIL PROTECTED] whispered secretively:
> > Nice move to disable init=/bin/sh. Really. Next one is moving kdelibs
> > into the kernel?
> Nah, AIUI the initramfs runs *first*;
> it's its job to parse those parts
> of the kernel
On Sunday 27 November 2005 11:37, Blaisorblade wrote:
> > Like "/tmp/uml.ctl" in arch/um/drivers/daemon_kern.c, line 70?
> >
> > (It's not obvious where this file is actually created, it's one of those
> > funky callback things where data in a structure is used somewhere
> > else...)
>
> It's not a
On Sun, 27 Nov 2005, [EMAIL PROTECTED] whispered secretively:
> (as an aside, I do despise learning *so* fast... I wouldn't be able to use
> socket() without manuals, and there's a lot of stuff I'd like to learn well.
> And I'd really like to _start_ and finish even a little project on my own...
On Sun, 27 Nov 2005, [EMAIL PROTECTED] whispered secretively:
> It's not a file, it's a AF_UNIX socket bound there - and bind() fails if the
> file exists. So it's a different story (I was puzzled by a missing
> bind(O_EXCL), but I learned with trial there's no need).
There's an (optional) abstr
On Sat, 26 Nov 2005, Rob Landley murmured woefully:
> On Friday 25 November 2005 20:12, Nix wrote:
>> If it's a problem you have both hostile users and no size limits on /tmp
>> and you therefore have bigger problems anyway. :)
>
> The size limits on /tmp aren't per-user.
True. TODO: add tmpfs qu
?u?K?T?C?g???H?v?v???H
?C???`?L???T?C?g???q
?A?j???A?C(?A?\?R?H)?G?b?`(*^^*)
???p???B
http://thirdlove.info/9/
:
[Sorry for response delay, steaming cold/flu]
On Fri, 25 Nov 2005, Rob Landley worried:
> On Friday 25 November 2005 15:04, Nix wrote:
>> The ~/.kde directory doesn't contain temporary files, but persistent state:
>
> ~/.kde/share/apps/kmail/lock is persistent state?
No, but KDE is a bit of a me
On Saturday 26 November 2005 12:47, Rob Landley wrote:
> On Friday 25 November 2005 20:12, Nix wrote:
> > If it's a problem you have both hostile users and no size limits on /tmp
> > and you therefore have bigger problems anyway. :)
> My original point was that the semantics of what UML wants is s
On Saturday 26 November 2005 11:44, Rob Landley wrote:
> On Friday 25 November 2005 17:33, Blaisorblade wrote:
> > On Friday 25 November 2005 22:04, Nix wrote:
> > > On Fri, 25 Nov 2005, Rob Landley moaned:
> > > > On Friday 25 November 2005 13:33, Nix wrote:
> That a normal user can allocate pers
On Friday 25 November 2005 23:31, Rob Landley wrote:
> On Friday 25 November 2005 15:04, Nix wrote:
> > The ~/.kde directory doesn't contain temporary files, but persistent
> > state:
>
> ~/.kde/share/apps/kmail/lock is persistent state?
>
> I do know that half the time the darn battery runs out an
On Saturday 26 November 2005 11:44, Rob Landley wrote:
> On Friday 25 November 2005 17:33, Blaisorblade wrote:
> > - back in 2.4, tmpfs on /tmp broke mkinitrd since it tried to loop-mount
> > the new initrd, which was in /tmp. And loop-mount over tmpfs didn't work.
>
> I vaguely remember this bein
On Saturday 26 November 2005 23:22, Andreas Wohlfeld wrote:
> On Sat, Nov 26, 2005 at 01:03:42PM -0600, Rob Landley wrote:
> > Lilo is saying that ubda is not a device with partitions.
> >
> > Anybody know what it's talking about? (I've got a ubda1. I'm trying to
> > make a disk image I can test
22 matches
Mail list logo
