Debian 12 Desktops have different commands

johnlinux

New Member
Joined
Jan 2, 2024
Messages
28
Reaction score
2
Credits
242
When using Debian 12 if you install live KDE ISO it has the Rsync command installed If you install XFCE it does not have the Rsync command. There are a few other commands but can anyone provide a reason why a desktop would have different commands located in /usr/sbin ?

I would expect the operating system commands to be constant with the exception of Desktop version command support. Rsync is a file transfer command.
 


When using Debian 12 if you install live KDE ISO it has the Rsync command installed If you install XFCE it does not have the Rsync command. There are a few other commands but can anyone provide a reason why a desktop would have different commands located in /usr/sbin ?

I would expect the operating system commands to be constant with the exception of Desktop version command support. Rsync is a file transfer command.
The expectation that "system commands ... be constant" in different versions of debian releases, whilst seeming reasonable, doesn't take account of the way in which different versions are created. Each version, be it KDE or xfce, has its own maintainers who decide on the selection of packages that will be included. The teams that maintain these versions have maintainer's web pages which may provide some details. Users are free to contact maintainers with comments, suggestions and requests.

Basically, since the distro is free and open source, run in the main by volunteers, the decisions that are made will have their own justifications, which may or may not be publicised. Such decisions however, may have little or no substantial effect because packages are freely available to users for download so any "disadvantage", if it exists, is really only at most, an inconvenience which is a small price to pay for a free fully-featured working computer installation.
 
The expectation that "system commands ... be constant" in different versions of debian releases, whilst seeming reasonable, doesn't take account of the way in which different versions are created. Each version, be it KDE or xfce, has its own maintainers who decide on the selection of packages that will be included. The teams that maintain these versions have maintainer's web pages which may provide some details. Users are free to contact maintainers with comments, suggestions and requests.

Basically, since the distro is free and open source, run in the main by volunteers, the decisions that are made will have their own justifications, which may or may not be publicised. Such decisions however, may have little or no substantial effect because packages are freely available to users for download so any "disadvantage", if it exists, is really only at most, an inconvenience which is a small price to pay for a free fully-featured working computer installation.
That does not explain why the live version has rsync command but the installed version removes the command.
 
That does not explain why the live version has rsync command but the installed version removes the command.
If it's a problem for you why not report to the Debian developers? Also Debian is known for minimalism and stability and Debian users like to do things themselves, so running a "apt install rsync" is not seen as a problem to their user-base.

Maybe because the installer and the live iso serve different purposes and are different tools for doing something with Debian and maybe the different iso's have different people working on them.
I actually suspect the latter, as in different people working on different live iso's and the installer since it has the rsync in one of the live iso's. Why not just report it to the Debian developers instead of complaining about it here or just use apt to install it yourself?
 
If it's a problem for you why not report to the Debian developers? Also Debian is known for minimalism and stability and Debian users like to do things themselves, so running a "apt install rsync" is not seen as a problem to their user-base.

Maybe because the installer and the live iso serve different purposes and are different tools for doing something with Debian and maybe the different iso's have different people working on them.
I actually suspect the latter, as in different people working on different live iso's and the installer since it has the rsync in one of the live iso's. Why not just report it to the Debian developers instead of complaining about it here or just use apt to install it yourself?
it was reported to Debian in version 12.1. The live version showcases the product and using XFCE in version 12 if you decide to install that same live XFCE version the installed version removes rsync. Yet the live version of KDE does not remove rsync on installation.
 
it was reported to Debian in version 12.1. The live version showcases the product and using XFCE in version 12 if you decide to install that same live XFCE version the installed version removes rsync. Yet the live version of KDE does not remove rsync on installation.
Nothing anyone here can do about it. Report it: https://www.debian.org/Bugs
 
I understand. I was interested if anyone had a possible idea as to why /usr/sbin commands are different for different desktop environments.
 
@f33dm3bits

...instead of complaining about it here...

is a little harsh. I do not see the OP as having complained at all, he is simply asking why, and if we know something.

I believe it is a valid question.

@johnlinux there are precedents across the board for this type of inconsistency with Linux distros, but that does not provide an answer for your question.

With Linux Mint, for example, the installer (Ubiquity) near the end of the process of installation, removes GParted (as does Ubuntu), which I believe to be a poor choice. Ubuntu used to even remove Synaptic Package Manager, which to my mind is also an essential tool.

That being said, you would have to ask the individual distributors for an official reason, and if you find same, perhaps you can share it with us? TIA.

We do have a Dev here, and by mentioning his userid, this will bring this thread to his attention, and he may have some input.

@GatorsFan

Cheers

Chris Turner
wizardfromoz
 
is a little harsh. I do not see the OP as having complained at all, he is simply asking why, and if we know something.

I believe it is a valid question.
First the question.
There are a few other commands but can anyone provide a reason why a desktop would have different commands located in /usr/sbin ?
Then OP gets an answer from @osprey, Then OP asks the same question again.
That does not explain why the live version has rsync command but the installed version removes the command.
Then I give an answer. Then OP comments saying the same thing again.
The live version showcases the product and using XFCE in version 12 if you decide to install that same live XFCE version the installed version removes rsync. Yet the live version of KDE does not remove rsync on installation.
How it is that not complaining, asking the same thing more than once.

Since OP said this in their first post.
When using Debian 12 if you install live KDE ISO it has the Rsync command installed If you install XFCE it does not have the Rsync command.
Answer is most likely what I have said in reply #4 but can't be sure because I am not a Debian developer.
maybe the different iso's have different people working on them.

I actually suspect the latter, as in different people working on different live iso's and the installer since it has the rsync in one of the live iso's.

That being said, you would have to ask the individual distributors for an official reason, and if you find same, perhaps you can share it with us? TIA.
That's why I've been saying to report it to the Debian developers as in no one is going to know for sure if the answer is correct or not. I wasn't trying to be mean or unhelpful either, otherwise I would have not taken the time to write out a reply about their question.
 
...asking the same thing more than once.

It wasn't, IMO, rather it contained a different version of the question, but we are best off to agree to differ.

We're good

Cheers

Chris
 
Why not just report it to the Debian developers instead of complaining about it here or just use apt to install it yourself?
Debian bug tracking system
is a little harsh. I do not see the OP as having complained at all, he is simply asking why, and if we know something.
I had a poor word choice at the time of replying, I should have used the word "asking", because back to my most recent reply.
How it is that not complaining, asking the same thing more than once.
Same here.

That's why I've been saying to report it to the Debian developers as in no one is going to know for sure if the answer is correct or not. I wasn't trying to be mean or unhelpful either, otherwise I would have not taken the time to write out a reply about their question.
 
Last edited:
I would expect the operating system commands to be constant with the exception of Desktop version command support. Rsync is a file transfer command.
The simple answer is it either did not get installed due to forgetfulness, or it was not intended in the first place - I know I have forgot to put things in my Expirion Linux sometimes that should have been there - but it is up to the lead developer as to what goes in and what does not so there may be inconsistencies over different desktops, if forgotten it may be updated at the next point release
 
The simple answer is it either did not get installed due to forgetfulness, or it was not intended in the first place - I know I have forgot to put things in my Expirion Linux sometimes that should have been there - but it is up to the lead developer as to what goes in and what does not so there may be inconsistencies over different desktops, if forgotten it may be updated at the next point release
You have not understood the question. this is a fresh install no user on any distrubution has the option of deciding which linux commands get installed. All that was performed is disk partition, selection of language and time zone and that is it.
 
this is a fresh install no user on any distrubution has the option of deciding which linux commands get installed. All that was performed is disk partition, selection of language and time zone and that is it.
It depends on how you install Debian, there is "expert option" during install where you can fine tune what gets installed, you can even run a terminal after installation but before system is booted to install additional software.
 
You still do not understand. This is a live version so when Debian starts up I click on "Install Debian" and the screen i provided is what appears.
Since it appears to have worked in cinamon what are the URL links for "Known issues" and "release notes"
debian 12.6 release notes notes does not work.png
 
This appears to be a bug best reported on the Debian forums. There's not much we can do about it here.
 
You still do not understand. This is a live version so when Debian starts up I click on "Install Debian" and the screen i provided is what appears.
Since it appears to have worked in cinamon what are the URL links for "Known issues" and "release notes"
To answer the last question on links, check the following.
Link to known issues in debian bookworm:

Link to release notes:
and here:

With a problem during installation such as appears in post #16, there are several things you can do to discover some information about it.

One step is to find the log file for the installation and see if it has any useful information. During installation, it's usually the case that the user can access the virtual consoles through pressing the keys:
cntl+alt+F1, cntl+alt+F2, cntl+alt+F3, cntl+alt+F4.
In the past usage there has usually been 4 terminals, one of which is the GUI installer, but since I haven't used it recently, I can't say more about this particular disk version.

Once a log file has been found, it can usually be opened by one of the following commands
Code:
more <logfile>
less <logfile>
cat <logfile>
vi <logfile>
where <logfile> is the name of the logfile in the filesystem.

Logfiles could be in a number of different locations in the filesystem like / or /root or /root/.cache depending on the installation configurations. One can search through the filesystem on the terminals in the usual way changing directories and listing files including dotfiles.

Another means of looking for a basis for the problem is to search the source code of the calamares installer which is here: https://github.com/calamares/calamares

On nosing through the source code, in the file: netinstall.conf is the following comment:
The packages module must be correctly configured and the package manager must be runnable from within the installed system at the point where it is invoked, otherwise you'll get nothing.

That's about as close as I could get to any explanation. Essentially the on-screen message in post #16:
Failed to execute default Web Browser
input/output error
looks like a few things could have occurred. For example, the installer was not able to access the network location for the default web browser in order to install it for the user to use at this point in the installation because that location was unreachable at this particular point in time during the installation. Or, perhaps there's a problem with the hardware itself, which is often what an "input/output" error means ... the operating system may have trouble accessing the location on the disk where the application is located and so can't "take" it to RAM to run it, hence that error message. It's possible there's a bug in the code itself, though since it "worked in cinnamon", mentioned in post #16, it's difficult to know.

It's probably worth noting that linux is free of cost and the licence that is issued with the kernel and so many of the applications is an Open Source licence like the GPLv2 which is very clear and includes this statement:
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
 
Last edited:
You still do not understand. This is a live version so when Debian starts up I click on "Install Debian" and the screen i provided is what appears.
Since it appears to have worked in cinamon what are the URL links for "Known issues" and "release notes"
View attachment 22400
I can't help you because I've never had that issue because I never use the graphical installer... read: don't use the graphical installer.
The CLI one works great (and is easier) and there's a near-zero difference in the layout or functionality during the install process other than you use they keyboard.
Use the CLI installer. Issue solved.
Also, with Debian, I highly recommend the netinstall image (now merged with the firmware-non-free counterpart) because you'll get the most up-to-date system OOTB and, for next time round, it's a smaller download (~600MB ISO)

PS: If I'm coming across like an Arch Chad would, it's only because I'm being a little hyperbolic. I in no way want to sound offensive, but if I do, apologies in advance.
 
To answer the last question on links, check the following.
Link to known issues in debian bookworm:

Link to release notes:
and here:

With a problem during installation such as appears in post #16, there are several things you can do to discover some information about it.

One step is to find the log file for the installation and see if it has any useful information. During installation, it's usually the case that the user can access the virtual consoles through pressing the keys:
cntl+alt+F1, cntl+alt+F2, cntl+alt+F3, cntl+alt+F4.
In the past usage there has usually been 4 terminals, one of which is the GUI installer, but since I haven't used it recently, I can't say more about this particular disk version.

Once a log file has been found, it can usually be opened by one of the following commands
Code:
more <logfile>
less <logfile>
cat <logfile>
vi <logfile>
where <logfile> is the name of the logfile in the filesystem.

Logfiles could be in a number of different locations in the filesystem like / or /root or /root/.cache depending on the installation configurations. One can search through the filesystem on the terminals in the usual way changing directories and listing files including dotfiles.

Another means of looking for a basis for the problem is to search the source code of the calamares installer which is here: https://github.com/calamares/calamares

On nosing through the source code, in the file: netinstall.conf is the following comment:


That's about as close as I could get to any explanation. Essentially the on-screen message in post #16:

looks like a few things could have occurred. For example, the installer was not able to access the network location for the default web browser in order to install it for the user to use at this point in the installation because that location was unreachable at this particular point in time during the installation. Or, perhaps there's a problem with the hardware itself, which is often what an "input/output" error means ... the operating system may have trouble accessing the location on the disk where the application is located and so can't "take" it to RAM to run it, hence that error message. It's possible there's a bug in the code itself, though since it "worked in cinnamon", mentioned in post #16, it's difficult to know.

It's probably worth noting that linux is free of cost and the licence that is issued with the kernel and so many of the applications is an Open Source licence like the GPLv2 which is very clear and includes this statement:
The link you provided for known issues is not correct as it includes items that are optional to the installation of Debian.
 

Members online


Latest posts

Top