global mounts in a manually-installed bedrock
So I've got a bedrock system set up and working. Manual install, so global is its own strata, as is rootfs. The Bedrock boots, gets net, runs x-windows (including keyboard & mouse input functionality), browses the web and plays audio. So far so good. I've not tested video playback yet but with everything else working the way it is, I can't see why that would not.
At the moment, the only partitions mounted by the fstab are the "/" partition and the swap partition. I have a partition that is Fat32, for use in sharing files with windows. I also have a partition used for the permanent /home directory and a miscellaneous files partition. Now, I can put entries for the above in the global fstab file, that much I understand. There is no need to mount these partitions early, before one picks the init and strata to finish booting from. However... My understanding of the Bedrock documentation is that since global is not rootfs, /home should be mounted to /bedrock/strata/global/home, not to /home. in the fstab. The default framework settings will then ensure it is accessible in the other strata. The idea is that it will appear as /home once booted into bedrock? A question: is that correct? A second question, does a "share = /home" need to be added to the default framework section of the /bedrock/etc/strata.conf file? Or no? Or would it instead be "share = /bedrock/strata/global/home"? A third question: to mount the actual windows ntfs partition requires me specifying ntfs-3g (fuse) like so: /dev/sda1 /win7 ntfs-3g fmask=111,dmask=000 1 0 My understanding is that the global fstab is interpreted by the busybox mount command, not the chosen strata's mount. If this is so, will the use of ntfs-3d (fuse) be parsed OK? Thank you. |
Quote:
Quote:
Quote:
Both are global. That is, all processes see the same thing when they look at either of those paths. If one process messes with one of those files, all the other processes will see the result. /etc/fstab is intended to be your normal /etc/fstab, nothing special there. /bedrock/etc/fstab is intended for the weird situation where you need to mount the stratum that provides init. Most distros don't have this because they require the init system to be on the root filesystem, but Bedrock's flexibility tries to offer the choice to have it on another filesystem. Per the documentation I wrote, either should work. The convention would be to use `/etc/fstab` since `/home` doesn't need to be mounted before the init, as you mentioned. However, there seems to be an issue between the way Bedrock handles these things and some versions of `mount` that I'm working on narrowing down. Essentially, Bedrock mounts something to `/home` before `/etc/fstab` is read with the expectation that mount will read `/etc/fstab` and mount over the preexisting mount. However, some `mount` versions see the existing mount and just silently skip the `/etc/fstab` entry. As a work around, you could either:
I plan to rework the relevant bit of documentation soon (hopefully tomorrow) now that I understand what the actual issue is. I also have thoughts on how to remedy it for the upcoming release. Quote:
Mount points mounted by `/bedrock/etc/fstab` is a bit weird, though, as they are mounted before Bedrock sets up all the global share stuff. I'm actually not sure whether a line in `/bedrock/etc/fstab` would prefer `/home` or `/bedrock/strata/global/home`, or if it even makes a difference. You may need to guess and check, and just try the other one if the first doesn't work. Or use `/etc/rc.local` as I mentioned above, which would then work with either but `/home` would be the convention. Quote:
Quote:
Quote:
/etc/fstab is interpreted by the stratum you select to provide init and should support ntfs-3g fine if the corresponding distro would normally support it. Bedrock doesn't do anything to make `/win7` global. Only the stratum that mounts it will be able to access files in there by default. You could edit the default framework to add a `share=` field for it, although then you have the headache I described above with `/home`. Another option would be to put it in `/mnt`, e.g. `/mnt/win7`, if that's not a problem for you workflow/muscle-memory. `/mnt` is global by default and it's not mounting directly on top of another mount point so the mount/fstab confusion won't happen (as its mounting in a subdirectory instead). Quote:
Nyla's handle of this whole area is, IMO, overly complicated and easily confused. Let me know if that didn't make sense and I can try to rephrase. I'm planning on completely reworking this for the upcoming release to be much simpler, plus provide more examples in the documentation. |
Thank you for the reply.
Quote:
Was that bad? :o Quote:
Quote:
|
Quote:
Quote:
Quote:
Quote:
|
All times are GMT -5. The time now is 11:51 AM. |