Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #223405 > unrolled thread
| Started by | ROHIT SONI <rs499647@gmail.com> |
|---|---|
| First post | 2020-06-13 07:10 +0200 |
| Last post | 2020-06-16 13:20 +0200 |
| Articles | 20 on this page of 65 — 18 participants |
Back to article view | Back to linux.debian.user
Need commands ROHIT SONI <rs499647@gmail.com> - 2020-06-13 07:10 +0200
Re: Need commands deloptes <deloptes@gmail.com> - 2020-06-13 08:20 +0200
Re: Need commands Richard Owlett <rowlett@cloud85.net> - 2020-06-13 12:50 +0200
Re: Need commands Teemu Likonen <tlikonen@iki.fi> - 2020-06-13 13:20 +0200
Re: Need commands Mike McClain <mike.junk.46@att.net> - 2020-06-14 06:10 +0200
Re: Need commands David Wright <deblis@lionunicorn.co.uk> - 2020-06-14 17:20 +0200
Re: Need commands mick crane <mick.crane@gmail.com> - 2020-06-14 13:30 +0200
Re: Need commands <tomas@tuxteam.de> - 2020-06-14 13:50 +0200
Re: Need commands mick crane <mick.crane@gmail.com> - 2020-06-14 14:20 +0200
Re: Need commands mick crane <mick.crane@gmail.com> - 2020-06-14 14:40 +0200
Re: Need commands <tomas@tuxteam.de> - 2020-06-14 15:50 +0200
Re: Need commands Greg Wooledge <wooledg@eeg.ccf.org> - 2020-06-15 14:10 +0200
Re: Need commands <tomas@tuxteam.de> - 2020-06-15 14:10 +0200
Re: Need commands davidson <davidson@freevolt.org> - 2020-06-16 10:50 +0200
bash-completion pros/cons (was: Re: Need commands) l0f4r0@tuta.io - 2020-06-16 13:00 +0200
Re: bash-completion pros/cons (was: Re: Need commands) Greg Wooledge <wooledg@eeg.ccf.org> - 2020-06-16 13:30 +0200
Re: bash-completion pros/cons (was: Re: Need commands) l0f4r0@tuta.io - 2020-06-16 14:00 +0200
Re: bash-completion pros/cons (was: Re: Need commands) <tomas@tuxteam.de> - 2020-06-16 15:00 +0200
Re: bash-completion pros/cons The Wanderer <wanderer@fastmail.fm> - 2020-06-16 15:20 +0200
Re: bash-completion pros/cons David Wright <deblis@lionunicorn.co.uk> - 2020-06-16 21:50 +0200
Re: bash-completion pros/cons Anders Andersson <pipatron@gmail.com> - 2020-06-17 10:10 +0200
Re: bash-completion pros/cons David Wright <deblis@lionunicorn.co.uk> - 2020-06-18 21:20 +0200
Re: bash-completion pros/cons David Wright <deblis@lionunicorn.co.uk> - 2020-06-18 22:20 +0200
Re: bash-completion pros/cons David Wright <deblis@lionunicorn.co.uk> - 2020-06-19 04:20 +0200
Re: bash-completion pros/cons <tomas@tuxteam.de> - 2020-06-17 10:40 +0200
Disabling recommends - was [Re: bash-completion pros/cons] Richard Owlett <rowlett@cloud85.net> - 2020-06-17 12:00 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] <tomas@tuxteam.de> - 2020-06-17 13:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Richard Owlett <rowlett@cloud85.net> - 2020-06-17 13:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] <tomas@tuxteam.de> - 2020-06-17 13:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Richard Owlett <rowlett@cloud85.net> - 2020-06-17 14:00 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] <tomas@tuxteam.de> - 2020-06-17 14:30 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Richard Owlett <rowlett@cloud85.net> - 2020-06-17 14:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-17 19:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] David Wright <deblis@lionunicorn.co.uk> - 2020-06-17 21:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-17 21:50 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] David Wright <deblis@lionunicorn.co.uk> - 2020-06-18 21:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-19 17:30 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Marco Möller <talby@debianlists.mobilxpress.net> - 2020-06-19 23:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Tom Dial <tddial@comcast.net> - 2020-06-19 23:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-20 01:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-20 17:00 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-20 19:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-20 21:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Tom Dial <tddial@comcast.net> - 2020-06-21 01:10 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-21 14:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-19 05:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-19 17:00 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-19 05:30 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Richard Owlett <rowlett@cloud85.net> - 2020-06-19 13:30 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] David Wright <deblis@lionunicorn.co.uk> - 2020-06-19 16:40 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Andy Smith <andy@strugglers.net> - 2020-06-19 19:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-20 17:10 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-19 19:50 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-18 02:00 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] <tomas@tuxteam.de> - 2020-06-18 10:20 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Richard Owlett <rowlett@cloud85.net> - 2020-06-18 13:50 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] <tomas@tuxteam.de> - 2020-06-18 14:50 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] Brian <ad44@cityscape.co.uk> - 2020-06-18 21:00 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] <tomas@tuxteam.de> - 2020-06-18 21:10 +0200
Re: Disabling recommends - was [Re: bash-completion pros/cons] David Wright <deblis@lionunicorn.co.uk> - 2020-06-18 21:20 +0200
Re: bash-completion pros/cons (was: Re: Need commands) davidson <davidson@freevolt.org> - 2020-06-18 09:30 +0200
Re: bash-completion pros/cons (was: Re: Need commands) <tomas@tuxteam.de> - 2020-06-18 10:20 +0200
Re: bash-completion pros/cons (was: Re: Need commands) davidson <davidson@freevolt.org> - 2020-06-18 09:10 +0200
Re: bash-completion pros/cons (was: Re: Need commands) l0f4r0@tuta.io - 2020-06-18 20:40 +0200
Re: Need commands mick crane <mick.crane@gmail.com> - 2020-06-16 13:20 +0200
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-06-20 17:00 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjN8l-Hf-3@gated-at.bofh.it> |
| In reply to | #223675 |
[Multipart message — attachments visible in raw view] — view raw
On Vi, 19 iun 20, 15:12:27, Tom Dial wrote: > > I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it > appears the "cmd" to be executed once selections are made (line 24 from > the end) is > > apt-get -q -y -o APT::Install-Recommends=true -o \ > APT::Get::AutomaticRemove=true -o APT::Acquire::Retries=3 install > > I suspect that has something to do with the apparent fact that tasksel > ignores "recommends=false" from other sources. I also suspect that > editing that line would change the behavior in the desired direction. > >From long-standing practice and inclination I have no wish to test this, > but someone else might. > > I assume this would need to be done by skipping tasksel during > installation of the d-i minimal system, then altering and running the > installed tasksel after the post-install reboot. Why not just run 'apt install task-<whatever>' afterwards? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2020-06-20 19:40 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjPDb-2gT-1@gated-at.bofh.it> |
| In reply to | #223733 |
On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote: > On Vi, 19 iun 20, 15:12:27, Tom Dial wrote: > > > > I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it > > appears the "cmd" to be executed once selections are made (line 24 from > > the end) is > > > > apt-get -q -y -o APT::Install-Recommends=true -o \ > > APT::Get::AutomaticRemove=true -o APT::Acquire::Retries=3 install > > > > I suspect that has something to do with the apparent fact that tasksel > > ignores "recommends=false" from other sources. I also suspect that > > editing that line would change the behavior in the desired direction. > > >From long-standing practice and inclination I have no wish to test this, > > but someone else might. > > > > I assume this would need to be done by skipping tasksel during > > installation of the d-i minimal system, then altering and running the > > installed tasksel after the post-install reboot. > > Why not just run 'apt install task-<whatever>' afterwards? Without the suggested alteration made by Tom Dial? How does that fulfill Richard's desired outcome of not installing recommended packages? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-06-20 21:20 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjRbY-3hl-3@gated-at.bofh.it> |
| In reply to | #223748 |
[Multipart message — attachments visible in raw view] — view raw
On Sb, 20 iun 20, 18:37:31, Brian wrote: > On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote: > > > On Vi, 19 iun 20, 15:12:27, Tom Dial wrote: > > > > > > I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it > > > appears the "cmd" to be executed once selections are made (line 24 from > > > the end) is > > > > > > apt-get -q -y -o APT::Install-Recommends=true -o \ > > > APT::Get::AutomaticRemove=true -o APT::Acquire::Retries=3 install > > > > > > I suspect that has something to do with the apparent fact that tasksel > > > ignores "recommends=false" from other sources. I also suspect that > > > editing that line would change the behavior in the desired direction. > > > >From long-standing practice and inclination I have no wish to test this, > > > but someone else might. > > > > > > I assume this would need to be done by skipping tasksel during > > > installation of the d-i minimal system, then altering and running the > > > installed tasksel after the post-install reboot. > > > > Why not just run 'apt install task-<whatever>' afterwards? > > Without the suggested alteration made by Tom Dial? How does that fulfill > Richard's desired outcome of not installing recommended packages? As far as I know all tasks are now[1] metapackages that one can just install with apt, hence one doesn't need tasksel at all. If you are referring to the lack of '--no-install-recommends', I was under the impression that we are in the context of a system installed with 'recommends=false' preseeded, which as per your posting[2] is already configured to not install recommends. I just now realised that skipping the tasksel step completely makes 'recommends=false' optional (it's only use would be to get a system pre-configured to not install recommends), so one should add '--no-install-recommends' as needed to the above ;) [1] they used to be separate lists of packages consumed by tasksel (and aptitude?) [2] https://lists.debian.org/debian-user/2020/06/msg00648.html Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Tom Dial <tddial@comcast.net> |
|---|---|
| Date | 2020-06-21 01:10 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjUMy-5uj-11@gated-at.bofh.it> |
| In reply to | #223756 |
On 6/20/20 13:17, Andrei POPESCU wrote: > On Sb, 20 iun 20, 18:37:31, Brian wrote: >> On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote: >> >>> On Vi, 19 iun 20, 15:12:27, Tom Dial wrote: >>>> >>>> I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it >>>> appears the "cmd" to be executed once selections are made (line 24 from >>>> the end) is >>>> >>>> apt-get -q -y -o APT::Install-Recommends=true -o \ >>>> APT::Get::AutomaticRemove=true -o APT::Acquire::Retries=3 install >>>> >>>> I suspect that has something to do with the apparent fact that tasksel >>>> ignores "recommends=false" from other sources. I also suspect that >>>> editing that line would change the behavior in the desired direction. >>>> >From long-standing practice and inclination I have no wish to test this, >>>> but someone else might. >>>> >>>> I assume this would need to be done by skipping tasksel during >>>> installation of the d-i minimal system, then altering and running the >>>> installed tasksel after the post-install reboot. >>> >>> Why not just run 'apt install task-<whatever>' afterwards? >> >> Without the suggested alteration made by Tom Dial? How does that fulfill >> Richard's desired outcome of not installing recommended packages? > > As far as I know all tasks are now[1] metapackages that one can just > install with apt, hence one doesn't need tasksel at all. This seems to be quite correct: apt would happily install each of the tasksel-listed tasks as described. With "APT::Install-Recommends=false" it will do it without the recommends. I do wonder how appropriate or useful it would be to install these task groups without the recommends, though. On my system (with gnome installed), for instance, task-xfce-desktop would install 37 packages exclusive of the recommends and 213 more with recommends included. I have to think some of them would be useful almost to the point of necessity. Sometimes you have to be careful what you ask for, lest you get it, as Mencken put it, good and hard. > > If you are referring to the lack of '--no-install-recommends', I was > under the impression that we are in the context of a system installed > with 'recommends=false' preseeded, which as per your posting[2] is > already configured to not install recommends. > > I just now realised that skipping the tasksel step completely makes > 'recommends=false' optional (it's only use would be to get a system > pre-configured to not install recommends), so one should add > '--no-install-recommends' as needed to the above This approach is much better than hacking a file that a standard package installed. > > [1] they used to be separate lists of packages consumed by tasksel (and > aptitude?) > [2] https://lists.debian.org/debian-user/2020/06/msg00648.html > > Kind regards, > Andrei > -
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2020-06-21 14:40 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Ak7qq-4wW-5@gated-at.bofh.it> |
| In reply to | #223785 |
On Sat 20 Jun 2020 at 16:51:12 -0600, Tom Dial wrote: > > > On 6/20/20 13:17, Andrei POPESCU wrote: > > > On Sb, 20 iun 20, 18:37:31, Brian wrote: > >> On Sat 20 Jun 2020 at 17:53:56 +0300, Andrei POPESCU wrote: > >> > >>> On Vi, 19 iun 20, 15:12:27, Tom Dial wrote: > >>>> > >>>> I notice that tasksel (= /usr/bin/tasksel) is a Perl program in which it > >>>> appears the "cmd" to be executed once selections are made (line 24 from > >>>> the end) is > >>>> > >>>> apt-get -q -y -o APT::Install-Recommends=true -o \ > >>>> APT::Get::AutomaticRemove=true -o APT::Acquire::Retries=3 install > >>>> > >>>> I suspect that has something to do with the apparent fact that tasksel > >>>> ignores "recommends=false" from other sources. I also suspect that > >>>> editing that line would change the behavior in the desired direction. > >>>> >From long-standing practice and inclination I have no wish to test this, > >>>> but someone else might. > >>>> > >>>> I assume this would need to be done by skipping tasksel during > >>>> installation of the d-i minimal system, then altering and running the > >>>> installed tasksel after the post-install reboot. > >>> > >>> Why not just run 'apt install task-<whatever>' afterwards? > >> > >> Without the suggested alteration made by Tom Dial? How does that fulfill > >> Richard's desired outcome of not installing recommended packages? > > > > As far as I know all tasks are now[1] metapackages that one can just > > install with apt, hence one doesn't need tasksel at all. > > This seems to be quite correct: apt would happily install each of the > tasksel-listed tasks as described. With "APT::Install-Recommends=false" > it will do it without the recommends. Indeed. > I do wonder how appropriate or useful it would be to install these task > groups without the recommends, though. On my system (with gnome > installed), for instance, task-xfce-desktop would install 37 packages > exclusive of the recommends and 213 more with recommends included. I > have to think some of them would be useful almost to the point of necessity. > > Sometimes you have to be careful what you ask for, lest you get it, as > Mencken put it, good and hard. The changelog for debconf has * Install recommends by default. That's from 2009. Here is not the place to recount the history, but the reasons for the change are not trivial. > > If you are referring to the lack of '--no-install-recommends', I was > > under the impression that we are in the context of a system installed > > with 'recommends=false' preseeded, which as per your posting[2] is > > already configured to not install recommends. > > > > I just now realised that skipping the tasksel step completely makes > > 'recommends=false' optional (it's only use would be to get a system > > pre-configured to not install recommends), so one should add > > '--no-install-recommends' as needed to the above > > This approach is much better than hacking a file that a standard package > installed. Agreed. One may hope that Richard will see it in the same light. I am not sure that the only use for 'recommends=false' > ... would be to get a system pre-configured to not install > recommends ... It is possible that it is obeyed when preseeding with pkgsel and a late_command. Not having tried it, I wouldn't know. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-06-19 05:20 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjfJn-64N-1@gated-at.bofh.it> |
| In reply to | #223601 |
[Multipart message — attachments visible in raw view] — view raw
On Mi, 17 iun 20, 20:48:50, Brian wrote: > > debootstrap is only run during the installation of the base system. It > installs recommended packages. That is in contradiction to what the > Manual says. For "regular" use deboostrap does not install Recommends. According to the manpage it does have a '--debian-installer' option for "internal purposes by the debian-installer" with no other information on what it does. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2020-06-19 17:00 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjqEN-42q-7@gated-at.bofh.it> |
| In reply to | #223645 |
On Fri 19 Jun 2020 at 06:15:48 +0300, Andrei POPESCU wrote: > On Mi, 17 iun 20, 20:48:50, Brian wrote: > > > > debootstrap is only run during the installation of the base system. It > > installs recommended packages. That is in contradiction to what the > > Manual says. > > For "regular" use deboostrap does not install Recommends. This has always been my understanding too. > > According to the manpage it does have a '--debian-installer' option for > "internal purposes by the debian-installer" with no other information on > what it does. I back down completely on my statement above regarding debootstrap and recommended packages. It was based on a laxness in not checking the Priority: of a package. The Manual is correct and there is no contradiction. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-06-19 05:30 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjfT3-67J-1@gated-at.bofh.it> |
| In reply to | #223585 |
[Multipart message — attachments visible in raw view] — view raw
On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote: > > The purpose is to determine if I want to do future installs debootstrap. > I attempted to use debootstrap a few years ago and understand it will take > some time/effort to learn it. If you are going to start from scratch you should consider mmdebstrap instead (preferably the version in bullseye). It is mostly a drop-in replacement for deboostrap, but significantly faster and with some very useful additional features. As to the learning curve, deboostrap itself is quite easy. The hard part is getting a usable system *after* the deboostrap step. At that point one gets to really appreciate the hard work that went behind debian-installer ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2020-06-19 13:30 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Ajnnz-2d8-9@gated-at.bofh.it> |
| In reply to | #223646 |
On 06/18/2020 10:25 PM, Andrei POPESCU wrote: > On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote: >> >> The purpose is to determine if I want to do future installs debootstrap. >> I attempted to use debootstrap a few years ago and understand it will take >> some time/effort to learn it. > > If you are going to start from scratch you should consider mmdebstrap > instead (preferably the version in bullseye). It is mostly a drop-in > replacement for deboostrap, but significantly faster and with some very > useful additional features. IIRC I had looked at it when experimenting with debootstrap and was confused by its use of chroot. My goal was creating a bootable system on a flash drive. > > As to the learning curve, deboostrap itself is quite easy. The hard part > is getting a usable system *after* the deboostrap step. > > At that point one gets to really appreciate the hard work that went > behind debian-installer ;) You are "preaching to the choir" ;/ That why I'm investigating making the installer do what I want. In a way, my underlying problem is Debian has done too good a job in creating a system maximally useful to the broadest spectrum of users. They don't use my preferred programs for some functions and including functions I have no interest in. That results in unnecessary clutter and size.
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-06-19 16:40 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Ajqls-3VR-5@gated-at.bofh.it> |
| In reply to | #223648 |
On Fri 19 Jun 2020 at 06:23:00 (-0500), Richard Owlett wrote: > On 06/18/2020 10:25 PM, Andrei POPESCU wrote: > > On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote: > > > > > > The purpose is to determine if I want to do future installs debootstrap. > > > I attempted to use debootstrap a few years ago and understand it will take > > > some time/effort to learn it. > > > > If you are going to start from scratch you should consider mmdebstrap > > instead (preferably the version in bullseye). It is mostly a drop-in > > replacement for deboostrap, but significantly faster and with some very > > useful additional features. > > IIRC I had looked at it when experimenting with debootstrap and was > confused by its use of chroot. My goal was creating a bootable system > on a flash drive. > > > > As to the learning curve, deboostrap itself is quite easy. The hard part > > is getting a usable system *after* the deboostrap step. > > > > At that point one gets to really appreciate the hard work that went > > behind debian-installer ;) > > You are "preaching to the choir" ;/ > > That why I'm investigating making the installer do what I want. > > In a way, my underlying problem is Debian has done too good a job > in creating a system maximally useful to the broadest spectrum of > users. They don't use my preferred programs for some functions and > including functions I have no interest in. That results in unnecessary > clutter and size. I couldn't agree less; I think you're starting at the wrong end. There's plenty of evidence in the lists that you have run the d-i countless times, yet I haven't seen any evidence that you've tried to analyse how it works by, say, reading the source, notwithstanding the fact that you play your cards close to your chest. In choosing to work on "taming" the d-i, you've chosen a piece of software that, by its very nature, is obscure in how it works. It's even composed of packages that differ from their "grown-up" cousins in the final OS installation, limiting the transfer of knowledge. A Debian installation is loaded up with any number of introspective tools for examining its own composition and behaviour. None of that is available to you while the d-i is running. Just crudely trying to understand what it did after the event involves merging its log, apt's history, and the screens displayed by its front-end (if you remembered to record their timings). And even that casts little light on the debootstrap stage. Looking at its log, you can see that, for much of the time, the system is in a semi-broken state, ignoring its own dependency and configuration problems. Is that really what you want to work on? Why not start with a minimal working system, even adding a few select tools, and then see what isn't necessary for your own minimalist system. Now you can try removing them from a *working* system and, should you go too far, you still have the tools to diagnose what's gone wrong, and fix it. That way, you end up having constructed a post-installation script that, instead of installing nearly 300 packages and purging two like mine, will purge a modest number of packages and install very few. One other benefit: the knowledge and skills you gain in this process will be far more transferable than a deeper understanding of the d-i. After all, I haven't gained the impression that you're in technical charge of rolling out, say, 5000 installations of Debian across some institution or other. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2020-06-19 19:20 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjsQh-5vZ-1@gated-at.bofh.it> |
| In reply to | #223650 |
Hello, On Fri, Jun 19, 2020 at 09:30:30AM -0500, David Wright wrote: > Why not start with a minimal working system, even adding a few > select tools, and then see what isn't necessary for your own > minimalist system. Now you can try removing them from a *working* > system and, should you go too far, you still have the tools to > diagnose what's gone wrong, and fix it. The way I handle this is to indeed install a minimal Debian system with d-i and preseeding and then use configuration management software to turn that system into what it is "supposed" to be, There are a plethora of configuration management solutions that are all pretty well documented, and there are multiple choices that have an active vibrant community. I currently use Ansible, other popular choices include Puppet. There are many more. Basically I would advocate doing a minimal job of OS installation in d-i+preseed and then doing the rest in something more understandable and verbose. Given that you can run arbitrary commands in the installed system you can automate anything at all in the configuration management. It also has the advantage of recording the recipe for baking that particular kind of system as an item of code/configuration that gets stored in source code control (e.g. git, subversion, …) forever; changes to it can be documented and reasoned about at a later date. I have explained all this to Richard before but he doesn't appear interested in investigating this, preferring to try to wrangle the d-i for every task. I don't think it's a good strategy. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-06-20 17:10 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AjNi1-ZO-1@gated-at.bofh.it> |
| In reply to | #223650 |
[Multipart message — attachments visible in raw view] — view raw
On Vi, 19 iun 20, 09:30:30, David Wright wrote: > > One other benefit: the knowledge and skills you gain in this process > will be far more transferable than a deeper understanding of the d-i. > After all, I haven't gained the impression that you're in technical > charge of rolling out, say, 5000 installations of Debian across > some institution or other. I would argue that for significantly customized installations[1] at such scale there are again better tools than the installer (e.g. FAI). [1] beyond what the preseeding mechanism can do reasonably easy Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2020-06-19 19:50 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Ajtjk-5FM-15@gated-at.bofh.it> |
| In reply to | #223648 |
On Fri 19 Jun 2020 at 06:23:00 -0500, Richard Owlett wrote: > On 06/18/2020 10:25 PM, Andrei POPESCU wrote: > > On Mi, 17 iun 20, 06:51:18, Richard Owlett wrote: > > > > > > The purpose is to determine if I want to do future installs debootstrap. > > > I attempted to use debootstrap a few years ago and understand it will take > > > some time/effort to learn it. > > > > If you are going to start from scratch you should consider mmdebstrap > > instead (preferably the version in bullseye). It is mostly a drop-in > > replacement for deboostrap, but significantly faster and with some very > > useful additional features. > > IIRC I had looked at it when experimenting with debootstrap and was confused > by its use of chroot. My goal was creating a bootable system on a flash > drive. > > > > > As to the learning curve, deboostrap itself is quite easy. The hard part > > is getting a usable system *after* the deboostrap step. > > > > At that point one gets to really appreciate the hard work that went > > behind debian-installer ;) > > You are "preaching to the choir" ;/ I've sometimes thought you were using a different hymn sheet though. :) > That why I'm investigating making the installer do what I want. That's a laudable aim, but d-i will not be bent to doing what it is not designed to do. For example, suppose you want to install the MATE task without its recommended packages; you are on a loser. > In a way, my underlying problem is Debian has done too good a job > in creating a system maximally useful to the broadest spectrum of users. > They don't use my preferred programs for some functions and including > functions I have no interest in. That results in unnecessary clutter and > size. I am unsure whether Debian has created any system. What it has done is an outstanding job of packaging and providing a competent installer. It is up to a user to create a system that suits their needs. Your preferred programs are not installed using task-mate-desktop? It includes programs of little interest to you? Dead easy. Do apt install install task-mate-desktop --no-install-recommends and go from there. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2020-06-18 02:00 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AiQ8h-7j2-1@gated-at.bofh.it> |
| In reply to | #223583 |
On Wed 17 Jun 2020 at 06:31:16 -0500, Richard Owlett wrote: > On 06/17/2020 06:12 AM, tomas@tuxteam.de wrote: > > On Wed, Jun 17, 2020 at 04:53:45AM -0500, Richard Owlett wrote: > > > On 06/17/2020 03:34 AM, tomas@tuxteam.de wrote: > > > > [snip] > > > > > > > > A couple of those led me to disable recommends completely. It seems > > > > I'm a freak monster or sometning ;-@ > > > > > > > > > > Is there a way to totally disable recommends when installing Debian? > > > I wish to set up a machine for experimenting to find out what I > > > really want. Long long term I am considering using debootstrap to > > > install a extremely customized system. > > > > I have this in the file /etc/apt/apt.conf.d/95no-recommends: > > > > APT::Install-Recommends no: > > > > If I understand correctly, I need to add > /etc/apt/apt.conf.d/95no-recommends to the ISO of the installer's DVD1. No you don't. A user preseeds with recommends=false But you know for a fact that this doesn't work. Therefore, an answer to your enquiry > Is there a way to totally disable recommends when installing Debian? is "no". -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-06-18 10:20 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <AiXWb-3Jv-15@gated-at.bofh.it> |
| In reply to | #223614 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote: [...] > No you don't. A user preseeds with > > recommends=false > > But you know for a fact that this doesn't work. Therefore, an answer to > your enquiry > > > Is there a way to totally disable recommends when installing Debian? > > is "no". Or file a bug report? ;-P Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2020-06-18 13:50 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Aj1dn-5A5-3@gated-at.bofh.it> |
| In reply to | #223619 |
On 06/18/2020 03:13 AM, tomas@tuxteam.de wrote: > On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote: > > [...] > >> No you don't. A user preseeds with >> >> recommends=false >> >> But you know for a fact that this doesn't work. Therefore, an answer to >> your enquiry >> >> > Is there a way to totally disable recommends when installing Debian? >> >> is "no". > > Or file a bug report? > > ;-P > Questions to ask before filing a bug report (even a wishlist): 1. Is it a "bug" or a "feature"? 2. Do I "know" something that is not actually true? 3. Do I have an unrecognized void in my understanding?
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-06-18 14:50 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Aj29r-690-3@gated-at.bofh.it> |
| In reply to | #223626 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Jun 18, 2020 at 06:48:26AM -0500, Richard Owlett wrote: > On 06/18/2020 03:13 AM, tomas@tuxteam.de wrote: > >On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote: > > > >[...] > > > >>No you don't. A user preseeds with > >> > >> recommends=false > >> > >>But you know for a fact that this doesn't work. Therefore, an answer to > >>your enquiry > >> > >> > Is there a way to totally disable recommends when installing Debian? > >> > >>is "no". > > > >Or file a bug report? > > > >;-P > > > > Questions to ask before filing a bug report (even a wishlist): > 1. Is it a "bug" or a "feature"? *If* Brian is right with his assessment (and I haven't a reason to doubt it, though I haven't checked either), I'd say it isn't a feature. Either the program or the doc should be corrected. > 2. Do I "know" something that is not actually true? That is anyone's guess. I know I know many things which aren't true. But alas, I don't know which ones ;-) > 3. Do I have an unrecognized void in my understanding? See above. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2020-06-18 21:00 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Aj7Vv-19b-1@gated-at.bofh.it> |
| In reply to | #223627 |
On Thu 18 Jun 2020 at 14:41:19 +0200, tomas@tuxteam.de wrote: > On Thu, Jun 18, 2020 at 06:48:26AM -0500, Richard Owlett wrote: > > On 06/18/2020 03:13 AM, tomas@tuxteam.de wrote: > > >On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote: > > > > > >[...] > > > > > >>No you don't. A user preseeds with > > >> > > >> recommends=false > > >> > > >>But you know for a fact that this doesn't work. Therefore, an answer to > > >>your enquiry > > >> > > >> > Is there a way to totally disable recommends when installing Debian? > > >> > > >>is "no". > > > > > >Or file a bug report? > > > > > >;-P > > > > > > > Questions to ask before filing a bug report (even a wishlist): > > 1. Is it a "bug" or a "feature"? > > *If* Brian is right with his assessment (and I haven't a reason to doubt > it, though I haven't checked either), I'd say it isn't a feature. Either > the program or the doc should be corrected. I agree with what you say (apart from the big "If" ;) ). I think Richard is concerned that when it comes to installing a desktop the Recommends: are pulled in spite of preseeding with "recommends=false". Considering the Guide in 6.3.5 says: The rule described above only takes effect after this point in the installation process. that is a reasonable concern. A bug submitted against the Guide would not be out of place. > > 2. Do I "know" something that is not actually true? > > That is anyone's guess. I know I know many things which aren't true. > But alas, I don't know which ones ;-) Are these classed as known unknowns or unknown knowns? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2020-06-18 21:10 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Aj85b-1rU-9@gated-at.bofh.it> |
| In reply to | #223632 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Jun 18, 2020 at 07:50:39PM +0100, Brian wrote: > On Thu 18 Jun 2020 at 14:41:19 +0200, tomas@tuxteam.de wrote: > > > On Thu, Jun 18, 2020 at 06:48:26AM -0500, Richard Owlett wrote: [...] > > > 2. Do I "know" something that is not actually true? > > > > That is anyone's guess. I know I know many things which aren't true. > > But alas, I don't know which ones ;-) > > Are these classed as known unknowns or unknown knowns? If I knew which ones they were, I could tell you which ones they are. Or, uh, something, y'know ;-) Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-06-18 21:20 +0200 |
| Subject | Re: Disabling recommends - was [Re: bash-completion pros/cons] |
| Message-ID | <Aj8eS-1v9-13@gated-at.bofh.it> |
| In reply to | #223626 |
On Thu 18 Jun 2020 at 06:48:26 (-0500), Richard Owlett wrote: > On 06/18/2020 03:13 AM, tomas@tuxteam.de wrote: > > On Thu, Jun 18, 2020 at 12:53:55AM +0100, Brian wrote: > > > > [...] > > > > > No you don't. A user preseeds with > > > > > > recommends=false > > > > > > But you know for a fact that this doesn't work. Therefore, an answer to > > > your enquiry > > > > > > > Is there a way to totally disable recommends when installing Debian? > > > > > > is "no". > > > > Or file a bug report? > > > > ;-P > > > > Questions to ask before filing a bug report (even a wishlist): > 1. Is it a "bug" or a "feature"? That's for you to determine. You need to figure out what your expectations are for both the program and its documentation. Then you need to gather your observations and see how they stack up against your expectations. Then think about whether the d-i team are going to sweat over this, particularly when they have already given a caveat for "technical reasons". Unless you file a bug and a patch for the documentation, the immediate response might just be a "wontfix". > 2. Do I "know" something that is not actually true? That seems likely. The scientific method is the usual manner in which we deal with that, by means of experimentation. > 3. Do I have an unrecognized void in my understanding? Yes, the unknown unknowns. Unfortunately, some of these might also be unknowable. We don't know. Cheers, David.
[toc] | [prev] | [next] | [standalone]
Page 3 of 4 — ← Prev page 1 2 [3] 4 Next page →
Back to top | Article view | linux.debian.user
csiph-web