On Wed 02 Feb 2022 at 11:16:18 (+0100), Yvan Masson wrote:
>
> > > > > Slightly off-topic question: using pre-5.15 kernel, how can I
> > > > > mount a
> > > > > partition with kernel driver?
> > > >
> > > > You can'
Slightly off-topic question: using pre-5.15 kernel, how can I
mount a
partition with kernel driver?
You can't, the NTFS kernel driver first appeared in Linux 5.15.
From what I understand, there was a read-only driver before 5.15:
- see for example
https://superuser.com/questions/1
; > >
> > > > As far as I know, NTFS3 is not enabled in any Debian kernel. 🤔
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998627
> > > >
> > > Which probably explains why I could not mount using `mount -t
> > > ntfs` :-)
> >
/bugreport.cgi?bug=998627
Which probably explains why I could not mount using `mount -t ntfs` :-)
Slightly off-topic question: using pre-5.15 kernel, how can I mount a
partition with kernel driver?
You can't, the NTFS kernel driver first appeared in Linux 5.15.
From what I understand, there
> > As far as I know, NTFS3 is not enabled in any Debian kernel. 🤔
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998627
> >
> Which probably explains why I could not mount using `mount -t ntfs` :-)
>
> Slightly off-topic question: using pre-5.15 kernel, how can I mount a
> partition with kernel driver?
You can't, the NTFS kernel driver first appeared in Linux 5.15.
--
Tixy
Andrei for
confirming what I supposed): this means that in some cases, NTFS3 is not
as mature as ntfs3g.
As far as I know, NTFS3 is not enabled in any Debian kernel. 🤔
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998627
Which probably explains why I could not mount using `mount -t ntfs
On 2022-01-31 11:43 UTC+0100, Yvan Masson wrote:
> Thanks for the links, I missed that NTF3 was already included in the
> kernel I use (from Debian testing). So in my case ntfs3g is able to
> mount a rescued partition, while NTFS3 is not (thanks Andrei for
> confirming what I supposed): this
Le 31/01/2022 à 16:19, Michael Stone a écrit :
On Mon, Jan 31, 2022 at 11:43:10AM +0100, Yvan Masson wrote:
Thanks for the links, I missed that NTF3 was already included in the
kernel I use (from Debian testing). So in my case ntfs3g is able to
mount a rescued partition, while NTFS3 is not (th
On Mon, Jan 31, 2022 at 11:43:10AM +0100, Yvan Masson wrote:
Thanks for the links, I missed that NTF3 was already included in the
kernel I use (from Debian testing). So in my case ntfs3g is able to
mount a rescued partition, while NTFS3 is not (thanks Andrei for
confirming what I supposed): thi
Le 28/01/2022 à 17:51, David Wright a écrit :
On Fri 28 Jan 2022 at 11:34:44 (+0100), Yvan Masson wrote:
I had to recover a NTFS partition from a broken drive (I used GNU
ddrescue with a domain log file generated by partclone), so I now have
a file "recovered_partition.img"
On Fri 28 Jan 2022 at 11:34:44 (+0100), Yvan Masson wrote:
>
> I had to recover a NTFS partition from a broken drive (I used GNU
> ddrescue with a domain log file generated by partclone), so I now have
> a file "recovered_partition.img":
>
> $
On Vi, 28 ian 22, 11:34:44, Yvan Masson wrote:
>
> Could it be because `mount` uses kernel driver and `mount.ntfs` uses
> ntfs-3g, and that the latter has better "quality" even for read-only? (Note
> that this sentence is a complete guess)
Try 'ls -l /sbin/mount.ntfs
Hi list,
I had to recover a NTFS partition from a broken drive (I used GNU
ddrescue with a domain log file generated by partclone), so I now have a
file "recovered_partition.img":
$ file recovered_partition.img
recovered_partition.img: DOS/MBR boot sector, code offset 0x52+2, OEM
On Jo, 26 nov 20, 01:29:13, Kanito 73 wrote:
> to...@tuxteam.de Wrote:
>
> > This is a pattern which I like to call "emergent evil". Most likely
> > nobody does it on purpose, yet it happens often enough to annoy
> > competing ecosystems. Magic!
>
> HAHAHAHAHA (with capital letters)... As far as
On Mi, 25 nov 20, 21:56:06, Charlie Gibbs wrote:
>
> In situations like this, I think not of Occam's, but of Hanlon's Razor:
>
> Never attribute to malice that which can
> be adequately explained by stupidity.
+1
> At this point, though, a little voice in the back of my mind says,
> "Bu
On Thu, Nov 26, 2020 at 09:06:49AM +, Joe wrote:
> On Thu, 26 Nov 2020 01:29:13 +
> Kanito 73 wrote:
>
> >
> > I hate Windoze as an operating system but some programs and games are
> > cool... [...]
> > environments (when computers had simple text terminals) and further
> > graphical op
On Thu, 26 Nov 2020 01:29:13 +
Kanito 73 wrote:
>
> I hate Windoze as an operating system but some programs and games are
> cool... And there is a fact: THE ONE WHO HITS FIRST, HITS TWICE
> (translated from spanish). Bill Gates was pioneer of the graphical
> environments (when computers had
gt; >> competing ecosystems. Magic!
> >
> > NTFS has been NTFS since the 90s, while Linux has had ext2, ext3,
> > ext4, Reiser among other filesystems. Is it not likely that 'NTFS'
> > has really been a similar parade of different filesystems with each
> &
;>> to MS.
>>
>> This is a pattern which I like to call "emergent evil". Most likely
>> nobody does it on purpose, yet it happens often enough to annoy
>> competing ecosystems. Magic!
>
> NTFS has been NTFS since the 90s, while Linux has had ext2,
> Microsoft has a bad habit of changing things under the hood without
> bumping the version number. They could very well have changed NTFS
> enough to bollix Linux NTFS libraries and not bothered to tell anyone.
Except that `ntfs-3g` can read and write NTFS and hasn't seen the need
o annoy Linux users since long time ago... Installing Windoze disables
Linux to boot... NTFS was cryptic for years with no tech specifications of the
filesystem, a mystery so for many years Linux developers were unable to create
a driver to access such partitions, in fact I remember that in th
On Wed, 25 Nov 2020 21:22:30 +
Joe wrote:
> NTFS has been NTFS since the 90s, while Linux has had ext2, ext3,
> ext4, Reiser among other filesystems. Is it not likely that 'NTFS'
> has really been a similar parade of different filesystems with each
> version of Windows
". Most likely
> nobody does it on purpose, yet it happens often enough to annoy
> competing ecosystems. Magic!
>
NTFS has been NTFS since the 90s, while Linux has had ext2, ext3, ext4,
Reiser among other filesystems. Is it not likely that 'NTFS' has really
been a similar p
On Wed, Nov 25, 2020 at 03:47:12PM -0500, Stefan Monnier wrote:
> > Microsoft changes the system required to kill the fast-boot every so often,
> > almost surely to make it difficult for users of Linux to access Windows from
> > the Linux system.
>
> That seems highly unlikely: it's a tiny number
> Microsoft changes the system required to kill the fast-boot every so often,
> almost surely to make it difficult for users of Linux to access Windows from
> the Linux system.
That seems highly unlikely: it's a tiny number of users, and not only
they're not a threat but annoying them won't bring
only RTL*
(rtl8821ae.ko) the right 8821ce.ko was already loaded and I thought
it was the rtl8821ae activating my wifi. [SOLVED]
Now I have another BIG problem. I installed both Windows10
(version OCTOBER 2020) and Debian 10.0.6 in dual boot and left a
large NTFS partition for data on the primary
the only RTL*
>> (rtl8821ae.ko) the right 8821ce.ko was already loaded and I thought
>> it was the rtl8821ae activating my wifi. [SOLVED]
>>
>> Now I have another BIG problem. I installed both Windows10
>> (version OCTOBER 2020) and Debian 10.0.6 in dual boot and lef
0 (100Gb+)
sda5-sda7 Debian 10 (100Gb+)
sda8 Data partition (700Gb NTFS)
SDD:
sdb1 Data partition (128Gb NTFS)
Thanks for sharing!
My primary OS is Linux, rarely I use Windows but I require a native
installation to run some programs with direct access to the hardware... Most
programs ca
RAM, GPU)
> applications?
HDD:
sda1-sda4 Windows 10 (100Gb+)
sda5-sda7 Debian 10 (100Gb+)
sda8 Data partition (700Gb NTFS)
SDD:
sdb1 Data partition (128Gb NTFS)
My primary OS is Linux, rarely I use Windows but I require a native
installation to run some programs with direct access to the h
the rtl8821ae activating my wifi.
[SOLVED]
Now I have another BIG problem. I installed both Windows10 (version OCTOBER
2020) and Debian 10.0.6 in dual boot and left a large NTFS partition for data
on the primary disk (HDD) and the whole secondary disk (SDD) also as a unique
NTFS
P.S. Debian is working 100% perfectly, it is up and running, the
unique problem is the access to the NTFS partitions
You are running into Windows "hibernation" that leaves the disks in an
"unclean" state when shut down in that manner (sadly, a
default..."fastboot&
1ce.ko was already loaded and I thought
> it was the rtl8821ae activating my wifi. [SOLVED]
>
> Now I have another BIG problem. I installed both Windows10 (version
> OCTOBER 2020) and Debian 10.0.6 in dual boot and left a large NTFS
> partition for data on the primary disk (HDD) an
he right 8821ce.ko was already loaded and I thought
> it was the rtl8821ae activating my wifi. [SOLVED]
>
> Now I have another BIG problem. I installed both Windows10 (version
> OCTOBER 2020) and Debian 10.0.6 in dual boot and left a large NTFS
> partition for data on the primary d
and I thought it was the rtl8821ae activating my wifi. [SOLVED]
Now I have another BIG problem. I installed both Windows10 (version OCTOBER
2020) and Debian 10.0.6 in dual boot and left a large NTFS partition for data
on the primary disk (HDD) and the whole secondary disk (SDD) also as a unique
activating my wifi. [SOLVED]
Now I have another BIG problem. I installed both Windows10 (version OCTOBER
2020) and Debian 10.0.6 in dual boot and left a large NTFS partition for data
on the primary disk (HDD) and the whole secondary disk (SDD) also as a unique
NTFS partition.
Well, I installed Windows
On Mi, 29 mai 19, 11:12:22, songbird wrote:
>
> i have never experienced a problem with writing to
> a NTFS file system.
>
> i use an external drive that has a NTFS file
> system on it for backups and as a scratch space
> if i need to save something large for a while.
n an hour later there was another update and all started playing
nicely again.
But this has nothing to do with the original question. We even do not
know
what linux or debian developers will do next ;-)
The point is that OP should know that ntfs-3g works well under linux. I
guess there shoul
deb wrote:
>
>
> I saw this question come up
>
> and it set off bells.
>
>
> Someone asked what the status of WRITING to NTFS drives was.
>
> That it was not yet supported (?) .
>
>
>
> *MY* Assumptions:
>
> * MIXED NETWORK, with Win, Mac, Lin
r there was another update and all started playing
> nicely again.
But this has nothing to do with the original question. We even do not know
what linux or debian developers will do next ;-)
The point is that OP should know that ntfs-3g works well under linux. I
guess there should be additional t
Debian -> Windows with mc.
I've been writing directly to ntfs with ntfs-3g for many years now. Not
on
daily bases, but doing backup and restore couple of times on different
notebooks, PCs etc.
Thing is you don't know what windows is going to do next.
Was an update a few days ago that
h mc.
I've been writing directly to ntfs with ntfs-3g for many years now. Not on
daily bases, but doing backup and restore couple of times on different
notebooks, PCs etc.
On 2019-03-11 18:13, deb wrote:
Someone asked what the status of WRITING to NTFS drives was.
I move files windows -> Debian with WinScp.
You can move files Debian -> Debian with mc and a ssh connection in the
other window.
Interested to see that there is a ssh server available on wind
On Lu, 11 mar 19, 14:13:38, deb wrote:
>
> Someone asked what the status of WRITING to NTFS drives was.
>
> That it was not yet supported (?) .
In addition to what was already said in the thread, I've been using the
excuse that some data might need to be accessible from Win
Hi.
On Tue, Apr 09, 2019 at 04:13:15PM +0200, Hans wrote:
> Hi folks,
>
> I am not sure, but when I want to mount a ntfs-filesystem using ntfs-3g, I
> always need to input the password of root.
>
> According to the manual, if ntfs-3g is setuid-root, it shall allow
Hi folks,
I am not sure, but when I want to mount a ntfs-filesystem using ntfs-3g, I
always need to input the password of root.
According to the manual, if ntfs-3g is setuid-root, it shall allow normal
users to mount ntfs-files.
So, I have rwsr-xr-x with owner root:root, which IMO should do
initial
> > > queston
> > > about writing to NTFS file systems from Linux and Windows
> > > alternately.
> > > Although he does this in a dual boot environment, and with either
> > > Ubuntu
> > > or Mint, they should be similar enough to Debian
On 3/13/19 3:43 PM, Thomas D Dial wrote:
[...]
I contacted a relative who does this routinely. Windows alternately, I
contacted a relative who does this routinely about the initial queston
about writing to NTFS file systems from Linux and Windows alternately.
Although he does this in a dual
On 3/13/19 3:43 PM, Thomas D Dial wrote:
On Wed, 2019-03-13 at 11:12 -0400, deb wrote:
On 3/12/19 9:50 PM, David Christensen wrote:
On 3/11/19 11:13 AM, deb wrote:
I saw this question come up
and it set off bells.
Someone asked what the status of WRITING to NTFS drives was.
That it was
On Wed, 2019-03-13 at 11:12 -0400, deb wrote:
> On 3/12/19 9:50 PM, David Christensen wrote:
> > On 3/11/19 11:13 AM, deb wrote:
> > >
> > > I saw this question come up
> > >
> > > and it set off bells.
> > >
> > >
&g
On 3/12/19 9:50 PM, David Christensen wrote:
On 3/11/19 11:13 AM, deb wrote:
I saw this question come up
and it set off bells.
Someone asked what the status of WRITING to NTFS drives was.
That it was not yet supported (?) .
*MY* Assumptions:
* MIXED NETWORK, with Win, Mac, Linux
On 3/11/19 11:13 AM, deb wrote:
I saw this question come up
and it set off bells.
Someone asked what the status of WRITING to NTFS drives was.
That it was not yet supported (?) .
*MY* Assumptions:
* MIXED NETWORK, with Win, Mac, Linux (EXT4 formatted).
* many portable 1-5TB drives
On 3/11/19 3:35 PM, Thomas D Dial wrote:
On Mon, 2019-03-11 at 14:13 -0400, deb wrote:
I saw this question come up
and it set off bells.
Someone asked what the status of WRITING to NTFS drives was.
That it was not yet supported (?) .
*MY* Assumptions:
* MIXED NETWORK, with Win, Mac
On 3/11/19 3:47 PM, Alexander V. Makartsev wrote:
On 11.03.2019 23:13, deb wrote:
I saw this question come up
and it set off bells.
Someone asked what the status of WRITING to NTFS drives was.
That it was not yet supported (?) .
*MY* Assumptions:
* MIXED NETWORK, with Win, Mac
On Mon, 11 Mar 2019 14:59:25 -0400
deb wrote:
> On 3/11/19 2:47 PM, Joe wrote:
> > On Mon, 11 Mar 2019 14:13:38 -0400
> > deb wrote:
> >
> >> I saw this question come up
> >>
> >> and it set off bells.
> >>
> >>
> >>
On Mon, 2019-03-11 at 14:13 -0400, deb wrote:
> I saw this question come up
>
> and it set off bells.
>
>
> Someone asked what the status of WRITING to NTFS drives was.
>
> That it was not yet supported (?) .
>
>
>
> *MY* Assumptions:
>
> *
On 11.03.2019 23:13, deb wrote:
>
>
> I saw this question come up
>
> and it set off bells.
>
>
> Someone asked what the status of WRITING to NTFS drives was.
>
> That it was not yet supported (?) .
>
>
>
> *MY* Assumptions:
>
> * MIXED NETWORK, wi
On 3/11/19 2:47 PM, Joe wrote:
On Mon, 11 Mar 2019 14:13:38 -0400
deb wrote:
I saw this question come up
and it set off bells.
Someone asked what the status of WRITING to NTFS drives was.
That it was not yet supported (?) .
I don't think that has been true for several years, t
On Mon, 11 Mar 2019 14:13:38 -0400
deb wrote:
> I saw this question come up
>
> and it set off bells.
>
>
> Someone asked what the status of WRITING to NTFS drives was.
>
> That it was not yet supported (?) .
>
I don't think that has been true for several y
I saw this question come up
and it set off bells.
Someone asked what the status of WRITING to NTFS drives was.
That it was not yet supported (?) .
*MY* Assumptions:
* MIXED NETWORK, with Win, Mac, Linux (EXT4 formatted).
* many portable 1-5TB drives making the rounds, formatted with
On 07.03.2019 3:46, Long Wind wrote:
> freebsd say it can read reliably from ntfs, but write to it unreliably
>
> i've just checked stretch manual for mount, it seem to support write
> to ntfs?
>
> early linux can't write to ntfs
>
>
ntfs is supported via &qu
- Original Message -
From: "Felix Miata"
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
On Friday 16 September 2016 05:42:29 David Wright wrote:
> noone is reading this, are they?
I am!! Hey! Look! Over here!
Lisi
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
>>>> /de
at includes Windows 10:
>
> >> # grep ntfs /etc/fstab
> >> /dev/sda6 /win/C ntfs-3g
> >> nofail,users,gid=100,fmask=0111,dmask=,locale=en_US.UTF-8 0 0
>
> > Already this doesn't work.
>
> Of course it doesn't. A seed isn't a fr
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-3
g ins and outs of Debian. Due to later I've wiped the disk
and reinstalled multiple times in a single day. [If retirement is
not for education, of what use might it be ;]
Thank you for your time.
On a USENET group discussing an unrelated topic I came across
partitions formatted as ntfs. I had
I upgrade from Wheezy to Jessie finally, and now can't mount my second
hdd that has a win7 installation on it, in two partitions, both ntfs,
one with the actual windows system, another with just data, files, etc.
When I boot the machine (to jessie), it looks like the partitions on
that driv
tl (rw,relatime)
/dev/sdb1 on /mnt/disk type fuseblk
(rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
ntfs-3g version is ntfs-3g i386 1:2014.2.15AR.2-1+deb8u2
[ FIXED ]
After a bit of googling around I found that the wheezy version of ntfs-3g
works. This is obviously not a very satisf
On Tuesday 12 May 2015 22:12:36 German wrote:
> probably stupid question, but do I need the same size drive using this
> program? Just to make sure until I got my next decision. Thanks
Have you heard of google?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
Quoting German (gentger...@gmail.com):
> probably stupid question, but do I need the same size drive using this
> program? Just to make sure until I got my next decision. Thanks
I typed scrounge-ntfs into google and looked at the third hit,
the ubuntu man page. The answer appears to
probably stupid question, but do I need the same size drive using this
program? Just to make sure until I got my next decision. Thanks
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://
Mounting an NTFS partition as a user was set-up and working properly.
the partition is ON MY HARDDISK. a lot of what i'm reading about the problem
seems to be associated with usb sticks (??)
upgraded (i'm running wheezy)
now i get this :
Unprivileged user can not mount NTFS blo
ain of the advantage if you are a member of user. You can
use the USER tag in the rule to run commands as someone other than
root.
> Plex should work in either case with wide-open 777 mode.
>
Agreed
> ACTION=="add", PROGRAM=="/sbin/blkid -o value -s TYPE /dev/%k",
>
, Scott Ferguson wrote:
On 26/11/14 16:14, Rick Macdonald wrote:
On 25/11/14 08:46 PM, Scott Ferguson wrote:
I do have an udev rule (see attached and cp it to /etc/udev/rules.d)
that will automagically mount a NTFS formatted slice on an external
drive that has the LABEL "WinBackup"
t;>>> On 26/11/14 12:23 AM, Scott Ferguson wrote:
>>>>>
>>>>> On 26/11/14 16:14, Rick Macdonald wrote:
>>>>>>
>>>>>> On 25/11/14 08:46 PM, Scott Ferguson wrote:
>>
I do have an udev rule (see attached and cp it to /etc
>>
>> Quick comment (I will get back to this later today or early tomorrow):-
>> grep ntfs /lib/udev/rules.d/*.rules
>> /lib/udev/rules.d/80-udisks.rules:ENV{ID_FS_TYPE}=="ntfs|vfat", \
>>
>> If this does control the effect you note, (which is easy
that it's involved but I don't see
any file modes.
That's were I'm at now. I played with udev rules a bit but I've never
worked with them before.
Quick comment (I will get back to this later today or early tomorrow):-
grep ntfs /lib/udev/rules.d/*.rules
/lib/udev/rules.
that it's involved but I don't see
any file modes.
That's were I'm at now. I played with udev rules a bit but I've never
worked with them before.
Quick comment (I will get back to this later today or early tomorrow):-
grep ntfs /lib/udev/rules.d/*.rules
/lib/udev/rules.
s coming from the udisks-daemon (or
> its parent). Strace on udevd shows that it's involved but I don't see
> any file modes.
>
> That's were I'm at now. I played with udev rules a bit but I've never
> worked with them before.
Quick comment (I will get back
d me a link to the Mint desktop
manager with the same name as the typo...
I'm away from the box where I set-up a set environment, and the desk
with my notes (this email client is being remotely accessed). I'll be
back there later today. Note I put an NTFS file system on a USBKey with
the
worked/works. It's always worked to some extent, so
I've never had to fuss with it.
ntfs-3g's umask/dmask/fmask options all default to 0, but somebody is
calling it with dmask=0077,fmask=0177. I haven't figured out the chain
of commands involved.
Sorry for replying to my own
;t lead
anyone to think I'm asking about a boot-time mount issue.
Over the years the hot-plug system (if that's the name for it) seems to
have changed a few times, and I admit I've never understood how hal,
udev, etc worked/works. It's always worked to some extent, so I'v
On 26/11/14 04:36 AM, Scott Ferguson wrote:
I vaguely remember reading somewhere (may have been on this list) that
putting anybody in the disk group is a big no no, I think it was to do
with security.
*It is* (shoot foot material). So is setting ntfs-3g setuid. Which is
another practise used
On 26/11/14 21:27, Chris Bannister wrote:
> On Wed, Nov 26, 2014 at 02:46:24PM +1100, Scott Ferguson wrote:
>>
>> In which case I'd "recommend":-
>> *1.* uncommenting the user_allow_other line in /etc/fuse.conf
>>
>> *2.* changing the fstab line
On Wed, Nov 26, 2014 at 02:46:24PM +1100, Scott Ferguson wrote:
>
> In which case I'd "recommend":-
> *1.* uncommenting the user_allow_other line in /etc/fuse.conf
>
> *2.* changing the fstab line to:-
> LABEL=WinBackup /media/WinBackup ntfs-3g
> uid=1000,g
On 26/11/14 16:14, Rick Macdonald wrote:
> On 25/11/14 08:46 PM, Scott Ferguson wrote:
>> Sorry, I don't know what DE means!
>> Desktop Environment e.g. GNOME, KDE, XFCE, LXDE, etc
>
> KFCE.
??
https://packages.debian.org/search?keywords=kfce&searchon=names&suite=all§ion=all
Gives me nothing :(
On 25/11/14 10:14 PM, Rick Macdonald wrote:
OK, I tried all that and it makes no difference. With either line in
fstab there are no messages in syslog from fuse/ntfs-3g about that
partition, and I have to mount it manually. We're you expecting it to
auto-mount?
The following run as
allow_other
I had already uncommented that line, but it made no difference. I
couldn't see that I had to restart any service. I didn't reboot.
In which case I'd "recommend":-
*1.* uncommenting the user_allow_other line in /etc/fuse.conf
*2.* changing the fstab line t
I missed some questions there :(
On 26/11/14 14:46, Scott Ferguson wrote:
> On 26/11/14 11:41, Rick Macdonald wrote:
>> On 25/11/14 04:04 PM, Scott Ferguson wrote:
>>> On 26/11/14 08:03, Rick Macdonald wrote:
>>
>> "fuse" doesn't seem to be a binary executable,
Not by that name.
/sbin/mount.f
;m running up-to-date wheezy.
>> DE?
>
> Sorry, I don't know what DE means!
Desktop Environment e.g. GNOME, KDE, XFCE, LXDE, etc
Probably irrelevant now - given your requirements (Plex) and your stated
usage (only user) the fstab I've suggested solve the mounting
requireme
top that's been
running Debian since the 0.93 days in the mid-90's before Buzz was
released (OK, it's gone through some hardware upgrades ;-).
How does one override or change to options fuse gives to ntfs-3g (if I
have that right)?
I have an NTFS filesystem on a USB-connected hard dr
On 26/11/14 08:03, Rick Macdonald wrote:
> Well, many hours of googling, and running grep on my entire filesystem,
> have failed me this time.
>
> I'm running up-to-date wheezy.
DE?
>
> How does one override or change to options fuse gives to ntfs-3g (if I
> have t
Well, many hours of googling, and running grep on my entire filesystem,
have failed me this time.
I'm running up-to-date wheezy.
How does one override or change to options fuse gives to ntfs-3g (if I
have that right)?
I have an NTFS filesystem on a USB-connected hard drive. With nothi
Hi,
Thank you very much for your help.
Replacing
ikki-fstype=ntfs,gid=46,dmask=002,fmask=113 :/dev/ikki
with
ikki-fstype=fuse,gid=46,dmask=002,fmask=113 :ntfs-3g#/dev/ikki
solved the problem.
ntfs-3g was already installed on my system.
Regards.
Thierry
On Sun, 16 Nov
Hi.
On Sun, 16 Nov 2014 12:42:31 +0100
Thierry Rascle wrote:
> The automounting used to work for all of the entries, but now does not
> for the three entries with "-fstype=ntfs".
Install ntfs-3g, replace
-fstype=ntfs,gid=46,dmask=002,fmask=113 :/dev/ikki jacala
with
-fs
Hi list,
I'm using sid, with wmii as my only window manager and desktop
environment.
I'm using autofs for automounting my external devices:
- CD/DVD drives,
- USB sticks formatted as FAT or NTFS,
- external hard disk drives formatted has EXT4 or NTFS. or NTFS),
CD-ROM drives, ext
"57442D575845304139395337303334", RUN+="/bin/mkdir /media/wd"
ACTION=="add", SUBSYSTEMS=="usb",
ATTRS{serial}=="57442D575845304139395337303334", RUN+="/bin/mount -t
ntfs-3g -o rw,uid=1000,umask=022,posix,shortname=winnt /dev/wd1 /media/wd&quo
following
(not sure how they got generated initially)
/dev/sda1 /windows/C ntfs-3g
auto,users,noexec,uid=1000,gid=users,dmask=002,fmask=113,relatime 0 0
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
In a fresh installed Debain Weekly Build amd64 CD1 system leaving anything
in the installer by default, when I plug in a 1T 3.5 USB 3.0 SATA HDD Drive
formatted as NTFS, I got this warning:
Error mounting: mount exited with exit code 1: helper failed with:
Unprivileged user can not mount NTFS
On Sat, Nov 17, 2012 at 11:11 AM, Oleg Sadov wrote:
> 17/11/2012 в 15:56 +0200, Rudi Ahlers wrote:
>> On Sat, Nov 17, 2012 at 3:36 PM, Andrew Z wrote:
>>
>> root@master:[~]$ yum install ntfs-3g
>> Loaded plugins: security
>> Setting up Install Process
>>
1 - 100 of 681 matches
Mail list logo
