With only 2GB of RAM each, both worked perfectly. We found installation very slow, but to be fair, we were trying it on two very old PCs: a Thinkpad X61 convertible and a Sony Vaio P, a sub-netbook powered by an elderly Atom.
Debian 11 formally debuts and hits the Bullseye.Two non-Gtk Linux desktops have put out new versions.Out of beta and ready for data: 64-bit Raspberry Pi OS is here.Raspberry Pi OS update beefs up security.It configures a Raspberry Pi-themed graphical startup screen and so on, and once installed, a first-run wizard automatically starts which installs updates, creates a user account and finalizes the config. It's rather simpler than the default Debian installation process. You get the PIXEL desktop environment, which is a lightly customized version of LXDE and some basic tools: the Chromium browser, Claws email, LibreOffice, and some educational and programming-related tools.Īlthough the installation program hasn't been branded – it still says Debian everywhere – the resulting OS has. There's no choice of desktop or components, the only thing you can adjust is the disk partitioning. It asks almost no questions during installation and has very few options to tweak. I have no idea how dpkg-architecture deduces the architecture, but you could look at its documentation or source code (dpkg-architecture and much of the dpkg system in general are Perl).The Raspberry Pi Desktop is a welcome exception. You can print just one of those variables or do a test against their values with command line options to dpkg-architecture. (Normally these are the same though.) Example output on a 64-bit machine: DEB_BUILD_ARCH=amd64 It includes both what it's configured to build for, as well as the current host. I was wondering about this specifically for building software in Debian (the installed Debian system can be a 32-bit version with a 32 bit kernel, libraries, etc., or it can be a 64-bit version with stuff compiled for the 64-bit rather than 32-bit compatibility mode).ĭebian packages themselves need to know what architecture they are for (of course) when they actually create the package with all of its metadata, including platform architecture, so there is a packaging tool that outputs it for other packaging tools and scripts to use, called dpkg-architecture.
0 kommentar(er)
