Regarding the boot problem:
Not sure if/how that is relevant but you did not mentioned having fdisk
change the boot flag to another device.
>
>
> Schlomo Schapiro wrote:
>
> > In SuSE's admin tool YaST you can choose wether the hardware clock is set
> > to GMT or local time. Maybe you got this wrong ?
>
>
> Nope.
>
>
> >
> > Alternatively make sure that your /etc/rc.config contains something like
> > this:
> >
> > --------------
> > #
> > # Set to "-u" if your system clock is set to GMT, otherwise "".
> > #
> > GMT=""
> >
> > #
> > # Timezone (e.g. CET)
> > # (this will set /usr/lib/zoneinfo/localtime)
> > #
> > TIMEZONE="Israel"
> >
> > -------------------
> >
>
>
> Did that. On my "junk" system, there is no problem; on the main system there is.
>
>
> > Schlomo
> >
> >
> > On Tue, 16 Oct 2001, Shaul Karl wrote:
> >
> >
> >>>Hi folks!
> >>>
> >>>1. I reorganised my system, splitting it into multiple mount points for logistic
> >>>reasons. I tried using Partiton Magic, as I usually do, but on a 30Gb drive it
> >>>bombed out, so there was nothing for it, but to build a new minimal system,
> >>>install bru (my backup choice) and restore everything with overwrite i.e. what
> >>>came out at the other end was (after fiddling fstab and lilo.conf), a perfect
> >>>working system - same as before EXCEPT ... the time (IST, local time (not GMT))
> >>>insists on being two hours ahead of the CMOS clock. I can only correct it per
> >>>boot by manually using date MMDDhhmm etc. Any ideas what might be causing this &
> >>>how to fix? (Env = {SuSE 7.1, kernel 2.4.9, ...}) (I tried a few other nonesense
> >>>settings and always get the same thing. Win 2000 works OK).
> >>>
> >>>
> >>
> >>
> >>Doesn't the fact that Win 2000 works OK means that your CMOS time is adjusted
> >>to show IST?
> >>IIRC, this can explains your time problem: Linux is adjusted to read the CMOS
> >>time as UTC and thus add 2 hours when it needs to show IST.
> >>It could be that at least with Debian, hwclock and/or some setting for the
> >>boot scripts can fixed that. Probably something similar for SUSE.
> >>BTW: hwclock can show you the CMOS actual time. IIRC it can also set the CMOS
> >>time. Should help you to find the cause and fix the problem.
> >>
> >>
> >>
> >>
> >>>2. One of the "junk" systems I put together, has a P166 + 32Mb and a "dafuk" IDE
> >>>primary slot (The machine originally had Win 95 on a 2Gb drive which booted OK
> >>>from the the second IDE slot.) With Linux, I can only boot off a floppy, since
> >>>lilo won't allow an IDE hard disk boot from anthing other than
> >>>/dev/hda<something>. Upon examining the lilo.conf man page I found all sorts of
> >>>interesting tricks for remapping the IDE drive ID's: e.g.
> >>>disk=/dev/hdc bios=0x80
> >>>or
> >>>map-drive=0x82 to=0x80
> >>>
> >>>My root device is /dev/hdc5, and I boot from on /dev/fd0. I would like to use
> >>>the above disk= ... mapping. I modified lilo.conf to root, /dev/hda5, boot from
> >>>/dev/hda2 and put the boot sector on /dev/hda MBR. I also modified fstab to
> >>>reflect the new arrangement. Of coure lilo failed, because the new arrangements
> >>>are meaningless until I reboot, which I cannot do! What to do?
> >>>
> >>>Thanks to the people who supplied the "junk". I'm still looking for Pentium
> >>>stuff, MB with slot 7 or better.
> >>>
> >>>Regards,
> >>>
> >>>
> >>>Dan Feiglin
> >>>
> >>>
> >>>=================================================================
> >>>To unsubscribe, send mail to [EMAIL PROTECTED] with
> >>>the word "unsubscribe" in the message body, e.g., run the command
> >>>echo unsubscribe | mail [EMAIL PROTECTED]
> >>>
> >>>
> >>
> >
>
>
--
When responding, please qoute my entire message.
Shaul Karl <[EMAIL PROTECTED]>
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
