[SOLVED] Slackware 15.0 Alpha 1

larrybpsu · 02-20-2021, 08:08 AM

Running Dual PPro, the first i686! Took three DAYS to slackpkg the Alpha 1 updates (current to 2/19). An amazing 400MHz of CPU power on this box.

Can't ssh into the system any more.

I get this error on the originating system:

Code:

PTY allocation request failed on channel 0

have to ^C out.

On the System itself, if get this in the syslog:

Code:

sshd[433]: error: openpty: No such file or directory   
sshd[433]: error: session_pty_req: session 0 alloc failed

I'm assumming that it's something to do with either openssh or glibc since openpty is part of glibc.

SCerovec · 02-20-2021, 07:48 PM

Quote:

Originally Posted by GazL

Yeah, that's the danger of these overly long development cycles. Inertia will keep folks around for a while, but once they're gone inertia will keep them from returning.

One could argue it's exactly that what filters out the most worthy ones, from those who lack the staying power and patience.

ChuangTzu · 02-20-2021, 09:55 PM

Quote:

Originally Posted by Daedra

Reading your post I immediately thought of this lol
https://www.youtube.com/watch?v=ObWrdYQ_6xY

LOL, that could apply to so many things right now...

ChuangTzu · 02-20-2021, 09:57 PM

Quote:

Originally Posted by hitest

This is a bit dark, I did laugh though. I think you're engaging in hyperbole. I think that 15.0 will arrive in months.

Remember, years are made up of months. I had too. Cheers on the news!

GazL · 02-21-2021, 05:01 AM

Quote:

Originally Posted by SCerovec

One could argue it's exactly that what filters out the most worthy ones, from those who lack the staying power and patience.

However comforting it might be to dismiss those who have left as "less worthy", I can't support that. One man's "staying power and patience" is another's "blind faith and stubbornness". Who's to say which?

hitest · 02-21-2021, 09:13 AM

Quote:

Originally Posted by GazL

However comforting it might be to dismiss those who have left as "less worthy", I can't support that. One man's "staying power and patience" is another's "blind faith and stubbornness". Who's to say which?

I like this! I agree completely! I have used Slackware since 2004 (version 10.0) and continue to do so. I do have faith that Patrick will deliver a stellar version of Slackware.
Slackware 15.0 is shaping up to be an amazing release.

hazel · 02-21-2021, 09:43 AM

Now I have got myself into a silly little knot. I'm sure there's a simple way out but I can't find it.

I have created a starter installation of Slackware-current on a new partition. It includes all the A-set packages (apart from a few that I definitely don't need) and I now want to chroot into it to create my initrd and do a few other small jobs. Then I can make it bootable via EFI/elilo and do the rest of the installation from the inside.

But I can't get chroot to work because the new bash links to an extra library (libtinfo) and also looks for a special flag (GLIBC_2.25) in glibc. These are present on the new partition of course, but it looks as if chroot won't access them by default until after it has launched the shell.

How do I get around this?

Petri Kaukasoina · 02-21-2021, 09:57 AM

Quote:

Originally Posted by hazel

But I can't get chroot to work because the new bash links to an extra library (libtinfo) and also looks for a special flag (GLIBC_2.25) in glibc. These are present on the new partition of course, but it looks as if chroot won't access them by default until after it has launched the shell.

How do I get around this?

Code:

chroot /path/to/new/install ldconfig
chroot /path/to/new/install

hazel · 02-21-2021, 10:01 AM

Thanks! That did it. I knew it would be something simple.

gegechris99 · 02-21-2021, 10:54 AM

32-bit i686 sshd error!

Quote:

Originally Posted by larrybpsu

On the System itself, if get this in the syslog:

Code:

sshd[433]: error: openpty: No such file or directory   
sshd[433]: error: session_pty_req: session 0 alloc failed

According to an Arch Linux forum thread, error could be linked to devpts not being mounted. A proposed workaround is:

Quote:

I have the same problem and I have a work around:

ssh <servername> "/bin/bash -i"
mount -t devpts devpts /dev/pts
exit

ssh <servername> and fault is gone.

But after a reboot the problem is back.

First check the proposed workaround. If it solves the problem, then you need to check /etc/fstab for the devpts mount options.

larrybpsu · 02-22-2021, 11:18 AM

Quote:

Originally Posted by gegechris99

32-bit i686 sshd error!

According to an Arch Linux forum thread, error could be linked to devpts not being mounted.

That's the problem. devpts is NOT mounted. I tried the workaround, but got this:

Code:

mount -t devpts devpts /dev/pts
mount: /dev/pts: mount point does not exist.

Quote:

First check the proposed workaround. If it solves the problem, then you need to check /etc/fstab for the devpts mount options.

This line is in the fstab, and it looks ok compared to all my other systems.

Code:

devpts           /dev/pts         devpts      gid=5,mode=620   0   0

Tried this:

Code:

mount -a
mount: /dev/pts: mount point does not exist.
mount: /dev/shm: mount point does not exist.

It's not mounting both devpts and tmpfs.

Thanks for the workaround!

bassmadrigal · 02-22-2021, 12:04 PM

Quote:

Originally Posted by larrybpsu

That's the problem. devpts is NOT mounted. I tried the workaround, but got this:

Code:

mount -t devpts devpts /dev/pts
mount: /dev/pts: mount point does not exist.

This line is in the fstab, and it looks ok compared to all my other systems.

Code:

devpts           /dev/pts         devpts      gid=5,mode=620   0   0

Tried this:

Code:

mount -a
mount: /dev/pts: mount point does not exist.
mount: /dev/shm: mount point does not exist.

It's not mounting both devpts and tmpfs.

Thanks for the workaround!

/dev/pts and /dev/shm should've been created by the devs package. Can you try reinstalling that?

LuckyCyborg · 02-22-2021, 12:08 PM

Quote:

Originally Posted by bassmadrigal

/dev/pts and /dev/shm should've been created by the devs package. Can you try reinstalling that?

Man, what sense have to reinstall devs package when all its devices are masked by (e)udev with a shiny tmpfs?

Also, reinstalling devs has a single result: messing totally the devices until reboot. Said so even Mr. Volkerding.

And all may boxes runs fine without devs, BTW...

bassmadrigal · 02-22-2021, 12:12 PM

Quote:

Originally Posted by LuckyCyborg

Man, what sense have to reinstall devs package when all its devices are masked by (e)udev with a shiny tmpfs?

Also, reinstalling devs has a single result: messing totally the devices until reboot. Said so even Mr. Volkerding.

And all may boxes runs fine without devs, BTW...

I just saw that the /dev/pts and /dev/shm locations were missing, and those locations are provided by the devs package. Seems logical to suggest reinstalling that package...

LuckyCyborg · 02-22-2021, 12:24 PM

Quote:

Originally Posted by bassmadrigal

I just saw that the /dev/pts and /dev/shm locations were missing, and those locations are provided by the devs package. Seems logical to suggest reinstalling that package...

The devices from this devs package are NOT used by system from the moment when eudev starts. Absolutely no static devices are visible on /dev.

This package was not yet removed yet from Slackware just because it is a bit difficult to uninstall it, the single proper way I found it is to bind root somewhere else and to remove the package via this directory binding.