OK, I've managed to get both my desktop and laptop running with Slack-9.1
(current) and 2.6.0-test11. Everything seems to work, sound, agp etc.

Except that on the desktop machine, I can no longer open a KDE console shell!
When I try I get an error message saying "Unable to open a suitable terminal
device"

It works OK as root (clue?) and works fine on the laptop for all users. It also
works fine for all users under 2.4.23.

Obviously, I've missed something somewhere.....

Your mission, should you choose to accept it, is to tell me what..... ;-)

--
Pete
christy@NOattglobalSPAM.net
(make the obvious amendments to reply!)

Peter Christy wrote:
> OK, I've managed to get both my desktop and laptop running with Slack-9.1
> (current) and 2.6.0-test11. Everything seems to work, sound, agp etc.
>
> Except that on the desktop machine, I can no longer open a KDE console shell!
> When I try I get an error message saying "Unable to open a suitable terminal
> device"
>
> It works OK as root (clue?) and works fine on the laptop for all users. It also
> works fine for all users under 2.4.23.
>
> Obviously, I've missed something somewhere.....
>
> Your mission, should you choose to accept it, is to tell me what..... ;-)
>

There lives /usr/bin/konsole_grantpty which should be setuid root, maybe
this is the problem.

HTH.

bards wrote:

> There lives /usr/bin/konsole_grantpty which should be setuid root, maybe
> this is the problem.

Er, no - don't have that file on either machine (and one works). Surely, that
would affect 2.4.23 as well?

--
Pete
christy@NOattglobalSPAM.net
(make the obvious amendments to reply!)

Peter Christy wrote:

> Obviously, I've missed something somewhere.....

While configuring kernel on the misbehaving machine did you set
UNIX98_PTYS=yes ?

--
Jabber: molchun@jabber.org
PGP ID: 0x304563A8

Molchun wrote:

> While configuring kernel on the misbehaving machine did you set
> UNIX98_PTYS=yes ?

Good thought, but yes, I did configure it.

--
Pete
christy@NOattglobalSPAM.net
(make the obvious amendments to reply!)

>> OK, I've managed to get both my desktop and laptop running with Slack-9.1
>> (current) and 2.6.0-test11. Everything seems to work, sound, agp etc.
>>
>> Except that on the desktop machine, I can no longer open a KDE console
>> shell! When I try I get an error message saying "Unable to open a
>> suitable terminal device"
>>
>> It works OK as root (clue?) and works fine on the laptop for all users.
>> It also works fine for all users under 2.4.23.
>>
>> Obviously, I've missed something somewhere.....
>>
>> Your mission, should you choose to accept it, is to tell me what..... ;-)

I don't have the original post on my nes server, so excuse me answering like
this....

There is one change in 2.6 vs 2.4 regarding PTYs, that I had a problem
with...


in 2.4 if you use the devfs filesystem, you didnt need the devpts
filesystem mounted in /dev/pts...

But in 2.6 the devfs filesystem is striped down, so you have to use the
devpts filesystem too. So check to make sure you have
devpts /dev/pts devpts gid=5,mode=620 0 0
in /etc/fstab, and that you have the devpts option in the kernel
(CONFIG_DEVPTS_FS=y).




--
Дамјан (jabberID:damjan@bagra.net.mk)

Intel: where Quality is job number 0.9998782345!

?????? ?. wrote:

> There is one change in 2.6 vs 2.4 regarding PTYs, that I had a problem
> with...
>
>
> in 2.4 if you use the devfs filesystem, you didnt need the devpts
> filesystem mounted in /dev/pts...
>
> But in 2.6 the devfs filesystem is striped down, so you have to use the
> devpts filesystem too. So check to make sure you have
> devpts /dev/pts devpts gid=5,mode=620 0 0
> in /etc/fstab, and that you have the devpts option in the kernel
> (CONFIG_DEVPTS_FS=y).

Yahoo! Yes that was the correct answer, and you have won todays star prize!

Seriously, many thanks! I should have remembered that, because I remember
reading about it somewhere when I started messing about with 2.6. Somehow it
slipped down the drain and round the u-bend of my mind!

Well spotted!

--
Pete
christy@NOattglobalSPAM.net
(make the obvious amendments to reply!)