Visit Our UNIX and Linux User Community

Full Discussion: Mac OS X Question
Top Forums UNIX for Dummies Questions & Answers Mac OS X Question Post 24713 by amicrawler on Wednesday 17th of July 2002 12:01:20 AM
Old 07-17-2002
Question BSD

mac os X is ran under a mock kernal of bsd it's called darwin os X is under the FreeBSD 4.5 so yes but you must run under the shell to do it
amicrawler
 
Test Your Knowledge in Computers #500
Difficulty: Easy
Comments in code provide a high-level description of what a block of code, function, or program does.
True or False?

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Mac OSX question

Hi. Is it possible to execute a Cocoa (or Carbon or eaven a classic) program for mac OSX in the terminal window? OSX finder can sometimes be so busy that it wont respond for several minutes, ie if you are uploading a very big file/files to a afp server. Then it would have been nice to start... (7 Replies)
Discussion started by: nicke30
7 Replies

2. UNIX for Dummies Questions & Answers

Mac OS X/UNIX/Terminal Question

Hey everyone I'm new to UNIX due to the new Mac OS X operating system and would like some help. I'm trying to send an email via the UNIX-Shell-Terminal i Mac OS X, (it's called darwin) How do I do that? When I enter the Command mail I can send messages to root and with the command -forward... (4 Replies)
Discussion started by: onkel
4 Replies

3. UNIX for Dummies Questions & Answers

mac os question

i would like to ask those who know of the subject to please answer this question. could it be possible to somehow run mac os x in a newly built computer of mine. the computer i made myself (a clone) and it runs linux just nicely. would there be some way to emulate mac os x to be compatible for... (2 Replies)
Discussion started by: ChildrenoftheOS
2 Replies

4. UNIX for Dummies Questions & Answers

Help with Unix/Mac OS question

Hope someone can help give me a clue what is going on here, I work in a Macintosh computer lab in a college institution and currently we run Mac G4's with what is becoming dated software but everything has been fine until recently, when a new student purchased a new Mac G5 system in order to do her... (1 Reply)
Discussion started by: kd4rmm
1 Replies

5. Solaris

Cisco Mac Question

When I do a snmpwalk of my router the mac address are not what I expected. Then return looking like this How would you convert them to 001c.c92a.b677 when a shell script? (3 Replies)
Discussion started by: mrlayance
3 Replies

6. IP Networking

Mac OS X IP traffic shaping question

Not sure if this considered traffic shaping or not, so I'll appreciate the enlightenment... Setup- Mac Pro, Mac OS X 10.5.6, Crashplan Pro Backup server. the Mac Pro has 2 E-net ports, en0, en1. Both E-net ports are connected to the same network, different IP's. Problem- We are planning to... (1 Reply)
Discussion started by: pbenware
1 Replies
SYSTEMD-NSPAWN(1)						  systemd-nspawn						 SYSTEMD-NSPAWN(1)

NAME
systemd-nspawn - Spawn a namespace container for debugging, testing and building SYNOPSIS
systemd-nspawn [OPTIONS...] [COMMAND] [ARGS...] DESCRIPTION
systemd-nspawn may be used to run a command or OS in a light-weight namespace container. In many ways it is similar to chroot(1), but more powerful since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and the host and domain name. systemd-nspawn limits access to various kernel interfaces in the container to read-only, such as /sys, /proc/sys or /sys/fs/selinux. Network interfaces and the system clock may not be changed from within the container. Device nodes may not be created. The host system cannot be rebooted and kernel modules may not be loaded from within the container. Note that even though these security precautions are taken systemd-nspawn is not suitable for secure container setups. Many of the security features may be circumvented and are hence primarily useful to avoid accidental changes to the host system from the container. The intended use of this program is debugging and testing as well as building of packages, distributions and software involved with boot and systems management. In contrast to chroot(1) systemd-nspawn may be used to boot full Linux-based operating systems in a container. Use a tool like debootstrap(8) or mock(1) to set up an OS directory tree suitable as file system hierarchy for systemd-nspawn containers. Note that systemd-nspawn will mount file systems private to the container to /dev, /run and similar. These will not be visible outside of the container, and their contents will be lost when the container exits. Note that running two systemd-nspawn containers from the same directory tree will not make processes in them see each other. The PID namespace separation of the two containers is complete and the containers will share very few runtime objects except for the underlying file system. OPTIONS
If no arguments are passed the container is set up and a shell started in it, otherwise the passed command and arguments are executed in it. The following options are understood: --help, -h Prints a short help text and exits. --directory=, -D Directory to use as file system root for the namespace container. If omitted the current directory will be used. --user=, -u Run the command under specified user, create home directory and cd into it. As rest of systemd-nspawn, this is not the security feature and limits against accidental changes only. --private-network Turn off networking in the container. This makes all network interfaces unavailable in the container, with the exception of the loopback device. EXAMPLE 1 # debootstrap --arch=amd64 unstable debian-tree/ # systemd-nspawn -D debian-tree/ This installs a minimal Debian unstable distribution into the directory debian-tree/ and then spawns a shell in a namespace container in it. EXAMPLE 2 # mock --init # systemd-nspawn -D /var/lib/mock/fedora-rawhide-x86_64/root/ /sbin/init systemd.log_level=debug This installs a minimal Fedora distribution into a subdirectory of /var/lib/mock/ and then boots an OS in a namespace container in it, with systemd as init system, configured for debug logging. EXIT STATUS
The exit code of the program executed in the container is returned. SEE ALSO
systemd(1), chroot(1), debootstrap(8), mock(1) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer systemd 10/07/2013 SYSTEMD-NSPAWN(1)

Featured Tech Videos

All times are GMT -4. The time now is 04:48 AM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy