Jump to content

theYinYeti

Members
  • Posts

    2151
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by theYinYeti

  1. Oh sorry, my previous post was related to the first link, which suggests making the changes in gconf-editor (Menu : Sytem : Preferences : Configuration editor — the icon of which is a red car being repaired). In this editor, the post instructs to change the value of /apps/panel/applets/clock/prefs/custom_format.

     

    The value I use is what I posted in the previous post. Actually, I now changed it to:

    <span color="#CCFFDD"><small>Semaine %V — %a %d %b — </small><big>%H:%M</big></span>

    (“Semaine†in French means “Week†in English, “lun.†means “mon.â€, “févr.†means “febr.â€).

     

    For example, today the clock reads:

    Semaine 09 — lun. 23 févr. — 09:19

     

    Yves.

  2. I have this exact same problem in Gnome. So far, I manage by choosing a theme that results in a proper contrast (and my clock is in a toolbar on its own).

     

    There is however a solution. I know that. I saw it once. It's just I don't remember where it is… I only remember it involves specifying the expected look (colors, font…) in the GTK rc-file.

     

    Well, now that I'm not alone in this, I'll try and find the solution again. :)

     

    Yves.

  3. I see. So if I understand correctly, the best filesystem is the one with the least written bits for a given amount of data; all else is taken care of in hardware. Does anyone know if there is any way to compare ext2 and vfat in light of this, or if maybe the difference is bound to be negligible?

     

    Yves.

  4. Hello,

     

    I read this article and saw the linked-to video and it was a revelation. Now I'm thinking: I should run my own server.

     

    As my needs are small, I'd like to find a Linux-compatible PC with any computing power, but:

    — less than 100 €, or at least less than 250 €,

    — using less than 5 W if possible, or at most 15 W,

    — and having at least an Ethernet port, two if possible.

     

    Do you have suggestions?

     

    Yves.

  5. If I may intrude on this thread, I have a related question.

    I've read several times in the past two years (but can't remember where), that different Linux filesystems were being designed especially for USB sticks, with emphasis on wear-leveling and performance. Why then are we still stuck with fat or ext2 nowadays?

     

    Yves.

  6. Nexus, I can confirm neddie is right in most circomstances :)

     

    If you move files within the same partition, then only pointers to those files (the inodes, or “TOCâ€) are updated; there's no copy+delete. That's what allows the mv to have this wonderful property within a partition: the move is atomic, at least for each single file (see further down).

     

    If you move files from a partition to another, then indeed this move is longer than a copy because it is a copy AND a delete.

     

    What I don't know is wether inodes are a tree (A -> {B -> {files…}, …}, …) or a list (A, A/B, A/B/files, …). Depending on this, moving a directory (not a single file) may imply updating two inodes (old parent + new parent) or as many inodes as there are entries within the moved directory (recursively). I guess this depends on the filesystem…

     

    Yves.

     

    [edit] If the inodes are a tree, then following on neddie's idea, it might be faster to do so (depending on the number of entries):

    — move A/* except A/B into A/B/,

    — move A/B to TMP_NAME,

    — remove A and rename TMP_NAME to A.

    This would work even if A doesn't only contain B, but the difference is bound to be negligible, so in my opinion not worth the effort.

  7. Anyway, don't be afraid if the new system doesn't boot. The most likely cause of “failure†is for the naming of partitions to change (eg: hdc becomes sdc, or sda becomes sdd…), but that's easy to cure with a LiveCD (hence my suggestion to have one at hand).

     

    Yves.

  8. Basically, that's it. Your current install will be usable on your new setup. Before changing anything to your hardware, though, be sure:

    — to have a good Live CD at hand, such as System Rescue CD,

    — to install the “task-x11†and â€harddrake†packages if they are not already,

    — [edit:DELETE]to ensure that the harddrake startup service (daemon) is enabled,[/DELETE; thanks ffi]

    — that the proprietary packages for your new hardware are installed, especially regarding connectivity (network),

    — that your system is up-to-date.

     

    From there, whatever happens (apart from hardware damage), we should be able to help you.

     

    Yves.

     

    [edit] I forgot: moving /home to the new hard drive will come in a second stage, when your new system has booted fine.

  9. I have a minor but very annoying bug. When my Gnome session is locked, and I try to unlock it by entering the password (this dialog is the “gnome-screensaver-dialog†process), the password-checking seems to take an infinite amount of time. So I have to CtrlAltF2, login as root, killall gnome-screensaver-dialog, CtrlAltF7, and try again.

     

    Sometimes, the bug doesn't happen, sometimes, it happens only once, sometimes twice, sometimes 5 or 6 times. The success always comes eventually, but this is very annoying.

     

    This happens since I switched to Mandriva 2009.0 (2008-10-17), but I didn't report anything so far because my Gnome session is heavily modified, and the home-directory is a bit old (2007).

    But I recently did a fresh install of Mandriva 2009.0 on my “sedentaire†PC, with a new user having a default Gnome session, and the bug happened; that's when I decided it was time to ask.

     

    What are the cause and the cure to this problem?

     

    Yves.

  10. Compiling as root is no big deal if you trust the sources you are compiling.

    However, a Makefile is able to launch anything, even the dreaded “rm -rf /†(DON'T TRY), so a “carefully-crafted Makefile†(as the saying goes) could wipe all your drives if compromized by a cracker and you run it as root.

     

    Yves.

×
×
  • Create New...