>linux filesystem uses "/" as the root of everything, instead separating files and directories in drivesHow do linux users know whether disconnecting one of their drives will remove files or directories they want to keep? It seems ambiguous.For example let's say there's this file structure in linux.>/foo/bar/baz.txtWhat if foo is stored in hard drive 1, bar is stored in hard drive 2, and baz.txt is stored in hard drive 3.What would happen to this file structure if you decided to disconnect hard drive 2?
>>109615678/foo/bar/baz.txt will appear as a path even if hard drive 1 and 2 are disconnected i believethe file system stores files as inodes anyways and then they are mapped back to pathsthat how hard links work where two paths map to the same inode
>>109615678>How do linux users know whether disconnecting one of their drives will remove files or directories they want to keep?you mount/unmount drives like thatthe core system utilities are typically on a single drive
This really should have been in the stupid questions thread.>>109615678>if you decided to disconnect hard drive 2?If you unplugged the drive without telling linux :- linux you tell you there was a hardware problem- you wouldn't be able to access bar or anything inside bar- to access drive 3 in this scenario you'd have to tell linux to associate drive 3 with some other path (that you can actually access)If you told linux first- linux would tell you that drive 3 is connected inside bar (and so that needs to be dealt with first)>>109615678>How do linux users know whether disconnecting one of their drives will remove files or directories they want to keep?mount
>>109615678>What would happen to this file structure if you decided to disconnect hard drive 2?As in "Just disconnect it for shits and giggles while the system is running"?Then some of the file structure may be stored in memory still and you'll be able to see it but the system will shit itself with I/O errors if you try to do anything.TLDR; Don't do that.
>>109615782>- linux would tell you that drive 3 is connected inside bar (and so that needs to be dealt with first)Can you have circular dependencies in the filesystem?
>>109615678What's the difference between system libraries and system binaries?I hate ms but having windows and program files directories is just better
>>109615811windows isn't that much better, you forgot about>AppData/Local>AppData/LocalLow>AppData/Roaming
>>109615811Libraries are executables but executable system binaries aren't libraries.Does that help?
>>109615678/bar folder would contain both HDD2 and HDD3 files so business as usual?
>>109615809If you need to rsync /foo into /foo/bar you have to be careful about the parameters or it will go in an infinite loop. It happened to me a few times when i forgot i had something mounted.these are just skill issues though and not something wrong with GNU slash Linucks itself
>>109615835That one actually makes perfect sense.Settings and state that is only relevant to the local machine goes in local. Settings and state that makes sense to roam with the user to multiple distinct machines, goes in Roaming.LocalLow is kinda confusing because it's the same thing as Local but for programs that are deemed lower-trust or are running partially sandboxed.
>>109615835And then there's a hidden Documents and Settings folder which is automatically symlink to the user folder.
>>109615678I want Gobo Linux to become mainstream...
>>109615847>Executables are libraries >executable binaries (aka executables) aren't librariesThis is not helpful
