On Dec 29, 2007, at 5:41 PM, Darrick Hartman wrote:

> Lonnie Abelbeck wrote:
>> On Dec 29, 2007, at 2:57 PM, John Novack wrote:
>>
>>> When one uses the web editing of rc.conf, and ignores or forgets
>>> the instruction elsewhere to set the filesystem first to rw, it
>>> seems one is able to bumble right in, successfully edit and save
>>> the file without first setting to rw, then after a reboot, Linux
>>> complains that the filesystem is dirty.
>>> Since it is complaining about hda1, which is the boot device, there
>>> is no way to fix without booting from a different device.
>>> I fear that this can be a real tripping point for those of us who
>>> often are in a fog, and even worse for those who can't even figure
>>> out how to fix it.
>>> Shouldn't the web editing feature either set the filesystem to rw
>>> first, or refuse to allow the save? It seems to me that even
>>> OPENING the file without making any changes gives the same bad  
>>> result
>>>
>>> Or am I completely off base here?
>>>
>>> John Novack
>>
>> John,
>>
>> The astlinux web interface might be handy to view your rc.conf ( and
>> other /etc/asterisk/ files ), but I would not use (trust) it to edit
>> files.  Besides, /etc/rc.conf is a link to a temp file in memory.
>> (Possibly the Save As: and Submit_Changes should be removed in future
>> versions?)
>
> That's not entirely true.  If you don't have a key disk, the rc.conf
> file is on a ram disk.  However, if you do have a key disk setup, the
> symbolic link does point to the file on the key disk and is  
> editable via
> the web interface.

That's not entirely true. ;-)

If a person has a rc.conf.d directory on the keydisk (as I do) the  
contents are copied to ramdisk.

--- from /etc/rc ---
cp -a /mnt/kd/rc.conf.d/*.conf /tmp/etc/rc.conf.d/
...
cat /tmp/etc/rc.conf.d/*.conf >> /tmp/etc/rc.conf 2> /dev/null
------

But, Darrick is correct for a single /mnt/kd/rc.conf keydisk file,  
that is linked to the system rc.conf file, and when /etc/rc.conf is  
edited it 'sticks'.

Lonnie

BTW:  Using the keydisk rc.conf.d directory method has the advantage  
of automatically including any newly defined variables in /stat/etc/ 
rc.conf from version to version, and my rc.conf.d/z.local.conf file  
entry only needs to include any differences to the master file.  I  
like that.




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to [EMAIL 
PROTECTED]

Reply via email to