Why does Debian not include POSIX-specified commands like bc and ed by default?
POSIX.1-2001 Utilities[1] and POSIX.1-2008 Utilities[2] both list the commands "bc" and "ed" to be part of POSIX. Yet, in a brand new Debian installation (version 10 for example), these commands are missing by default: $ bc bash: bc: command not found $ ed bash: ed: command not found Why does Debian not include these commands by default? Of course, I can install them with "apt-get" and I did that. apt-get install bc ed The "bc" binary is only 87K in size. The entire package including the man page and documentation is only 209K in size. Similarly the "ed" binary is only 55K in size. The entire package is only 93K in size. What good reason is there not to include these tiny packages even though they are specified in POSIX? [1]: https://pubs.opengroup.org/onlinepubs/009695399/idx/utilities.html [2]: https://pubs.opengroup.org/onlinepubs/9699919799/idx/utilities.html
Re: Testing CDs for GNOME3, KDE and LXDE are missing from the download page
It makes sense that CDs are dead. But it still helps a user like me if the download size that is around 600MB to 700 MB, which is one-fifth the size of a DVD download thereby saving me bandwidth cost while being large enough to contain most of the essential software I need. netinst is too restrictive for me because I would like to write the ISO on to a CD or USB drive once and then use that to bring up my base system for the next few years. DVD is too large for me because the download five times bigger. A 600 MB to 700 MB CD download is just right for me. I understand that Gnome and KDE no longer fits in a 700 MB CD and that's fine. I also appreciate that you guys are making an effort to still provide XFCE CDs. It really does not matter whether you call it CD or DVD as long as you can provide me a 600-700 MB download. I am pretty sure there would be users who would similarly prefer 700 MB downloads for LXDE. On 16 March 2017 at 20:33, Steve McIntyre <st...@einval.com> wrote: > On Sun, Mar 12, 2017 at 09:17:49AM +0530, Lone Learner wrote: >>On 9 March 2017 at 14:51, Steve McIntyre <st...@einval.com> wrote: >>> >>> We've stopped building CDs for most purposes - they're just too small >>> to be useful in a lot of cases, and have been causing issues for >>> users. We also switched to offering the choice of desktop at tasksel >>> time, which makes it less important to offer multiple different CDs >>> tuned to install each desktop. >>> >>> For some time now we've only been building two CDs per architecture: >>> the netinst and *1* single-desktop installer CD for xfce. If you want >>> to install other desktops, grab the netinst and select during >>> installation or use DVD#1. >> >>Can someone please share why the single-desktop installer CD was made >>in favour of Xfce? Why was not some other desktop like GNOM3, KDE or >>LXDE selected for the single-desktop installer CD? > > Gnome and KDE don't fit on a single CD - we've been struggling for a > couple of releases to get a reasonable subset of each to fit, and it's > just not working any more. We actually dropped the CDs altogether for > a while, then on request brought back XFCE as a lone option for a > single-CD desktop. XFCE is reasonably small. and popular enough. > > CDs are basically dead - the world moved on to DVDs several years ago, > and now USB flash is probably most common for most users. > > -- > Steve McIntyre, Cambridge, UK.st...@einval.com > Is there anybody out there? >
Re: Testing CDs for GNOME3, KDE and LXDE are missing from the download page
On 12 March 2017 at 10:16, Felix Miata <mrma...@earthlink.net> wrote: > Lone Learner composed on 2017-03-12 09:17 (UTC-0530): > >> Can someone please share why the single-desktop installer CD was made >> in favour of Xfce? Why was not some other desktop like GNOM3, KDE or >> LXDE selected for the single-desktop installer CD? > > > Dunno, but I have to guess it is the most popular "complete" DE that > actually can be fit onto a live CD along with the other utility expected of > live media. > > Felix Miata *** http://fm.no-ip.com/ I am not talking about live CD here. I am talking about regular installer CD.
Re: Testing CDs for GNOME3, KDE and LXDE are missing from the download page
On 9 March 2017 at 14:51, Steve McIntyrewrote: > learnerl...@gmail.com wrote: >>The download page for Debian stable CDs at >>http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ has a bunch >>of options like CD-1, CD-2, etc., KDE, LXDE and XFCE. >> >>But the download page for Debian testing CDs at >>http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ does not >>seem to have CD-1 (GNOME3), KDE, LXDE, etc. >> >>Why is that? > > We've stopped building CDs for most purposes - they're just too small > to be useful in a lot of cases, and have been causing issues for > users. We also switched to offering the choice of desktop at tasksel > time, which makes it less important to offer multiple different CDs > tuned to install each desktop. > > For some time now we've only been building two CDs per architecture: > the netinst and *1* single-desktop installer CD for xfce. If you want > to install other desktops, grab the netinst and select during > installation or use DVD#1. > > -- > Steve McIntyre, Cambridge, UK.st...@einval.com Can someone please share why the single-desktop installer CD was made in favour of Xfce? Why was not some other desktop like GNOM3, KDE or LXDE selected for the single-desktop installer CD?
Testing CDs for GNOME3, KDE and LXDE are missing from the download page
The download page for Debian stable CDs at http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ has a bunch of options like CD-1, CD-2, etc., KDE, LXDE and XFCE. But the download page for Debian testing CDs at http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ does not seem to have CD-1 (GNOME3), KDE, LXDE, etc. Why is that? Where can I download the testing CDs for GNOME3, KDE, LXDE, etc.?
Why doesn't fc-match respect my match and edit rule for Courier when it does for Consolas?
I am using Debian with XFCE. Default behavior: No match or alias --- First, let me show the default behavior of my system when ~/.config/fontconfig/fonts.conf has no match or alias tags. ?xml version=1.0? !DOCTYPE fontconfig SYSTEM fonts.dtd fontconfig /fontconfig In this case, fc-match outputs the following for Courier and Consolas. lone@debian:~$ fc-match Courier n022003l.pfb: Nimbus Mono L Regular lone@debian:~$ fc-match Consolas DejaVuSans.ttf: DejaVu Sans Book Custom behaviour: When match is defined Now I have the following in ~/.config/fontconfig/fonts.conf. ?xml version=1.0? !DOCTYPE fontconfig SYSTEM fonts.dtd fontconfig !-- Courier = DejaVu Sans Mono -- match test name=familystringCourier/string/test edit name=familystringDeja Vu Sans Mono/string/edit /match !-- Consolas = DejaVu Sans Mono -- match test name=familystringConsolas/string/test edit name=familystringDeja Vu Sans Mono/string/edit /match /fontconfig In this case, fc-match outputs the following. lone@debian:~$ fc-match Courier n022003l.pfb: Nimbus Mono L Regular lone@debian:~$ fc-match Consolas DejaVuSansMono.ttf: DejaVu Sans Mono Book Question Here we see that the system has respected my substitution rule for Consolas, but it has not respected my substitution rule for Courier. Why is output of `fc-match Courier` still Nimbus Mono L and not DejaVu Sans Mono? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CANy+pPar-BvQPsaqVDJz2oHTYS-CYPuGZ1eu1dM=qg6onuj...@mail.gmail.com
Re: Editing org.gnome.desktop.background in /etc/gdm3/greeter.settings doesn't change login wallpaper
I solved the problem using the instructions in http://fabhax.com/technology/change-wallpapers-in-gnome-3.4/ On 8 October 2012 19:48, Fernando Freire freir...@up.edu wrote: On Sun, Oct 7, 2012 at 3:01 PM, Lone Learner learnerl...@gmail.com wrote: I am trying to change my GNOME 3.4 login background using the instructions in http://www.stderr.nl/Blog/Software/Gnome/Gnome3-Gdm3-Background.html But that method didn't work for me. I am using Debian (Wheezy) testing. My /etc/gdm3/greeter.settings file is like this: [org.gnome.desktop.background] picture-uri='file:///opt/wallpapers/space.jpg' picture-options='zoom' [org.gnome.desktop.session] session-name='gdm-fallback' [org.gnome.login-screen] logo='/usr/share/icons/gnome/48x48/places/debian-swirl.png' fallback-logo='/usr/share/icons/gnome/48x48/places/debian-swirl.png' [org.gnome.power-manager] icon-policy='never' [org.gnome.metacity] compositing-manager=false I have made sure that root as well as Debian-gdm user has permission to read /opt/wallpapers/space.jpg. I have also run dpkg-reconfigure gdm3 and /etc/init.d/gdm3 restart. But I don't see space.jpg as the login wallpaper. What is the issue? This method likewise did not work for me. However, I followed these directions from within a running X session from my gentoo box running GNOME3.4 and was successfully able to change my background: https://wiki.archlinux.org/index.php/GDM#Configuration I was not, however, able to change the GNOME theme, I am currently still troubleshooting this. HTH, -Fernando -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMdM6rr3KU+tLGwrVWpH_ydJvgBHZKLymLsh8Vp=klnms8a...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANy+pPb=c8e=kezc4vk+eeqw09-j4r_yor9g6dyapypy-t0...@mail.gmail.com
Re: Editing org.gnome.desktop.background in /etc/gdm3/greeter.settings doesn't change login wallpaper
Yes, it is. Do you think I am missing any step? What more can I do to troubleshoot this? On 8 October 2012 13:20, Jon Dowland j...@debian.org wrote: Is /opt definitely mounted at the time gdm3 starts? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121008075046.GA10625@debian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cany+ppz5amttuksndaqjhpswhvlph0kneb7kyq0yenyrg-v...@mail.gmail.com
Editing org.gnome.desktop.background in /etc/gdm3/greeter.settings doesn't change login wallpaper
I am trying to change my GNOME 3.4 login background using the instructions in http://www.stderr.nl/Blog/Software/Gnome/Gnome3-Gdm3-Background.html But that method didn't work for me. I am using Debian (Wheezy) testing. My /etc/gdm3/greeter.settings file is like this: [org.gnome.desktop.background] picture-uri='file:///opt/wallpapers/space.jpg' picture-options='zoom' [org.gnome.desktop.session] session-name='gdm-fallback' [org.gnome.login-screen] logo='/usr/share/icons/gnome/48x48/places/debian-swirl.png' fallback-logo='/usr/share/icons/gnome/48x48/places/debian-swirl.png' [org.gnome.power-manager] icon-policy='never' [org.gnome.metacity] compositing-manager=false I have made sure that root as well as Debian-gdm user has permission to read /opt/wallpapers/space.jpg. I have also run dpkg-reconfigure gdm3 and /etc/init.d/gdm3 restart. But I don't see space.jpg as the login wallpaper. What is the issue?
Why does Audacity show me internal mics: Internal Mic: 0 and Internal Mic: 1?
I have AlsaMixer v1.0.24.2 and if I press F6 to select sound card after running alsamixer, I get two options: - (default) 0 HDA Intel If I select - (default), the card name and chip name are displayed as PulseAudio in the top left corner. If I select HDA Intel the card name is displayed as HDA Intel and chip name is displayed as Realtek ACL268. When I launch Audacity 1.3.14-beta (Unicode), I see the following options for each pulldown menu. Audio Host: ALSA OSS Output Device (when ALSA is selected as audio host): pulse default Input Device (when ALSA is selected as audio host): HDA Intel: ALC268 Analog (hw:0,0) HDA Intel: ALC268 Analog (hw:0,2): Mic:0 HDA Intel: ALC268 Analog (hw:0,2): Internal Mic:0 HDA Intel: ALC268 Analog (hw:0,2): Line:0 HDA Intel: ALC268 Analog (hw:0,2): Mic:1 HDA Intel: ALC268 Analog (hw:0,2): Internal Mic:1 HDA Intel: ALC268 Analog (hw:0,2): Line:1 pulse: Mic:0 pulse: Internal Mic:0 pulse: Line:0 pulse: Mic:1 pulse: Internal Mic:1 pulse: Line:1 default: Mic:0 default: Internal Mic:0 default: Line:0 default: Mic:1 default: Internal Mic:1 default: Line:1 I can set the input device to any one of the following and record my voice successfully: pulse: Internal Mic:0 pulse: Internal Mic:1 default: Internal Mic:1 default: Internal Mic:1 But if I set the input device to anything else, I can't record my voice. I want to know why I have got two internal mics? As far as I know, my laptop has got only one internal mic. Why do I see two in Audacity? Here is some more output. I hope it will help you to answer my questions. If you need more output, please tell me. lone@learner:~$ arecord -l List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 2: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 lone@learner:~$ arecord -L default Playback/recording through the PulseAudio sound server pulse Playback/recording through the PulseAudio sound server front:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog Front speakers surround40:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers lone@learner:~$ aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 lone@learner:~$ aplay -L default Playback/recording through the PulseAudio sound server pulse Playback/recording through the PulseAudio sound server front:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog Front speakers surround40:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Intel,DEV=0 HDA Intel, ALC268 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
Problems detected: package initscripts left obsolete init.d script behind, package initscripts left obsolete init.d script behind, package initscripts left obsolete init.d script behind
I am not able to switch to dependency based boot. Here is the relevant output. debian:/boot/grub# dpkg-reconfigure sysv-rc info: Checking if it is safe to convert to dependency based boot. error: Unable to migrate to dependency based boot sequencing. error: Problems detected: package initscripts left obsolete init.d script behind, package initscripts left obsolete init.d script behind, package initscripts left obsolete init.d script behind See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more information about dependency based boot sequencing. To reattempt the migration process run 'dpkg-reconfigure sysv-rc'. debian:/boot/grub# dpkg-query -W -f='${Conffiles}\n' initscripts /etc/init.d/bootlogs db75db678fb0a8cce7138f5c18e44dd6 /etc/init.d/bootmisc.sh d8c6b3fb84741af57a74c3d32bc09dfb /etc/init.d/checkfs.sh 74457ecf8bd853fe1a2ba758053735dc /etc/init.d/checkroot.sh efc13158c7d643b5d4baaf68c984dcd1 /etc/init.d/halt 6ae1b3b1b8198567a5e32116077f12a2 /etc/init.d/hostname.sh 2180072dbb4e2f42f7ad4df4a2f9888d /etc/init.d/killprocs 5e404d35091fab6c4889302736ed4602 /etc/init.d/mountall.sh 6c6a7d08757efe8bd86a86cae822ce7f /etc/init.d/mountall-bootclean.sh d4994c72205f718f3b369d4dc69e0b0e /etc/init.d/mountnfs.sh 75f63a36c8957e943a297d0240ed19a3 /etc/init.d/mountnfs-bootclean.sh 6df926cddd77372967e4a1f22c174b88 /etc/init.d/mountoverflowtmp 066812f55fd49c260af4efb3eed07b96 /etc/init.d/mountdevsubfs.sh 51801719b56a5acddfb1fdefdb3bfeb1 /etc/init.d/mountkernfs.sh 3b2d43b60bc5eac5a507530f3d86bfdc /etc/init.d/mtab.sh 5cf80378aabd8f3d4622e54fa02762cd /etc/init.d/rc.local 2964c1446c6453cdde4213eede97ac38 /etc/init.d/reboot 1b9db1ef7bfd79b128ef85d5065721a6 /etc/init.d/rmnologin 3e720aea2c7de0696879cce254b00d87 /etc/init.d/sendsigs 00ed9a4cdc73711fceef76ddef67dd12 /etc/init.d/single dc13cb373c5c098a8fb95424701373e3 /etc/init.d/umountfs 11bb443ffc22d6e3f49926160812b5f1 /etc/init.d/umountnfs.sh fc0eb4b497d2d80ac3c2f39470fd3499 /etc/init.d/umountroot 3e6a08830565a2938fb009b63d8bd0b9 /etc/init.d/urandom 96d5bd37396a40ab5fe7071139f780fc /etc/default/devpts fc857c5ac5fb84d80720ed4d1c624f6e /etc/default/halt 18d9844cf8ca8608e2a559a4555e593a /etc/default/tmpfs 43c56edaa7b9a5f11017613656397493 /etc/network/if-up.d/mountnfs b46589e980727a12f480d193bad25055 /etc/init.d/stop-bootlogd 4544c7e1a2d0c713d29424d02faad237 obsolete /etc/init.d/stop-bootlogd-single 648d8624e708151500c5e299a6005afe obsolete /etc/init.d/bootlogd 267ceea04f703171e6c62f506fda3305 obsolete How can I fix this issue and convert to dependency based boot?