Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #172282 > unrolled thread

Re: NTFS access on Debian boot

Started byFelix Miata <mrmazda@earthlink.net>
First post2016-09-16 05:50 +0200
Last post2016-09-16 19:10 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.debian.user


Contents

  Re: NTFS access on Debian boot Felix Miata <mrmazda@earthlink.net> - 2016-09-16 05:50 +0200
    Re: NTFS access on Debian boot David Wright <deblis@lionunicorn.co.uk> - 2016-09-16 06:50 +0200
      Re: NTFS access on Debian boot Felix Miata <mrmazda@earthlink.net> - 2016-09-16 08:30 +0200
      Re: NTFS access on Debian boot Lisi Reisz <lisi.reisz@gmail.com> - 2016-09-16 10:40 +0200
    Re: NTFS access on Debian boot Alan McConnell <alan@his.com> - 2016-09-16 19:10 +0200

#172282 — Re: NTFS access on Debian boot

FromFelix Miata <mrmazda@earthlink.net>
Date2016-09-16 05:50 +0200
SubjectRe: NTFS access on Debian boot
Message-ID<shSk1-7zW-1@gated-at.bofh.it>
Alan McConnell composed on 2016-09-15 21:02 (UTC-0400):
 
> Felix Miata composed:

>> I'll provide a seed for you to try to fix on your own. This is from Jessie
>> on a multiboot Dell that includes Windows 10:

>> # grep ntfs /etc/fstab
>> /dev/sda6 /win/C ntfs-3g nofail,users,gid=100,fmask=0111,dmask=0000,locale=en_US.UTF-8 0 0

> Already this doesn't work. 

Of course it doesn't. A seed isn't a fruiting plant. It's not ready for cut and
paste.

1: /dev/sda6 needs to be adjusted to the partitioning on your HD, a complete
picture of which you have yet to show us. If Windows is on /dev/sda1, then
that's what your fstab needs.

2: /win/C probably doesn't exist on your Jessie /. You need to choose where
you want to mount the Windows partition, create a new place if necessary, then
replace /win/C with that location in your fstab.

3: It might be required that you substitute nfts for ntfs-3g in your fstab.
 
> ...Were your examples from a box with Windoze already on it?

"Already" at what point? Windows XP was installed before Jessie. Windows 10
was a subsequent fresh installation which began by reformatting the existing
partition created for XP. Before XP, several Linux distros were installed. All
of this is irrelevant, because I install and setup Grub myself, writing my own
primary bootloader menu, including in it whatever I please. I can load Grub
from the Windows boot menu if and when I please as well.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [next] | [standalone]


#172284

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2016-09-16 06:50 +0200
Message-ID<shTg5-8ie-15@gated-at.bofh.it>
In reply to#172282
On Thu 15 Sep 2016 at 23:42:22 (-0400), Felix Miata wrote:
> Alan McConnell composed on 2016-09-15 21:02 (UTC-0400):
>  
> > Felix Miata composed:
> 
> >> I'll provide a seed for you to try to fix on your own. This is from Jessie
> >> on a multiboot Dell that includes Windows 10:
> 
> >> # grep ntfs /etc/fstab
> >> /dev/sda6 /win/C ntfs-3g nofail,users,gid=100,fmask=0111,dmask=0000,locale=en_US.UTF-8 0 0
> 
> > Already this doesn't work. 
> 
> Of course it doesn't. A seed isn't a fruiting plant. It's not ready for cut and
> paste.
> 
> 1: /dev/sda6 needs to be adjusted to the partitioning on your HD, a complete
> picture of which you have yet to show us. If Windows is on /dev/sda1, then
> that's what your fstab needs.
> 
> 2: /win/C probably doesn't exist on your Jessie /. You need to choose where
> you want to mount the Windows partition, create a new place if necessary, then
> replace /win/C with that location in your fstab.
> 
> 3: It might be required that you substitute nfts for ntfs-3g in your fstab.

That's the type of mount I posted in
https://lists.debian.org/debian-user/2016/09/msg00488.html
but I think it limits you to readonly, which suits me.

If you (noone is reading this, are they?) decide to go for read-write access,
it might pay to look at "Windows hibernation and fast restarting" on
http://www.tuxera.com/community/ntfs-3g-manual/
which is one of several reasons I don't bother with it. I just don't
trust M$ to allow anything outside their realm to work properly.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#172286

FromFelix Miata <mrmazda@earthlink.net>
Date2016-09-16 08:30 +0200
Message-ID<shUOR-XQ-7@gated-at.bofh.it>
In reply to#172284
David Wright composed on 2016-09-15 23:42 (UTC-0500):

> On Thu 15 Sep 2016 at 23:42:22 (-0400), Felix Miata wrote:
...
>>> Felix Miata composed:
...
>>>> Jessie on a multiboot Dell that includes Windows 10:

>>>> # grep ntfs /etc/fstab
>>>> /dev/sda6 /win/C ntfs-3g nofail,users,gid=100,fmask=0111,dmask=0000,locale=en_US.UTF-8 0 0

When I wrote that originally, I followed it with:
# mount | grep eblk
/dev/sda6 on /win/C type fuseblk (rw,nosuid,nodev,noexec,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
...
# ls -gG /win/C
...
-rw-rw-rw- 1 1648193536 Aug  5 03:52 hiberfil.sys
-rw-rw-rw- 1 1476395008 Aug  5 03:52 pagefile.sys
-rw-rw-rw- 1  268435456 Aug  5 03:52 swapfile.sys
...

Do note that mount reports rw.
 
> That's the type of mount I posted in
> https://lists.debian.org/debian-user/2016/09/msg00488.html
> but I think it limits you to readonly, which suits me.

I booted W10 minutes ago, without noticing anything unusual. Then I restarted
into Jessie to find those three files with new timestamps at previous sizes.
Next I deleted the two larger, following that up by disconnecting the ethernet
cable and booting W10 again, again without noticing anything unusual, not that
I'd notice what would be "unusual" about running W10. About the only things I've
done with W10 is allow it to update, and open Edge to see what it looks like.

> If you (noone is reading this, are they?) decide to go for read-write access,
> it might pay to look at "Windows hibernation and fast restarting" on
> http://www.tuxera.com/community/ntfs-3g-manual/
> which is one of several reasons I don't bother with it. I just don't
> trust M$ to allow anything outside their realm to work properly.

I went to that site, then did as it suggested, opened an administrator command
prompt and ran powercfg /h off. Following that with "dir /ah \", hiberfil.sys
is not listed. Its absence seems confirmed by restarting into Jessie. While in
Jessie, I touched linuxWroteThis while in /win/C, wrote 7 ASCII characters into
it, then restarted into Windows, and opened it with Wordpad. Then I selected
all 7, copied, and pasted, all with mouse. Enough time on Windows for this
month; restarted into Jessie, then shutdown.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]


#172287

FromLisi Reisz <lisi.reisz@gmail.com>
Date2016-09-16 10:40 +0200
Message-ID<shWQF-2fE-1@gated-at.bofh.it>
In reply to#172284
On Friday 16 September 2016 05:42:29 David Wright wrote:
> noone is reading this, are they?

I am!! Hey!  Look!  Over here!  

Lisi

[toc] | [prev] | [next] | [standalone]


#172310

FromAlan McConnell <alan@his.com>
Date2016-09-16 19:10 +0200
Message-ID<si4Od-7DO-7@gated-at.bofh.it>
In reply to#172282

----- Original Message -----
From: "Felix Miata" <mrmazda@earthlink.net>
To: debian-user@lists.debian.org
Sent: Thursday, September 15, 2016 10:42:22 PM
Subject: Re: NTFS access on Debian boot

Alan McConnell composed on 2016-09-15 21:02 (UTC-0400):
 
> Felix Miata composed:

>> I'll provide a seed for you to try to fix on your own. This is from Jessie
>> on a multiboot Dell that includes Windows 10:

>> # grep ntfs /etc/fstab
>> /dev/sda6 /win/C ntfs-3g nofail,users,gid=100,fmask=0111,dmask=0000,locale=en_US.UTF-8 0 0

> Already this doesn't work. 

Of course it doesn't. A seed isn't a fruiting plant. It's not ready for cut and
paste.
        Hmm . . . a good aphorism, I guess.

        However, what _does_ work is the command  'blkid'  Its output for my
        /dev/sda3 is: LABEL="OS"!  !   So much for the adherents here of
        os-prober(You know who you are!)

        After further exploration, I found that the command to mount the
        Windoze system is: mount UUID="ddddd . . ." /mnt2.  The 'ddd. . . " is
        a sixteen digit string given by the blkid command.  And /mnt2 is another
        mount point I created, anticipating this use.

        With this I can, as root or as user, cd to /mnt2 and explore the arcana
        of Windows 10.  I didn't try copying to or from /mnt2, since I was
        afraid of disrupting the Windoze system.

        Perhaps a lurking installer maintainer can pick up on this.  It
        shouldn't be hard to set up a grub file with the capacity to install
        Windoze, if desired.  Or to put a mount point into fstab.



of this is irrelevant, because I install and setup Grub myself, writing my own
primary bootloader menu, including in it whatever I please. I can load Grub
from the Windows boot menu if and when I please as well.
        There is an enviable talent!  I don't think I'll need more than I
        presently have.  My hope is still to get jessie working as well as
        wheezy did.  I can now use X11, but I still need to get my jessie
        connected to the Internet.  I have a message about that to reply to.

Thanks, Felix, and best wishes to all you other folk!

Alan

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web