File System Manager Question on OS 6.0

Trying to make a file system read-only by default but Openserver 6.0 is not
cooperating.

If I leave the "Device File:" blank (as it is on entry), and select the "v"
in the "Access Mode:" field, the choices are Read-write and Read-only.

I select "Read-Only" then select the Device File and the Access Mode
switches from read-only to read-write. File system /dev/oldsys is type vxfs.

+------------------- Add Local Mount Configuration on serv1 -------------------+
| |
| +--------------------------------------------------+|
| Device File: ||/dev/oldsys____________________________________|v||
| +--------------------------------------------------+|
| |
| Mount Point: |/oldsys___________________________________________||
| |
| Description (optional): |__________________________________________________||
| |
|+------------------------------------------+ +Mount Options: ----------------+|
|| Filesystem Type:+------------+______| | |[ Check and Repair Options... ]||
|| Access Mode:| Read-write | |v] | |[ Advanced Options... ]||
|| Can Users Mount?+------------+ | +-------------------------------+|
|| | +When to Mount: ----------------+|
|| | |[ ] Now ||
|| | |[ ] At System Startup ||
|| | | ||
|| | | ||
|| | | ||
|+------------------------------------------+ +-------------------------------+

Trying "mkdev fs" (as I have on 5.0.x) and answering the questions as shown
below:

Enter a device name and press <Return> or q to quit: /dev/oldsys
Enter a directory name and press <Return> or q to quit: /oldsys
Reserving slots in lost+found directory ...

When entering multiuser mode:
1. Always mount /dev/oldsys.
2. Never mount /dev/oldsys.
3. Prompt before mounting /dev/oldsys.

Select an option: 2

Do you want to allow users to mount this file system? (y/n) n
Updating system files ...
Filesystem has been successfully added.


But then...

# mount /dev/oldsys
UX:mount: ERROR: cannot determine special device
# mount oldsys
UX:mount: ERROR: cannot determine special device

But the following works:

# mount /dev/oldsys /oldsys
# dfspace
/ : Disk space: 6524.41 MB of 9000.99 MB available (72.49%).
/stand : Disk space: 33.74 MB of 39.99 MB available (84.37%).
/u : Disk space: 6705.00 MB of 9000.99 MB available (74.49%).
/tmp : Disk space: 126.61 MB of 126.62 MB available (99.99%).
/oldsys : Disk space: 3469.11 MB of 7812.49 MB available (44.40%).

Total Disk Space: 16858.90 MB of 25981.11 MB available (64.89%).


Openserver 6.0 "not ready for Prime Time" TM
.

Relevant Pages

  • Re: mount() function problem !
    ... mount() attaches the filesystem specified by source (which is often a device name, ... point within a file system. ... details of the options available for each filesystem type. ... Specifies the journalling mode for file data. ...
    (comp.lang.c)
  • Re: bin, sbin, etc as seperate LVM volumes
    ... RD>>that's where mount lives, and you almost certainly need to mount ... driver modules needed to get to the root file system. ... to start with -- these all must be all on the same file system. ...
    (comp.os.linux.misc)
  • RE: Machine not Booting - Continued
    ... If you see /etc/rc.sysinit you can see some sections for managing raid partitions. ... Otherwise specify the same mkraid and mount command in /etc/rc.local. ... it has no proper file system to mount. ... For address and company registration details of certain entities ...
    (RedHat)
  • Re: Salvaging data from USB flash disk
    ... mount: wrong fs type, bad option, bad superblock on /dev/loop0, ... Disk /dev/sda doesn't contain a valid partition table ... Your flash disk most likely has a vfat file system. ... only the partition containing the file system with data. ...
    (comp.os.linux.hardware)
  • Re: Init.c, making it chroot
    ... simply let init mount it in all cases, ... The kernel needs to mount devfs because that's how it finds the device node to mount the root file system from. ...
    (freebsd-hackers)