Comments on: Kernel 2.6.15 Released with NTFS Write http://www.mjmwired.net/linux/2006/01/04/kernel-2615-released-with-ntfs-write/ making sense of mixed up software Sun, 20 Jul 2008 15:01:29 +0000 http://wordpress.org/?v=1.5.2 Comment on Kernel 2.6.15 Released with NTFS Write by: Ed b http://www.mjmwired.net/linux/2006/01/04/kernel-2615-released-with-ntfs-write/#comment-42 Tue, 10 Jan 2006 04:43:07 +0000 http://www.mjmwired.net/linux/2006/01/04/kernel-2615-released-with-ntfs-write/#comment-42 oooops -- regarding my previous comment: disregard!!! The problem was I hadn't set the umask. (I still don't know what that is, but I now know i need it!) Thanks for the guide. oooops — regarding my previous comment: disregard!!!

The problem was I hadn’t set the umask. (I still don’t know what that is, but I now know i need it!)

Thanks for the guide.

]]> Comment on Kernel 2.6.15 Released with NTFS Write by: Ed b http://www.mjmwired.net/linux/2006/01/04/kernel-2615-released-with-ntfs-write/#comment-41 Tue, 10 Jan 2006 04:28:24 +0000 http://www.mjmwired.net/linux/2006/01/04/kernel-2615-released-with-ntfs-write/#comment-41 Hi there -- this piqued my interest: "The standard kernel works perfectly with NTFS read" because I've been having some trouble sharing out an ntfs partition with Samba. I am using the kernel driver along with a totally stock Fedora Core 4 installation. I can access the ntfs (for reading) just fine locally. But when I try to connect to it with a windows box on my network I get "not accessible". My other samba shares (these are either shares to ext3 or fat32 filesystems) work fine. I have share-level security, and allow access to "everyone". It seems like is *should* work -- any thoughts would be appreciated. Hi there — this piqued my interest:
“The standard kernel works perfectly with NTFS read”
because I’ve been having some trouble sharing out an ntfs partition with Samba. I am using the kernel driver along with a totally stock Fedora Core 4 installation. I can access the ntfs (for reading) just fine locally. But when I try to connect to it with a windows box on my network I get “not accessible”.
My other samba shares (these are either shares to ext3 or fat32 filesystems) work fine.

I have share-level security, and allow access to “everyone”.

It seems like is *should* work — any thoughts would be appreciated.

]]>