Re: [oi-dev] ext2 on OI Hipster 20151003 follow-up
Bruce Lilly wrote: On Wed, Oct 14, 2015 at 12:40 PM, Jean-Pierre André wrote: What is this file mode changing about ? See http://openindiana.org/pipermail/oi-dev/2015-October/003804.html Depends on your use case... If you do not want to define the user mapping to Windows, you just have to mount with option fmask=0111 to hide the execution right. If you want the rights interoperable with Windows, you have to bear the Windows rules, which usually define an inherited execution right for files created by Windows. You can however define an inheritance rule in the parent directory so that files created by Windows in that directory do not have the execution right. You can even make this rule inheritable to inner directories, to only have to set the rule on the root directory. This is only for files created by Windows, for files created by OpenIndiana the Posix rules apply. Jean-Pierre ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] ext2 on OI Hipster 20151003 follow-up
On Wed, Oct 14, 2015 at 12:40 PM, Jean-Pierre André wrote: > What is this file mode changing about ? See http://openindiana.org/pipermail/oi-dev/2015-October/003804.html ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] ext2 on OI Hipster 20151003 follow-up
Bruce Lilly wrote: NTFS wouldn't be practical for me; it is a "foreign" filesystem as far as all of the installed OSes are concerned. Changing file modes would be a considerable problem, What is this file mode changing about ? and then there are issues of mapping user and group IDs and possibly modification time, I am not aware of a modification time issue. I have just discovered there is an access time issue, caused by vfs reading from its own cache, without ntfs-3g being notified. not to mention tools availability (fsck, etc.). There are several tools included in Hipster(resizing, cloning, undeleting, etc.) You can also run the Windows chkdsk on OpenIndiana : http://jp-andre.pagesperso-orange.fr/runwin.zip (you will have to recompile using a compiler compatible with Windows, if you have difficulties ask me for an executable). Jean-Pierre ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] ext2 on OI Hipster 20151003 follow-up
Actually,Use the precompiled 64-bit code from the main site which is 2015.3.14. From there, you can use ext2 driver (or update it).You can read/write ext2/3/4. http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html You can usually contact Jean-Pierre on any issues. ~ Ken On Monday, October 12, 2015 10:09 AM, Bruce Lilly wrote: NTFS wouldn't be practical for me; it is a "foreign" filesystem as far as all of the installed OSes are concerned. Changing file modes would be a considerable problem, and then there are issues of mapping user and group IDs and possibly modification time, not to mention tools availability (fsck, etc.). FAT also wouldn't work as it doesn't support chmod, etc. The 8-character mount probable-bug is disconcerting. Even more so is that the wiki page listing source repositories ( http://wiki.openindiana.org/oi/Source+Repositories ) appears to be quite out-of-date, so even if it were possible to easily find the source there, it might not be what's actually used. Therefore I gave up trying to look (ever wonder why there are so few developers working on OI...?). On Mon, Oct 12, 2015 at 6:51 AM, Nikolam wrote: > FUSE works right on Openindiana /hipster-2015, I installed it with with NTFS > support from: > http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html > I mount my NTFS partition in OI just right, > only bug I see is that files copied from Ntfs partition are all marked > executable when copied. > If it could be used with ext2/3(4?) read-only, (if fs name is 8 characters > ;)) that would be great. > > If FUSE and Ntfs is also included in OI repositories, that would be also > more great. > > On Mon, Oct 12, 2015 at 6:12 AM, Bruce Lilly wrote: >> >> Ken Mays kindly suggested using fuse from SFE and/or ntfs-3G. >> >> Fuse didn't work because of what looks like a bug in /sbin/mount: >> >> # mount -F fuse-ext2 /dev/dsk/c2t0d0p7 /mnt >> mount: FSType fuse-ext2 exceeds 8 characters >> >> "fuse-ext2", the name of the fuse module for ext2 is indeed 9 characters >> long. >> Why /sbin/mount should have a problem with that is another matter. >> The mount(1M) manual page, which has a recent date but doesn't look quite >> like the usual illumos/openindiana man pages, gives no clue, but it >> mentions >> the man page mnttab(4). >> The mnttab(4) man page also provides no insight, but refers to >> /usr/include/sys/mntio.h. >> With appropriate packages installed, /usr/include/sys/mntio.h shows >> character >> array mtl_fstype sized _ST_FSTYPSZ. >> _ST_FSTYPSZ is defined in /usr/include/sys/stat.h as 16. >> /sbin/mount has a compiled-in string "%s: FSType %s exceeds %d >> characters". >> So if mount is using something less than _ST_FSTYPSZ-1, what is it using >> (evidently something that evaluates to 8) and why? >> >> This is apparently an old issue; it also shows up on a system running >> oi_151a9. >> >> ntfs-3G might or might not have a more recent fuse driver, but no ext2 >> support per se, >> so wouldn't help with this problem. >> >> This, incidentally, is on a triple-boot laptop which also has NetBSD 7.0 >> and >> openSUSE 13.1 Linux installed (both with native ext2 support) and both >> mounting >> 5 ext2 data partitions in peaceful coexistence. >> >> ___ >> oi-dev mailing list >> oi-dev@openindiana.org >> http://openindiana.org/mailman/listinfo/oi-dev > > > > ___ > oi-dev mailing list > oi-dev@openindiana.org > http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] ext2 on OI Hipster 20151003 follow-up
NTFS wouldn't be practical for me; it is a "foreign" filesystem as far as all of the installed OSes are concerned. Changing file modes would be a considerable problem, and then there are issues of mapping user and group IDs and possibly modification time, not to mention tools availability (fsck, etc.). FAT also wouldn't work as it doesn't support chmod, etc. The 8-character mount probable-bug is disconcerting. Even more so is that the wiki page listing source repositories ( http://wiki.openindiana.org/oi/Source+Repositories ) appears to be quite out-of-date, so even if it were possible to easily find the source there, it might not be what's actually used. Therefore I gave up trying to look (ever wonder why there are so few developers working on OI...?). On Mon, Oct 12, 2015 at 6:51 AM, Nikolam wrote: > FUSE works right on Openindiana /hipster-2015, I installed it with with NTFS > support from: > http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html > I mount my NTFS partition in OI just right, > only bug I see is that files copied from Ntfs partition are all marked > executable when copied. > If it could be used with ext2/3(4?) read-only, (if fs name is 8 characters > ;)) that would be great. > > If FUSE and Ntfs is also included in OI repositories, that would be also > more great. > > On Mon, Oct 12, 2015 at 6:12 AM, Bruce Lilly wrote: >> >> Ken Mays kindly suggested using fuse from SFE and/or ntfs-3G. >> >> Fuse didn't work because of what looks like a bug in /sbin/mount: >> >> # mount -F fuse-ext2 /dev/dsk/c2t0d0p7 /mnt >> mount: FSType fuse-ext2 exceeds 8 characters >> >> "fuse-ext2", the name of the fuse module for ext2 is indeed 9 characters >> long. >> Why /sbin/mount should have a problem with that is another matter. >> The mount(1M) manual page, which has a recent date but doesn't look quite >> like the usual illumos/openindiana man pages, gives no clue, but it >> mentions >> the man page mnttab(4). >> The mnttab(4) man page also provides no insight, but refers to >> /usr/include/sys/mntio.h. >> With appropriate packages installed, /usr/include/sys/mntio.h shows >> character >> array mtl_fstype sized _ST_FSTYPSZ. >> _ST_FSTYPSZ is defined in /usr/include/sys/stat.h as 16. >> /sbin/mount has a compiled-in string "%s: FSType %s exceeds %d >> characters". >> So if mount is using something less than _ST_FSTYPSZ-1, what is it using >> (evidently something that evaluates to 8) and why? >> >> This is apparently an old issue; it also shows up on a system running >> oi_151a9. >> >> ntfs-3G might or might not have a more recent fuse driver, but no ext2 >> support per se, >> so wouldn't help with this problem. >> >> This, incidentally, is on a triple-boot laptop which also has NetBSD 7.0 >> and >> openSUSE 13.1 Linux installed (both with native ext2 support) and both >> mounting >> 5 ext2 data partitions in peaceful coexistence. >> >> ___ >> oi-dev mailing list >> oi-dev@openindiana.org >> http://openindiana.org/mailman/listinfo/oi-dev > > > > ___ > oi-dev mailing list > oi-dev@openindiana.org > http://openindiana.org/mailman/listinfo/oi-dev ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
Re: [oi-dev] ext2 on OI Hipster 20151003 follow-up
FUSE works right on Openindiana /hipster-2015, I installed it with with NTFS support from: http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html I mount my NTFS partition in OI just right, only bug I see is that files copied from Ntfs partition are all marked executable when copied. If it could be used with ext2/3(4?) read-only, (if fs name is 8 characters ;)) that would be great. If FUSE and Ntfs is also included in OI repositories, that would be also more great. On Mon, Oct 12, 2015 at 6:12 AM, Bruce Lilly wrote: > Ken Mays kindly suggested using fuse from SFE and/or ntfs-3G. > > Fuse didn't work because of what looks like a bug in /sbin/mount: > > # mount -F fuse-ext2 /dev/dsk/c2t0d0p7 /mnt > mount: FSType fuse-ext2 exceeds 8 characters > > "fuse-ext2", the name of the fuse module for ext2 is indeed 9 characters > long. > Why /sbin/mount should have a problem with that is another matter. > The mount(1M) manual page, which has a recent date but doesn't look quite > like the usual illumos/openindiana man pages, gives no clue, but it > mentions > the man page mnttab(4). > The mnttab(4) man page also provides no insight, but refers to > /usr/include/sys/mntio.h. > With appropriate packages installed, /usr/include/sys/mntio.h shows > character > array mtl_fstype sized _ST_FSTYPSZ. > _ST_FSTYPSZ is defined in /usr/include/sys/stat.h as 16. > /sbin/mount has a compiled-in string "%s: FSType %s exceeds %d characters". > So if mount is using something less than _ST_FSTYPSZ-1, what is it using > (evidently something that evaluates to 8) and why? > > This is apparently an old issue; it also shows up on a system running > oi_151a9. > > ntfs-3G might or might not have a more recent fuse driver, but no ext2 > support per se, > so wouldn't help with this problem. > > This, incidentally, is on a triple-boot laptop which also has NetBSD 7.0 > and > openSUSE 13.1 Linux installed (both with native ext2 support) and both > mounting > 5 ext2 data partitions in peaceful coexistence. > > ___ > oi-dev mailing list > oi-dev@openindiana.org > http://openindiana.org/mailman/listinfo/oi-dev > ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
[oi-dev] ext2 on OI Hipster 20151003 follow-up
Ken Mays kindly suggested using fuse from SFE and/or ntfs-3G. Fuse didn't work because of what looks like a bug in /sbin/mount: # mount -F fuse-ext2 /dev/dsk/c2t0d0p7 /mnt mount: FSType fuse-ext2 exceeds 8 characters "fuse-ext2", the name of the fuse module for ext2 is indeed 9 characters long. Why /sbin/mount should have a problem with that is another matter. The mount(1M) manual page, which has a recent date but doesn't look quite like the usual illumos/openindiana man pages, gives no clue, but it mentions the man page mnttab(4). The mnttab(4) man page also provides no insight, but refers to /usr/include/sys/mntio.h. With appropriate packages installed, /usr/include/sys/mntio.h shows character array mtl_fstype sized _ST_FSTYPSZ. _ST_FSTYPSZ is defined in /usr/include/sys/stat.h as 16. /sbin/mount has a compiled-in string "%s: FSType %s exceeds %d characters". So if mount is using something less than _ST_FSTYPSZ-1, what is it using (evidently something that evaluates to 8) and why? This is apparently an old issue; it also shows up on a system running oi_151a9. ntfs-3G might or might not have a more recent fuse driver, but no ext2 support per se, so wouldn't help with this problem. This, incidentally, is on a triple-boot laptop which also has NetBSD 7.0 and openSUSE 13.1 Linux installed (both with native ext2 support) and both mounting 5 ext2 data partitions in peaceful coexistence. ___ oi-dev mailing list oi-dev@openindiana.org http://openindiana.org/mailman/listinfo/oi-dev
