liam@cs.qmw.ac.uk (William Roberts;) (03/21/91)
In <12567@goofy.Apple.COM> ksand@Apple.COM (Kent Sandvik) writes: >William, could you please post that file that I sent out earlier for >the A/UX Q&A about A/UX 2.0.1? I typed that stuff with vi, and never >saved a copy for own use... This is the message Kent was talking about, it also includes a couple of other useful things: ------ here's a list of the most important new things in A/UX 2.0.1: Q: What's new in A/UX 2.0.1? A: * Support for Macintosh si (with FPU unit) * Mouse control settings now working in Control Panel * Multiple Monitors support * Time and Date settings via Control Panel (as root) * New version of awk (AT&T New awk) * Latest version of Korn shell * ANSI C header file changes * Asynchronous Serial Manager support * vt100 application keypad support in the CommandShell environment * Fixed many problems with AppleTalk NBP protocol under A/Ux * sendmail will now optionally use NIS (Yellow Pages) to perform mail alias lookups. Q: Are the any known limitations with A/UX 2.0.1? A: * A/UX 2.0.1 has a new version of shared libraries. This means that binaries created with shared libraries under 2.0.1 will not work under 2.0. Either don't use shared libraries, or ship the binary with the binary with the 2.0.1 shared libraries. Note that binaries created under 2.0 with 2.0 shared libraries *will* work under 2.0.1. * The u-dot structure in the kernel has changed, so if a device driver accesses the u_phys or any field located after u_phys, it needs to be recompiled with the new header files. * Don't power-on the system with a CD-ROM inserted into the CD drive. * Don't place shared libraries on NFS mounted servers, this could cause A/UX system errors. Shared libraries should always reside on local file systems. * Support for using Imagewriters with troff text processing is not provided with 2.0.1. * In CommandShell, do not attempt "Open" from or "Save Selection" to an AppleShare volume, this will crash the Macintosh environment. * If you change the keyboard layout using the Control Panel, you need to log out and log in again to cause CommandShell to use the new keyboard layout. Q: Are there any problems with having System folders mounted with NFS under A/UX? A: Don't use the same System Folder via NFS for more than one A/UX Finder session at the same time. Files in the System folder can get corrupted if more than one user is modifying them at the same time. Q: My system freezes suddenly when I open a folder from the Finder? What's wrong? A: One problem case is that the A/UX file system is full. The A/UX file manager maintains a database in the active System Folder. If the file system is full, the File Manager can't complete many of it's operations. The suggested operation is to free some hard disk space by removing unneded files. When the hang occurs, press Control-Command-e to terminate the session. Info about the A/UX support server: Internet: aux.support.apple.com, 130.43.6.2 Phone: +1 408 559 3066 (has a Trailblazer T2500) Contains official and inoffical patches to A/UX, as well as archives of comp.unix.aux, as well as other A/UX related information. OK, if there's anything special that you would like me to check out, let me know. I would also like to see the document before it's published the first time. regards, Kent Sandvik, MacDTS
d88-jwa@byse.nada.kth.se (Jon W{tte) (03/22/91)
In article <> liam@cs.qmw.ac.uk (William Roberts;) writes:
* Don't power-on the system with a CD-ROM inserted into the CD drive.
Why ? I have _a_lot_ of stuff symlinked to the CD. It works in
2.0, ao why and how is it broken in 2.0.1 ?
* If you change the keyboard layout using the Control Panel, you need
to log out and log in again to cause CommandShell to use the new keyboard
layout.
If you start the mac envmt (or boot) with CAPS LOCK, it won't
notice caps lock until you turn it off and on again. You might
also need to type using another modifier while caps lock is off.
Has this been fixed ? I use Caps Lock to switch between Swedish
and American keyboard layout (my own KCHR) and it's _very_
annoying.
Cheers,
h+@nada.kth.se
Jon W{tte
--
"The IM-IV file manager chapter documents zillions of calls, all of which
seem to do almost the same thing and none of which seem to do what I want
them to do." -- Juri Munkki in comp.sys.mac.programmerbarnett@grymoire.crd.ge.com (Bruce Barnett) (03/22/91)
In article <3007@redstar.cs.qmw.ac.uk> liam@cs.qmw.ac.uk (William Roberts;) writes: > * Support for using Imagewriters with troff text processing is not > provided with 2.0.1. If anyone is lucky (:-) enough to have an ImageWriter or ImageWriter LQ, I wrote a filter that PROPERLY handles tbl and nroff output. The boxes and half-line feeds are supported. It also makes nroff (manual pages, etc) output print 2 times faster. My new version also "rotates" the ink on the ribbon through all 4 "colors". That is, if you have a black ribbon, it will switch "colors" on every page, making sure you don't use up all of the ink in just one of the four bands of black. Note I said nroff. Troff is another beast. But at least I can print out rough drafts in an efficient manner and have the pages line up. -- Bruce G. Barnett barnett@crd.ge.com uunet!crdgw1!barnett
coolidge@cs.uiuc.edu (John Coolidge) (03/23/91)
liam@cs.qmw.ac.uk (William Roberts;) writes: >* ANSI C header file changes Unfortunately, they still suffer from needing both _BSD_SOURCE and _SYSV_SOURCE defined to compile large classes of programs. Someday I'll patch this... >* The u-dot structure in the kernel has changed, so if a device driver >accesses the u_phys or any field located after u_phys, it needs to >be recompiled with the new header files. This probably will break gdb. A fixed version will be out Real Soon Now (note: I don't _know_ that gdb is broken, but it definitely accesses things after u_phys). >* Don't place shared libraries on NFS mounted servers, this could cause >A/UX system errors. Shared libraries should always reside on local >file systems. This may be true; however, we've been doing this since 2.0 came out with not a system crash yet. I've tried it several times with 2.0.1 and no ill effects have been forthcoming (we keep the X shared libraries on /usr/local/shlib; /usr/local is on a SparcStation 2). --John -------------------------------------------------------------------------- John L. Coolidge Internet:coolidge@cs.uiuc.edu UUCP:uiucdcs!coolidge Of course I don't speak for the U of I (or anyone else except myself) Copyright 1991 John L. Coolidge. Copying allowed if (and only if) attributed. You may redistribute this article if and only if your recipients may as well.
rmtodd@servalan.uucp (Richard Todd) (03/23/91)
barnett@grymoire.crd.ge.com (Bruce Barnett) writes: >In article <3007@redstar.cs.qmw.ac.uk> liam@cs.qmw.ac.uk (William Roberts;) writes: >> * Support for using Imagewriters with troff text processing is not >> provided with 2.0.1. Still?? I thought they said they were going to put the ImageWriter drivers back in with 2.0.1. (For those who are newcomers to A/UX, A/UX 1.1 *had* ditroff->ImageWriter II drivers. Apple took them out with 2.0. Great Ghu alone knows why. Maybe it's a plot to sell more LaserWriters.) >If anyone is lucky (:-) enough to have an ImageWriter or ImageWriter >LQ, I wrote a filter that PROPERLY handles tbl and nroff output. Hey, now, the ImageWriter II's not a bad little dot-matrix printer, especially if you can pick one up used for a couple hundred or so. (Beats the heck out of what I was using before, which was an Epson MX/80 with Graftrax :-) >"rotates" the ink on the ribbon through all 4 "colors". That is, if >you have a black ribbon, it will switch "colors" on every page, >making sure you don't use up all of the ink in just one of the four >bands of black. Damn! That's a clever little trick. I may have to implement that in my copy of the TeX DVI->ImageWriter driver... >Note I said nroff. Troff is another beast. But at least I can print >out rough drafts in an efficient manner and have the pages line up. Well, given that John Coolidge has reportedly beaten g++ into mostly working order, it may be possible to port groff to the Mac. (I tried it once, with an earlier version of g++, but ran afoul of compiler bugs...) Groff puts out TeX DVI files, and DVI->ImageWriter drivers are easy to come by.... -- Richard Todd rmtodd@uokmax.ecn.uoknor.edu rmtodd@chinet.chi.il.us rmtodd@servalan.uucp "Try looking in the Yellow Pages under 'Psychotics'." -- Michael Santana