[kde-linux] 20090721KL -- SOLVED -- Dolphin And Partitions
Bruce MacArthur
bmacasuru at fastmail.us
Wed Jul 22 19:29:35 UTC 2009
Greetings, All --
I "top-post" this time.
A GREAT BIG "THANK YOU" to Anne, to David Jarvie, and to JD (Joe) for
their valuable comments and directions. The problem I specified is
COMPLETELY RESOLVED!!!!! Sure, I have a little more work to do, but
it is now entirely do-able! THANK YOU !!!!! (Perhaps the "shouting"
is acceptable in this context!)
Bruce
On Wednesday 22 July 2009 12:07, JD wrote:
> On 07/22/2009 09:06 AM, Bruce MacArthur wrote:
> > On Wednesday 22 July 2009 09:04, JD wrote:
> >> On 07/22/2009 12:03 AM, Bruce MacArthur wrote:
> >>> On Wednesday 22 July 2009 00:11, JD wrote:
> >>>> On 07/21/2009 07:36 PM, Bruce MacArthur wrote:
> >>>>> On Tuesday 21 July 2009 12:40, Anne Wilson wrote:
> >>>>>> On Tuesday 21 Jul 2009 17:58:25 Bruce MacArthur wrote:
> >>>>>>> Greetings --
> >>>>>>>
> >>>>>>> My computer has a single hard disk drive -- but many
> >>>>>>> partitions. A couple of those partitions are dedicated to
> >>>>>>> openSUSE 10.2, and the rest are Kubuntu Jaunty (also known as
> >>>>>>> Version 9.04).
> >>>>>>>
> >>>>>>> In the past, I have been able to use (Jaunty) Dolphin to view
> >>>>>>> all partitions -- which meant I could copy files from one
> >>>>>>> distro to the other. I no longer SEEM to have that option.
> >>>>>>> Although I see how to modify the default start-up folder, I
> >>>>>>> see nothing that would seem to help me restore the
> >>>>>>> cross-partition view. So I am blind!!! Can anyone point out
> >>>>>>> the obvious to me? THANKS for your time with this message!!!
> >>>>>>
> >>>>>> In each distro, do you have fstab mounts for the partitions of
> >>>>>> the other distro?
> >>>>>>
> >>>>>> Anne
> >>>>>
> >>>>> Hello, Anne --
> >>>>>
> >>>>> FIRST, Thank you for a quick and helpful reply.
> >>>>>
> >>>>> SECOND, a part of my delay in replying is due to problems that
> >>>>> I created for myself in the process of trying to install a
> >>>>> VHS-DVD player-recorder to use the "TV-AV" aspect of my
> >>>>> computer monitor! I am now back to normal. MEANWHILE, I have
> >>>>> been researching the issue that you have raised for me. I am
> >>>>> certain that the answer to your question is "No." But I am not
> >>>>> at all sure quite what I need to do!
> >>>>>
> >>>>> When I try to edit /etc/fstab in openSUSE, I see
> >>>>>
> >>>>> /dev/sda2 / /
> >>>>> acl,user_xattr 1 1 /dev/sda3 /home /home
> >>>>> acl,user_xattr 1 2 /dev/sda1 swap swap
> >>>>> defaults 0 0 proc /proc
> >>>>> /proc defaults 0 0 sysfs /sys
> >>>>> /sys noauto 0 0 debugfs /sys/kernel/debug
> >>>>> debugfs noauto 0 0 usbfs /proc/bus/usb
> >>>>> usbfs noauto 0 0 devpts /dev/pts
> >>>>> devpts mode=0620,gid=5 0 0 /dev/fd0 /media/floppy
> >>>>> auto noauto,user,synch 0 0
> >>>>>
> >>>>> The df shows
> >>>>>
> >>>>> /dev/sda2 18% /
> >>>>> udev 1% /dev
> >>>>> /dev/sda3 42% /home
> >>>>>
> >>>>>
> >>>>> Both commands produce radically different output in Jaunty
> >>>>> (9.04). Part of this is obviously due to the partitioning which
> >>>>> I did -- but part of it is a combination of other variables
> >>>>> (such as versions, etc.)! For example, edit /etc/fstab
> >>>>> produces a LOT of comment-code, not to mention some really
> >>>>> cryptic first-column device names! Trying to minimize the
> >>>>> confusion, let me present its output as follows. (If the names
> >>>>> are important, I will gladly supply them!)
> >>>>>
> >>>>> proc /proc
> >>>>> proc 0 0 /dev/sda6 /
> >>>>> ext3 0 1 /dev/sda11 /home
> >>>>> ext3 0 2 /dev/sda10 /opt
> >>>>> ext3 0 2 /dev/sda7 /root
> >>>>> ext3 0 2 /dev/sda8 /tmp
> >>>>> ext3 0 2 /dev/sda12
> >>>>> /usr ext3 0 2 /dev/sda9
> >>>>> /var ext3 0 2 /dev/sda1
> >>>>> none swap 0 0 /dev/sda5
> >>>>> none swap 0 0 /dev/scd0
> >>>>> /media/cdrom0 udf,iso9660 0 0 /dev/fd0 /media/floppy
> >>>>> auto 0 0
> >>>>>
> >>>>> The first column in the preceeding listing is taken from the
> >>>>> comments and seems to be something from "prior to
> >>>>> installation". The third-from-last column is --
> >>>>> defaults
> >>>>> relatime,error=remount -ro
> >>>>> relatime
> >>>>> relatime
> >>>>> relatime
> >>>>> relatime
> >>>>> relatime
> >>>>> relatime
> >>>>> sw
> >>>>> sw
> >>>>> user,noauto,exec,utf8
> >>>>> rw,user,noauto,exec,utf8
> >>>>>
> >>>>> The results of the df command are also much more extensive --
> >>>>>
> >>>>> /dev/sda6 9% /
> >>>>> tmpfs 0% /lib/init/rw
> >>>>> varrun 1% /var/run
> >>>>> varlock 0% /var/lock
> >>>>> udev 1% /dev
> >>>>> tmpfs 1% /dev/shm
> >>>>> lrm 1% /lib/modules/2.6.28-11-g
> >>>>> eneric/volatile
> >>>>> /dev/sda11 2% /home
> >>>>> /dev/dsa10 1% /opt
> >>>>> /dev/sda7 4% /root
> >>>>> /dev/sda8 2% /tmp
> >>>>> /dev/sda12 10% /usr
> >>>>> /dev/sda9 5% /var
> >>>>>
> >>>>> I really do NOT understand the fact that "tmpfs" appears TWO
> >>>>> times above the "eneric/volatile" entry, but I did not copy
> >>>>> this one in error!!!
> >>>>>
> >>>>>
> >>>>> I notice that you mentioned that I should have fstab mounts for
> >>>>> the partitions of EACH distro in the other. This makes
> >>>>> excellent good sense if I am going to be moving things in both
> >>>>> directions. I do not anticipate doing this -- the moves will be
> >>>>> entirely from openSUSE to Jaunty. Can I "get away with" adding
> >>>>> openSUSE partitions to Jaunty's fstab -- or will things
> >>>>> effectively blow-up in my face if I fail to balance the
> >>>>> equation?
> >>>>>
> >>>>> THANKS for your time and assistance!!!!!
> >>>>
> >>>> I had a similar situation.
> >>>> Part of the problem for you "might" be that the 2 OS'es do not
> >>>> use the same device names for the partitions in question. So,
> >>>> you will need to do some work to be sure (for example - that
> >>>> /dev/sdb3 in one OS is the same as /dev/sdd3 in the other os).
> >>>> What I am trying to point out is that the disk numbering scheme
> >>>> in the two OS'es might not match. So once you are able to
> >>>> identify the device names in both OS'es and map them 1 - 1
> >>>> correctly, then adding them correctly into both OS'es fstabs
> >>>> should be very trivial.
> >>>
> >>> Hello, Joe --
> >>>
> >>> For a short time, Dolphin saw ALL of my partitions, and it was
> >>> certain (to me!) which ones were openSUSE and which were Jaunty.
> >>> What a PLEASANT surprise!!! You have a point in suggesting that
> >>> those days may well be history. I will be observant.
> >>>
> >>>> So, your devices on jaunty are:
> >>>>
> >>>> /dev/sda6 / ext3 0 1
> >>>> /dev/sda11 /home ext3 0 2
> >>>> /dev/sda10 /opt ext3 0 2
> >>>> /dev/sda7 /root ext3 0 2
> >>>> /dev/sda8 /tmp ext3 0 2
> >>>> /dev/sda12 /usr ext3 0 2
> >>>> /dev/sda9 /var ext3 0 2
> >>>> /dev/sda1 none swap 0 0
> >>>> /dev/sda5 none swap 0 0
> >>>>
> >>>> PS: I do not know how jaunty creates 12 partitions in a Linux
> >>>> disk! Jaunty seems to be using BSD partitioning scheme, no?? If
> >>>> that is the case, your opensuse will probably not be able to
> >>>> mount jaunty's non-standard Linux partitions. Standard Linux
> >>>> kernels simply do not write BSD partitions - even the config
> >>>> menu says it is dangerous to config and build the linux kernel
> >>>> with write support for BSD's UFS partitions.
> >>>> I do know that you could have for example 3 extended
> >>>> partitions and 4 sub-partitions in each extended partition.
> >>>> Perhaps that is what you did - in which case my comment re: BSD
> >>>> UFS does not apply.
> >>>
> >>> Jaunty did NOT (automatically) create all those partitions!
> >>> Instead, I studied one book about Ubuntu Linux in its discussion
> >>> of partitioning, and tried to set things up well. I think that I
> >>> have one Primary partition for openSUSE and another similar
> >>> partition for Jaunty. The rest are "sub-partitions". Also, be
> >>> aware that MY openSUSE will never need to mount Jaunty partitions
> >>> -- only the reverse is needed. To the best of my knowledge, "BSD
> >>> partitions" (thankfully!!!) have nothing to do with this
> >>> installation.
> >>>
> >>>> Your devices on opensuse are:
> >>>> /dev/sda2 / / acl,user_xattr 1 1
> >>>> /dev/sda3 /home /home acl,user_xattr 1 2
> >>>> /dev/sda1 swap swap defaults 0 0
> >>>>
> >>>> Now, which devices do you wish to be visible to both OS'es??
> >>>
> >>> I think that I need sda2 and sda3 visible to both. openSUSE
> >>> needs them to run at all, and Jaunty needs them to bring some
> >>> data over to the Jaunty installation. NOTHING that is presently
> >>> Jaunty-only needs to be visible to openSUSE.
> >>>
> >>>> Also, in each OS, issue the command
> >>>> fdisk -l /dev/sd
> >>>> for all disks visible to the OS. Look in /dev to see how
> >>>> many sd devices there are. Save the outputs
> >>>> and label them so a reader will know which OS the command
> >>>> was run on.
> >>>
> >>> In openSUSE, I tried running this command, both as myself and as
> >>> sudo. Both times I was told "fdisk: command not found".
> >>> Obviously I need to do some research -- unless this is just more
> >>> of the reason for my move away from openSUSE. Please understand
> >>> that I am not "mad" at SUSE, but I am very perturbed about my own
> >>> installation )which was done by a store's personnel)!
> >>>
> >>> Also, searching for the file yielded one "fdisk" in "sbin/". It
> >>> has some 86,352 bytes, and is "Read Only", NOT executable!
> >>>
> >>> In Kubuntu Jaunty my results were dramatically different, like
> >>> this --
> >>>
> >>> Disk /dev/sda: 250.0 GB, 250059350016 bytes
> >>> 255 heads, 63 sectors/track, 30401 cylinders
> >>> Units = cylinders of 16065 * 512 = 8225280 bytes
> >>> Disk identifier: 0x000dcd1b
> >>>
> >>> Device Boot Start End Blocks ID
> >>> System /dev/sda1 1 131 1052226
> >>> 82 Linux swap / Solaris
> >>> /dev/sda2 132 2742 20972857+ 83 Linux
> >>> /dev/sda3 2743 16428 109932795 83 Linux
> >>> /dev/sda4 16429 30401 112238122+ 5 Extended
> >>> /dev/sda5 16429 16793 2931831 82 Linux swap
> >>> / Solaris
> >>> /dev/sda6 16794 17158 2931831 83 Linux
> >>> /dev/sda7 17159 17766 4883728+ 83 Linux
> >>> /dev/sda8 17767 18982 9767488+ 83 Linux
> >>> /dev/sda9 18983 20198 9767488+ 83 Linux
> >>> /dev/sda10 20199 22630 19535008+ 83 Linux
> >>> /dev/sda11 22631 26277 29294496 83 Linux
> >>> /dev/sda12 26278 30401 33125998+ 83 Linux
> >>>
> >>>> This will help identify which disks have same partitioning
> >>>> scheme and partition types, ..etc.
> >>>
> >>> What I show above is PERFECTLY consistent with what I was
> >>> previously seeing in Dolphin -- but Dolphin is not yet seeing
> >>> things this way again! And my immediate goal is to have Dolphin
> >>> see this again.
> >>>
> >>> THANK YOU, Joe, for your time with this and for any additional
> >>> insights or directions you can give me -- they are MOST
> >>> appreciated!!!
> >>>
> >>>> Cheers,
> >>>>
> >>>> Joe
> >>
> >> OK, So on Jaunty you only have sda . Fine.
> >> On Opensuse, you were not able to run fdisk because it is not
> >> executable. So, do this to make it executable:
> >> sudo chmod 755 /sbin/fdisk
> >>
> >> and then
> >> for every /dev/sdX where X is a, b, c, d ...etc, run
> >> /sbin/fdisk -l /dev/sdx
> >
> > I have followed your directions with ease -- but it has not worked!
> > In spite of the change of permissions to 755, the search utility
> > still shows it to be "Read-Only"! I think that this is related to
> > a VERY faulty installation; it is NOT simply an openSUSE problem.
> >
> >> So, that aside, one thing is still not clear:
> >> is your meachine a dual boot machine? or you simply have
> >> two machines? I was proceeding on the premise that you
> >> have a dual boot machine, which might not be what you have.
> >
> > This is one computer only. It has a single hard disk drive only.
> > And, yes, it IS dual-boot. Your understanding both was and is
> > correct.
> >
> >> If you have two machines, then you have two choices
> >> for exposing opensuses's disks to jaunty:
> >> 1. On Opensuse:
> >> export them via NFS.
> >> So to export, you need to do this on opensuse:
> >> sudo exportfs /home (for exmple).
> >>
> >> On Jaunty, you mount opensuse's exported partition like this:
> >> sudo mount -t nfs 192.168.bla.bla:/home -o w /mnt/home
> >>
> >> Of course /mnt/home has to exsit as a directory on jaunty.
> >>
> >> OR
> >> 2. use samba to advertise the mounted partitions on opensuse and
> >> mount them as cifs type partitions on jaunty. This is a more
> >> involved process requiring you to edit the smb.conf file and
> >> restarting themb and nmb services. There may be a gui tool
> >> for configuring samba exports (or shares, as they are
> >> called). I do not know if jaunty is similar to fedora, so how you
> >> mount them on jaunty will be something like
> >> mount -t cifs //192.168.bla.bla/SOME-NAME /mnt/some-dir-name
> >> or it could be
> >> smbmount //192.168.bla.bla/SOME-NAME /mnt/some-dir-name
> >>
> >> Joe
>
> In that case, the advice you received from another individual is
> correct. The only partitions that jaunty is not mounting are the
> partitions of opensuse.
>
> So, in your jaunty's /etc/fstab, add lines like
>
> /dev/sda2 /suse ext3 acl,user_xattr 0 2
> /dev/sda3 /suse/home ext3 acl,user_xattr 0 2
>
> Assuming, of course, that you have done
>
> sudo mkdir -p /suse/home
> on jaunty
>
> Cheers,
>
> Joe
--
布鲁斯 麦克阿瑟
Bruce Mac Arthur
15875 Switzer
Overland Park, KS 66221
913-897-4157
bmacasuru at fastmail.us
More information about the kde-linux
mailing list