01-20-2011
I would guess that one or the other machine has to be aware of both user accounts.
While mounting the volume on the Mac is apparently an option the userMac account does not have write permissions for the files on that mounted volume.
Try mounting the volume on the mac as userBSD?
Try adding userMac (with the same userMac password) as an account on the freeBSD machine?
Try adding userBSD (with the same userBSD password) as an account on the Mac?
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
When I try to run a script with ". "(dot space) in my home, it gives me error ".: Permission denied".
Any explanation for this behaviour?
Thanks in advance,
-Ashish (3 Replies)
Discussion started by: shriashishpatil
3 Replies
2. UNIX for Dummies Questions & Answers
HI All,
I am using solaris
i created a user adam and updated his permissions
in vi sudoers file as follows
adam ALL=(ALL) NOPASSWORD: ALL
...........
when i create user by logging as sudo user .
$ sudo useradd -d /home/kalyan -m -s /bin/sh kalyan
sudo: not found
... (6 Replies)
Discussion started by: kalyankalyan
6 Replies
3. UNIX for Advanced & Expert Users
guest@ulidtko:~$ id
uid=126(guest) gid=134(guest) groups=134(guest)
guest@ulidtko:~$ ls -ld /home
drwxr-xr-x 8 root root 4096 May 12 19:47 /home
guest@ulidtko:~$ ls -l /home
ls: cannot open directory /home: Permission denied
guest@ulidtko:~$ cat /proc/mounts
rootfs / rootfs rw 0 0... (4 Replies)
Discussion started by: ulidtko
4 Replies
4. Solaris
Let me preface with I am semi-new to Solaris. I work with it in the labs at work and that's about my extent (although I run Linux at home).
Well, a week ago security comes around with updated requirements, some of which are the need to audit all failures. For the life of me I cannot get a... (0 Replies)
Discussion started by: mph275
0 Replies
5. Linux
Hello friends,
I have scratched my system and after that when I am trying to access the console via root login it's failing with an error message of "permission denied". I am able to access the other login, I am having only problem with root and some other user login. I am using an telnet... (2 Replies)
Discussion started by: sanoop
2 Replies
6. UNIX for Advanced & Expert Users
Hello friends,
I have scratched my system and after that when I am trying to access the console via root login it's failing with an error message of "permission denied". I am able to access the other login, I am having only problem with root and some other user login. I am using an telnet... (7 Replies)
Discussion started by: sanoop
7 Replies
7. Solaris
hello everyone,
I am new on unix systems. I am working with a Solaris 10 OS.
When i try to change netmask on certain interface:
I get:
How can i enable permission for changing that ? I have administrator privileges.
Your help is much appreciated.
thanks, (13 Replies)
Discussion started by: pablod76
13 Replies
8. OS X (Apple)
Hi,
I hope this is the correct section in the forum to post as I'm trying to SSH from my MacBook.
I was looking to see whether ssh on my jailbroken iPhone 6s (10.3.1) still works fine and was following this old reddit guide. I installed OpenSSH&OpenSSL from Cydia and changed the password using... (7 Replies)
Discussion started by: hss1
7 Replies
LEARN ABOUT FREEBSD
rescue
RESCUE(8) BSD System Manager's Manual RESCUE(8)
NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with FreeBSD 5.2, there is a real possibility that the standard tools in /bin and /sbin may become
non-functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /sbin, and /usr/lib, possibly mounting a FreeBSD rescue or ``live file system'' CD-ROM
(e.g., disc2 of the officially released FreeBSD ISO images) and copying files from there. Once it is possible to successfully run /bin/sh,
/bin/ls, and other standard utilities, try rebooting back into the standard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. To build a
FreeBSD system where space is critical, /rescue can be used as a replacement for the standard /bin and /sbin directories; simply change /bin
and /sbin to be symbolic links pointing to /rescue. Since /rescue is statically linked, it should also be possible to dispense with much of
/usr/lib in such an environment.
In contrast to its predecessor /stand, /rescue is updated during normal FreeBSD source and binary upgrades.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO
crunchgen(1), crash(8)
HISTORY
The rescue utilities first appeared in FreeBSD 5.2.
AUTHORS
The rescue system was written by Tim Kientzle <kientzle@FreeBSD.org>, based on ideas taken from NetBSD. This manual page was written by
Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the ncurses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD
July 23, 2003 BSD