Sponsored Content
Full Discussion: Migration to Unix
Top Forums UNIX for Dummies Questions & Answers Migration to Unix Post 56918 by Kukur on Thursday 14th of October 2004 01:36:27 PM
Old 10-14-2004
Question Migration to Unix

Hello,

I work for a very small ISP who up until now has run a combination of Win2000 and NT4 servers for our services (mail, DNS, dial-up).

Our equipment is showing it's age and we have been looking into changing into a Unix environment.

Our biggest challenge right now is our dial-up customers. The modem racks we currently have are embedded into Compaq NT4 machines and getting very tempermental.

We have one Portmaster 3, that we would like to migrate over to (once that is established we would add another PM3), but getting the user database over to a Win2000 server (and the every cooperative Active Directory) has been less than pleasant.

At this point I can either go and start learning Win2000/2003 and Active Directory or Unix.

Being an Apple fan for many years, and since the release of OS X, I would rather invest my time learning the Unix side and translate that over to the servers here at work.

My question basically is this...

What resources (websites or books) would you guys recommend for a Unix newbie to get a hold of to gain the knowledge needed to convert a small ISP into a Unix environment.

I apologize for such a broad statement (I realize there are a number of things to do), but I can't seem to get a start anywhere while I am constantly putting out the Win fires I currently have.

TIA
 

10 More Discussions You Might Find Interesting

1. Solaris

Problems with migration from Reliant Unix to Solaris

:confused: Hello folks, my company had decided to migrate from Reliant Unix to Solaris. We have an amount of sources that have to be changed a little, because these UNIX'es are slightly different. Is there a tool (hopefully free), which can do this job? Does anyone know the exactly differences, I... (2 Replies)
Discussion started by: MS-No
2 Replies

2. Shell Programming and Scripting

SCO UNIX to Linux migration

hi all i m working in a company ...and i have to migrate a C application running on SCO-UNIX to Red hat linux. can anybody tell me what is the difference between C commands and shell scripting on SCO-UNIX and LINUX. best regards harsh (3 Replies)
Discussion started by: vickey
3 Replies

3. Shell Programming and Scripting

Perl Application Migration From MPE To Unix

Hi, Iam working on migration of perl applicaion from MPE/ix OS to UNIX. Perl Application uses MPE::File Package which cannot be used in HPUX. I have identified IO::File and Filehandle package as replacement. Will the functionality of the MPE Package & Unix filehandle Package will match? ... (0 Replies)
Discussion started by: tc.omkumar
0 Replies

4. UNIX for Dummies Questions & Answers

file migration windows -> unix

I've spent all of my career on windows boxes and maybe 30 secs here an there with unix. Now I find myself with a project of migrating web files (html, swf, etc) from windows to unix. I know that unix is case sensitive and there can be no spaces in file/folder names. What else do I need to... (2 Replies)
Discussion started by: mjglass
2 Replies

5. Red Hat

tool for migration from HP Tru64 UNIX to Linux Red Hat 5

Hi, We are going to migrate our Dataware House system from HP Tru64 UNIX to Red Hat Linux 5. There are more than 500 shell scripts which are written in ksh. The schedule is very tight. So, I want to learn whether there is a tool that can help us find the incompatible shell scripts in... (2 Replies)
Discussion started by: franksubramania
2 Replies

6. UNIX for Dummies Questions & Answers

Unix file migration

Hi all, Is there a program that would make sense out of the data below; this is from MPAC unix system. I would like to get usable data that could be transferred into excel? Rich, (5 Replies)
Discussion started by: berkmillionare
5 Replies

7. HP-UX

C++ Code migration from HP Unix 11.11 to 11.31

i'm facing some problem to make my source code work in HP Unix 11.31 which works fine in HP Unix 11.11. Recently our unix server is upgraded to HP Unix 11.31, i was able to compile my source code successfully in 11.31 but i see some system call failure and socket failure. is there any steps to... (5 Replies)
Discussion started by: Madanxyz
5 Replies

8. Shell Programming and Scripting

UNIX to Linux Migration

We have certain number of scripts that run on AIX server using ksh. Now that we migrate these scripts to Linux servers. We need to know what are the changes that we have to perform in script to make it compatible to run on Linux. Say like in our Unix -AIX "print" command worked. But that did... (6 Replies)
Discussion started by: SIva81
6 Replies

9. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

10. Shell Programming and Scripting

Need advice for project UNIX to Linux migration

I am working on UNIX AIX to Linux migration. Does anybody know the good site for doing this? Thanks for contribution (4 Replies)
Discussion started by: digioleg54
4 Replies
WVDIAL.CONF(5)							File Formats Manual						    WVDIAL.CONF(5)

NAME
wvdial.conf - wvdial configuration file DESCRIPTION
When wvdial starts, it first loads its configuration from /etc/wvdial.conf, which contains basic information about the modem port, speed, and init string, along with information about your Internet Service Provider (ISP), such as the phone number, your username, and your pass- word. The configuration file /etc/wvdial.conf is in Windows "ini" file format, with sections named in square brackets and a number of variable = value pairs within each section. Here is a sample configuration file: [Dialer Defaults] Modem = /dev/ttyS2 Baud = 57600 Init = ATZ Init2 = AT S11=50 Phone = 555-4242 Username = apenwarr Password = my-password [Dialer phone2] Phone = 555-4243 [Dialer shh] Init3 = ATM0 [Dialer pulse] Dial Command = ATDP The sample configuration file above contains all of the options necessary to run the two sample command lines given above. Here is a com- plete list of settings that wvdial understands: Modem The location of the device that wvdial should use as your modem. The default is /dev/modem. Baud The speed at which wvdial will communicate with your modem. The default is 57600 baud. Init1 ... Init9 wvdial can use up to nine initialization strings to set up your modem. Before dialing, these strings are sent to the modem in numerical order. These are particularly useful when specifying multiple sections. See above for an example that uses Init3 to turn the modem's speaker off. The default is "ATZ" for Init1. Phone The phone number you want wvdial to dial. You can add up to 9 other phone numbers that wvdial will dial in order, by adding: Phone1 Phone2 Phone3 Phone4 Phone5 Phone6 Phone7 Phone8 Phone9 Dial Prefix wvdial will insert this string after the dial command and before the phone number. For example, to disable call waiting (in North America, anyway) set this to "*70,". Dial Command wvdial will use this string to tell the modem to dial. The default is "ATDT". Username You must set this to the username you use at your ISP. Login Prompt If your ISP has an unusual login procedure that wvdial is unable to figure out, you can use this option to specify a login prompt. When this prompt is received from your ISP, wvdial will send the Login string. Password You must set this to the password you use at your ISP. Ask Password By setting this option wvdial will prompt for your password on every dialin. Thus you don't have to save your password in /etc/wvdial.conf. (Option added by SuSE.) Password Prompt If your ISP has an unusual login procedure that wvdial is unable to figure out, you can use this option to specify a password prompt. When this prompt is received from you ISP, wvdial will send the Password string. PPPD Path If your system has pppd somewhere other than /usr/sbin/pppd, you will need to set this option. Auto DNS Try to get the Domain Nameserver (DNS) from the provider. This option is "on" by default. (Option added by SuSE.) Check DNS Check the Domain Nameserver (DNS) after the connection has been set up. This option is "on" by default. (Option added by SuSE.) DNS Test1 First DNS lookup for DNS check. (Option added by SuSE.) DNS Test2 Second DNS lookup for DNS check. (Option added by SuSE.) Check Def Route Check the default route after the connection has been set up. This option is "on" by default. (Option added by SuSE.) Force Address This option only applies if you have a static IP address at your ISP, and even then you probably don't need it. Some ISP's don't send the IP address as part of the PPP negotiation. This option forces pppd to use the address you give it. Remote Name If your ISP uses PAP or CHAP authentication, you might need to change this to your ISP's authentication name. In most cases, how- ever, it's safe to use the default value, "*". Carrier Check wvdial checks your modem during the connection process to ensure that it is actually online. If you have a weird modem that insists its carrier line is always down, you can disable the carrier check by setting this option to "no". Stupid Mode When wvdial is in Stupid Mode, it does not attempt to interpret any prompts from the terminal server. It starts pppd immediately after the modem connects. Apparently there are ISP's that actually give you a login prompt, but work only if you start PPP, rather than logging in. Go figure. Stupid Mode is (naturally) disabled by default. New PPPD You need this option if you have pppd version 2.3.0 or newer, to make wvdial create the file /etc/ppp/peers/wvdial. This option is enabled by default, thus if you have older pppd you need to set it to `no' (or upgrade pppd). Default Reply When wvdial detects a prompt, and it hasn't seen any clues that indicate what it should send as a response to the prompt, it defaults to sending "ppp". Sometimes this is inadequate. Use this option to override wvdial's default prompt response. Auto Reconnect If enabled, wvdial will attempt to automatically reestablish a connection if you are randomly disconnected by the other side. This option is "on" by default. Idle Seconds Set the hangup timeout in seconds. If there is inactivity for the given time the connection is shut down. A hangup timeout of 0 disables this feature. Abort on Busy If enabled, wvdial will not retry the connection if the modem says that the line is busy. This option is "off" by default. Abort on No Dialtone If enabled, wvdial will not retry the connection if the modem says that there is no dialtone. This option is "on" by default. Dial Attempts If value is set, wvdial will quit after that many tries .If set to 0, wvdial will happily keep dialling forever. Dial Timeout The maximum time in seconds that wvdial will wait for a connection to be made. Default value is 60 seconds. The wvdialconf(1) program can be used to detect your modem and fill in the Modem, Baud, and Init/Init2 options automatically. AUTHORS
Dave Coombs and Avery Pennarun for Net Integration Technologies Inc. Great contributions have been made by many people, including SuSE and RedHat. Thanks guys! SEE ALSO
wvdial(1), wvdialconf(1), pppd(8). WvDial December 2005 WVDIAL.CONF(5)
All times are GMT -4. The time now is 01:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy