file:/mnt/floppy does not exist

[finder]

To the list;

This is exactly what the original post brought up.Got ony ideas?

With a floppy in the floppy drive this was the output.

knoppix@ttyp0[knoppix]$ mnt /dev/fd0
bash: mnt: command not found
knoppix@ttyp0[knoppix]$ mount /dev/fd0
/dev/fd0: Input/output error
mount: mount point /mnt/auto/floppy does not exist
knoppix@ttyp0[knoppix]$ su
root@ttyp0[knoppix]# mnt /dev/floppy
bash: mnt: command not found
root@ttyp0[knoppix]# mount /dev/floppy
mount: can't find /dev/floppy in /etc/fstab or /etc/mtab
root@ttyp0[knoppix]# mount /dev/fd0
/dev/fd0: Input/output error
mount: mount point /mnt/auto/floppy does not exist
root@ttyp0[knoppix]# mount /dev/auto/floppy
mount: can't find /dev/auto/floppy in /etc/fstab or /etc/mtab
root@ttyp0[knoppix]# mnt /dev/auto/fd0
bash: mnt: command not found
root@ttyp0[knoppix]#


thanks again

finder

[CrashedAgain]

knoppix@ttyp0[knoppix]$ mount /dev/fd0
/dev/fd0: Input/output error
mount: mount point /mnt/auto/floppy does not exist

That should work. So, since it appears from fstab that konoppix is finding your floppy drive, lets try without the automounter & lets specify a mount point we know exists.

First 'sudo /etc/init.d/autofs stop' to shut down the automounter.
Now check that there is a directory /mnt/test
ls /mnt
You should get a list of the subdirectories in directory /mnt and one of them should be 'test'
Now 'sudo mount /dev/fd0 /mnt/test'
If you don't get any error message do:
ls /mnt/test
and you should get a read from your floppy.

[finder]

To the list;
Sorry about the length of these messages but what about this information?

any ideas?

let me know

finder



This is a copy of what was in my file:/etc/security/accessconf file.
Is the lower information correct?


# Login access control table.
#
# When someone logs in, the table is scanned for the first entry that
# matches the (user, host) combination, or, in case of non-networked
# logins, the first entry that matches the (user, tty) combination. The
# permissions field of that table entry determines whether the login will
# be accepted or refused.
#
# Format of the login access control table is three fields separated by a
# ":" character:
#
# [Note, if you supply a 'fieldsep=|' argument to the pam_access.so
# module, you can change the field separation character to be
# '|'. This is useful for configurations where you are trying to use
# pam_access with X applications that provide PAM_TTY values that are
# the display variable like "host:0".]
#
# permission : users : origins
#
# The first field should be a "+" (access granted) or "-" (access denied)
# character.
#
# The second field should be a list of one or more login names, group
# names, or ALL (always matches). A pattern of the form user@host is
# matched when the login name matches the "user" part, and when the
# "host" part matches the local machine name.
#
# The third field should be a list of one or more tty names (for
# non-networked logins), host names, domain names (begin with "."), host
# addresses, internet network numbers (end with "."), ALL (always
# matches) or LOCAL (matches any string that does not contain a "."
# character).
#
# If you run NIS you can use @netgroupname in host or user patterns; this
# even works for @usergroup@@hostgroup patterns. Weird.
#
# The EXCEPT operator makes it possible to write very compact rules.
#
# The group file is searched only when a name does not match that of the
# logged-in user. Both the user's primary group is matched, as well as
# groups in which users are explicitly listed.
#
# TTY NAMES: Must be in the form returned by ttyname(3) less the initial
# "/dev/" (e.g. tty1 or vc/1)
#
################################################## ############################
#
# Disallow non-root logins on tty1
#
#-:ALL EXCEPT root:tty1
#
# Disallow console logins to all but a few accounts.
#
#-:ALL EXCEPT wheel shutdown sync:LOCAL
#
# Disallow non-local logins to privileged accounts (group wheel).
#
#-:wheel:ALL EXCEPT LOCAL .win.tue.nl
#
# Some accounts are not allowed to login from anywhere:
#
#-:wsbscaro wsbsecr wsbspac wsbsym wscosor wstaiwde:ALL
#
# All other accounts are allowed to login from anywhere.
#

This was found at the end of the /etc/services/groups conf file.
Is is possible that the mnt/dev/fd0 could have been placed into a group and made off-limits
to the users? Is it possible to make these changes remotely in Knoppix when you can't have a
secure root or ssh or telnet services can be opened and run remotely?


#

#
# Here is a simple example: running 'xsh' on tty* (any ttyXXX device),
# the user 'us' is given access to the floppy (through membership of
# the floppy group)
#

#xsh;tty*&!ttyp*;us;Al0000-2400;floppy
# another example: running 'xsh' on tty* (any ttyXXX device),
# the user 'sword' is given access to games (through membership of
# the sound and play group) after work hours. (The games group owns
# high-score files and so on, so don't ever give users access to it.)
#

#xsh; tty* ;sword;!Wk0900-1800;sound, play
#xsh; tty* ;*;Al0900-1800;floppy


#
# End of group.conf file
#

This was from the end of the /etc/services/time file.
This is telling me that a time lock out can occur from root via a ssh or
telnet connection. How can this be prevented?

#
# Here is a simple example: running blank on tty* (any ttyXXX device),
# the users 'you' and 'me' are denied service all of the time
#

#blank;tty* & !ttyp*;you|me;!Al0000-2400

# Another silly example, user 'root' is denied xsh access
# from pseudo terminals at the weekend and on mondays.

#xsh;ttyp*;root;!WdMo0000-2400

#
# End of example file.



This was the only line in my /etc/services/fileshare.conf file

RESTRICT=no


*************************************

[finder]

To the list;

This is what I got when I tried your suggestion.


knoppix@ttyp0[knoppix]$ sudo /etc/init.d/autofs stop
Stopping automounter: done.
knoppix@ttyp0[knoppix]$ ls /mnt
auto cdrom floppy hd test
knoppix@ttyp0[knoppix]$ ls /mnt/test
knoppix@ttyp0[knoppix]$ ls /mnt/hd test
ls: test: No such file or directory
/mnt/hd:
knoppix@ttyp0[knoppix]$ ls /mnt/test
knoppix@ttyp0[knoppix]$ ls /mnt/fd0
ls: /mnt/fd0: No such file or directory
knoppix@ttyp0[knoppix]$ ls /mnt/dev/fd0
ls: /mnt/dev/fd0: No such file or directory
knoppix@ttyp0[knoppix]$ ls /mnt/dev/floppy
ls: /mnt/dev/floppy: No such file or directory
knoppix@ttyp0[knoppix]$ ls /mnt/floppy
knoppix@ttyp0[knoppix]$ su
root@ttyp0[knoppix]# mnt /dev/fd0
bash: mnt: command not found
root@ttyp0[knoppix]# mount /dev/fd0
/dev/fd0: Input/output error
mount: you must specify the filesystem type
root@ttyp0[knoppix]#


When I put in the last command my fd0 light lit for a few moments.

any ideas?

finder

[OErjan]

try

mount -t vfat /dev/fd0 /mnt/floppy

[CrashedAgain]

finder: you tried almost every possible combination of commands except the one I suggested:
'sudo mount /dev/fd0 /mnt/test'

AS for the possibility that some hacker is adjusting your /dev/fd0 permissions, I don't think it is possible.
But, just to be certain, read this message, copy down the commands you are going to try then shutdown your computer. Since you have no HD, there is no way a trojan con be stored on your system either on your HD or on your read only CD. So, disconnect your internet, then restart your computer. You are now guaranteed to be trojan-free so try to access your disk drive.

try

mount -t vfat /dev/fd0 /mnt/floppy

I don't think there is a '/floppy' directory on the CD, there is just a /mnt/floppy. But for certain there is a /mnt/test.

[finder]

To the list;

This was the output from your suggestion.

knoppix@ttyp0[knoppix]$ sudo mount /dev/fd0 /mnt/test
/dev/fd0: Input/output error
mount: you must specify the filesystem type
knoppix@ttyp0[knoppix]$


I very frequently reboot the machine and I cut the current/power to the machine but somehow this doesn't keep the hacker out. I somehow think that in the cron files is the ability to send a fax with a ip and with that the hacker knows where to go. The confusing part is that you do not start over anew when you reboot. There is files that remain altered. Somehow things don't function properrly and security is all disabled.
My nessus log has nothing in it for Novenmber. It never reports anything. I go to Control Center/system administration/Linux Kernel and get the following error message.

Sorry

The kernel configuration could not be read due to the following error:
cannot open /usr/src/linux/arch//config.in for reading.
Either your kernel sources contain invalid configuration rules or you just found a bug in the KDE Kernel Configurator.

any ideas?

finder

[finder]

knoppix@ttyp0[knoppix]$ mount -t vfat /dev/fd0 /mnt/floppy
mount: only root can do that
knoppix@ttyp0[knoppix]$
knoppix@ttyp0[knoppix]$ su
root@ttyp0[knoppix]# mount -t vfat /dev/fd0 /mnt/floppy
mount: mount point /mnt/floppy is a symbolic link to nowhere
root@ttyp0[knoppix]#
root@ttyp0[knoppix]#


any ideas?

finder

[CrashedAgain]

knoppix@ttyp0[knoppix]$ mount -t vfat /dev/fd0 /mnt/floppy
mount: only root can do that
knoppix@ttyp0[knoppix]$
knoppix@ttyp0[knoppix]$ su
root@ttyp0[knoppix]# mount -t vfat /dev/fd0 /mnt/floppy
mount: mount point /mnt/floppy is a symbolic link to nowhere
root@ttyp0[knoppix]#
root@ttyp0[knoppix]#


any ideas?

finder

/mnt/floppy is probably a link to /mnt/auto/floppy which doesn't exist since it is created by the automounter
try mounting on a mount point (directory) known to exist.
if you are root:
mount -t vfat /dev/fd0 /mnt/test
or if you are not root:
sudo mount -t vfat /dev/fd0 /mnt/test

[finder]

knoppix@ttyp0[knoppix]$ sudo mount -t vfat /dev/fd0 /mnt/test
mount: wrong fs type, bad option, bad superblock on /dev/fd0,
or too many mounted file systems
knoppix@ttyp0[knoppix]$ su
root@ttyp0[knoppix]# mount -t vfat /dev/fd0 /mnt/test
mount: wrong fs type, bad option, bad superblock on /dev/fd0,
or too many mounted file systems
root@ttyp0[knoppix]#