Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Solaris problems HELP, please

0 views
Skip to first unread message

Lord of flying horned octopi

unread,
Jun 6, 1994, 5:06:11 PM6/6/94
to
I am running tcsh in a xterm on Solaris 2.3. I am having troubles getting
the intr and susp keys to work. Ctrl-c does not kill the current process and
ctrl-z does not suspend the current process. If I rlogin as another user,
the user using a csh, the two keys work fine. "stty -a" shows that both
keys are enabled.

I am also having trouble using su. I cannot seem to su to any other user.
I simply get the message, "su: sorry" without ever being prompted for a
password. The problem began when I switched to a tcsh.

I am also having troubles with gdb. Everytime a source line is printed after
a 'n' command I also get the error message, "[tcsetpgrp failed in
terminal_inferior: Inappropriate ioctl for device]". Again, this problem
began when I started using tcsh.

Oh, and why doesn't the -x option of /usr/ucb/ps not work? "ps -x" produces
the same output as "ps". The reason I want to use /usr/ucb/ps instead of
the sysv /usr/bin/ps is because of the -x option. Why'd they go and break
the most useful ps option of all?

These are just a few of the many problems I have been having since upgrading
to Solaris. Was anything fixed from 4.x to 5.x or did they just break a
bunch of stuff?

Any help anyone could give me would be greatly apprieciated.

Michael Bresnahan

mathew

unread,
Jun 7, 1994, 12:55:33 PM6/7/94
to
In article <2t0343$p...@bigfoot.wustl.edu>,

Lord of flying horned octopi <mj...@cec1.wustl.edu> wrote:
>I am running tcsh in a xterm on Solaris 2.3. I am having troubles getting
>the intr and susp keys to work. Ctrl-c does not kill the current process and
>ctrl-z does not suspend the current process. If I rlogin as another user,
>the user using a csh, the two keys work fine. "stty -a" shows that both
>keys are enabled.
>
>I am also having trouble using su. I cannot seem to su to any other user.
>I simply get the message, "su: sorry" without ever being prompted for a
>password. The problem began when I switched to a tcsh.
>
>I am also having troubles with gdb. Everytime a source line is printed after
>a 'n' command I also get the error message, "[tcsetpgrp failed in
>terminal_inferior: Inappropriate ioctl for device]". Again, this problem
>began when I started using tcsh.

I have no trouble with ^C, ^Z and su under tcsh on Solaris 2.3. I can
send you my configuration files for the compile if you like. I can't
help with the gdb problem, as I don't use gdb.

>Oh, and why doesn't the -x option of /usr/ucb/ps not work? "ps -x" produces
>the same output as "ps". The reason I want to use /usr/ucb/ps instead of
>the sysv /usr/bin/ps is because of the -x option. Why'd they go and break
>the most useful ps option of all?

The /usr/ucb/ps is only there for compatibility. Learn to love /bin/ps.

>These are just a few of the many problems I have been having since upgrading
>to Solaris. Was anything fixed from 4.x to 5.x or did they just break a
>bunch of stuff?

Things which are a zillion times better in Solaris 2.3:

* Terminfo works
* CDs auto-mount
* Setting up modems doesn't take two days, you can use the admintool
* Some things are faster (although booting is 'king slow)
* Packages allow you to install optional stuff more easily
* Shadow passwords

That's just off the top of my head. I could probably think of more
advantages.

I think the main bone of contention is that people don't like the
printing system in SVR4. Probably with good reason, but I can't say
as I don't use it.

It's a mindset thing. If you accept that there are going to be
radical changes to your way of working, and just throw yourself in and
explore, you'll probably like it. If you're stuck in your BSD ways
and try and do things in the same way on Solaris 2.3, you'll scream in
anguish.

One thing: Your life will be much better if you avoid anything with
the letters "ucb" in. That includes /usr/ucb, /usr/ucblib and
/usr/ucbinclude. In fact, it can be helpful to rename them so that
auto-install packages can't find them.


mathew
--
http://www.mantis.co.uk/~mathew/
Looking for: POP server which understands Content-Length headers
Bug-tracking systems for UNIX, DOS and Windows

Ruth Milner

unread,
Jun 7, 1994, 5:27:32 PM6/7/94
to
In article <2t28q5$r...@sunforest.mantis.co.uk> mat...@mantis.co.uk (mathew) writes:
> * Some things are faster (although booting is 'king slow)

Actually, my impression is that booting takes about the same amount of time
as 4.1.2 . It just *feels* slower because it doesn't tell you as much while
it's coming up, so there are bigger pauses between things.

I don't suppose there's any way to get it to tell you what devices it detected
on boot? It's sure nice to be able to see how it identifies things.
--
Ruth Milner NRAO/VLA Socorro NM
Manager of Computing Systems rmi...@aoc.nrao.edu

Robert Montjoy

unread,
Jun 7, 1994, 9:33:56 PM6/7/94
to
In article <1994Jun7.2...@Mr-Hyde.aoc.nrao.edu>,

Ruth Milner <rmi...@Mr-Hyde.aoc.nrao.edu> wrote:
>In article <2t28q5$r...@sunforest.mantis.co.uk> mat...@mantis.co.uk (mathew) writes:
>> * Some things are faster (although booting is 'king slow)
>
>Actually, my impression is that booting takes about the same amount of time
>as 4.1.2 . It just *feels* slower because it doesn't tell you as much while
>it's coming up, so there are bigger pauses between things.
>
>I don't suppose there's any way to get it to tell you what devices it detected
>on boot? It's sure nice to be able to see how it identifies things.

boot -v will give you verbose output. To make it the default you
will need to change the eeprom settings.

BTW, I think booting takes just a tad longer(on our server).


--
Rob Montjoy - Computer Engineer/Systems Administrator
University of Cincinnati - Electrical and Computer Engineering
E-Mail: Rob.M...@UC.EDU - Personal or Other E-Mail

-- To Save the Earth. The Humans must die.

Adrian Booth Computing Consultants

unread,
Jun 8, 1994, 3:30:29 AM6/8/94
to

>I don't suppose there's any way to get it to tell you what devices it detected
>on boot? It's sure nice to be able to see how it identifies things.

Use boot -v from the boot PROM.

--------------------------------------------------------------------------
| Adrian Booth | |
| Adrian Booth Computing Consultants | Ph/Fax: (09) 354 4936 |
| 7 Glenrowan Pl., Willetton WA 6155 | ab...@DIALix.oz.au |
| AUSTRALIA | |
--------------------------------------------------------------------------
for a in past present future; do
for b in clients employers associates relatives neighbours pets; do
echo The opinions in this article in no way reflect the opinions of my $a $b.
done;done

Lupe Christoph

unread,
Jun 8, 1994, 2:52:29 AM6/8/94
to
rmi...@Mr-Hyde.aoc.nrao.edu (Ruth Milner) writes:

>I don't suppose there's any way to get it to tell you what devices it detected
>on boot? It's sure nice to be able to see how it identifies things.

boot -v keeps you entertained :-)
--
| lu...@alanya.isar.muc.de (private, German IN) | Disclaimer: |
| lu...@cic.de (company, XLink) | This is an unofficial |
| suninfo!alanya!lupe (for Sun Germany) | opinion of Christoph & |
| Non sunt multiplicanda entia praeter necessitatem. | Imschweiler Consulting |

0 new messages