this post was submitted on 15 Mar 2024
1002 points (97.2% liked)
linuxmemes
21263 readers
689 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
nvme0n1p1
mmcblkxpy
(SD Card)
x = device number
y = partition number
NVMe device names follow this pattern: nvme n , where: is an integer that is assigned by Linux during the boot process. The first NVMe device that is detected is assigned 0
You also can have a 'c' in there, when it wants to model multipath nvme...
I still don't understand the point of namespaces. I guess it's less overhead to pass through a namespace to a VM rather than having a virtualised disk image or bind mount.
The other dragons aren't specifying a partition
So the 3rd dragon should just be
/dev/nvme%d
ONIPI
This made me chuckle, thank you!!