this post was submitted on 14 Nov 2026
42 points (87.5% liked)

Linux

68768 readers
796 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 7 years ago
MODERATORS
42
A joke... (lemmy.ca)
submitted 1 day ago* (last edited 1 day ago) by chenwu@lemmy.ca to c/linux@lemmy.ml
 

When I feel like scrapping the whole project and starting over:

Me: (in the project dir) sudo rm -rf /*
Me: (after waiting a while) Something feels off… Why is it taking so long to delete everything?
Me: (suddenly realizing) ^C ^C ^C
System: Press any key to continue...

当我想把整个项目推倒重做时:
我:(在项目目录)sudo rm -rf /*
我:(等了一会儿)有点不对劲。。。怎么删了这么长时间还没删完
我:(恍然大悟)^C ^C ^C
系统: Press any key to continue...

you are viewing a single comment's thread
view the rest of the comments
[–] intrepid@lemmy.ca 1 points 41 minutes ago

This is apparently a joke! But I have done this in real life. It's an honest mistake you can make if you're experienced, fast, complacent and careless. Always be prepared for it. Here are some tips:

  1. Don't use sudo for anything other than system operations. Not even for editing configuration files.

  2. Never put any development/sysadmin projects under ownership of root. Always develop the project under your personal unprivileged user account. Use sudo only for the final deployment of project to system directories.

  3. Use sudoedit to edit any system configuration files.

  4. Avoid ./* at all times in favor of just *. While this is counterintuitive, this is actually safer. You will have less habitual urge to type the / alone by accident.

  5. Avoid the -f flag in all instances for any command until some operation fails. That will leave you with enough time to reflect on your mistakes when you make one.

  6. Always keep a data recovery plan. Backups are highly recommended. If you use Btrfs partitions, you can make periodic read-only snapshots of your critical data. You can automate this process with a tool like Snapper.
    Btrfs snapshots store de-duplicated data. So each snapshot stores only the changes from the previous one. It doesn't use a lot of space, even when backing up large media files. You'll still get the chance to recover your data at the time of the last snapshot.

  7. Most operating system files aren't critical data and don't need to be backed up. Backup the system configuration files in /etc and the package installation list if your package manager facilitates it.

  8. This is optional, but useful in case your Linux installation gets nuked somehow, including this nonsense.
    You can always reinstall the distro and start over again. But often times, you can trivially recover the installation by booting from a live USB/CD and doing some manual repair. Learn to chroot into your nuked root partition and operate from inside it.
    Most live disks give you an option to repair an installation, in case you deleted the root partition by accident. You can also repopulate the deleted files using commands like debootstrap and pacstrap.