Sponsored Content
Full Discussion: Sink or Swim
Top Forums UNIX for Dummies Questions & Answers Sink or Swim Post 303 by divern2deep on Tuesday 21st of November 2000 10:13:51 AM
Old 11-21-2000
Question

My background as a nuclear engineer has provided me many opportunities to interact with computing. I have now decided to make the career change into the wonderful world of UNIX since my industry continues to die a slow death. Can my vague college experience (beginner at best) using UNIX suffice to get my foot in the door of a programming company while I quickly come up to speed using the books both of you (PxT and Neo) recommended? I mean you have to start somewhere in the computing industry.

I am looking at an offer to do quality assurance work using UNIX and Oracle for a company. The work would require me to work by myself writing code to test new products. I am very good at developing tests as a quality assurance engineer in the nuclear industry, but I don't know enough of the commands in UNIX to work with the language. I have not written any scripts, although I do know what they are. I am willing to learn through the discipline way both of you recommend (i.e. no shortcuts). My question now becomes, is it possible to learn as you go on the job and still keep the job? Or should I decline the offer, read and study more until I get more comfortable programming, and then re-apply later? Both of you gentleman say the only way to learn is trial by fire, but I cannot afford to accept a job and then lose it because of incompetance. (Family, etc.)

Please give me your recommendation for a humble beginning of someone who wants to get their foot in the door. I really appreciated your recent threads on your humble beginnings.

Treading Water
 

We Also Found This Discussion For You

1. Solaris

SunFire V240 CPU Heat Sink Replacement

I got a replacement Heatsink and Fan unit, but the OEM unit has the SUN Thermal Interface Material (TIM) already on the heatsink matting surface. Because mine is used it does not have the TIM. Also there are 2 different TIM material SUN used based on the Processor (1-1.28GHz uses a glue backed... (1 Reply)
Discussion started by: danneskjold0809
1 Replies
bg(1)							      General Commands Manual							     bg(1)

NAME
bg - Runs jobs in the background SYNOPSIS
bg [job_id...] Note The C shell has a built-in version of the bg command. If you are using the C shell, and want to guarantee that you are using the command described here, you must specify the full path /usr/bin/bg. See the csh(1) reference page for a description of the built-in command. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: bg: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
None OPERANDS
Specifies the job to be resumed as a background job. If no job_id operand is given, the most recently suspended job is used. The format of job_id is described in the Jobs section of the ksh(1) reference page. DESCRIPTION
If job control is enabled (see the description of set -m in the ksh(1) reference page), the bg utility resumes suspended jobs from the cur- rent environment by running them as background jobs. If the job specified by job_id is a job already running in the background, the bg utility has no effect and will exit successfully. Using bg to place a job into the background causes its process ID to become "known in the current shell execution environment", as if it had been started as an asynchronous list. See the Jobs section of the ksh(1) reference page. RESTRICTIONS
If job control is disabled, the bg utility exits with an error and no job is placed in the background. The bg utility does not work as expected when it is operating in its own utility execution environment because that environment has no suspended jobs. EXIT STATUS
The following exit values are returned: Successful completion. An error occurred. ENVIRONMENT VARIABLES
The following environment variables affect the execution of bg: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: csh(1), fg(1), jobs(1), kill(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), wait(1) Standards: standards(5) bg(1)
All times are GMT -4. The time now is 07:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy