Sponsored Content
Full Discussion: features of a new SHELL
Top Forums Shell Programming and Scripting features of a new SHELL Post 302275414 by nsharath on Saturday 10th of January 2009 09:52:34 AM
Old 01-10-2009
Bug My work

Hello sir,
I am very happy to see the optimistic note of the posts above.I have finished handling the "command not found" exception. I am currently working on "help me linux".
Here my target is the linux newbie who know nothing abt commands.He can enter his doubts like = "how to list a file?" And my perl code will tell him about "ls". I also want to handle queries like "how to lst a file?".Here the spelling is wrong, even then I am working with commands like aspell,hunspell to do the job for me.

I also have ideas like encrypting files,derectories with gpg so that even if one could get root password, he cannot open it, searching in LAN using openSSH. Can you please tell me where I stand now.I dont know whether I am going in the right direction or not !!!
 

8 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

V2.2.0 new features?

Neo, can you tell us about some of the new features since the upgrade, or are they mostly "behind the scenes"? (1 Reply)
Discussion started by: PxT
1 Replies

2. UNIX for Advanced & Expert Users

Help with Additional Password Features

Hello: I have a customer who is requesting the following security features on a Solaris 8 system: 1. Password history for the three previous passwords. 2. User account lockout after 3 failed login attempts. Can anyone help provide me with a solution or direction for the above? (1 Reply)
Discussion started by: rambo15
1 Replies

3. AIX

AIX OS Features versus Solaris OS Features

Hi Unix Experts, I like to compile and compare all the features that AIX OS (541L) and Solaris OS (Solaris 10) provide. If somebody can shed on this topic would be highly appreciated. Thank you, Khan (0 Replies)
Discussion started by: hkhan12
0 Replies

4. Windows & DOS: Issues & Discussions

Evaluate uUNIX and MSDOS shell script features

I need to select the main features of shell scripting on UNIX and evaluate their MSDOS equivalent. can anyone suggest some online resources articles anything?? Thanks in advance (0 Replies)
Discussion started by: deemon111
0 Replies

5. UNIX for Dummies Questions & Answers

Shell features ???

Hi Can anybody explain the following shell features with example a) Command line editing b) filename completion c) job control (1 Reply)
Discussion started by: skyineyes
1 Replies

6. UNIX for Dummies Questions & Answers

Features explanation???

HI Can anybody explain following UNIX features? Removable file system Dynamic file space allocation Thanks (1 Reply)
Discussion started by: skyineyes
1 Replies

7. Programming

Unix shell with history features like in bash

hii to all i am developing a simple unix shell in c i want to add history feature in that how could i do that plz help if there is any tutorial or website plz put it here history feature should be like that in bash, when press up key show the previous command typed in console plz be... (1 Reply)
Discussion started by: vipin_jss
1 Replies

8. Ubuntu

useradd - shell missing features after adding user

Hi, I need to create a user from a bash script so i have to use useradd. The problem is that when i create a user with: useradd -d /home/sample -m sample after i login with that user I have no history in bash, path do not appears, i can't use arrows and so on. When I use adduser everything is... (5 Replies)
Discussion started by: ktm
5 Replies
NSENTER(1)							   User Commands							NSENTER(1)

NAME
nsenter - run program with namespaces of other processes SYNOPSIS
nsenter [options] [program] [arguments] DESCRIPTION
Enters the namespaces of one or more other processes and then executes the specified program. Enterable namespaces are: mount namespace mounting and unmounting filesystems will not affect rest of the system (CLONE_NEWNS flag), except for filesystems which are explic- itly marked as shared (by mount --make-shared). See /proc/self/mountinfo for the shared flag. UTS namespace setting hostname, domainname will not affect rest of the system (CLONE_NEWUTS flag). IPC namespace process will have independent namespace for System V message queues, semaphore sets and shared memory segments (CLONE_NEWIPC flag). network namespace process will have independent IPv4 and IPv6 stacks, IP routing tables, firewall rules, the /proc/net and /sys/class/net directory trees, sockets etc. (CLONE_NEWNET flag). PID namespace children will have a set of PID to process mappings separate from the nsenter process (CLONE_NEWPID flag). nsenter will fork by default if changing the PID namespace, so that the new program and its children share the same PID namespace and are visible to each other. If --no-fork is used, the new program will be exec'ed without forking. See the clone(2) for exact semantics of the flags. If program is not given, run ``${SHELL}'' (default: /bin/sh). OPTIONS
Argument with square brakets, such as [file], means optional argument. Command line syntax to specify optional argument --mount=/path/to /file. Please notice the equals sign. -t, --target pid Specify a target process to get contexts from. The paths to the contexts specified by pid are: /proc/pid/ns/mnt the mount namespace /proc/pid/ns/uts the UTS namespace /proc/pid/ns/ipc the IPC namespace /proc/pid/ns/net the network namespace /proc/pid/ns/pid the PID namespace /proc/pid/root the root directory /proc/pid/cwd the working directory respectively -m, --mount [file] Enter the mount namespace. If no file is specified enter the mount namespace of the target process. If file is specified enter the mount namespace specified by file. -u, --uts [file] Enter the UTS namespace. If no file is specified enter the UTS namespace of the target process. If file is specified enter the UTS namespace specified by file. -i, --ipc [file] Enter the IPC namespace. If no file is specified enter the IPC namespace of the target process. If file is specified enter the IPC namespace specified by file. -n, --net [file] Enter the network namespace. If no file is specified enter the network namespace of the target process. If file is specified enter the network namespace specified by file. -p, --pid [file] Enter the PID namespace. If no file is specified enter the PID namespace of the target process. If file is specified enter the PID namespace specified by file. -r, --root [directory] Set the root directory. If no directory is specified set the root directory to the root directory of the target process. If direc- tory is specified set the root directory to the specified directory. -w, --wd [directory] Set the working directory. If no directory is specified set the working directory to the working directory of the target process. If directory is specified set the working directory to the specified directory. -F, --no-fork Do not fork before exec'ing the specified program. By default when entering a pid namespace enter calls fork before calling exec so that the children will be in the newly entered pid namespace. -V, --version Display version information and exit. -h, --help Print a help message. SEE ALSO
setns(2), clone(2) AUTHOR
Eric Biederman <ebiederm@xmission.com> AVAILABILITY
The nsenter command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils /util-linux/>. util-linux January 2013 NSENTER(1)
All times are GMT -4. The time now is 01:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy