Malcolm Ferguson wrote:
[snip]
2) This makes me wonder why we don't restart affected processes after
applying security patches. For instance, today's OpenSSL patch seemed
to affect ssh and bind. Well, I had to restart them as part of remount
/usr ro. Presumably those processes were still usin
On a couple of Woody systems I put together recently I followed advice
I'd seen that recommended mounting /usr as read-only. I haven't seen a
security patch yet that has left me able to remount /usr read-only,
which is quite annoying. I've configured a Dpkg Post-Invoke step to
My apt.conf said:
Post-Invoke {"mount -o remount,ro /usr";}.
So dselect changed /usr from rw to ro.
Thanks. Hans Gubitz
On Thu, Dec 09, 1999 at 07:55:40PM +0100, Hans Gubitz wrote:
> On potato /usr is told to be a Read-only file system ?!
>
> My fstab says: /dev/hda7 /usr ext2 defaults 0 2
>
> On potato /usr is told to be a Read-only file system ?!
>
> My fstab says: /dev/hda7 /usr ext2 defaults 0 2
>
The defaults of mount (8) in this context is rw.
IMHO, having /usr mounted ro is only a suggestion. Where have you read that?
Hi,
> On potato /usr is told to be a Read-only file system ?!
>
> My fstab says: /dev/hda7 /usr ext2 defaults 0 2
man mount:
defaults
Use default options: rw, suid, dev, exec,
auto, nouser, and async.
So, what's wrong here?
Regards, Thoma
On potato /usr is told to be a Read-only file system ?!
My fstab says: /dev/hda7 /usr ext2 defaults 0 2
--
Hans Gubitz <[EMAIL PROTECTED]>
6 matches
Mail list logo