Sponsored Content
Top Forums UNIX for Dummies Questions & Answers ScreenSaver into Background Question Post 302501758 by Corona688 on Friday 4th of March 2011 04:41:17 PM
Old 03-04-2011
/ tells it to go all the way to the root of the disk. You'd have to type the whole thing:

/System/Library/Frameworks/ScreenSaver.framework/Resources/ScreenSaverEngine.app/Contents/MacOS/ScreenSaverEngine -background ...which actually would work, if you wanted to make it all on one line. You wouldn't even need to CD that way, I think.

You need ./ because the shell doesn't run things in the current directory. You have to tell it 'in the current directory' explicitly. This is a security feature (so someone can't drop files in your directory and have you unknowingly run them.)
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Screensaver and 'fortune'

(SuSE Linux 8.2 Personal) I'm sure the answer to this will be simple, but it's been driving me insane for the last couple days. SuSE 8.2 comes with a bunch of screensavers, but a handful of them just repeatedly display 'sh: line 1: fortune: command not found'. I've been scouring endlessly... (4 Replies)
Discussion started by: Darkstripes
4 Replies

2. Filesystems, Disks and Memory

how to create screensaver for unix in java??

i would like to create a screensaver for unix platform in java. with an interface through which i can change the kinds of *.jpg images that r being displayed and also the background music. i don't know how to go about it. can anyone help please :confused: (0 Replies)
Discussion started by: madatyou1
0 Replies

3. UNIX for Advanced & Expert Users

Move mouse to disable screensaver?

All XKCD jokes aside, can a feature be added to a bash script to move the mouse every X seconds to prevent the screensaver from activating? As is it, I launch mplayer through a script that sets some preferences (such as -zoom). Can I add something to that script which wiggles the mouse? Relevant... (1 Reply)
Discussion started by: dotancohen
1 Replies

4. Linux

Question about background processes

Hi! First of all, let me warn you I'm quite new to the world of LINUX and Operating Systems understanding, so that's why I pose these newbie and stupid qustions... Anyway, I'm trying to build my own simple shell in C and I'm getting some problems in implementing the background process ('&')... (10 Replies)
Discussion started by: neimaD
10 Replies

5. AIX

Question on background running job

Guys, We use AIX 5.3 at our work place. I only in my team have a strange problem of not able run jobs background. Other colleagues are able to run without any problem. Once I kick off background job using nohup and & command, It immediately stops. The following error I get when I run. ... (2 Replies)
Discussion started by: anandsbr
2 Replies

6. Shell Programming and Scripting

A question about the PID of a background function

Dear all, I'm writing a KornShell script that calls inside it a function in background mode #!/bin/ksh function myfunction { . . .} myfunction |& . . . How can I capture the PID of the function myfunction that runs in background? Thanks in advance :) (2 Replies)
Discussion started by: dariyoosh
2 Replies

7. Solaris

ScreenSaver issue with Solaris 10

I have a Dell Vostro running Solaris 10 x86 and I am trying to get it to activate the screensaver when no one is logged it. However, the screensaver only seems to activate when someone logs in and then the computer locks. How would I go about fixing this problem? Any help yall can offer would be... (3 Replies)
Discussion started by: MajorJRO
3 Replies
chroot(8)						      System Manager's Manual							 chroot(8)

NAME
chroot - Changes the root directory of a command SYNOPSIS
/usr/sbin/chroot directory command DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in effect, directory is relative to the current root of the running process. Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file system and the relevant pathnames for the files map correctly in the new root file system. For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and /etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on description files produced by the ctab command may also fail if the required description files are not present in the new root file system. The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe- cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new root file system in the appropriate locations. EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec- ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among others) on the new root file system. Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial root file system. To create a file relative to the original root rather than the new one, use this syntax and enter: chroot directory command > file CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite the file system. FILES
Specifies the command path. RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1) Functions: chdir(2), chroot(2) exec(2) delim off chroot(8)
All times are GMT -4. The time now is 01:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy