Just a note : I tried again reinstalling the OS and then gdm . But it again showed the same thing.So it seems like the gdm itself is broken (or not) , anyhow thanks all once again. P.S Thank god I had a backup this time ;-) On Fri, May 28, 2010 at 11:56 AM, Ravi Shukla <rvshkl18@gmail.com> wrote:
Hello,
You know what , you guys just rock . Thanks to all specially Carlos ;-) . So , Yes I am reinstalling the software and will get back if anything again I stumble upon .
Thanks once again
Ravi
On Fri, May 28, 2010 at 3:15 AM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Thu, May 27, 2010 at 4:48 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2010-05-27 at 23:30 +0530, Ravi Shukla wrote:
On Thu, May 27, 2010 at 11:05 PM, Carlos E. R. <> wrote:
Any help on this ? (I have very important docs and family pics in the disk and I dont want to loose it )
You can access them in text mode.
I know its a silly question, but how can I transfer it to my portable hard drive ?
Ok. First, you can open several terminals in text mode, and go from one to the other via ctrl-alt-F1, F2... to F6. In one of them log in as root, and type "tailf /var/log/messages". Then, plug in the external hard disk. You will see appearing messages in that terminal that will tell the device name the disk gets. Similar to this:
nimrodel kernel: usb-storage: waiting for device to settle before scanning nimrodel kernel: scsi 0:0:0:0: Direct-Access SanDisk Cruzer Micro 8.02 PQ: 0 ANSI: 0 CCS nimrodel kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk nimrodel kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 nimrodel kernel: usb-storage: device scan complete nimrodel kernel: sd 0:0:0:0: [sda] 15695871 512-byte hardware sectors (8036 MB) nimrodel kernel: sd 0:0:0:0: [sda] Write Protect is off nimrodel kernel: sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08 nimrodel kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through nimrodel kernel: sd 0:0:0:0: [sda] 15695871 512-byte hardware sectors (8036 MB) nimrodel kernel: sd 0:0:0:0: [sda] Write Protect is off nimrodel kernel: sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08 nimrodel kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through nimrodel kernel: sda: sda1
The important thing above is "sda1", the partition. Then open another terminal, as root. Make sure you have a mount point available, an empty directory like /mnt, or /mnt/tmp.
You can verify the external disk is the correct one by several methods. One:
nimrodel:~ # file -s /dev/sda1 /dev/sda1: x86 boot sector
Another:
nimrodel:~ # fdisk -l /dev/sda
Disk /dev/sda: 2041 MB, 2041577472 bytes 61 heads, 60 sectors/track, 1089 cylinders Units = cylinders of 3660 * 512 = 1873920 bytes Disk identifier: 0x04030201
Device Boot Start End Blocks Id System /dev/sda1 1 1090 1993608 6 FAT16
We now only have to mount it:
nimrodel:~ # mount -t vfat /dev/sda1 /mnt/tmp nimrodel:~ #
Or:
nimrodel:~ # mount /dev/sda1 /mnt/tmp
(normally it will autodetec the file system type).
Then an "ls /mnt/mnt" will tell you if things worked.
Next step is to copy everything you need. If it is your user's things, log into another terminal (you have six), this time as your normal user, and type "mc". This is a file browser in text mode. In fact, it is so good that I use it in graphical mode, too. Use one of the panels to chose what to copy (the "ins" key selects files), and in the other panel the destination. F5 will copy. You can copy entire directories.
If the destination is an vfat disk, and you want to save user and permission data, you can store to an archive: navigate to a directory (like /home/user), inside, and type "F2". You get a menu, and one of the entries will be "Compress the current subdirectory (tar.gz)". Use it. You get the archive by default in the parent of the current directory.
After you finish, type as root "umount /mnt/mnt". If it refuses (busy) make sure you are not inside that directory in one of the terminals.
A backup is always necessary, but you can try to simply reinstall "gdm". Or, uninstall gdm and install kdm for a while. Or xdm. The problem is that reinstalling gdm perhaps doesn't replace configuration files that you modified.
HTH
- -- Cheers, Carlos E. R.
Great job Carlos.
You are a service to the community!
Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org