Linmodems Mailing list Archives

	Web archives.linmodems.org

Return-Path: <stodolsk@rcn.com>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 17038 invoked from network); 30 Jun 2001 17:59:45 -0000
Received: from smtp03.mrf.mail.rcn.net (207.172.4.62)
  by www.linmodems.org with SMTP; 30 Jun 2001 17:59:45 -0000
Received: from 66-44-16-178.s1702.apx2.lnh.md.dialup.rcn.com ([66.44.16.178] helo=rcn.com)
	by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.30 #2)
	id 15GP1y-0004hy-00 ; Sat, 30 Jun 2001 13:59:43 -0400
Sender: marv
Message-ID: <3B3E1367.DE14BD8B@rcn.com>
Date: Sat, 30 Jun 2001 12:59:03 -0500
From: Marvin Stodolsky <stodolsk@rcn.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.4.5 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Araneda, Dorian" <dorian.araneda@intel.com>
CC: "'discuss@linmodems.org'" <discuss@linmodems.org>
Subject: Re: what is  the Hamregistry used by the Intel HaM driver.
References: <F55DFDA7A48DD411AC6A00A0C95D746E016C5D09@fmsmsx63.fm.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Linux on laptop folk (like me) will often make substantial configuration
changes  without rebooting, such as alternate use of ppp and ethernet,
so its not obvious that a Registry with Persitance info has much
desirability.  Startup applications, the initial size and positions of
Xwindows can be preset, and almost all applications have default
settings capablity. Thus the roles for Persistance don't seen great. 

For MS Windows, which crashes unpredictable but frequently, the virtue
of such a Persistance Registry is obvious.  But for much stabler
Linux/Unix systems, forced reboots are very RARE.  There might however
be some advantagers, for those doing crash prone development work.

Does hamregistry have any role at all in on-line HaM functionality? If
not I'd rather have free ram for other functionalities.

MarvS

>"Araneda, Dorian" wrote:
> 
> hamregistry provides the ham driver
> with data persitance.  the mechanism  emulates the windows registry for the
> linux driver.
> 
> the windows driver stores data that it needs from reboot to reboot
> in the registry.
> items like the eeprom data (at&w  profile storage and init profile)
> and homologation settings.
> 
> if the app is not running, there will be no persitance between reboots
> and the driver will have to depend on hard coded defaults on initalization.
> 
> according to what i read  about linux module data persistance support,
> it is still under debate whether it will be supported.  but this may be old
> news.
> 
> There was a hint in the 2.4 kernel code for a module persistance struct
> pointer and it had a "//TBD" next to it.
> 
> It may be that i am wrong and there is support for it.
> 
> if there is, can anyone share info so that i can try to implement it?
> 
> personal opinion: if i am right about linux not supporting persitance,
> I think the linux kernel needs to do a little catching up to the idea of a
> registry and
> not text file initialization and configuration.
> (maybe it is a conspiracy created by script writers?)
> 
> -----Original Message-----
> From: Marvin Stodolsky [mailto:stodolsk@rcn.com]
> Sent: Friday, June 29, 2001 3:50 PM
> To: Araneda, Dorian
> Subject: Hamregistry
> 
> Dorian,
> 
> Could you briefly explain what the funtion of hamregistry is.
> Preferring a lean kernel, I'm managinging it with the drivers through a
> line in /etc/modules.conf:
> pre-install ham hamregistry
> post-remove ham hamregistry
> 
> If the answer is of general interest, respond to the List.
> 
> Marv