LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 05-05-2004, 03:02 PM   #1
hanmanius
LQ Newbie
 
Registered: May 2004
Location: wisconsin
Distribution: fedora core 1&2, freebsd
Posts: 4

Rep: Reputation: 0
Samba and NTFS


I am somewhat new to Linux although I know my way around. I am currently using Fedora Core 1 and was trying to get NTFS working. I recompiled or so I thought with an RPM by the folks over at linux-ntfs at sourceforge and it caused something in KDE to go haywire and so I had to undo the damage it did. I was using the correct RPM as I have an Athlon. So my question is twofold, what do I need to recompile the kernel with NTFS support or can I just share my drive using samba without doing all that work? Or maybe it'll be good for me to do. Thanks.
 
Old 05-05-2004, 03:13 PM   #2
hanmanius
LQ Newbie
 
Registered: May 2004
Location: wisconsin
Distribution: fedora core 1&2, freebsd
Posts: 4

Original Poster
Rep: Reputation: 0
I just tried again using an RPM from the afformentioned website and it causes a error in nautilus. Does anyone know of anything if you do please help. I edited fstab per websites instructions:
/dev/hdb1 /files ntfs users,owner,ro,umask=000 0 0
/dev/hdb2 /files ntfs users,owner,ro,umask=000 0 0
and then got term window and mount -a then natilus comes up with an error.

Last edited by hanmanius; 05-05-2004 at 03:26 PM.
 
Old 05-05-2004, 03:36 PM   #3
queezythegreat
LQ Newbie
 
Registered: Jul 2003
Location: Canada
Distribution: Red Hat Linux 9.0 / Gentoo
Posts: 15

Rep: Reputation: 0
I don't recommend using a RPM based installation of NTFS support for the kernel. You should instead recompile your kernel with NTFS support enable. First you should get the sources of the current kernel that you are using, usualy you can get that from the Fedora CDs, it should be called something like kernel-sources(I don't know the exact name because it has been a long time since I used the RPM version of kernel sources ). Once you have that installed there should be a new directory in /usr/src, that is called identically to your current kernel. Now we can get to work. Okey cd into that directory and clean the source of any files left by the development team using the following command : make mrproper. Copy you current kernel configuration file from the /boot directory, it should be called config-KERNEL_VERSION_HERE into the source directory(cp /boot/config-KERNEL_VERSION .config). Now rename your kernel name to something diffrent than the current one, so that it dosen't conflict with the current kernel(vi Makefile - change the EXTRAVERSION variable to something you like ex. NTFS-Enabled). Configure now you kernel with make menuconfig. You will need to navigate to File systems, once there scroll down to "NTFS file system support (read only)" and select it a either a module or as built-in. One thing you should now is that you will only have read support, you will be unable to write to the NTFS system, there is write support in the kernel but it is very unstable and very limited, so I don't recommend using it. Now you need to finish up by saving the config file by exiting the menuconfig program and issuing the following command : make dep && make bzImage && make modules && make modules_install. This will make all the dependencies, make the kernel(bzImage), make all the modules and the install them. This is a lengthy process, so you better go do something else. Once it finishes you will have a new kernel ready to be copied. Copy the new kernel : cp arch/i386/boot/bzImage /boot/vmlinuz-KERNEL_VERSION . Then copy the config file so that if in the futer you want to recompile the kernel you will have the configuration file : cp .config /boot/config-KERNEL_VERSION. And finaly copy the System.map : cp System.map /boot/System.map-KNERNEL_VERSION . Your almost home free, the last thing to do is add a new entry to you boot loader, simply open the config file of the boot loader and duplicate the entry of the current kernel, but changing it so that it points to the file that you just copied into the /boot folder. I hope this helped you, and if you have any question please ask it.
 
Old 05-05-2004, 07:22 PM   #4
hanmanius
LQ Newbie
 
Registered: May 2004
Location: wisconsin
Distribution: fedora core 1&2, freebsd
Posts: 4

Original Poster
Rep: Reputation: 0
Thanks a ton. Im workin on it now. Again thanks.
 
Old 05-06-2004, 01:48 AM   #5
hanmanius
LQ Newbie
 
Registered: May 2004
Location: wisconsin
Distribution: fedora core 1&2, freebsd
Posts: 4

Original Poster
Rep: Reputation: 0
ok well done and over with but I was looking at my boot folder and my grub.conf more specifically and this is what is put in there along with my changes thusfar

default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core NTFS Enabled
root (hd0,0)
kernel /vmlinuz-NTFS-enabled.nptl ro root=LABEL=/ hdd=ide-scsi rhgb
initrd /initrd-2.4.22-1.2188.nptl.img
title Fedora Core (2.4.22-1.2188.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/ hdd=ide-scsi rhgb
initrd /initrd-2.4.22-1.2188.nptl.img
title DOS
rootnoverify (hd1,0)
chainloader +1

now the Fedora Core (2.4....... that is my current kernel which works perfect the Fedora Core NTFS Enabled is the one that I have been working on today. It is all compiled but I am worried cause the file I copied over doesn't have the .nptl actually no extension. Will it still work if I pull the .nptl off it so the first entry looks something like this

title Fedora Core NTFS Enabled
root (hd0,0)
kernel /vmlinuz-NTFS-enabled ro root=LABEL=/ hdd=ide-scsi rhgb
initrd /initrd-2.4.22-1.2188.nptl.img

and what is the initrd???

thanks for all the help.
 
Old 05-06-2004, 10:08 AM   #6
queezythegreat
LQ Newbie
 
Registered: Jul 2003
Location: Canada
Distribution: Red Hat Linux 9.0 / Gentoo
Posts: 15

Rep: Reputation: 0
You should not worry about the .nptl extension, it's just part of the kernel name. As for the initrd, I totaly forgot about it. This is a initial ram disk that holds the drivers needed for bootup. Usualy you need it, only if you have a device that needs a driver before the root file system has been loaded. Use the following command to create this file : /sbin/mkinitrd /boot/initrd-KERNEL_VERSION.img KERNEL_VERSION . Now you should be able boot into your new kernel. Good luck...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Samba and NTFS phatboyz Linux - Networking 4 12-21-2004 10:38 AM
accessing ntfs share through samba GraemeK Linux - Software 2 01-26-2004 09:15 AM
samba with ntfs hizroyalhajpaj Linux - Networking 9 12-09-2003 11:20 PM
NTFS, Samba, RHL 8 ganeshbic Linux - Networking 1 04-16-2003 04:47 AM
samba mounting into NTFS? n3wb1e Linux - Software 3 03-24-2003 05:27 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 01:55 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration