--------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EFX00002 Date: 11/26/97 From: FRED@GENESIS.DEMON.CO.UK Time: 09:48pm \/To: ALL (Read 4 times) Subj: Re: change server ip-address comp.unix.admin,comp.unix.bsd.misc,comp.unix.misc,comp.unix.questions,comp.uni x.sco.misc,fidonet.unix In article <347AD60D.36AA433C@hol.fr> christian.gilbert@hol.fr "Christian Gilbert" writes: >Marcel Post wrote: >> >> Hi there, >> >> How can I change the ip-address on my unix machine? >> (another machine uses this address already). >> >how about just a simple ifconfig ??? That won't make the change permanent. -- ----------------------------------------- Lawrence Kirby | fred@genesis.demon.co.uk Wilts, England | 70734.126@compuserve.com ----------------------------------------- --- * Origin: frackit -*- The Unix/Usenet side of the tracks (1:270/210) --------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EFY00000 Date: 11/27/97 From: KTF@BC3.GUN.DE Time: 12:52am \/To: ALL (Read 4 times) Subj: Re: change server ip-address comp.unix.admin,comp.unix.bsd.misc,comp.unix.misc,comp.unix.questions,comp.uni x.sco.misc,fidonet.unix Marcel Post (marcel@srctravel.nl) wrote: > How can I change the ip-address on my unix machine? > (another machine uses this address already). > The unix version I'm using is: > UNIX System V Release 3.2 This is not enough information. Which UNIX? SCO? If yes you will most likely just have to change the IP-address of your LAN-adapter (network card). Run 'netconfig' at the root prompt (I suggest single user mode) and follow the instructions. Look for your network card, then for "SCO TCP/IP". For there are many different SCO UNIX Versions 3.2.0 up to 3.2v5.0.4 the details may vary. After running netconfig a kernel rebuild is neccessary (I think this will be done automatically). Then reboot. -- Klaus ter Fehn Wagnerstr. 4 Mobile: +49-172-2529379 40212 Duesseldorf Phone: +49-211-356880 ktf@gun.de FRG/Germany Fax: +49-211-356881 --- * Origin: frackit -*- The Unix/Usenet side of the tracks (1:270/210) --------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EFY00001 Date: 11/26/97 From: RACHAEL MUNNS Time: 05:07pm \/To: BILAL HUSAIN (Read 4 times) Subj: Re: Unix Passwd file.. In fidonet.unix, Bilal Husain wrote: >don't know where our !@#!@#! SysAdmin is keepin that file. Although I >got that file once, but when I tried next time it was gone..!! If you aren't the sysadmin, you don't need the shadow file, do you? HAND. -- Rachael Munns .............................................. 2:442/600 --- FIDOGATE 4.1.2 * Origin: TDM2, for all your Linux needs - +44-1222-689812 (2:442/600.1) --------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EFZ00000 Date: 11/26/97 From: STEVEN WILKINSON Time: 11:04pm \/To: ALL (Read 4 times) Subj: Mouse Help! I'm sorry for the cross posting but I didn't know where to put this call for help. Can anyone out there help me I need to find out what signals are present on the various lines between a serial mouse and the computer (port) when: 1. The left hand button is pressed. 2. the right hand button is pressed. The reason for the need for this information is because I'm building an interface which will need to behave as if either of the mouse buttons have been pressed. Much obliged for any help Steve. ... "What?!? This isn't the Files section?!?" ___ Blue Wave/QWK v2.12 --- ViaMAIL!/WC4 v1.30 * Origin: ViaMAIL! - Lightning Fast Mailer for Wildcat! (2:2502/1000) --------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EG100000 Date: 11/27/97 From: RPROCHOT@MAG-NET.COM Time: 06:14pm \/To: ALL (Read 4 times) Subj: Help Please-No More Windows Available comp.unix.misc,comp.unix.bsd.misc,comp.unix.sco.misc,fidonet.unix,comp.unix.ad min,comp.unix.questions --------------AAEDB27B275BFB9F005A8886 Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Date: Thu, 27 Nov 1997 10:59:58 -0800 (PST) From: Hector Subject: Unix/Portfolio MIME-Version: 1.0 Sender: hrl@hh.bc.ca We run SCO Unix, v. 3.2.4.2 and Office Portfolio, v. 2.0 on a Wyse 66 Mhz box with 48 MB RAM and 1 x 1 GB HD and 1 x 4 GB HD and WordPerfect v 5.0 and 5.2+, Faximum (electronic fax program). We have 30 -35 users running Wyse 85 or 185 terminals in vt220 mode. Our basic system as above was installed in '92. The hardware was upgraded in '94. Until this year and approximately July of this year, we have never known the problem as outlined below. The only significant change, perhaps coincidentally, was the installation of a new 4 GB HD also around this time in July. The Problem: Randomly the system will send a message to a potential user, "No More Windows Available" and the user cannot logon to the system, or, if they are able to get the Application menu, they cannot access WordPerfect. This occurs first thing in the morning or periodically throughout the day. Windows allocation method: Whenever a user starts SCO Office Portfolio, multiview allocates the desktop window a pseudo-tty. Portfolio uses the ptys stored in /dev directory and allocates them on an as needed basis. Additional pseudo-ttys are allocated (and then freed) as users open and close more windows. Portfolio runs through the mvw_ptys file which contains a list of the pseudo-ttys available on the system. Portfolio recommends 5 windows be allocated per user with a magic number of 37 users. The os uses ptys [0-32] and I believe Unix will only support up to 256 ptys. I have decreased the number of windows available through op adm and then increased the number. Both options did not correct the problem. The kernel was rebuilt each time. Suspecting a corrupt ptty as a possibility, I moved all pty's and created all new ones. No change. If two terminals attempt to logon to the system and hang, the third terminal is generally successful in getting to the desktop and application. Any suggestions? PLEASE SEND YOUR REPLIES TO ME DIRECTLY at or as well as to this news-group as I may not be able to locate your reply once you post it since I am a true novice when it comes to news groups. THANK YOU ALL VERY MUCH in advance. 8-) --------------AAEDB27B275BFB9F005A8886 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 27 Nov 1997 10:59:58 -0800 (PST)
From: Hector <hrl@hh.bc.ca>

Subject: Unix/Portfolio
MIME-Version: 1.0
Sender: hrl@hh.bc.ca
 
 

We run SCO Unix, v. 3.2.4.2 and Office Portfolio, v. 2.0 on a Wyse 66 Mhz
box with 48 MB RAM and 1 x 1 GB HD and 1 x 4 GB HD and WordPerfect v 5.0
and 5.2+, Faximum (electronic fax program).  We have 30 -35 users running
Wyse 85 or 185 terminals in vt220 mode.

Our basic system as above was installed in '92.  The hardware was
upgraded in '94.  Until this year and approximately July of this year, we
have never known the problem as outlined below.  The only ignificant
change, perhaps coincidentally, was the installation of a new 4 GB HD
also around this time in July.

The Problem: Randomly the system will send a message to a potential
user, "No More Windows Available" and the user cannot logon to the
system, or, if they are able to get the Application menu, they cannot
access WordPerfect.  This occurs first thing in the morning or
periodically throughout the day.

Windows allocation method:    Whenever a user starts SCO Office
Portfolio, multiview allocates the desktop window a pseudo-tty.
Portfolio uses the ptys stored in /dev directory and allocates them on an
as needed basis.  Additional pseudo-ttys are allocated (and then freed)
as users open and close more windows.  Portfolio runs through the
mvw_ptys file which contains a list of the pseudo-ttys available on the
system.

Portfolio recommends 5 windows be allocated per user with a magic number
of 37 users.  The os uses ptys [0-32] and I believe Unix will only
support up to 256 ptys.   I have decreased the number of windows
available through op adm and then increased the number.  Both options did
not correct the problem.  The kernel was rebuilt each time.

Suspecting a corrupt ptty as a possibility, I moved all pty's and created
all new ones.  No change.

If two terminals attempt to logon to the system and hang, the third
terminal is generally successful in getting to the desktop and application.

Any suggestions?

PLEASE SEND YOUR REPLIES TO ME DIRECTLY at <hrl@hh.bc.ca> or <rlangner@mag-net.com> as well as to this news-group as I may not be able to locate your reply once you post it since I am a true novice when it comes to news groups. THANK YOU ALL VERY MUCH in advance. 8-)
  --------------AAEDB27B275BFB9F005A8886-- --- * Origin: frackit -*- The Unix/Usenet side of the tracks (1:270/210) --------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EG100001 Date: 11/29/97 From: GRAYDS@APCI.NET Time: 10:06pm \/To: ALL (Read 4 times) Subj: Re: change server ip-address comp.unix.admin,comp.unix.bsd.misc,comp.unix.misc,comp.unix.questions,comp.uni x.sco.misc,fidonet.unix Ensure these files have the correct entries: -- /etc/defaultrouter (the default gateway/router) -- /etc/defaultdomain -- /etc/hostname.le0 -- /etc/hosts -- /etc/hosts.allow -- /etc/netmasks -- /etc/nodename -- /etc/resolv.conf Now type this command: ifconfig le0 XXX.XXX.XXX.XXX (the new IP address) Reboot and you should be done! --- * Origin: frackit -*- The Unix/Usenet side of the tracks (1:270/210) --------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EG300000 Date: 12/01/97 From: MODERATOR Time: 03:10am \/To: ALL (Read 3 times) Subj: UNIX Echo Guidelines (8/23/97) ========================================================================== I N T E R N A T I O N A L F I D O N E T U N I X C O N F E R E N C E ========================================================================== G U I D E L I N E S (1) All messages from me in my capacity as moderator will contain my "Moderator" signature with date and time of creation or indicate that status with a 'From: Moderator' heading. (2) All discussions relating to the installation, operation, and support of the Linux Operating System or applications of a Linux-specific port should be directed to the LINUX echo (available on the Zone One Backbone). Discussions pertaining to the comparision of Linux with various flavors of Unix are permitted, provided the discussion does not degenerate in to a 'How do I do this?' situation. (3) We are all professionals, and as such, should behave accordingly. Although I encourage debate on appropriate subjects, please refrain from anything that remotely resembles a personal attack upon another person's character. Stick to the facts/opinions. (4) The official language of Fidonet is English. I recognize that we do have a significant contingent of foreign participants; however the non-English speaking participants should also recognize that non-English posts are quite likely to result in a reduced response rate, therefore the use of English is encouraged. (5) Commercial advertising is prohibited, although informational postings of product or service availability may be allowed, provided that the announcement does not appear to result in commercial gain of the poster or his/her associates, and the product or service is related to the Unix Operating System. These type of postings must be limited to one message and one posting. (6) Posting of multi-part listings take up extra disk space and transfer time, and may not be of interest to all readers. It is preferred that 'lists' be offered as a text file for File Request. If a user believes that the echo would benefit from the posting of the list, the list should be netmailed to the moderator for approval prior to posting. (7) All notifications of rules violations and other rules discussions will take place via netmail. Rules violations will be crash netmailed to the participant and host sysop. Requests for cooperation posted in the echo are not to be construed as "notifications" for purposes of Rule 8. All participants must be capable of receiving crash netmail on the BBS that they post from. Check with your sysop, if you are unsure of the availa- bility. Sysops who do not provide an -inbound- netmail service to their users, will have this echo restricted from their system. (8) (a) The first notification of a rules violation will assume the violator was unfamiliar with the rules, although -all- participants are responsible for knowing and understanding the rules. As such, the first notification is intended to be -informational- only. (b) The second notification of violation of the -same- rule will be considered a warning. Only one warning will be issued per specific violation. (c) A third violation will result in the participant's access and/or sysop's feed being restricted. (9) There are no restrictions in this echo on public key encrypted ignature blocks. However, in accordance with Backbone Operating FAQ (BOFAQ), Question #8, the Backbone will not transfer -encrypted- messages, and s such, are not allowed in this echo. Until stated otherwise by the Backbone, PGP digital signature blocks with cleartext messages, do not- constitute encrypted traffic. (10) There are no restrictions on 8-bit characters. This is an International Echo, and as such has an obligation to support the necessary use of international character sets. However, abuse of the International Character Set for artistic purposes is not appropriate. (11) There are no restrictions on signature blocks; however, in onsideration of those systems that do not receive their feeds on a fixed fee or costsharing basis, please keep them to a minimum. (12) Real names are required. If it is not contained within the header of the message, then it should be included as a signature line. ========================================================================== Last Revision: 3/31/1996 Summary of changes: Changed Paragraph 4 from "European participants" to "foreign rticipants" Lawrence Garvin, lawrence@eforest.houston.tx.us Moderator, International Fidonet Unix Conference --- SendMsg/2 v1.00 --- Squish/386 v1.11 * Origin: The Enchanted Forest * Houston, Texas (1:106/6018) --------------- FIDO MESSAGE AREA==> TOPIC: 176 UNIX Ref: EG300001 Date: 12/01/97 From: MODERATOR Time: 03:10am \/To: ALL (Read 3 times) Subj: UNIX Message Statistics Status report for: UNIX ==================================================== Checked on : Fri Aug 29 21:38:20 1997 ==================================================== Number of nodes : 118 Number of messages : 123 Earliest message : Tue Jul 08 09:56:06 1997 Latest message : Fri Aug 29 19:30:22 1997 Messages per week : 16.4 over 7.5 weeks