Sponsored Content
The Lounge War Stories Do you trust your users to follow your instructions? Post 302954183 by gull04 on Saturday 5th of September 2015 06:09:50 AM
Old 09-05-2015
Hi Guys,

In a long time in this industry I've seen quite a lot, when it comes to data recovery two incidents come to mind.

The first was when a customer asked me to recover some data from an 8" floppy disk if I could.

I gave them specific instructions about making a copy and packing it for collection, when the package arrived in the office for my attention - it contained a photo copy of the original disk along with a list of files that they wanted me to recover.

The second was somewhat later and was a 5 1/4" floppy from the same customer, it arrived with a note attached saying that it was the only copy they had - the note was on a compliments slip that had been carefully stapled to the disk.

If I have learned anything in the business, it's when you think that you've made things idiot proof - you find out that the idiots have been upgraded.Smilie

Regards

Dave
 

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ssh2-keygen trust issue

I have two systems SysA & SysB having the same userid sharing the home directory via NFS mount. I need to know the steps to setup ssh trust between these two systems given that both share the home dir. I have tried all the steps to generate the keys & then creating identification &... (2 Replies)
Discussion started by: deo_kaustubh
2 Replies

2. Solaris

configuring user as trust

Hi Gurus, Got another issue. I am trying to configure a user to run some scripts through trusted user where in while logging to remote system it shouldn't ask for password. i did following to get it working but its not working i create a private and public key with the below... (1 Reply)
Discussion started by: kumarmani
1 Replies

3. HP-UX

Not Trust Host 10.10.10.10

I get a message similar to this, in the syslog file. Actually, I am trying to let the host at 10.10.10.10 access the HP-UX system. How do I get it trusted? Thanks! (2 Replies)
Discussion started by: instant000
2 Replies

4. UNIX for Dummies Questions & Answers

ssh trust issue

Hi, i am setting up ssh trust setup between two servers where SVRA is a solaris box and SVRB is a Red Hat Linux. It is asking for the password all the time. I have copied over the SVRA:/home/nagios/.ssh/id_dsa.pub as authorized_keys on to SVRB:/dat01/home/nagios/.ssh/ -bash-3.00$ ssh -vvv... (4 Replies)
Discussion started by: uxadmin007
4 Replies

5. Linux

SCEP and Trust Anchor

Hi Does anybody knows about the simple certificate enrollment protocol details ? if yes please provide me the details. And what is a trust anchor profile ? Thanks in advance. (0 Replies)
Discussion started by: chaitus.28
0 Replies

6. Shell Programming and Scripting

SSH Trust Testing

Hi, I want test the ssh trust between two host. It works fine if the trust is working fine but if the trust is not working fine it gets stuck. #!/bin/sh >/users/test/ssh.txt for i in `cat /users/test/host.txt`; do ssh test@$i uname -a >> /users/test/ssh.txt test=`cat... (0 Replies)
Discussion started by: Abhayman
0 Replies

7. What is on Your Mind?

Twitter Users: Follow the Forums on Twitter

Hey Twitter Users, You can follow the forums on Twitter: https://twitter.com/unixlinux @unixlinux Current Twitter Stats: TWEETS 76.4K FOLLOWERS 54.3K Comments or questions? Please post below. (1 Reply)
Discussion started by: Neo
1 Replies
mtools(1)						      General Commands Manual							 mtools(1)

NAME
mtools - Provides a collection of tools for manipulating DOS files DESCRIPTION
The mtools commands are a public domain collection of programs that let you read, write, and manipulate files on a DOS file system (typi- cally a diskette) from a UNIX system. Each command attempts to emulate the DOS equivalent command as closely as possible. The following commands are available: Converts a DOS file to UNIX Changes DOS file attribute options Changes or reports the DOS working directory Copies DOS files to and from a UNIX operating system Deletes a DOS file Displays contents of a DOS directory Copies a diskette to another diskette as a bit-image copy Adds a DOS file system to a low-level formatted diskette Creates a shell script to restore UNIX file names from DOS Labels a DOS volume Makes a DOS directory Removes a DOS directory Performs a low level read (copy) of a DOS file to UNIX Renames an exist- ing DOS file Displays the contents of a DOS file Performs a low level write (copy) of a UNIX file to DOS Converts a UNIX file to DOS format DOS file names optionally are composed of a drive letter followed by a colon, a subdirectory, and a file name. Subdirectory names can use either the '/' or '' separator. The use of the '' separator or wildcards requires the names to be enclosed in quotes to protect them from the shell. The regular expression "pattern matching" routines follow the UNIX rules. For example, an asterisk (*) matches all DOS files in place of asterisks separated by a dot (.) such as *.*. The archive, hidden, read-only and system attribute bits are ignored during pattern match- ing. Not all UNIX file names are supported in the DOS world. The mtools commands may have to change UNIX names to fit the DOS file name conven- tions. Most commands provide the verbose option (-v), that displays new file names if they have been changed. The following table shows some examples of file name conversions: ----------------------------------------------- UNIX name DOS name Reason for the change ----------------------------------------------- thisisatest THISISAT file name too long file.stuff FILE.STU extension too long prn.txt XRN.TXT PRN is a device name .abc X.ABC null file name hot+cold HOTXCOLD illegal character ----------------------------------------------- All options use the minus (-) option, not the slash (/) as provided under DOS conventions. The mcd command is used to establish the device and the current working directory (relative to the DOS file system), otherwise the default is assumed to be A:. All the mtools commands return 0 on success and 1 on complete failure. All mtools require a floppy diskette properly installed on the system. All mtools facilities address a device named /dev/disk/floppy, therefore, a symbolic link between the floppy device and /dev/disk/floppy is also required. RESTRICTIONS
If the proper device is not specified (when multiple disks capacities are supported), an error message from the device driver may be dis- played. This message can be ignored. EXAMPLES
If the diskette is a SCSI attached floppy drive designated device rz13, the following example sets up a floppy diskette for access by the mtools commands: # cd /dev # ./MAKEDEV disk/dsk13 You can then link the device to /dev/disk/floppy as follows: # ln -s /dev/rdisk/dsk/13c /dev/disk/floppy The following example sets up a floppy diskette for access by the mtools commands if the floppy drive is FDI attached: # cd /dev # ./MAKEDEV fd0 You can then link the device to /dev/disk/floppy as follows: # ln -s /dev/rfd0c /dev/disk/floppy The following example also sets up a SCSI attached floppy diskette for access by the mtools commands: # /usr/sbin/mknod /dev/rdisk/dsk13c c 8 21506 You can then link the device to /dev/disk/floppy as follows: # ln -s /dev/rdisk/dsk13c /dev/disk/floppy Remember to use the appropriate SCSI name and minor number for your configuration. In this example, this is dev/rdisk/dsk13c. Caution This method is recommended for use only by experienced system administrators. SEE ALSO
Commands: dos2unix(1), ln(1), mattrib(1), mcd(1), mcopy(1), mdel(1), mdir(1), mdiskcopy(1), mformat(1), mlabel(1), mmd(1), mrd(1), mread(1), mren(1), mtype(1), mwrite(1), unix2dos(1) Floppy disk interface: fd(7) Utilities: MAKEDEV(8), mknod(8) mtools(1)
All times are GMT -4. The time now is 08:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy