May i inquire what exactly is the goal, because the real distinction is if you actually need ring 0. Python can do either but which do you really need if it's arguing with you?
On Sat, Apr 18, 2026, 1:07 PM Greg Wooledge <[email protected]> wrote: > On Sat, Apr 18, 2026 at 11:54:30 -0600, D. R. Evans wrote: > > I have installed from scratch, from the official debian packages, jupyter > > itself, and the kernels for ipython (which is auto-installed along with > the > > jupyter installation) and R. Those kernels appear to work as expected. > > I don't think the word "kernel" means what you think it means. > > This sounds like userspace programming language stuff. Python. > > > Now how do I go about re-adding, for example, the bash kernel (which was > one > > of several kernels that used to be available and to work, but now fails > to > > do so -- any attempt to use it results in a connection failure)? All the > > various advice I've been able to find online has failed in one way or > > another, so I would very much appreciate a step-by-step description of > what > > to do in trixie to add a bash kernel. > > What on *earth* are you even talking about? > > Bash is a shell. It's a userspace application, a command interpreter > with both interactive and non-interactive modes. > > It comes in a package named "bash". You almost certainly have it > installed: > > hobbit:~$ dpkg -l bash | tail -n 1 > ii bash 5.2.37-2+b8 amd64 GNU Bourne Again SHell > > Bash is not a kernel. Linux is a kernel. Your kernel packages will > look something like this: > > hobbit:~$ dpkg -l linux-image\* | grep ^.i > ii linux-image-6.12.73+deb13-amd64 6.12.73-1 amd64 > Linux 6.12 for 64-bit PCs (signed) > ii linux-image-6.12.74+deb13+1-amd64 6.12.74-2 amd64 > Linux 6.12 for 64-bit PCs (signed) > ii linux-image-amd64 6.12.74-2 amd64 > Linux for 64-bit PCs (meta-package) > > Bash, Python, and Linux are three entirely separate things, and they have > nothing to do with one another. > > What issue are you actually having? If you're running a command which > gives an error, show us the entire terminal session, from your prompt > to the end of the output. > >
