Forum Home
Press F1
Thread ID: 48935	2004-09-05 08:36:00	yoper help	i-gordon (962)	Press F1

Post ID	Timestamp	Content	User
269483	2004-09-06 07:32:00	Google for it man! (www.google.com)	Chilling_Silence (9)
269484	2004-09-06 07:41:00	Hope nothing I said led to your Yoper Lilo packing a sad i-. Basically I shot my Mepis Lilo by trying to add Yoper to it without knowing what I was doing and ended up in a similar situation with no OS out of 3 bootable. You could try reinstalling Yoper over the top but select the "This is an upgrade" option rather than the new install and hopefully it will rebuild your Lilo conf. If it was Graham, Chill or Jen, no doubt they would boot a Live CD distro and fix it from there, so awaiting their instruction would be the best advice I can give you. Cheers Murray P	Murray P (44)
269485	2004-09-06 08:49:00	Murray, Thanks for the help Not the first time Ihave wrecked the bootmanager and I will probably do it many more times before I get Linux working on this anti Linux computer. I usually get around the problem by reinstalling. I was hoping there was a shorter method. Chill, I did a Google on the captive ntfs, far to complicated for me. Do I really need to study this.?	i-gordon (962)
269486	2004-09-06 13:06:00	Samba has a work around to NTFS does it not, could this be employed to access your windows files. Cheers Murray P	Murray P (44)
269487	2004-09-06 13:54:00	Some success, I have my windows partitions showing up in filemanager but I cant access anything unless I go into root. I tried to alter permissions while in root and I got a warning about protocol devices not supported. blah blah. Any ideas anyone	i-gordon (962)
269488	2004-09-06 14:04:00	Can you copy and paste your fstab file here? for others to check of course :) Cheers Murray P	Murray P (44)
269489	2004-09-07 06:10:00	> Can you copy and paste your fstab file here? for > others to check of course :) > > Cheers Murray P Unfortunately I have reinstalled Yoper again before I read your message . I have done the editing of fstab again as I thought it was, but I'm back again where I was after Jen C gave me the original instructions . This is the error message I got from from this mount: wrong fs type,bad option,bad superblock on dev/hda5 or too many mounted file systems Please check that the disk is entered correctly f# Begin /etc/fstab # filesystem mount-point fs-type options dump fsck-order /dev/fd0 /floppy auto rw,exec,noauto,users 0 0 #/dev/cdrom /mnt/cdrom/ auto ro,noauto,users,exec 0 0 /dev/cdrom /mnt/cdrom supermount fs=iso9660,dev=/dev/cdrom,--,ro,iocharset=iso8859-1 0 0 none /dev/pts devpts gid=4,mode=620 0 0 none /proc proc defaults 0 0 /dev/hdb1 / ext3 defaults 1 1 /dev/hdb5 swap swap defaults 0 0 /dev/hdb6 /home ext3 defaults 1 1 /dev/scd0 /mnt/cdwriter supermount fs=iso9660,dev=/dev/scd0,--,ro,iocharset=iso8859-1 0 0 /dev/hda5 /mnt/Files ntfs auto,unmask=000,user 0 0 /dev/hda6 /mnt/Music ntfs auto,unmask=000,user 0 0 ~ ~ ~ ~ ~ "/etc/fstab" 16 lines, 825 characters 1,0-1 All stab	i-gordon (962)
269490	2004-09-07 06:19:00	That's probably trying to mount the NTFS partition before the FS driver is loaded . Won't work . That's exactly the error message I would expect for that . ;-) Next step is to get the FS driver loaded before then . ;-) If you downloaded a package, it will have had files with names like README and INSTALL which are text and will tell you what to do . Or put a couple of lines in /etc/rc . d/local . rc like modprobe nameofntfsmodule mount /mnt/Files and change the "auto" to "noauto" in fstab . rc . local is done last of all in the boot sequence .	Graham L (2)
269491	2004-09-07 06:21:00	Success again. unmask = umask framing iriot Thanks everyone OK now	i-gordon (962)
269492	2004-09-07 06:27:00	unmask .NEQ. umask :D And people call some of us "pedants" (or worse) when we say that spelling matters. :-( fstab, and all the other configuration files only have to be exactly right. So, another happy Linux user. ;-)	Graham L (2)
1 2 3