Jump to content

sermat

Members
  • Posts

    46
  • Joined

  • Last visited

Posts posted by sermat

  1. iphitus: yes, you are absolutely correct. I just got home and booted metisse using qemu, and I didn't put a stop watch on it, but it took maybe 10 + minutes just to get the login screen (and this is a 2.4 GHz PIV machine.

     

    By the way, what is the login username/password for Metisse?

     

    Any way, my thanks go to pmpatrick for pointing me to try qemu, which i had never tried before.

     

    Regards to all,

    sermat.

  2. Thanks for the clarification re. Arch. Although I am not a Linux CLI expert, I have now lots of time on my hands (I just turned 60 years of age and just retired) so I just might download Arch and prove (at least to myself) that an oooold dog CAN learn some new tricks.

    Any way, you have been quite kind and I do thank you for your help.

    Regards,

    serge.

  3. Thanks scarecrow. Yes, I should have noticed the Arch avatar (Arch is based on Slackware, isn't it ?). The main reason i'm (have been) using Mandriva is their Control Center. For example, it configures my printers so easily. Other distros had trouble with that.

    Oh, just to note, re. the rpmdrake/KDE problem: I'm using Gnome now and all is well.

    REgards and thanks again,

    serge.

  4. Hi again, scarecrow:

    Ehmmm, hard to answer. It's both a bug and "expected behavior".

    GTK simply hates some elements of KDE themes (remember that your Mandy desktop is KDE, while urpmi is a bunch of perl scripts with a gtk graphical interface...), and bangs when the desktop theme uses some "strange" elements.

    If do not wish to change desktop theme every time you want to use mcc, then you should either:

    - Logout and log back in using another desktop manager, say icewm, or

    - Ask Mandy developers doing a qt4 port of mcc.

    I won't do any of the above, as I have stopped using Mandriva effectively three years ago, but... you can make a choice.

    Regards.

    OK, In the last half hour I experimented a bit, and can confirm that switching KDE theme to "classic" causes rpmdrake to crash. Now I don't know if the following is connected to this also, but Seamonkey crashes so often on certain web sites. But Konqueror does not crash on these same sites.

     

    Also, you say "...as I have stopped using Mandriva effectively three years ago", May I ask, and I hope I'm not intruding, what are you using now?

     

    Thanks again for your help,

    serge.

  5. Have you changed desktop theme recently?

    Reset it to default and try again.

     

    scarecrow !!! Man you are good !!! This is exactly what I did (i.e., changed the theme a couple of days ago). And your suggested fix solved the problem !!! Thanks a million. But just a stupid question: is this a bug, or expected behavior?

     

    Thanks and best regards,

    serge.

  6. Hi to all: Just a quick problem: I must have mucked up something on my 2007, because when I run "rpmdrake" I get this error:

     

    [root@localhost ~]# rpmdrake &

    [1] 4565

    [root@localhost ~]# examining synthesis file [/var/lib/urpmi/synthesis.hdlist.update_source.cz]

    examining synthesis file [/var/lib/urpmi/synthesis.hdlist.main.cz]

    examining synthesis file [/var/lib/urpmi/synthesis.hdlist.contrib.cz]

    Gtk-WARNING **: Theme file for default has no name

    Gtk-WARNING **: Theme file for default has no directories

     

    [1]+ Segmentation fault (core dumped) rpmdrake

    [root@localhost ~]#

     

     

    Can anyone help.

    Regards,

    serge.

  7. The fully auto mode will probably never satisfy a coffee snob like me.... but that doesn't make anyone elses enjoyment of it any less!

     

    Hi Gowator: There probably isn't a better person to ask for an advice on how to make a great cup of coffee then a Parisian, like you. Would you care to share the secret? (especially for us, Canadians, who drink bad coffee most of the times).

    serge.

  8. Hi ianw1974: I'm extremely thankful and obliged for your help.

     

    It doesn't look like /etc/fstab needs any adjusting to make accessing the RAID1 volumes (ext3 and vfat) work --- it's all perfect as is.

     

    Just to let you know, I've just completed the setup of my little home server based on Mandriva 2007 and, with your help, it looks like a total success !!! I do not want to waste space on this forum, but feel so good about this, that will briefly summarize my setup:

     

    1) Computer is an old PII-300 (300 MHz, 4 GB hard drive), that I picked up for free on my street during last week's garbage day.

     

    2) OS is Mandriva 2007 that installed absolutely perfectly.

     

    3) Main back up storage is RAID1 set of two 200 GB hard drives. This was one item that required a bit of "fiddling", but was solved with ianw1974's generous help. Note: applying the KISS principle, I'm leaving the RAID1 setup in /etc/rc.d/rc.local for now, and will try to fiddle with the initrd image later).

     

    4) apache is configured to serve directories, so I can put Mandriva DVD "tree" on this server, so I can install Mandriva on my other PC's from this server, by just using the boot.iso CDRW and selecting the HTTP install method

     

    5) It's also a print server - MCC was used to absolutely effortlessly configure and share the Konica-Minolta 1400W printer (new cost at Future Shop is CAN$ 69.95). No other Linux Distro I tried could do that !!!

     

    6) Samba configuration took a bit of playing with but it's perfect now, and I can access this server from a client PCs running Linux or Windows.

     

    Again, thanks a lot ianw1974 !!!

     

    Best regards to all,

     

    serge.

  9. Hi again: Here are the answers/facts:

    1) When I do not have my "fix" with rc.local, mdadm is still started OK. But as I mentioned, I do not get any "md" devices in /dev/. So I'll get reading on your article, and try to rebuild initrd.img. I'm just wondering as to why SUSE and Fedora do this "/dev/md business" automatically and Mandriva is not?

     

    2) Regarding the fstab and the type of data I store on ext3 and vfat: it's everything, because, this is is going to be my main back-up system, so I'll be dumping all kind of stuff to md0 and md1: music, video, text, graphics, etc.

  10. Hi ianw1974: As I reported above, I had complete success by following your instructions. But just one problem: when I reboot the PC. the /dev/md0 and /dev/md1 are gone. So I did the following, and it works: I added this to the /etc/rc.d/rc.local:

     

    mknod /dev/md0 b 9 0

    mknod /dev/md1 b 9 1

    mdadm --assemble --scan

    mount /dev/md0 /mnt/md0

    mount /dev/md1 /mnt/md1

     

    And all is perfect now, even after reboot.

    Could you just comment weather this is the proper way to do it?

     

    Many, many thanks,

    serge.

  11. This is incredible: followed your instructions to the letter and ALL is perfect !!!!! I see data on my RAID1 hard drives without a problem. Here is the output of the mount command as you requested:

     

    #mount [Enter]

    /dev/hda5 on / type ext3 (rw)

    none on /proc/bus/usb type usbfs (rw)

    none on /sys type sysfs (rw)

    /dev/md0 on /mnt/md0 type ext3 (rw)

    /dev/md1 on /mnt/md1 type vfat (rw)

    #

     

    As you mentioned, you could suggest how to edit the /etc/fstab file. Would you, please.

     

    serge.

  12. Hi ianw1974: Thank you so much for offering to help! Yes it's software RAID1 and here is the output that you requested ( this output is from SUSE 10.1 and not Fedora as I originally mentioned, the reason being that I replaced Fedora last nite with SUSE 10.1):

     

    cat /etc/fstab

    /dev/hda1 / reiserfs acl,user_xattr 1 1

    /dev/hda2 swap swap defaults 0 0

    proc /proc proc defaults 0 0

    sysfs /sys sysfs 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,sync 0 0

     

    cat /proc/mdstat

    Personalities : [raid1]

    md1 : active raid1 hdc2[0] hdd2[1]

    52660992 blocks [2/2] [uU]

     

    md0 : active raid1 hdc1[0] hdd1[1]

    146480512 blocks [2/2] [uU]

     

    unused devices: <none>

     

    Again, thanks a lot,

    serge.

  13. Hi to all. I would be very grateful if somebody could help me. Here's the scenario: I have two hard drives with raid1 filesystem on them. But when I boot the PC with Mandriva 2006, they do not appear in the /dev/ directory at all. Just for refernece, when I boot the same PC with a Fedora, they do show in the /dev/ directory without me having to do anything. The reason I want this to work on Mandriva is that I'm deciding that Mandriva is the best and most effortless Linux distro to work with, and I am thinking to adopt Mandriva as my only distro for the time being.

    Many thanks,

    serge.

     

     

    [moved from Software by spinynorman - welcome aboard :)]

×
×
  • Create New...