Sponsored Content
The Lounge What is on Your Mind? Windows Admin switching to *nix Admin Post 302499144 by Corona688 on Wednesday 23rd of February 2011 10:23:44 AM
Old 02-23-2011
One way would be courses and certifications of course, though my experience with them has been poor... Lots of canned problems and canned answers, sometimes some really distro-specific things not applicable anywhere else, and not a lot of help teaching you how to troubleshoot. You will need to learn the basics to make much sense of it of course; file permissions, users, ownership and groups, disks and partitions are radically different from Windows' organization.

Install a variety of UNIX or Linux on a computer of your own -- doesn't have to be on your 'good' computer, in fact, probably better it isn't in case something goes seriously wrong. Most any "throwaway" PIII/PIV with 512M of RAM or better is great for a home server. Linux technically isn't UNIX by the way -- in the strictest sense that means an OS literally descended from one of the original UNIX varieties, but Linux was made from scratch and distanced from UNIX for copyright reasons. FreeBSD, NetBSD, or OpenSolaris are open varieties of UNIX. Don't install one of the toy Linux varieties(Ubuntu, Knoppix, Mandriva, anything really graphically-oriented) -- the GUI pretty much takes over those and you won't learn a lot. Try Gentoo, or Debian, or Fedoracore.

And once you have it, seriously use it. Make a home webserver/fileserver, get SSH going for remote access, see what problems you have to fight through to make things work.

Last edited by Corona688; 02-23-2011 at 11:34 AM..
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Admin over the web

Can some one axplain how I can administer my sco bix over the web. It is connected to a wan and the internet acces is at another location and we do have a harware software firewall. F,Ruiz. (1 Reply)
Discussion started by: ruizf
1 Replies

2. Advertise with Us

Windows to Unix Admin

Hi, I'm looking a bit of advice on a job offer I've been made. I'm currently a Microsoft Windows Administrator, with good experience in this and also in Novell. I've just been offered a job to re-train as a UNIX Administrator. I'm not sure whether to take it or not. It's more... (4 Replies)
Discussion started by: horhif
4 Replies

3. Solaris

Solaris admin

Hey Friends, Actullay we have to create 200 users in my server as early as possible . I m not that much aware abt script writing. thier is any alternative ways for creation of users ? Thanx (4 Replies)
Discussion started by: rajaramrnb
4 Replies

4. Solaris

I need some help from a Solaris admin

OK I have a Solaris 10 Sparc running on a SUN T3-1 and the scsi driver is missing for the drive the root is on so it won't boot. I need to know if the following procedure is what I need to do to add the driver to get the system back up and running? {0} ok boot -F failsafe # mount... (0 Replies)
Discussion started by: trinityforce
0 Replies

5. What is on Your Mind?

Regarding Admin life either as DBA or UNIX Linux admin

I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that. Can we get "DAY" shifts in any one of the admin Job ? Can't we have shift timings in any company ? Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 Replies
IRCD(8) 						      System Manager's Manual							   IRCD(8)

NAME
ircd - The Undernet Internet Relay Chat Daemon SYNOPSIS
ircd [-t] [-d directory] [-f configfile] [-x debuglevel] [-h hostname] DESCRIPTION
ircd is the Undernet Internet Relay Chat daemon. ircd is a server in that its function is to "serve" the client program irc(1) with messages and commands. All commands and user messages are passed directly to ircd for processing and relaying to other servers. irc(1) depends upon there being an ircd server running somewhere for it to connect to and thus allow the user to begin talking to other users. There are many common clients including ircII, EPIC, and BitchX for UNIX, mIRC and pIRCh for Windows, and IRCle and Homer for the Macintosh. OPTIONS
-d directory This option tells the server to change to that directory and use that as a reference point when opening ircd.conf and other startup files. -t Instructs the server run in the foreground and to direct debugging output to standard output. -x# Defines the debug level for ircd. The higher the debug level, the more messages get directed to debugging file (or standard output if the -t option is used). -w interface This option is deprecated. Outgoing connections are bound to the interface specified in the M: line, and incoming connections are accepted only on interfaces specified in the P: lines. -f filename Specifies the ircd.conf file to be used for this server. The option is used to override the default ircd.conf given at compile time. -c This flag must be given if you are running ircd from /dev/console or any other situation where fd 0 isn't a TTY and you want the server to fork off and run in the background. This needs to be given if you are starting ircd from an rc (such as /etc/rc.local) file. -h hostname Allows the user to manually set the server name at startup. The default name is hostname.domainname. -p portname This is deprecated in favor of specifying server ports in P: lines. CONFIGURATION
If you plan to connect your ircd server to an existing IRC network, you will need to alter your local ircd configuration file (typically named ircd.conf) so that it will accept and make connections to other IRC servers. This file contains the hostnames, network addresses, and passwords for connections to other IRC servers around the world. Because the description of the ircd.conf file is beyond the scope of this document, please refer to the INSTALL file in the ircd documentation directory. BOOTING THE SERVER: The ircd server can be started as part of the UNIX boot procedure or just by placing the server into Unix Background. Keep in mind that if it is *not* part of your UNIXES Boot-up procedure then you will have to manually start the ircd server each time your UNIX is rebooted. This means if your UNIX is prone to crashing or going for for repairs a lot it would make sense to start the ircd server as part of your UNIX bootup procedure. In some cases the irc(1) will automatically attempt to boot the ircd server if the user is on the SAME UNIX that the ircd is supposed to be running on. If the irc(1) cannot connect to the ircd server it will try to start the server on it's own and will then try to reconnect to the newly booted ircd server. EXAMPLE
tolsun% ircd Places ircd into UNIX Background and starts up the server for use. Note: You do not have to add the "&" to this command, the program will automatically detach itself from tty. COPYRIGHT
(c) 1988,1989 University of Oulu, Computing Center, Finland, (c) 1988,1989 Department of Information Processing Science, University of Oulu, Finland (c) 1988,1989,1990,1991 Jarkko Oikarinen For full COPYRIGHT see LICENSE file with IRC package. FILES
/etc/utmp "ircd.conf" SEE ALSO
irc(1) BUGS
See the file 'BUGS' included in the distribution. AUTHOR
The current authors of the undernet IRC daemon are coder-com@undernet.org, the original author was Jarkko Oikarinen. 10 July 2000 IRCD(8)
All times are GMT -4. The time now is 06:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy