With all due respect, RTFM. Mount and umount are two sides of the same operational coin. You mount the drive to use it and unmount it when you’re done. fstab is just a file system table used to remember and consistently apply the options used whether you’re mounting the drives manually or telling the system to do it at boot.
Deleting a line from fstab is not the same as unmounting, it is just a shortcut to tell the system how you want that drive mounted when you or the system run the mount command. Mount directories (usually the folders in /media/ or /mnt/ ) also do not get automatically deleted just because you “yanked the drive”. Again, those directories are just where your system is expecting to mount the drive. When the drive is mounted they will be the root path to its contents, when the drive is unmounted they will be empty but they still exist. If your planning on mounting the drive again leave them there. If you’re not planning on mounting them again, delete them.
If you’re not planning on regularly mounting a particular drive, it probably shouldn’t be listed in fstab and you should just run the mount command with the appropriate options (again fstab is just a table for remembering those options for the mount command).
Many desktop Linux distros are also capable of automatically mounting new removable drives in such a way that the user can access them and doesn’t have to worry about touching fstab or the mount directories.
For me at least, it’s not that you’re asking questions. I answered, so obviously I’m sympathetic to confusion in this area. I’m just trying to encourage you to seek your answers in the documentation and manuals FIRST. The way your question was worded led me to believe that you had not read the manuals at all and were simply copying snippets of code and commands from some random question and answer style forum that did not teach you anything about the fundamentals of what those commands and code actually did. That’s fine too, lots of people started off that way, myself included. Reading the manuals gives you the context to step back and understand how those commands work and what they’re really doing. If you do, you’ll be much better able to troubleshoot your own problems, you’ll be able to ask better questions in forums like this, and you’ll get better and more useful responses.
Sure, I mean I am used to reading (and writing) manuals and documentation, so I usually go that route first when I know where to look. And your answer was helpful. Anyway, what are some authoritative ressources I should consult concerning these fundamental concepts?
Start with the man pages. Running the command man followed by a space and then followed by the command you’re using will almost always give you a man page of the basics of how that command works. The fstab has its own man page too. An internet search “man fstab” or whatever command you’re interested in should also net many mirrors of the those man pages as well.
Hmmm. I have also installed linux mint xfce from scratch. So far so good. It stuck only one time since this install. And its been 5 days or so i guess.
My guess is this is in GNOME? If there isn’t an eject button next to the mount name, that’s just a “favorites” link that got added, and not the actual mount. Right-click to remove it if you don’t need it anymore.
RAM or Video card issue. Are you SURE the entire machine actually locks up, or just the display? Try ssh’ing into the machine when this happens to see if it’s actually staying alive, though the display stops working.
yeah, entire machine locks up. Yeah have tried ssh’ing from mobile and it was stuck one time when i did that during a freeze. have replugged RAM let’s see if system freezes again,
The tricky point to your needs is getting the app’s menu bar in the top bar. The rest are easy to do with almost all desktop environments. But getting the menu bar on the top bar, I think currently only KDE supports it (with a plugin), and MATE (with another plugin).
However, if you want the general feel of how MacOS 9/X feels, then Gnome with extensions would be your best bet. The rest feel more like simpler Windows, but in a mac skin. Gnome+extensions feel more accurately like a Mac, in terms of overall usability (even if the looks aren’t 100% there). So it depends what you’re after more: the feeling of using a mac, or the exact looks of it.
kinfocenter is an application in Plasma where you can see all kinds of information about your system. So no, they are not just adding k to random words like quantum in Ant-man. :)
KDE was originally called “Kool Desktop Environment” until they renamed it, first to “K Desktop Environment” then to just “KDE”.
It was the first Linux desktop environment that tried to make all its apps look consistent. Before KDE, Linux UI apps were very inconsistent, each one using whatever UI toolkit it wanted. They likely named all of them with a K to make the naming somewhat consistent too.
Gtk was released two years later, originally only used in GIMP (Gtk originally stood for for “GIMP ToolKit”) and it took a while for other desktop environments to have a consistent look and feel like KDE did.
This is part of the motherboard and can only be changed with specific tools from the manufacturer. Back in the days there was AMIDEDOS as a dos tool to change it in AMI Bios. You would need to find out, what tool can be used to change it in your UEFI. However, it’s possible that those tools are not available to the public.
@vaionko I’ve found this (scroll down to #5 if it won’t scroll automatically). It shows some tools that can be used to change DMI information for different Manufacturers.
You might be able to flash the retail BIOS to remove the OEM stuff, but often if it’s running a specific OEM BIOS it’ll block you from flashing a retail version.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.