From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Peter Leftwich <Hostmaster@Video2Video.Com>
Cc: debian-bsd@lists.debian.org, debian-user@lists.debian.org,
owner-linux-kernel@vger.kernel.org,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: mount from debian to 44bsd, chown bug report?
Date: Mon, 29 Dec 2003 01:56:08 +0200 [thread overview]
Message-ID: <1072655768.6994.125.camel@nosferatu.lan> (raw)
In-Reply-To: <20031228183005.G86605@rocket.alienwebshop.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Mon, 2003-12-29 at 01:43, Peter Leftwich wrote:
> Hello everyone. I am booting up into a bootable Knoppix 3.2 (Debian Linux)
> CD-R (www.knoppix.net) and trying to mount my FreeBSD 4.7-RELEASE partition.
>
> The working command-line is:
> `mount -t ufs -o ufstype=44bsd /dev/hda2 /mnt/fbsd`
>
> At one time I was naturally able to read/write files to the partition once
> it was mounted, but then I chowned the root directory to "knoppix." Now
> here is what's happening:
>
> # whoami ; mount | grep 44bsd
> root
> /dev/hda2 on /mnt/test type ufs (rw,ufstype=44bsd)
>
> # ls -al /mnt | grep knoppix
> drwxr-x--x 25 knoppix root 1024 Dec 18 22:10 /mnt/test
>
> # grep ufs /proc/filesystems
> ufs
>
> # chown root /mnt/test
> chown: changing ownership of `test': Read-only file system
>
> The error above contradicts the "mount" info, namely, the "rw" part!!
>
Uhm, if /mnt/test is in a ro filesystem, mounting a partition to it
rw will still not get you to change /mnt/test - sure, you will be
able to chown /mnt/test/foo ....
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-28 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 23:43 mount from debian to 44bsd, chown bug report? Peter Leftwich
2003-12-28 23:56 ` Martin Schlemmer [this message]
2003-12-29 3:21 ` Peter Leftwich
2003-12-29 7:41 ` Tomas Szepe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1072655768.6994.125.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=Hostmaster@Video2Video.Com \
--cc=debian-bsd@lists.debian.org \
--cc=debian-user@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=owner-linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.