Sponsored Content
The Lounge What is on Your Mind? How to become good UNIX engineer Post 302416393 by pseudocoder on Monday 26th of April 2010 10:27:10 AM
Old 04-26-2010
Quote:
Originally Posted by solaris_user
daily UNIX usage
Yea, but not only at home.
I (and probably your next potential employer) could not respect someone calling himself UNIX Engineer without having at least 5 yrs. of working experience in a (large) company.
Ideally you will have some certification too, eg. SCSA, SCNA, SCSECA

/me is also trying to get there where you want. Gotta look for a Junior UNIX Administrator/Manager/Engineer job opportunity.

Good luck Smilie
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Good Unix Shells ?

Hey Guys i am new to Unix and i have downlaoded Cygwin for Windows and deleted it. I was just wondering is there any good shells like that for windows that just as good thanks for your time ][ce (1 Reply)
Discussion started by: IceCold
1 Replies

2. UNIX for Dummies Questions & Answers

What is the industry standard for number of servers per Unix/Linux engineer?

What is the industry standard for number of servers per Unix/Linux engineer and are there any white papers or the like that discuss this? (1 Reply)
Discussion started by: Rav78uk
1 Replies

3. UNIX for Dummies Questions & Answers

Information on Network engineer and Unix Systems Engineer

Hi, I'm exploring a few different careers( Unix System's Admin, Network Engineer, and Unix System's Engineer). I asked in another thread about System's Admin, so I have some more info on that already. I'm not finding very much info on Network Engineers or Unix System Engineers though. Can you guys... (0 Replies)
Discussion started by: hpicracing
0 Replies

4. Advertise with Us

Systems Engineer- Emeryville, CA (UNIX, C)

Systems Engineer- Emeryville, CA (UNIX, C) Gracenote is seeking a Systems Engineer to develop features and fixes in Gracenote's online media recognition service. You will contribute regularly to team design and code reviews, and be responsible for the analysis and resolution of software defects... (0 Replies)
Discussion started by: cwilliams
0 Replies
mwrite(1)						      General Commands Manual							 mwrite(1)

NAME
mwrite - mtools utility to perform a low level write (copy) of a UNIX file to DOS SYNOPSIS
mwrite [-mntv] unixfile msdosfile mwrite [-mntv] unixfile [unixfiles...] [msdosdirectory] OPTIONS
Preserves the file modification time. Specifies that a warning is not issued when an existing file is specified as the target file. If this option is not specified, the mwrite command verifies whether or not to overwrite an existing file. Specifies a text file transfer. Line terminators are converted to the appropriate format. Specifies verbose mode. Displays the new file name if the UNIX file name requires conversion. DESCRIPTION
The mwrite command copies the specified UNIX file to the named DOS file, or copies multiple UNIX files to the named DOS directory. The destination directory cannot be omitted. Reasonable care is taken to create a valid DOS file name. If an invalid name is specified, the mwrite command changes the name, then displays the new name if the -v option is specified. DOS subdirectory names that contain the '/' or '' separator are supported. If you use the '' separator or wildcards, you must enclose file names in quotes to protect them from the shell. The mcd command can be used to establish the device and the current working directory (relative to DOS), otherwise the default is A:. Not all UNIX file names are supported in the DOS world. The mwrite command may have to change UNIX names to fit the DOS file name conven- tions. 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 ----------------------------------------------- EXIT STATUS
The following exit values are returned: Success. Failure. ENVIRONMENT VARIABLES
The following environment variables affect the execution of mwrite: If set, this variable names the file that contains the name of the cur- rent mtools working directory as established by the mcd command. If this variable is not set, the file $HOME/.mcwd is used. FILES
Contains the name of the current mtools working directory as established by the mcd command. If this file does not exist, the default mtools working directory is A:. Executable file SEE ALSO
Commands: dos2unix(1) mcd(1), mcopy(1), mdiskcopy(1), mkmanifest(1), mread(1), mtools(1), unix2dos(1) mwrite(1)
All times are GMT -4. The time now is 08:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy