On Sat, Feb 21, 2015 at 12:04:36AM +0100, Justus Winter wrote:
> > > $ showtrans /media/erich
> > > /hurd/ext2fs --no-atime /dev/hd2
> > > $ grep hd2 < /etc/fstab
> > > /dev/hd2/media/erich ext2 defaults 0 2
>
> That's odd. Though I must admit I do not use passive translat
tup is the new /hurd/init, I merely renamed it to a) reflect
the fact that it is the server speaking the startup protocol, and b)
to free /hurd/init for a roughly sysvinit-compatible minimal init.
> > in case) that would cause this non-root filesystem to be mounted that
> > early,
Hi!
On Fri, 20 Feb 2015 22:44:17 +0100, I wrote:
> As in the subject, and see the attached QEMU screenshot. Has something
> been changed in the boot process ("startup" is new; Justus CCed ;-) just
> in case) that would cause this non-root filesystem to be mounted that
>
Hi!
As in the subject, and see the attached QEMU screenshot. Has something
been changed in the boot process ("startup" is new; Justus CCed ;-) just
in case) that would cause this non-root filesystem to be mounted that
early, so that e2fsck can't then process it anymore? "Eri
I'd call that a bug in e2fsck. Empty symlinks used to be creatable and
work on GNU/Linux as well. It would be fine to disallow them, however.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Hi,
I created an empty symlink on an ext2 filesystem while I was in
GNU/Hurd. Later on that partitions was checked by e2fsck (in
GNU/Linux) and when it encountered that symlink, it reported a
filesystem inconsistency, which I had to repair manually.
That doesn't seem so sane to me, e
ght miss more serious messages).
>
> Uh, it is the default. Or I'm badly misinterpreting your question:
>
> e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
> The Hurd does not support the filetype feature.
> Clear? yes
>
> Pass 1: Checking inodes, blocks, and siz
ly POSIX calls, and at any rate e2fsck will just correct them if
they do get created by some obscure action.
It was reported to me by Thomas Bushnell that this wouldn't work, since
the Hurd allows you to transmogrify files from one type to another
(i.e., symlink to block device to FIFO, or s
ting hurd fs, this helps a lot (you could provide -y,
but then you might miss more serious messages).
Uh, it is the default. Or I'm badly misinterpreting your question:
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
The Hurd does not support the filetype feature.
Clear? yes
Pass 1: Chec
d never
use them, it doesn't affect the Hurd itself one way or another. These
situations would never be created by the Hurd on an ext2 filesystem by
using only POSIX calls, and at any rate e2fsck will just correct them if
they do get created by some obscure action.
Hi,
First: I apologize for being dumb. I completely misunderstood how this is
supposed to work. Now that I understood, I don't disagree with the problem
message anymore.
However, I think my result is partly the result of mke2fs -o hurd setting
the filetype feature on linux. Ted, can you make the
Hi,
e2fsck 1.19 will produce the following problem message on the Hurd with a
filesystem that has filetypes:
The Hurd does not support the filetype feature.
Clear ?
This will lead to problems with fsck --preen --writable, which is used
at boot time: fsck will barf out with an UNEXPECTED
#x27;t see how you
> > think this change would be correct.
>
> I have a scheme in the long run for making it work for one-link nodes.
I think you should let any pestering of the e2fsck maintainers wait until
such a scheme is closer to fruition.
> The reason not to ignore problem i
Roland McGrath <[EMAIL PROTECTED]> writes:
> I'm not sure why you think this is useful for the Hurd. Our ext2fs has no
> choice but to ignore the filetype field anyway, because an active
> translator setting might make it incorrect. Moreover, I don't see how you
> think this change would be cor
> I have submitted a bug report for e2fsck to prevent it from trying to
> set the in-directory inode type field on files with multiple links.
> It's OK if it does so on files with one link.
I'm not sure why you think this is useful for the Hurd. Our ext2fs has no
choic
15 matches
Mail list logo
