bam@sdchem.UUCP (Bret Marquis) (06/24/86)
I'm Trying to set up a login script for TRS-XENIX 1.3.? I find that I am unable to send any combination of characters which include an actual space. i.e. ogin--ogin--ogin net 1 assword burfle Theoretically I should be able to just quote "net 1" but this doesn't seem to work. Neither does \s. I don't have System III or V and my Berkeley manual doesn't apply. Any suggestions? Bret Marquis (sdcsvax,ihnp4,sys1)!bang!bam bang!bam@NOSC.ARPA
root@ozdaltx.UUCP (root) (06/27/86)
In article <246@sdchema.sdchem.UUCP>, bam@sdchem.UUCP (Bret Marquis) writes: >am unable to send any combination of characters which include an >actual space. > >i.e. ogin--ogin--ogin net 1 assword burfle >Theoretically I should be able to just quote "net 1" but this >doesn't seem to work. Neither does \s. > I assume you are setting up your L.sys file in /usr/lib/uucp..... As with the regular login, you can't include a space, neither can you do it here either. You'll have to use, 'net1' or something that conforms to the standard login parameters. Also, you might want pattern your entry to the example below: systemname Any ACU 1200 4257222 login:-BREAK-login:-BREAK-login: uucp word: roots Where if you are calling a system that is using a multispeed modem, the BREAKs help the speeds match up. Hope this helps..... Scotty ...ihnp4!cuae2!ltuxa!we53!sw013b!dj3b1!killer!ozdaltx!root XENIX Systems Consultant DISCLAIMER: "This system is mine, so this really isn't necessary!"
pmk@prometheus.UUCP (Paul M Koloc) (07/06/86)
In article <133@ozdaltx.UUCP> root@ozdaltx.UUCP (root) writes: >In article <246@sdchema.sdchem.UUCP>, bam@sdchem.UUCP (Bret Marquis) writes: >>am unable to send any combination of characters which include an >>actual space. >> >>i.e. ogin--ogin--ogin net 1 assword burfle >>Theoretically I should be able to just quote "net 1" but this >>doesn't seem to work. Neither does \s. >> > >I assume you are setting up your L.sys file in /usr/lib/uucp..... >As with the regular login, you can't include a space, neither can you >do it here either. You'll have to use, 'net1' or something that conforms >to the standard login parameters. *So far so good BUT.. . *** beware of the next poster *** > >Also, you might want pattern your entry to the example below: >systemname Any ACU 1200 4257222 login:-BREAK-login:-BREAK-login: \ > uucp word: roots >Where if you are calling a system that is using a multispeed modem, >the BREAKs help the speeds match up. Unfortunately.. . "BREAK"s are very disruptive and it takes "mucho electronic cycles" to effect the actual speed change .. . so always use "delays" with "BREAK"s. Then try one or two more logins at "that new speed" before trying the "next one". THIS CAN BE IMPORTANT IF THE CALLED SITE HASN'T RECOVERED BACK TO ITS GROUND STATE SPEED. If you call at 1200 and he first answers at 300 then switches to 1200 only use ONE "BREAK". If you need two breaks only use TWO "BREAK"s. As: if you call at 300 and he answers at 2400, then breaks to 1200, then breaks to 300. After each break you will need two or three "EOT" or delays. On some uucico's this can be expressed as \d. So consider the following double break line (calling a 2400/1200/300) baud modem supported computer. (The sample line has been broken at the backslash) sys1 Any ACU 300 5557222 login:-BREAK-EOT-EOT--log\ in:--login:-BREAK-EOT-EOT--login:--login: uucp word: burfle +---------------------------------------------------------+--------+ | Paul M. Koloc, President: (301) 445-1075 | FUSION | | Prometheus II, Ltd.; College Park, MD 20740-0222 | this | | {umcp-cs | seismo}!prometheus!pmk; pmk@prometheus.UUCP | decade | +---------------------------------------------------------+--------+