AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080403170422.47bacc49@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0941AACD@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 3 Apr 2008 17:04:53 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Subject: Re: saving clock
Message-ID: <20080403170453.7131a748@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0941AACD@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0941AA6C@onstor-exch02.onstor.net>
	<20080403165307.698f3cef@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0941AAB6@onstor-exch02.onstor.net>
	<20080403170010.3d3d7f16@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0941AACD@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 3 Apr 2008 17:02:02 -0700 "Maxim Kozlovsky"
<maxim.kozlovsky@onstor.com> wrote:

> 
> 
> >-----Original Message-----
> >From: Andy Sharp
> >Sent: Thursday, April 03, 2008 5:00 PM
> >To: Maxim Kozlovsky
> >Subject: Re: saving clock
> >
> >On Thu, 3 Apr 2008 16:53:46 -0700 "Maxim Kozlovsky"
> ><maxim.kozlovsky@onstor.com> wrote:
> >
> >> 10.2.10.2
> >>
> >> >-----Original Message-----
> >> >From: Andy Sharp
> >> >Sent: Thursday, April 03, 2008 4:53 PM
> >> >To: Maxim Kozlovsky
> >> >Subject: Re: saving clock
> >> >
> >> >On Thu, 3 Apr 2008 16:10:25 -0700 "Maxim Kozlovsky"
> >> ><maxim.kozlovsky@onstor.com> wrote:
> >> >
> >> >> Saving the system clock..
> >> >> Cannot access the Hardware Clock via any known method.
> >> >>
> >> >> What am I missing? I have done fresh install from Larry's
> >> >> rootfs.
> >> >
> >> >Can I log into your system?
> >
> >It's because you're on a bobcat.  I think that the bobcat platform
> >code needs some changes to work with the 2.6.22 rtc subsystem, and I
> >never bothered to go back and do it.
> [MK] 
> Well it needs to work somehow, the system is unusable currently.

I doesn't have any effect on the useability of the system.

I've heard that bobcat/linux doesn't work these days because of
problems in the txrx/fp code.
