"Garry Freemyer" (garryfre@pacbell.net) writes:
> Pata? I never said pata. I use Sata. If I typed Pata it was by mistake and
> not intentional. I've never even heard of Pata, but I imagine it tastes
> pretty good on tortillas.
>
> device node?!?
>

Precision is everything, if you expect an answer.

When you saw "I note that the /dev/mnt/floppy directory was empty",
how are we supposed to interpret that?

Is it an error in typing, and you mean /mnt/floppy directory or have
you ended up with a direcotry in /dev where it doesn't belong?

As someone said, a mount point can be anywhere, but if you aren't
actually mounting it where you think you've mounted it, then you
won't see the results you want.

Then you say "was not unmountable". I don't think there's any message
that uses the word "unmountable". I would take that to read that
you get a message saying it can't be unmounted, and a really common
reason for that is that something is accessing the mount point. Note
that then the error message would say something about the device being
busy (I don't recall the exact words, I admit they aren't exact, but
then it's not my problem). You get this message if something is parked
in that directory, like if you've
cd /mnt/floppy

You can't umount it until you've made sure no shells or applications
point to that directory.

Michael

> "Grant" <g_r_a_n_t_@dodo.com.au> wrote in message
> news:rn6lo1p7tmuq5a2h7hm5ig07mq9o7ct2nk@4ax.com...
>> On Mon, 28 Nov 2005 05:19:48 GMT, "Garry Freemyer" <garryfre@pacbell.net>
>> wrote:
>>
>>>As I said before, I did read the manual.
>>>
>>>The floppy will NOT unmount as I mentioned before.
>>>
>>>I note that the /dev/mnt/floppy directory was empty before putting in a
>>>floppy, that was also empty. I copied the stuff to that directory and then
>>>tried /umount /dev/fd0 and got a message that this device was not
>>>unmountable.
>>
>> You appear to be confusing device nodes with mountpoints, also,
>> you confuse SATA with PATA in OP: "2 Sata ... on same EIDE cable"
>>
>> Grant.
>
>

"Garry Freemyer" <garryfre@pacbell.net> wrote:
>>> 1. Bios does not see the /dev/hdc as a boot option but this might be bios
>>> problem.
>>
>> What do you mean by this? Do you mean when you select /dev/hdc as boot
>> device it does not boot off of it? Or do you mean you cannot select
>> /dev/hdc as a device to boot off?
>
> I mean that the drive does not show up in CMOS Setup as a bootable drive. I
> can mount /dev/hdc1 via lilo off a floppy or off itself via NTLoader just
> fine.

"mount via lilo"? What exactly do you mean by that? Do you mean giving the
root option to lilo to select your root file system?

>>> 2. Floppy and CD Drives do not sense when a disk is changed. LS shows the
>>> same content as the disk that was there beforehand. I've gotten it to
>>> finally read the real content, but only after fiddling about so long that
>>> I forget how I got it to re-read.
>>
>> Are you using mount/unmount or an automounter?
>
> I tried these, I get can't unmount error.

If you didn't umount the file system you should expect that kind of weird
behavior. As RAM memory is a lot faster than HD or floppy Linux caches
reads and writes from/to disc into RAM memory. This cache might not be
flushed until you umount the file system. Maybe you will get some more
help if you type in the exact error message.

> I'm looking into an auto mounter.

Automounting is a more advanced way to do things. You should learn the
easy manually mounting first before trying to become a master of autofs :-)

>>> This fake image persists between booting! I can put in a disk or CD in
>>> today, Turn off the machine turn it back on and goto /mnt/cdrom or
>>> /mnt/fd0 with the DVD and floppy drives empty or with different media in
>>> the drives and see the file names for media that I put in yesterday!

I see two possible explanations to that behavior. 1) As another poster
suggested that you never mounted the disc before accessing it and the
files are now really on your root file system. 2) That you didn't really
reboot. I have met many users that think reboots means logging out and
then logging in again :-).

>> What programs are you using to read the directories?

> Command line slackware file listing commands like ls and Dir.

Please give us a complete example of what you are doing. Show us your
commands for mounting, copying files, umount, remount and ls the files.
Then we might be able to help you better. It is always easier to help with
command line commands.

>>> Files copied to the floppy do not actually go onto the floppy (The
>>> light does not come on), but Slack thinks the file is there if I use
>>> cp.

This is normal behavior. Files stay in cache until the floppy is umounted.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc7(at)uthyres.com Examples of addresses which go to spammers:
root@variousus.net info@k-soft.se info@k-software.biz root@localhost

Garry Freemyer wrote:
<snip>
The usual convention is to quote the bare minimum of the previous post
to which you are replying and to either interleave your reply or post
it underneath, see:
http://www.xs4all.nl/~hanb/documents/quotingguide.html
http://www.caliburn.nl/topposting.html

The top posting is usually a result of using a Microsoft product, which
leaves the cursor above the previous post.
--
Two Ravens
"...hit the squirrel..."

Henrik Carlqvist wrote:
>>I mean that the drive does not show up in CMOS Setup as a bootable drive. I
>>can mount /dev/hdc1 via lilo off a floppy or off itself via NTLoader just
>>fine.
>
>
> "mount via lilo"? What exactly do you mean by that? Do you mean giving the
> root option to lilo to select your root file system?

I believe he meant boot not mount. My motherboards BIOS allows me to
boot of just about any drive, I'm not sure about the slaves. Other
BIOS's don't allow such booting, in which case you need to use a
bootloader installed on the first disk to boot systems of other HDD.

Richard

Yes, now things are starting to make some more sense here...

Forgive my lack of prescision, I don't know the buzzwords. I think it's time
for me to read the entire man article as it seems to be up-to date. You
would not believe the amount of contradictions I ran into when trying to
read up on Linux way back in the eighties.

Anyway, I meant to say /dev/mnt/floppy not /mnt/floppy.

Also, the /dev/mnt/floppy was created by slack on install.

I remember enough to modifiy the fstab and mtab.

I note that the system seems to eat my KDE config file or some reason and
I've had to restore from this morning's back up twice today.

I did'nt get a busy message, I did my attempt to unmount via links in KDE
and they had the correct files there so I know that it was accessing the
desired device.

Yeah, I'm well aquaninted with the blooper of being in a device you are
trying to unmount or having apps running that are using it.

I gotta admit, it's a strange one. I would not blame anyone for giving up,
its a bit of a nagger.

"Michael Black" <et472@FreeNet.Carleton.CA> wrote in message
news:dme9m3$1sr$1@theodyn.ncf.ca...
> "Garry Freemyer" (garryfre@pacbell.net) writes:
>> Pata? I never said pata. I use Sata. If I typed Pata it was by mistake
>> and
>> not intentional. I've never even heard of Pata, but I imagine it tastes
>> pretty good on tortillas.
>>
>> device node?!?
>>
>
> Precision is everything, if you expect an answer.
>
> When you saw "I note that the /dev/mnt/floppy directory was empty",
> how are we supposed to interpret that?
>
> Is it an error in typing, and you mean /mnt/floppy directory or have
> you ended up with a direcotry in /dev where it doesn't belong?
>
> As someone said, a mount point can be anywhere, but if you aren't
> actually mounting it where you think you've mounted it, then you
> won't see the results you want.
>
> Then you say "was not unmountable". I don't think there's any message
> that uses the word "unmountable". I would take that to read that
> you get a message saying it can't be unmounted, and a really common
> reason for that is that something is accessing the mount point. Note
> that then the error message would say something about the device being
> busy (I don't recall the exact words, I admit they aren't exact, but
> then it's not my problem). You get this message if something is parked
> in that directory, like if you've
> cd /mnt/floppy
>
> You can't umount it until you've made sure no shells or applications
> point to that directory.
>
> Michael
>
>> "Grant" <g_r_a_n_t_@dodo.com.au> wrote in message
>> news:rn6lo1p7tmuq5a2h7hm5ig07mq9o7ct2nk@4ax.com...
>>> On Mon, 28 Nov 2005 05:19:48 GMT, "Garry Freemyer"
>>> <garryfre@pacbell.net>
>>> wrote:
>>>
>>>>As I said before, I did read the manual.
>>>>
>>>>The floppy will NOT unmount as I mentioned before.
>>>>
>>>>I note that the /dev/mnt/floppy directory was empty before putting in a
>>>>floppy, that was also empty. I copied the stuff to that directory and
>>>>then
>>>>tried /umount /dev/fd0 and got a message that this device was not
>>>>unmountable.
>>>
>>> You appear to be confusing device nodes with mountpoints, also,
>>> you confuse SATA with PATA in OP: "2 Sata ... on same EIDE cable"
>>>
>>> Grant.
>>
>>
>
>

Yep, Migrainesoft made me do it.

"Two Ravens" <two-ravens@opera$mail.com> wrote in message
news:e6idnfiCRaX_KRfeRVnyiQ@pipex.net...
> Garry Freemyer wrote:
> <snip>
> The usual convention is to quote the bare minimum of the previous post
> to which you are replying and to either interleave your reply or post
> it underneath, see:
> http://www.xs4all.nl/~hanb/documents/quotingguide.html
> http://www.caliburn.nl/topposting.html
>
> The top posting is usually a result of using a Microsoft product, which
> leaves the cursor above the previous post.
> --
> Two Ravens
> "...hit the squirrel..."

Garry Freemyer wrote:

> Yep, Migrainesoft made me do it.

One is limited by the equipment one has, alas.
--
Two Ravens
"...hit the squirrel..."

Garry Freemyer wrote:

> Yes, now things are starting to make some more sense here...
>
> Forgive my lack of prescision, I don't know the buzzwords. I think it's
> time for me to read the entire man article as it seems to be up-to date.
> You would not believe the amount of contradictions I ran into when trying
> to read up on Linux way back in the eighties.

I would think it would've been very difficult to find good documentation on
linux in the 1980's.

--
alex

Garry Freemyer <garryfre@pacbell.net> wrote:
: I gotta admit, it's a strange one. I would not blame anyone for giving up,
: its a bit of a nagger.

Until you give us a complete, verbatim, step-by-step account of what you have
attempted to do, what error messages you received (exactly, word for word)
and so on, we cannot help you get to the root of this 'nagger' of a problem.
Keep a notebook, write everything down and copy it to us. It may be a bit of
a pain to have to copy everything down verbatim, but it is the best way to
determine the root of the problem.