Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I use df command to show the volumn , only found /home , / , /usr , /var , can advise if I want the path /boot also shown from the command df , what can i do ?
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,647
Rep:
Er... you don't want to mount anything to /boot. That's where the Linux kernel(s) live and boot from The minute you mounted anything there you would no longer have any access to the disk copy of the kernel. The running copy would have been loaded to RAM I'm thinking. No... It's just too ugly to think about. I can see no reason for mounting anything to /boot.
Why do you want df to show /boot? Why don't you just -
That's where the Linux kernel(s) live and boot from The minute you mounted anything there you would no longer have any access to the disk copy of the kernel. The running copy would have been loaded to RAM I'm thinking. No... It's just too ugly to think about. I can see no reason for mounting anything to /boot.
Don't panic He only ask about not showing /boot mount point. Anyway, about mounting, there are some reasons to do that on working system, and you are completly safe, because after reboot, orginal partition will be restored in that mounpoint, as long fstab hasn't been modified. For example, time ago, I realized that my boot partition was to small to properly install updated kernel, which fixes one of annoying bug. I remounted it on free directory, updated, and moved files to orginal boot partition. Other possibility is to unmount /boot partition or remount as read only (for example for security reason) if you currently do not maintenance system, it is necessary only during booting and updating.
That's where the Linux kernel(s) live and boot from The minute you mounted anything there you would no longer have any access to the disk copy of the kernel. The running copy would have been loaded to RAM I'm thinking. No... It's just too ugly to think about. I can see no reason for mounting anything to /boot.
Just for clarification: The kernel is loaded into RAM at boot time from your boot-manager. You don't need to have the kernel available on-disk while running. If you have a separate /boot partition this partition does not have to be mounted on a running system, except of course in the case you want to install newer kernels or change the bootloader configuration.
Therefore it is totally safe (but not really advisable) to mount anything to /boot.
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,647
Rep:
OK, I stand corrected. I just couldn't think of a valid reason for using /boot as a mount point. Thanks eSelex for clarification on that point. I usually hold two kernels in /boot and delete the oldest one before each upgrade. Obviously with something mounted on /boot you won't be able to upgrade the kernel without a load of faffing about.
If the Op has a separate /boot partition then you would get a result from df. He didn't mention his partition layout though.
I'll just go and stand in the corner then. Who's got the pointy hat?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.