new partition and mounting in yast

From: ac (aecnews_at_candt.demon.co.uk)
Date: 05/31/05 

Date: Tue, 31 May 2005 09:08:21 +0100

There is something I don't understand happening with creating and
mounting a partition via yast.

I have done a fresh 9.2 install, and during the install process I chose
to create a fat32 partition, in yast. In the same yast screen, for the
mount point I typed in
/fat32
install was onto a new unused hd so of course the mount point directory
fat32 did not previously exist.
It was accepted and all seemed to go ok.

After completion of the install I saw in konquerer that under root,
there are two entries listed as directories, each named fat32, although
one is shown in upper case FAT32

Konquerer Properties indicate that the lower case one is a link.

I think this sort of thing has occurred previously, but I had wondered
if it resulted from me having used the yast function and mounting a
newly created partition onto a pre-existing directory. Here it is
happening during a clean install.

Is a 'double' display, link and mounted partition, normal, or has
something gone wrong? Maybe there is a significance for the (original
entered) lower case, and the upper case indications?

It will be confusing for me so I will want to arrange only a single
indication.

I have sorted this out previously by carefully venturing into my areas
of inexperience - using command line methods - unmounting the offending
partition, deleting, and then using yast only to create and format (not
mount), and then using fstab to mount at boot. At least I think that is
more or less what I did. I am still trying to understand the subtleties.

Ownership of the partition (and mounting?) seemed to be important too -
I want the final mounted partition to be available to user1.

I also attempted later to change the ownership of one and both (link and
directory(?)) from root to user1, using konquerer in superuser mode,
then later login again as root. Unsuccessfully for these attempts. So I
am also missing something about changing access permissions and/or
ownership too.

I would certainly like to understand what is happening, firstly with
yast's actions, so I can decide when to use yast. And also to understand
better the sequence of activites I would follow (and why) without yast
at all.

A few comments and suggestions would be most appreciated.....

tia 

-- 
alanc

Relevant Pages

  • [opensuse] suse 10.3 ppc sound and wireless problems (+ minor irritations)
    ... WIFI: This could well be that I don't know what I am doing but I can connect to my AP with my other wifi enabled system just fine. ... PS yast wasn't too clever during the partition section of the install so here is what I did for the record in case it is usefull for anyone else: ... using the install disk boot so a shell. ...
    (SuSE)
  • [opensuse] Re: Partitioning problem in installing oS v11.1
    ... I don't see the use of a 8Mo partition. ... sda2 to the total. ... so calculating approx, 256-76=180, so YaST was only trying to install ... Good guess for YaST ...
    (SuSE)
  • Re: Installing SLES 9 on PPC Mac G4
    ... > install SLES, YaST bitches about not being able to partition the disks. ... YaST uses a disk tool that can not carve Mac Disk. ...
    (alt.os.linux.suse)
  • SUSE 9.0: Install cannot read partition table
    ... partitioning tool "Parted" that YAST uses to change the partition table. ... You may use the partitions on disk /dev/hda as they are. ... YAST from a SUSE 9.0 install from the exact ...
    (alt.os.linux.suse)
  • Windows on Mac - how to.
    ... No-nonsense instructions for those "in the know". ... A custom slipstreamed CD is required to install XP on a Mac. ... This procedure WILL WIPE YOUR iMAC DISK CLEAN. ... Partition the disk in two using the OSX CD: ...
    (uk.comp.sys.mac)