Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #90409
| From | rbowman <bowman@montana.com> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Manipulating C code at the AST level, in C |
| Date | 2026-08-23 19:08 +0000 |
| Message-ID | <nf0upkF5rktU23@mid.individual.net> (permalink) |
| References | (20 earlier) <36ucnelaq_rEYhX3nZ2dnZfqnPednZ2d@giganews.com> <116c3ot$143jr$2@dont-email.me> <jhudnZxUvu7JFxf3nZ2dnZfqnPWdnZ2d@giganews.com> <nevlruF5rktU19@mid.individual.net> <j72cnbFzwue2MRf3nZ2dnZfqnPsAAAAA@giganews.com> |
On Sun, 23 Aug 2026 04:16:13 -0400, c186282 wrote: > The previous FIVE updates NEVER TOOK - poorly specified > "dependencies" I wouldn't have the energy to track/fix regardless. > "inxi -S" showed the ORIGINAL 7.x.x kernel was STILL ruling. My Mint laptop is still 6.17. I don't always watch the update process so I assume it tried 7.0, failed in the DKMS attempt and stayed with 6.17. No big deal. > "apt dist-upgrade" works better than "upgrade" or "full-upgrade". When I first installed Debian I was queasy about 'upgrade'. To me upgrade meant going to the new major release which I didn't want to do. > MX ... there are two versions ... the 'regular' version and the "AHS" > (advanced hardware support) version. The AHS uses the 7.x.x kernels, > the regular the 6.x.x ones. Have ONE box that actually NEEDS the AHS, > but I've loaded it on a couple others Just Because. I used the regular version. I don't have any hardware that needs the latest kernel. > I'd find a Y2K version of SUSE, but it probably wouldn't recognize > 90% of my hardware I still have the box set of 8.1. It would be interesting. I've got an old Compaq tower in the shed but I don't know what shape it's in. I may have stolen the PS. It would be the right vintage. I think it may be Mandrake if it boots at all. > Downloaded the most recent Mint ... I'll try it in a VM. It's still > near the top of the DistroWatch list. I think "cachy.os", an Arch, is > currently at the top. Don't love the Arch packaging scheme however CachyOS supposedly has a kernel that's optimized for gamers although I have read reviews that weren't too impressed. There are subreddits like r/ DistroHopping where many of the posts start with 'Can I run games?' etc. Distrowatch doesn't claim to know how many distros are installed, only the count of how many have been poking at the distro, sort of like the TIOBE index. Traffic consisting of 'WTF is Rust' doesn't translate to how many people actually use Rust.
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Manipulating C code at the AST level, in C Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-14 12:26 +0100
Re: Manipulating C code at the AST level, in C Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2026-08-14 13:53 +0100
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-14 21:10 +0000
Re: Manipulating C code at the AST level, in C scott@slp53.sl.home (Scott Lurndal) - 2026-08-14 16:00 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-14 23:47 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-15 07:20 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-15 11:33 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-15 22:41 -0400
Re: Manipulating C code at the AST level, in C "Carlos E. R." <robin_listas@es.invalid> - 2026-08-16 10:50 +0200
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-16 19:04 +0000
Re: Manipulating C code at the AST level, in C Jim Jackson <jj@franjam.org.uk> - 2026-08-15 11:07 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-15 12:18 +0100
Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-15 12:20 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-16 02:09 -0400
Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-16 09:59 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-16 11:42 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-17 00:02 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-17 07:10 +0000
Re: Manipulating C code at the AST level, in C Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-17 09:32 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-17 10:13 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-17 17:15 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-17 20:58 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-17 22:24 -0400
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-18 04:55 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-18 06:17 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-18 22:11 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 04:21 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-19 02:26 -0400
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:29 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:36 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:28 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:24 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-18 10:19 +0100
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-18 16:30 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 04:11 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 04:22 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-19 04:38 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 05:34 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 06:39 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-19 07:04 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:59 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 01:31 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 03:26 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 11:50 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 12:06 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-20 12:51 -0400
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-21 13:34 +0100
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-20 04:02 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 06:35 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:31 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:47 +0000
[off-topic] MA 370 flight disappearance (Was: Re: Manipulating C code at the AST level, in C) Anton Antimo <anton@safunu.org> - 2026-08-20 10:04 -0300
Re: [off-topic] MA 370 flight disappearance (Was: Re: Manipulating C code at the AST level, in C) rbowman <bowman@montana.com> - 2026-08-20 21:11 +0000
Re: [off-topic] MA 370 flight disappearance The Natural Philosopher <tnp@invalid.invalid> - 2026-08-21 13:32 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-19 02:28 -0400
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 16:57 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 22:17 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 01:34 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 03:45 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-19 23:26 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 21:40 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-20 23:42 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-21 06:10 +0000
Re: Manipulating C code at the AST level, in C Lars Poulsen <lars@beagle-ears.com> - 2026-08-21 06:01 -0700
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-21 18:36 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-21 21:46 -0400
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-22 13:13 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-22 19:53 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-22 23:47 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-23 01:21 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-23 12:48 +0100
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-23 03:25 -0400
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-23 01:50 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-23 07:30 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-23 04:16 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-23 19:08 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 06:30 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-19 14:15 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-19 19:39 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-19 22:54 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 04:03 +0000
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-20 01:25 +0100
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 03:56 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-20 04:40 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-20 04:46 +0000
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-20 04:59 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-20 21:46 +0000
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-20 22:44 +0000
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-21 04:35 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-21 00:54 -0400
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-21 00:05 -0400
Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-16 19:13 +0000
Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-17 01:14 -0400
Re: Manipulating C code at the AST level, in C Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-08-17 16:58 +0000
Re: Manipulating C code at the AST level, in C Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2026-08-17 13:44 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-17 15:31 +0100
Re: Manipulating C code at the AST level, in C Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2026-08-18 13:23 +0100
Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-18 17:16 +0100
Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-17 20:27 +0100
csiph-web