Linux

56044 readers

242 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Made a big(?) mistake with mv /*/*/* ./ (lemmy.ml)

submitted 4 weeks ago* (last edited 4 weeks ago) by joeldebruijn@lemmy.ml to c/linux@lemmy.ml

37 comments fedilink hide all child comments

Background:

I think I messed up ... Wanted to get a lot of files out of a nested folderstructure 3 levels deep and used mv /*/*/* ./ somewhere deep in my personal folders. I got a lot of errors and quick as I could stopped it. Now that folder is is messed up with a lot of stuff (see below) which I dont know the origin of. The good news: I have fairly recent backups

Questions:

Could they be from subdirectories in my home folder?
Could they be from subdirectories outside my home folder? Especially grubenv caught my eye.
Could it be potentially dangerous to reboot? I leave my PC on untill I know more.
Would it be possible to reverse the moving in some way, to put them back where they belong, even manually?

Any help greatly appreciated.

Files:

Sorry for the long list

0 1 10 10:1 10:125 10:126 10:127 10:130 10:183 10:224 10:228 10:229 10:231 ... 116:8 116:9 ... 13:81 ... 8 81:0 81:1 81:2 81:3 9 arch_status attr autogroup by-diskseq by-id by-label by-partlabel by-partuuid by-path by-uuid cgroup cmdline comm coredump_filter cpu_resctrl_groups cpuset fd fdinfo fonts gid_map grubenv limits list.txt locale loginuid map_files maps mountinfo mounts net ns numa_maps nvme0n1p8_crypt oom_adj oom_score oom_score_adj projid_map sched schedstat sessionid setgroups smaps smaps_rollup stat statm status task timens_offsets timers timerslack_ns uid_map unicode.pf2 usb wchan x86_64-efi

you are viewing a single comment's thread
view the rest of the comments

[–] gonzo-rand19@moist.catsweat.com 2 points 4 weeks ago (1 children)

I can't say because those paths are relative and I don't know your file structure. That said, even if I did, restoring from backup would take out all of the guesswork here so I would recommend that over trying to do it manually.

[–] Enkers@sh.itjust.works 7 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

Just a quick clarification: /*/*/* is not a relative path. The first / references the root directory.

[–] gonzo-rand19@moist.catsweat.com 4 points 4 weeks ago

You're right. I thought it was ./*/*/* instead.