How do I activate my sdb5 partition and have it stay active continually.
Gene Heskett
gene.heskett at verizon.net
Mon Jan 5 17:31:56 UTC 2009
On Monday 05 January 2009, Steven Vollom wrote:
>> /dev/sda1 /media/sda1 ext3 owner,atime,noauto,rw,nodev,noexec,nosuid 0 0
>>
>> The difference is in the second option, I changed it from "/media" to
>> "/media/sda1".
>
>I think I screwed up. I opened the GUI to look at the partitions in
>Disk&Filesystems. I expected to find sda1 with a mount point of
>/media/sda1. It showed as /media/sdb1 instead of /media/sda1. I then
>opened the Konsole and entered sudo kedit /media/sdb2 to try to get to
>that error. This is what came on the Konsole:
>
>steven at Studio25:~$ sudo kedit /media/sdb1
>[sudo] password for steven:
>Error: "/tmp/kde-steven" is owned by uid 1000 instead of uid 0.
>
>kedit opened to a blank page and in the title bar it reads /media/sdb1 -
>KEdit <2>, like I have two KEdit windows open.
Oops, close that without saving.
>I want to go back and edit the mount point as /media/sda1.
A 'mount point' is nothing more nor less than a directory. If there is
nothing in it, it can be removed with an 'rmdir', see the manpage.
If there is something in that directory, probably because something was stored
there when no media was mounted, then if its precious, mv (see the manpage)
it to someplace safe.
Now, please understand that if I had a /media/westernsteer directory, I can
mount any partition visible to the system on that mount point with the mount
command.
Demo (all as root or sudo'd, and the # sign is the shell prompt, no pound sign
its the response to the command:
# mkdir /media/westernsteer
# df
(and get:)
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb3 468832020 97119656 347512852 22% /
/dev/sdb1 194442 81057 103346 44% /boot
/dev/sdc1 384578164 298590648 66452076 82% /amandatapes
tmpfs 2075600 0 2075600 0% /dev/shm
The above to verify where my /boot is (this box is an odd bird), then
# mount -t ext3 /dev/sdb1 /media/westernsteer
# ls /media/westernsteer
config-2.6.25.14-69.fc8 initrd-2.6.25.14-69.fc8.img memdisk
System.map-2.6.27-rc4 vmlinuz-2.6.26.5-28.fc8
config-2.6.26.3-14.fc8 initrd-2.6.26.3-14.fc8.img System.map
System.map-2.6.27-rc5 vmlinuz-2.6.26.6-49.fc8
config-2.6.26.5-28.fc8 initrd-2.6.26.5-28.fc8.img
System.map-2.6.25.14-69.fc8 System.map-2.6.27-rc6 vmlinuz-2.6.27.2
config-2.6.26.6-49.fc8 initrd-2.6.26.6-49.fc8.img System.map-2.6.26
System.map-2.6.27-rc7 vmlinuz-2.6.27.3
config-2.6.26.gz initrd-2.6.26.img
System.map-2.6.26.3-14.fc8 System.map-2.6.27-rc7-4 vmlinuz-2.6.27-4
config-2.6.27.2.gz initrd-2.6.27.2.img
System.map-2.6.26.5-28.fc8 System.map-2.6.27-rc8 vmlinuz-2.6.27.4
config-2.6.27.3.gz initrd-2.6.27.3.img
System.map-2.6.26.6-49.fc8 System.map-2.6.27-rc8-4 vmlinuz-2.6.27.5
config-2.6.27-4.gz initrd-2.6.27-4.img System.map-2.6.27.2
System.map-2.6.27-rc9-4 vmlinuz-2.6.27.6
config-2.6.27.4.gz initrd-2.6.27.4.img System.map-2.6.27.3
System.map-2.6.28 vmlinuz-2.6.28
config-2.6.27.5.gz initrd-2.6.27.5.img System.map-2.6.27-4
System.map-2.6.28.old
config-2.6.27.6.gz initrd-2.6.27.6.img System.map-2.6.27.4
vmlinuz-2.6.25.14-69.fc8
config-2.6.28.gz initrd-2.6.28.img System.map-2.6.27.5
vmlinuz-2.6.26
grub lost+found System.map-2.6.27.6
vmlinuz-2.6.26.3-14.fc8
It is in fact, my /boot partition, mounted someplace else. Now, clean up the
mess I just made:
# umount /media/westernsteer
# rmdir /media/westernsteer
# ls /media/westernsteer
ls: cannot access /media/westernsteer: No such file or directory
Does this help your understanding of how this works?
>Steven
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
QOTD:
"I don't think they could put him in a mental hospital. On the
other hand, if he were already in, I don't think they'd let him out."
More information about the kubuntu-users
mailing list