On Wed, 5 May 2004 14:53:46 +0200 (MEST)
"Sören Schulze" <[EMAIL PROTECTED]> wrote:
> I think Debian strips the binaries, but it sometimes provides packages
> with unstripped binaries seperatedly.
> But I do not have much experiences with gdb (typical DDD candy-ass
> ...) and I think understanding
At Wed, 5 May 2004 14:53:46 +0200 (MEST),
Sören Schulze wrote:
>
> > Can you set up a second filesystem and try to sync only that one (I am
> > not sure how to do that). When sync hangs, can you check what makes
> > it hang and what is going on in ext2fs?
>
> Hm, I see no option at sync which pr
On Wed, May 05, 2004 at 02:53:46PM +0200, "Sören Schulze" wrote:
> I think Debian strips the binaries, but it sometimes provides packages
> with unstripped binaries seperatedly.
I agree that it would make sense to have an unstripped hurd-dbg
eventually.
Michael
--
"The goal of Debian is to hav
> Can you set up a second filesystem and try to sync only that one (I am
> not sure how to do that). When sync hangs, can you check what makes
> it hang and what is going on in ext2fs?
Hm, I see no option at sync which provides an FS choice.
> You can do this by attaching gdb to ext2fs. Make s
[EMAIL PROTECTED] writes:
> I am having a problem with my ext2 filesystem. Sometimes at shutdown it
> seems not to be unmounted correctly. After printing all the shutdown
> messages, the system hangs then for some seconds. At the next startup, fsck
> tells wants me to repair the filesystem manuall
Michael Banck <[EMAIL PROTECTED]> writes:
> On Tue, May 04, 2004 at 04:33:45PM +0200, [EMAIL PROTECTED] wrote:
>> I am having a problem with my ext2 filesystem. Sometimes at shutdown it
>> seems not to be unmounted correctly. After printing all the shutdown
>> messages, the system hangs then for s
On Tue, May 04, 2004 at 04:33:45PM +0200, [EMAIL PROTECTED] wrote:
> I am having a problem with my ext2 filesystem. Sometimes at shutdown it
> seems not to be unmounted correctly. After printing all the shutdown
> messages, the system hangs then for some seconds. At the next startup, fsck
> tells w