Problems with 3000UX. Answers anyone?

[Richard Buck]

I can answer a few, but not all, of your questions.


emmonsl at athena.ecs.csus.edu (L. Scott Emmons) writes:
> Sdb seems to be unable to find my source file, and it's in the current
> working directory.  Yes, compiled with -g option.   Anyone build gdb for
> 3000UX?

Working on it, as well as improved versions of adb and sdb for 2.0.

> 
> I get i/o errors when I 'q' out of more when viewing man pages.  Maybe it
> has something to do with uncompress not being happy about having the
> pipeline shutdown abruptly?

No, it's a "feature" of the cat command.  No longer used and no longer a
problem in version 2.0.

> 
> Will there be plans to ship standard, printed manual pages?  Online manual
> is great, but I like 'em on paper too.  The only ones that come with the
> amiga are introduction-level.

We recommend that people buy any printed UNIX Press manuals they want.
Many other Release 4 vendors are starting to pursue this path, and USL is
pursuing an approach that will allow all vendors to ship a subset of the
documentation and refer buyers to the generic UNIX Press set.  The reason is
simple: nobody wants to make a customer pay for many printed books they don't
need, so we let people choose and pay for only the books they need, from the 
complete set that UNIX Press prints and sells through bookstores.

Amiga 3000UX systems are shipped with a discount order form from UNIX Press,
so you can order any books you want.  Our choice for supplemental books was
to address what you call the "introduction-level" users, since these are the
people least likely to be able to use regular USL manuals and man pages.  We
will be supplementing this introductory set with an advanced networking and
administration guide soon, but we will never try to replace or compete
with the complete programmer's documentation from USL.

> 
> Will the 'sysadm' tools be fixed so that the screen picture of function
> keys will match the physical location of them?

Sort of.

> 
> And lastly, finally, can the console be set to have a particular screen
> size, color, and font, like the rest of the virtual screens can? I can't
> seem to make it work.

For version 1.1, you can permanently set the color and font, not the
resolution, but in a different way than the other screens.  In 2.0, the same
conditions apply, but one screen characteristics file handles all screens,
including the console, the same way.

For 1.1, put a line like the following near the top of /etc/inittab.  This
simply applies the color command to the console at startup.

S2::sysinit:/usr/amiga/bin/color -bc 037 -fc fcb < /dev/console > /dev/console

You can do the same thing for fonts with an sioc setfont command.

>