08-02-2012
Why would *.* be much safer? That could potentially match . or .. on some systems. Besides, you can't really disable some globbing but not others.
What I usually see done to "safe" rm for root is putting alias rm="rm -i" in root's profile, so rm prompts for every single file removal.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello!
I want users in a certain group to be restricted to their home directory. So that they have full access to all files and folders in their home directory but the cant go to any directory above.
Does anyone know how to do this?
Anders (1 Reply)
Discussion started by: alfabetman
1 Replies
2. UNIX for Dummies Questions & Answers
Hi Gurus,
Tried searching for something similiar in this forum but not really what i want.
This is my case:
I have about 20 users running on sun workstation. We have done a upgrade recently and right now it seems that the users can access to terminal and console which they are not suppose... (12 Replies)
Discussion started by: lweegp
12 Replies
3. Solaris
Hi all,
How to restrict the perticular commands to users(or perticular users) in
solaris10?
Could you please assist me the precedure for above issue.
Thanks & Regards
krishna (0 Replies)
Discussion started by: krishna176
0 Replies
4. Shell Programming and Scripting
Hello all,
We have an FTP Server setup with VSFTPd and its working fine without anonymous login (we must maintain this standard)
The requirement is to restrict users not to overwrite (and delete) their files. In other words, once their files are uploaded to FTP Server, they should not be... (1 Reply)
Discussion started by: prvnrk
1 Replies
5. UNIX for Advanced & Expert Users
Hi All!
I would like to know if there is any specific way by which I can restrict access to apecific users (ip addresses).
OS : Red hat linux
Thanks!
nua7 (6 Replies)
Discussion started by: nua7
6 Replies
6. Red Hat
Hi,
I had installed vsftp in rhel5 and i want to restrict all the local users from accessing the ftp.
i want to allow specific users to access the ftp server.
Request you to please help.
Thanks & regards
Arun (1 Reply)
Discussion started by: Arun.Kakarla
1 Replies
7. Linux
Hi Everybody,
If there is a general NFS share in the LAN and for example this share has three files - a, b, c is there any way to restrict file access to the root user of one particular host(falcon) in the same LAN environment while the normal users from the same host(falcon) should be able... (4 Replies)
Discussion started by: sudhirav
4 Replies
8. Solaris
Hi All,
How to restrict the NIS users not to change their passwords in for NIS users??
and my NIS user is unable to login to at client location what could be the problem for this ?
Any body can help me. Thanks in advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies
9. Shell Programming and Scripting
is it possible that we can restrict the root user if he runs some commands?? e.g i want if root runs command 'rm etc/passwd', he shoudn't be able to run command and throws error :confused: (3 Replies)
Discussion started by: sheelsadan
3 Replies
10. AIX
Hello,
I would like to confirm whether the below procedure is correct.
disabled direct super user access on AIX server using below procedure. Please let me know if there is any additional step.
1) confirm the access to HMC, console to reach the LPARs
2) chuser rlogin=false root
... (3 Replies)
Discussion started by: dio34
3 Replies
LEARN ABOUT HPUX
convertfs
convertfs(1M) convertfs(1M)
NAME
convertfs - convert an HFS file system to allow long file names
SYNOPSIS
[special-file]
DESCRIPTION
The command converts an existing HFS file system supporting the default maximum file name length of 14 characters into one that supports
file names up to 255 characters long. Once an HFS file system is converted to long file names, it cannot be restored to its original
state, since the longer file names require a directory representation that is incompatible with the default HFS directory format. Since
this is an irreversible operation, prompts for verification before it performs a conversion.
forces the system to reboot if the root file system is converted. When converting the root file system, the system should be in single-
user mode, with all unnecessary processes terminated and all non-root file systems unmounted. Except for the root file system, requires
that the file system to be converted be unmounted.
If invoked without arguments, interactively prompts the user with a list of the HFS file systems from One or more or all of the listed file
systems can be selected for conversion. Typically, it is desirable to convert all of the file systems in to avoid inconsistencies between
two file systems mounted on the same system.
can also be invoked with an argument of either a block or character special-file name for a file system to be converted. Only the block
special file should be specified for a mounted root file system.
As part of the conversion process, performs an on each file system (see fsck(1M)).
Options
Do it quietly.
will perform the conversions without querying the user. Normally prompts the user before converting a file system.
RETURN VALUE
returns the following values:
Success.
Either successfully converted the file system, or the file system already allowed long file names.
Failure.
was not able to convert the file system due to some failure in processing.
AUTHOR
was developed by HP.
FILES
Default list of file systems to check.
SEE ALSO
fsck(1M), mkfs(1M), newfs(1M), fstab(4).
convertfs(1M)