Re: weired issues of debian squeeze (base system)
On Mon, Dec 13, 2010 at 12:40 AM, Geronimo <geronimo013@arcor.de> wrote:
> Hello,
>
> I have two separate installations of debian squeeze, each on a different
> harddisk. More by accident, than by intention it happens, that each
> installation has its own grub entry in the mbr of its harddisk.
> Both systems use ext3 and grub2 and hwclock runs at UTC.
>
first, some side comments that aren't going to answer your questions:
why not use a vm? virtualbox is free and easy to setup, there is also
kvm and a kernel module that allows *nix systems to run at processor
speeds for qemu. second, you can install both kde and gnome under the
same environment and it works just fine (or as good as you currently
have it) - it's what i used to do since i had so many packages from
each environment that i had 90%+ of each system installed anyway.
Now...
> 1. On both installtions it is impossible to boot the other squeeze
> installation. First I have to enter BIOS and reorder the boot sequence of the
> harddisks to enable the start of the other grub - so each grub can boot
> systems on the same harddisk only!
> I'm sure, that was not the case with grub1 and hints on how to get a system
> from a different harddrive booted are very appreciated!
>
pick a grub install - doesn't matter which, just pick one. add the
second hdd to the config so that it shows up on the menu. if you need
a reference to a howto, i'm sure i can find one in a few minutes...
> 2. One squeeze installation is a gnome system (with some kde apps added) and
> the other system is a kde (with some gnome apps added). As mentioned, time is
> UTC based on both installations.
> When I reboot the gnome system and change BIOS to use kde system the initial
> filesystem check claims, that the last mount time from superblock is in future.
> When the kde is up and running - its time is wrong by one hour - and I could
> not achieve to set the time, that it is right after next reboot.
> So I had to install ntp to get right times on kde
>
no idea. i know this happens to my VMs when i put them to sleep and
such, but i don't really care since they are for testing and i would
never run time sensitive apps on a vm (time skew in vm is a known
issue).
Reply to: