correction: "are rigging setups" On Thu, Mar 19, 2026 at 1:20 PM tom arnall <[email protected]> wrote:
> >you > >were able to describe the symptoms of your problem to your AI friend, > >and had no use for this list. > > describe the symptoms and nothing else since the bot can look at > everything in the system which relates to the problem and fix whatever > has to be fixed. > > By the way, Linux will eventually replace Windows OS. People have already > rigged setups that run on top of Linux, replacing all of the distro stuff. No > more having to whine about the fact that for example smplayer is screwed > up. You simply tell the bot which replaces the distro what you want to do > and how you want it done, the interface that is, and the bot sets it up. > The main problem with this setup, of course is the amount of energy > required to support it. But a lot of new work is being done in the nuclear > power industry. I suspect it is motivated by the need for computing power. > > > > > On Tue, Mar 17, 2026 at 9:47 PM David Wright <[email protected]> > wrote: > >> On Tue 17 Mar 2026 at 12:26:07 (-0700), tom arnall wrote: >> > On Mon, Mar 16, 2026 at 9:42 PM David Wright wrote: >> > > So summing up we have the following: >> > > >> > > A message /warns/ that in several years time new versions of Cups >> > > won't work with the current generation of printer drivers. >> > > >> > > Two openprinting links explain how and why Cups will make that >> > > transition. >> > > >> > > The OP runs cups 2.4.16-1, released back in December 2025. >> > > >> > > The OP upgraded hplip to 3.22.10+dfsg0-? (presumably >> > > 3.22.10+dfsg0-8.1), released back in April 2025. >> > > >> > > The OP can't print on an HP P1006 from a certain machine. >> > > We're not told which. >> > > >> > > The laptop can't print wirelessly to the printer, which doesn't >> > > appear to be a wireless printer anyway. >> > > >> > > Printing worked a few days ago. It's implied from linux, but >> > > but not by which machine and through what connection. >> > > >> > > A machine running Windows, presumably connected by USB, can print. >> > > >> > > It's not clear what's implied by "same machine". Does it refer back to >> > > the laptop? Or does it refer back to whatever was working a few days >> > > ago? Or does it refer forwards to the machine that's connected to the >> > > printer (ie "same" is redundant)? >> > > >> > > Or perhaps it's this scenario: the laptop should be able to print >> > > wirelessly via a router to a server connected to the (shared) printer, >> > > the server machine being able to run either Windows or linux. >> > > (Else why did the laptop try to print wirelessly?) >> > > >> > > "Can't print" is the only actual symptom that I see described here, >> > > so perhaps it doesn't really matter what refers to what. >> > > >> > > Yes, perhaps AI can see its way through all that. >> > > >> > i gave a very similar problem to codex and it saw that in about 10 >> minutes. >> > i just told it about the problem and it changed whatever on the system >> to >> > make the damn thing work. >> >> If that's the way you want to run your system, fine. But I assume you >> were able to describe the symptoms of your problem to your AI friend, >> and had no use for this list. >> >> My post was actually about describing symptoms of a problem to people >> who are unable to make direct observations themselves, because they >> don't have the problematic system sitting in front of them. >> >> Cheers, >> David. >> >>
