On Wed, Apr 22, 2009 at 02:02:43PM -0700, John Brahy wrote:
| # newfs /dev/wd0f
| newfs: /dev/wd0f: block device
| #
|
| I thought that I have done that before. Have we lost functionality in
| 4.5 or just my mind?
A bug that allowed newfs'ing block devices was fixed. We did not lose
John Brahy wrote:
Have I completely lost my mind or should I be able to give newfs a block device?
# df -ht ffs
Filesystem SizeUsed Avail Capacity Mounted on
/dev/wd0a 1006M203M753M21%/
/dev/wd0j 7.9G6.0G1.5G81%/home
/dev/wd0i 1006M
it used to be broken when it allowed newfs to non raw disks.
On Wed, Apr 22, 2009 at 03:18:16PM -0600, Tom Rosso wrote:
John Brahy wrote:
Have I completely lost my mind or should I be able to give newfs a block
device?
# df -ht ffs
Filesystem SizeUsed Avail Capacity Mounted on
Have I completely lost my mind or should I be able to give newfs a block device?
# df -ht ffs
Filesystem SizeUsed Avail Capacity Mounted on
/dev/wd0a 1006M203M753M21%/
/dev/wd0j 7.9G6.0G1.5G81%/home
/dev/wd0i 1006M6.0K956M 0%
Have I completely lost my mind or should I be able to give newfs a block
device?
The former. You cannot newfs a block device.
It was always wrong. Use the raw device.
On Wed, Apr 22, 2009 at 5:02 PM, John Brahy j...@brahy.com wrote:
Have I completely lost my mind or should I be able to give newfs a block
device?
# df -ht ffs
Filesystem SizeUsed Avail Capacity Mounted on
/dev/wd0a 1006M203M
John Brahy schrieb:
Have I completely lost my mind or should I be able to give newfs a block device?
# df -ht ffs
Filesystem SizeUsed Avail Capacity Mounted on
/dev/wd0a 1006M203M753M21%/
/dev/wd0j 7.9G6.0G1.5G81%/home
/dev/wd0i 1006M
7 matches
Mail list logo