Syndicated Linux NewsThis forum is for the discussion of Syndicated Linux News stories.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Lately, I’ve been hearing system administrators and managers ask about solutions to keep people from accidentally removing their data. These are very smart and dedicated people asking for a solution so that data isn’t lost either by accident or on purpose. A wild idea I’ve heard to solve the problem is getting rid of user access to the rm command. Is this truly a crazy idea?
I don't think that a restriction access to rm would help. Some users are dumb enough to delete their data in the app that they are using and then save the file. This way, the data is also lost, without using rm.
Question: If I delete a file using a file-manager, is this file-manager using rm to delete it?
Question: If I delete a file using a file-manager, is this file-manager using rm to delete it?
Depends on the file manager and settings. I set it to delete files immediately without confirmation (using rm) ... and I have never deleted any file I didn't want to delete ... no mistakes.
I think it's the extra confirmation that induces mistakes. I remember when I was using Window$ that there was always a confirmation, and sometimes I pressed the wrong button. It seems that removing the confirmation helps because: it makes you more careful, and it removes unnecessary confirmation.
For root, I have made a wrapper script for rm that will prevent deleting top level directories and two levels down or so, plus no recursive.
Are you sure you want to delete? Yes Really certain? Yes Last chance. Are you sure you don't want to change your mind? Yes OK then, but don't come crying to me in a couple of days when you realise you've made a mistake.
Are you sure you want to delete? Yes Really certain? Yes Last chance. Are you sure you don't want to change your mind? Yes OK then, but don't come crying to me in a couple of days when you realise you've made a mistake.
Sounds like Debian to me. I have a shell account at my uni. their server is running Debian and every time I want to rm a file in my directory I am always asked to confirm it. Its fscking annoying, especially when I want to just get rid of a directory, then I get asked file-by-file if I want to delete it! Attachment 5980
Is this how Debian is by default? If so it is just plain fscking stupid if you ask me!
Sounds like Debian to me. I have a shell account at my uni. their server is running Debian and every time I want to rm a file in my directory I am always asked to confirm it. Its fscking annoying, especially when I want to just get rid of a directory, then I get asked file-by-file if I want to delete it! Attachment 5980
Is this how Debian is by default? If so it is just plain fscking stupid if you ask me!
That is not the Debian default. I think the administrators have set up an alias for rm to rm -i. May be they have to deal with many dumb users.
Quote:
Perhaps, but even the login shell wasn't to my liking until I put:
Code:
export PS1='\u@\h:\w\$ '
in .bashrc. I got tired of issuing pwd to remind me what directory I was in. Plus it felt more like Slackware again .
Also not Debian default. I never chnged the prompt and I can see where I am.
I've got some weird kind of love/hate relationship with Debian. I keep installing it as a dual-boot with Slack, then getting fed up with it after a couple of weeks. This has happened a few times.
Ah well I don't have .bash_profile, and that file isn't even located in /usr/share/skel, just .bashrc where I copied to my home so I could at least change the way my login prompt is. I obviously can't modify /etc/profile but the alias for rm isn't even there anyways. Also I already removed alias rm= i from that file (.bash_aliases in my home).
Again I only assumed this is how Debian is by default, since all the aliases and .bashrc stuff is in some folder called /skel in /usr/share which is also something not found in Slackware.
Oh well I guess I will just have to live with it. At least my prompt is in the proper manner.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.