Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Dec 2001 00:25:07 -0600
From:      "Stephen Hilton" <nospam@hiltonbsd.com>
To:        "FreeBSD Questions" <freebsd-questions@FreeBSD.ORG>
Cc:        "Michael Silver" <michaelas@yahoo.com>
Subject:   RE: Unable to restore vi (among others)
Message-ID:  <KPEMJADBBBFPDEDOIOMBEENADNAA.nospam@hiltonbsd.com>
In-Reply-To: <015c01c17e07$290181c0$0200000a@silvertriad>

next in thread | previous in thread | raw e-mail | index | archive | help
Michael Silver wrote on Wednesday, December 05, 2001 9:36 PM

> > > I made a full dump of my /usr dir, however when trying to restore the
> > > /usr/bin (and a few others) I get errors with only certain files:
> > >
> > > ./bin/man: cannot create file: Operation not permitted
> >
> > Your secure level is set greater than -1 in your /etc/rc.conf file, the
> > files you have listed normally have the schg flag set on them. To see
> this:
> >
> > cd /usr/bin
> > ls -lao | more.
>
> I am not sure this is the problem.  According to 'sysctl
> kern.securelevel' I
> am at level -1 already.
>
> ...Michael...
>
What is the syntax used for your dump and restore commands Michael?  from
looking at the restore man page there is a -u option:

-u  When creating certain types of files, restore may generate a
    warning diagnostic if they already exist in the target directory.
    To prevent this, the -u (unlink) flag causes restore to remove
    old entries before attempting to create new ones.

And also:

-r  Restore (rebuild a file system).  The target file system should
    be made pristine with newfs(8), mounted and the user cd'd into
    the pristine file system before starting the restoration of the
    initial level 0 backup.  If the level 0 restores successfully,
    the -r flag may be used to restore any necessary incremental
    backups on top of the level 0.  The -r flag precludes an interac-
    tive file extraction and can be detrimental to one's health if
    not used carefully (not to mention the disk).

I do not know if this is the answer to your problem, but hope this may help.

Also setting kern_securelevel_enable="NO" in your /etc/rc.conf and rebooting
should help determine if secure level is a problem.

Regards,

Stephen Hilton


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?KPEMJADBBBFPDEDOIOMBEENADNAA.nospam>