Jump to content

scarecrow

Platinum
  • Posts

    5150
  • Joined

  • Last visited

Posts posted by scarecrow

  1. I'm managing two Debian Squeeze (AKA testing) servers. I am always updating them via aptitude safe-upgrade, and the upgrade included the kernel (just the one of them, because the other is using a statically built customized kernel made by OVH).

    Squeeze is IMHO much better that Ubuntu Server because of its rolling nature- it's quite unlikely to break the system by just safe-upgrading. Actually the only thing that worried me was Squeeze going from old good grub to grub2, but fortunately enough grub-legacy is still in the repos, and it will stay there for a long time.

  2. There is no clean way. Some people had success using a windows application named zalternator under WINE, but as mentioned it won't work with newer Zune firmware revisions. The only other way is full OS emulation (VirtualBox/VMWare).

    This is because of the proprietary, closed format of MTP protocol Microshaft is using on Zune.

  3. I am not really an Amarok fun. Whoever is may try Clementine, which immitates Amarok 1.4.X, but without any KDE dependency (just QT4), while Foobar2000 (arguably the best windoze music manager ever) works just fine under WINE- preferrably with OSS4 instead of alsa.

  4. The kernel itself shouldn't be responsible. However, there could be a gcc update, and some lib32-something compatibility libs being broken.

    Try running a few of your segfaulting 32-bit apps like "$ strace -o ~/errorlog programname"

    strace should be installed of course, and you can also try/install gdb, which cooperates with the KDE4 crash handler.

    Then, you can pick the full debugging info from the textfile "errorlog" located at the root of your user partition. This logfile can be HUGE.

  5. The best protection would be to encrypt the file systems and use a BIOS password but in a business environment that would require someone with the passwords to be on site at all times just in case.

    Root FS can be encrypted using a keyfile, which can either be stored in some network place, or in some USB-stick held by the computer operator. So, this isn't an issue at all. Encryption, while not a bulletproof solution, is still an excellent choice for corporate environments.

    I'm talking about kernel-based LUKS/dm-crypt filesystem encryption, but there are other effective solutions as well.

  6. Add ppa:kubuntu-ppa/backports to the repositories.

    Rather an odd piece of advice to give to a Mandriva user! :P

    KDE 4.4 is simply the best DE ever, and 4.4.1 cured many outstanding bugs. Personally, I only had one issue with KDM (logout/reboot/halt not working properly after upgrade), but the cure was really simple: dleteing kdmrc, and reinstalling KDM. Now, it's working perfectly (using both plain Archlinux/KDE 4.4.1 on my laptop, and Kdemod 4.4.1 on my desktop).

  7. Inkscape has a LOT of GNOME dependencies, and so installing a non-backport RPM is highly likely to fail.

    A safer solution is (as suggested) to install the latest available from backports, or compiling it yourself leaving out all unnecessary GNOME deps.

×
×
  • Create New...