Forum Home
Press F1
 
Thread ID: 31964 2003-04-05 11:57:00 Is this realistic, or am i pushing the preverbial uphill with a soft toothpick? Clueless (181) Press F1
Post ID Timestamp Content User
133638 2003-04-06 04:38:00 Perhaps I abbreviated too much. <foreigndisk> is a shorthand which means "whatever the disk is called" ... in the mount command that can be the /dev/hdXx hardware identification or the mountpoint name.

The hardware name depends on the interface it is connected to. That gives you "/dev/hdX". If there is only one partition, the x is 1. You would need to add fstab entries for multi partitions or use the full mount command.

so if the fstab includes the line :
"/dev/hdc1 /mnt/foreign auto ro,noauto 0 0" (if the drive was plugged to the second IDE) and you have a directory called /mnt/foreign, you can type "mount /deb/hdc1" or "mount /mnt/foreign" and the OS will check the drive, and (if it has a fs for that type) it will mount that disk. If there isn't a fs for that disk, it will complain that it hasn't got the appropriate fs available.
Graham L (2)
133639 2003-04-06 08:07:00 You could check out Mandrake 9.0 or perhaps 9.1 I'm pretty sure that I managed to mount an NTFS disk with 9.0 and even managed to muck around with some of the files.

I was going to check out whether this "memory" of my was correct, but sadly the APC disk has died. Gave my poor CD drive an extremely hard time :)

You could possibly see whether your local library has acopy of the November issue of APC and check it out, but I have not run Mandrake on a Pentium 166. I know SuSE 8.0 will run on a P1/166 with 128Mb of RAM because I happen to have that set-up :)
Gorela (901)
133640 2003-04-07 02:32:00 oops i'm confused here..

SuSE8 in its current form doesn't seem to support NTFS.
When i mounted the disk using yast2, there were options for most file systems i have heard of and "7", which is what it chose. This seems enough to see how full the disk is, and very little else. All i need to do is be able to read it, and copy what i want before removing and formatting it.

I've searched around and it seems that newer versions of the kernel do support atleast NTFS, which leads to the questions:

How do i check my kernel version, and how do i update it, and with what?

-----I thought i'd get it happening on my working machine before i set up a new one.

.Clueless
Clueless (181)
133641 2003-04-07 03:14:00 To check your kernel version you can look at your start-up boot log file . Probably easiest if you do this via Yast . The other place is usr/src/ . You are most likely running 2 . 4 . 18 4GB Kernel updates are possible, but can also lead to problems .

You need to download the latest kernel versions and then install them . Once this is accomplished you need to modify lilo so it will boot from the new kernel and rename the old kernel so you have a fall back if the new one doesn't work :)

Read this one ( . suse . de/en/sdb/html/maddin_kernel_config . html" target="_blank">sdb . suse . de) and then this ( . suse . de/en/sdb/html/81_update_kernel . html" target="_blank">sdb . suse . de) to update to 8 . 1 which is 2 . 4 . 19

With NTFS there is a site at sourceforge (http://linux-ntfs . sourceforge . net) that gives some details about what they are doing, although it sounds like you have been there already .
Gorela (901)
133642 2003-04-08 00:29:00 Well so much for Sam.......

The kernel is updated, and Sam now wont boot into Linux or "failsafe" , indeed the only thing Sam can now do is "memory check" itself.

I did have the foresight to make a renamed copy or the original kernel, which is living in what is or was /boot , but have no idea how to talk lilo into booting from the backup..

:( :(

.Clueless
Clueless (181)
133643 2003-04-08 00:37:00 You should just be able to edit the /etc/lilo.conf file as root, and specify the location of the backed up kernel file? Chilling_Silence (9)
133644 2003-04-08 00:41:00 How do i edit the etc/lilo.conf file when Sam wont actually boot up in the first place? Clueless (181)
133645 2003-04-08 01:19:00 Have you got a Knoppix CD handy?
Ive done that before.. Only it was to edit the XFree86 config file :-)
Chilling_Silence (9)
133646 2003-04-08 03:25:00 Use your rescue floppy. You did make one, didn't you? Did you run lilo to update the boot sector when you change the kernel? That is essential. I would have used the NTFS only as an installable module, not compiled it into the kernel.

If you didn't make a rescue floppy, you should have a repair mode in your original installation CD.

Is your new kernel expecting a NTFS disk as the Linux boot device, rather than IDE?
Graham L (2)
133647 2003-04-08 03:45:00 The NTFS rpm does NOT need to touch the kernel, as Im guessing you've figured out.

Can it boot from NTFS though, if its read-only?
Chilling_Silence (9)
1 2 3 4