Your message dated Thu, 11 Jul 2013 21:49:54 +0200
with message-id <20130711194954.ge22...@inutil.org>
and subject line Re: [linux-2.6] CONFIG_UFS_FS_WRITE is not set, makes
debootstrap from Linux to kFreeBSD difficult.
has caused the Debian Bug report #635291,
regarding [linux-2.6] CONFIG_UFS_FS_WRITE is not set, makes debootstrap from
Linux to kFreeBSD difficult.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
635291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-35
Severity: minor
--- Please enter the report below this line. ---
UFS is now supported in Debian GNU/Linux only in read only mode. I'm
aware of http://wiki.debian.org/Debian_GNU/kFreeBSD_FAQ and note, that
it's "likely to cause panics" (how old is this information?), but it
looks as stable in kernel.
There are only 3 filesystems that are "common" to Linux and kFreeBSD
kernel. ZFS (creation not possible from Debian GNU/Linux), UFS (read
only in Linux) and ext2 (obsolete, lack of features), so it makes
debootstrap from Linux to kFreeBSD difficult: it looks like first one
must to debootstrap to ext2, then reboot to this temporary system,
create UFS/ZFS and debootstrap once again.
Can you please consider enabling CONFIG_UFS_FS_WRITE? If someone don't
want to risk panic, always can mount UFS filesystem as RO, but current
situation takes the choice away.
CONFIG_UFS_FS_WRITE is not set not only in 2.6.32-35, but also in
2.6.38-bpo.2-686 (that's clear) and 2.6.39 from unstable.
Regards,
rozie
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.38-bpo.2-686
Debian Release: 6.0.2
500 stable-updates ftp.fi.debian.org
500 stable security.debian.org
500 stable ftp.fi.debian.org
500 stable deb.opera.com
400 unstable ftp.fi.debian.org
100 squeeze-backports backports.debian.org
100 experimental ftp.fi.debian.org
--- Package information. ---
Package's Depends field is empty.
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
On Sun, Jul 24, 2011 at 07:48:51PM +0200, Paweł Różański wrote:
> Package: linux-2.6
> Version: 2.6.32-35
> Severity: minor
>
> --- Please enter the report below this line. ---
> UFS is now supported in Debian GNU/Linux only in read only mode. I'm
> aware of http://wiki.debian.org/Debian_GNU/kFreeBSD_FAQ and note, that
> it's "likely to cause panics" (how old is this information?), but it
> looks as stable in kernel.
>
> There are only 3 filesystems that are "common" to Linux and kFreeBSD
> kernel. ZFS (creation not possible from Debian GNU/Linux), UFS (read
> only in Linux) and ext2 (obsolete, lack of features), so it makes
> debootstrap from Linux to kFreeBSD difficult: it looks like first one
> must to debootstrap to ext2, then reboot to this temporary system,
> create UFS/ZFS and debootstrap once again.
>
> Can you please consider enabling CONFIG_UFS_FS_WRITE? If someone don't
> want to risk panic, always can mount UFS filesystem as RO, but current
> situation takes the choice away.
>
> CONFIG_UFS_FS_WRITE is not set not only in 2.6.32-35, but also in
> 2.6.38-bpo.2-686 (that's clear) and 2.6.39 from unstable.
UFS_FS_WRITE is still marked as unsafe in current kernels:
| config UFS_FS_WRITE
| bool "UFS file system write support (DANGEROUS)"
| depends on UFS_FS
| help
| Say Y here if you want to try writing to UFS partitions. This is
| experimental, so you should back up your UFS partitions beforehand.
Unless upstream considers it safe enough we won't activate it. Closing the bug.
Cheers,
Moritz
--- End Message ---
