[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernels in testing (was: Re: Debian failed)





On Fri, Dec 16, 2022 at 8:01 AM <rhkramer@gmail.com> wrote:
On Thursday, December 15, 2022 11:35:04 PM George Olson wrote:
> I have an RX 6600 XT also. I use a 4 monitor setup and had to configure
> things so that it would work with 2 on top and 2 on the bottom. I can't
> remember exactly how I did it, but I first installed Bullseye and
> figured out it wasn't going to work. I had enough of a functional
> graphics environment and terminal to change all my sources to Testing,
> which goes by the codename Bookworm, because to me that was easier than
> trying to figure out how to use backports to install a newer kernel.

>From the peanut gallery (I almost always run with the default kernel in
whatever distro I'm using), I'm guessing that if the only thing you installed
from Testing was a kernel, that would be fairly stable.  (I imagine (but don't
know) that when kernels get to testing they have been tested fairly well, even
before showing up in Debian.


Testing and Sid track pretty close to the latest kernel releases. Testing currently has version 6.0.10. New kernel versions are first uploaded to Sid then after about a week they are uploaded to testing. Testing, when not in freeze, is more like a rolling distro than a stable distro.
 
 
 
> Once I got that running, it has basically been going without a hitch.
> Testing seems to be almost as stable as regular Debian Bullseye like I
> have on my laptop. I haven't run into any major snags yet.

--
rhk

(sig revised 20221206)

If you reply: snip, snip, and snip again; leave attributions; avoid HTML;
avoid top posting; and keep it "on list".  (Oxford comma (and semi-colon)
included at no charge.)  If you revise the topic, change the Subject: line. 
If you change the topic, start a new thread.

Writing is often meant for others to read and understand (legal documents
excepted?) -- make it easier for your reader by various means, including
liberal use of whitespace (short paragraphs, separated by whitespace / blank
lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and
references.

If someone has already responded to a question, decide whether any response
you add will be helpful or not ...

A picture is worth a thousand words.  A video (or "audio"): not so much --
divide by 10 for each minute of video (or audio) or create a transcript and
edit it to 10% of the original.

A speaker who uses ahhs, ums, or such may have a real physical or mental
disability, or may be showing disrespect for his listeners by not properly
preparing in advance and thinking before speaking.  (Remember Cicero who did
not have enough time to write a short missive.)  (That speaker might have been
"trained" to do this by being interrupted often if he pauses.)

A radio (or TV) station which broadcasts speakers with high pitched voices (or
very low pitched / gravelly voices) (which older people might not be able to
hear properly) disrespects its listeners.   Likewise if it broadcasts
extraneous or disturbing sounds (like gunfire or crying), or broadcasts
speakers using their native language (with or without an overdubbed
translation).

A person who writes a sig this long probably has issues and disrespects (and
offends) a large number of readers. ;-)
'



--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Reply to: