You're a legend!! /etc/lilo.conf had the 'i' attribute on making it
read-only (and various other things).
Thanks, and thanks to the others that responded to the soundcard mail.
Jin
Luke Szymanski wrote:
> lsattr /etc/lilo.conf
> -------- /etc/lilo.conf
> If you don't get '--------' man chattr
>
> If it's not that, I don't have a clue.
> Luke.
>
> On Thu, 1 Feb 2001, Jin Ting Liew wrote:
>
>> After reading an article on Linux security some time ago, I put some
>> extra security measures on my server (the same one that has the problem
>> with Redhad network update agent). This included protecting
>> /etc/lilo.conf. I am not sure what i did to it, but even as root or in
>> single user mode i cannot do anything to this file but read it. Even
>> the redhat 7 upgrade had problems with this file and aborted (causing a
>> huge headache, but this has been resolved).
>>
>> I am certain that the drive is mounted read / write and that I have the
>> appropriate permissions to write to the file.
>>
>> If anyone knows what I have done it would be great if you could let me
>> know = )
>
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
