Re: next LTS version?
On Wednesday 04 July 2018 04:50:43 didier gaumet wrote:
> Le 03/07/2018 à 23:52, Gene Heskett a écrit :
> > Greetings all;
> >
> > Since wheezy is pretty much EOL even for security stuffs, whats the
> > next version that will be LTS?
>
> From what I gather: *all* Debian stable releases are LTS for the
> relevant architectures (nowadays: x86, amd64, armhf). A possible
> source of confusion is that a stable release is managed by the Debian
> Team until its standard EOL and then by a different Debian LTS Team
> until its LTS EOL.
>
> > As a linuxcnc fan, I'd like to know what I have to build a rt, or
> > rtai-kernel on.
>
> I have never built a realtime kernel, but basically is it not about
> configuring relevant PREEMPT kernel options?
>
> And if have standard RT needs, you probably should not have to build a
> kernel at all:
> https://packages.debian.org/wheezy/linux-image-rt-686-pae
> https://packages.debian.org/wheezy/linux-image-rt-amd64
> https://packages.debian.org/wheezy/rtai
I get my sources from the kernels rt- git currently at 4.14-rt, and
have built it in under an hour on a rock64 for arm64, working on a usb3
attached drive. But before I could figure a way to install it to the
stretch it is running, the drive puked all over itself and no longer
spins up. So that work was lost. But I wasn't aware that debian actually
had rtai kernels available. That version is somewhat newer than my
machines are running.
But since I can get the sources for much newer rt kernels, I'd much
druther build that and future-proof things for a couple years.
But in terms of stability, jessie on the armhf (r-pi-3b) wins that
argument rather handily, which would mean I'd have support till the
end of june 2020. Stretch isn't there yet, at least not on the arm64,
not very stable, with 99% of its problems being related to a desktop
login that been broken since the install. So what little I do on it,
is done by a net login via ssh. And in 6 months, that well known problem
has not been fixed, so I am less than impressed.
I have a wheezy install on a spare old Dell I keep current to program
mesa cards with, running from an ssd and if it could be updated to
jessie w/o losing the data on it, would be a nearly ideal build-bot for
me. Just let it chug away until the new kernel build is done. Might even
be able, once up to jessie and the newer gcc, to cross-build for armhf
or arm64. Thats something I won't attempt on the pi as its limited
memory would make that at least a week long job probably failing in the
linker phase, binutils needs more ram than the pi has.
Is there such an updater that would take that old dell from current
wheezy to current jessie?
If so, where do I get that package? Network is available to all machines
here except that rock64.
Unforch, that stretch machine has lost the ability to define a gateway.
This is a local host based network, so how do I fix that? Here is what
did work a week ago, but now does not and nothing has been changed:
rock64@rock64:~$ cat /etc/network/interfaces.d/eth0
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.71.2
netmask 255.255.255.0
gateway 192.168.71.1
dns-nameserver 192.168.71.1
But this morning a route -n shows no gateway:
rock64@rock64:~$ sudo route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 0.0.0.0 0.0.0.0 U 202 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 202 0 0 eth0
192.168.71.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Just for completeness, resolv.conf which is a real file:
rock64@rock64:~$ cat /etc/resolv.conf
nameserver 192.168.71.1
search hosts,dns
domain coyote.den
If someone knows how to fix that, and keep it fixed in a static network,
I'd be thankfull.
Thanks for reading this far.
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: