Re: A little "research" on nvi given the vim-tiny issue

On Thu, Mar 19, 2020 at 12:35 AM James McCoy wrote: > On Wed, Mar 18, 2020, 17:29 Tom H wrote: >> >> PPS: Gentoo's vim[minimal] is vim configured using >> "--with-features=tiny" like Debian's vim-tiny. > > Debian's vim-tiny actual uses "--with-features

A little "research" on nvi given the vim-tiny issue

Russ A said [1] that nvi "is orphaned both upstream and in Debian". I wanted to emphasize that fact by pointing out that Gentoo's removing nvi for similar reasons, and trying to install it just now resulted in this "package.mask" message: $ sudo emerge -p nvi # Michał Górny (2020-02-17) # Based

Re: concerns about Salsa

On Tue, Jun 5, 2018 at 2:37 PM, Pierre-Elliott Bécue wrote: > Le lundi 04 juin 2018 à 12:54:32+0100, Ian Jackson a écrit : >> >> In practice, I have found that it is much easier to deploy a >> production service directly from its git tree. This makes it much >> easier to make changes. > > I've

Re: Naming of network devices - how to improve it in buster

On Fri, Jul 14, 2017 at 10:20 AM, Henrique de Moraes Holschuh <h...@debian.org> wrote: > On Fri, 14 Jul 2017, Tom H wrote: >> The classic naming scheme for network interfaces applied by the kernel >> is to simply assign names beginning with "eth0", &

Re: Naming of network devices - how to improve it in buster

On Thu, Jul 13, 2017 at 6:14 AM, Russell Stuart <russell-deb...@stuart.id.au> wrote: > On Thu, 2017-07-13 at 05:20 -0400, Tom H wrote: >> >> Stateless "/etc". >> >> Systems with multiple NICs where the order in which they're >> recognized by th

Re: Naming of network devices - how to improve it in buster

On Thu, Jul 13, 2017 at 12:22 AM, Russell Stuart wrote: > > I still don't understand what use case the current scheme is aimed at. Stateless "/etc". Systems with multiple NICs where the order in which they're recognized by the kernel can vary.

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

On Wed, Jul 12, 2017 at 2:40 PM, Roger Lynn wrote: > On 10/07/17 19:40, Marvin Renich wrote: >> >> There is an easy fix to revert the default behavior while still allowing >> knowledgeable sysadmins to get the new behavior. On the other hand, >> those who need to administer

Re: Too many Recommends (in particular on mail-transport-agent)

On Tue, Jun 6, 2017 at 9:55 AM, Adam Borowski wrote: > > dnsmasq-base: lxc > * BAD: how often are you on a network without a DNS server? The dnsmasq-base "recommends" is about providing a dhcp server for containers not a dns server. libvirt-daemon-system has the same

Re: Too many Recommends (in particular on mail-transport-agent)

On Thu, Jun 1, 2017 at 1:00 PM, Henrique de Moraes Holschuh wrote: > > The initramfs-tools does not depend or recommend mdadm. However, > initramfs-tools is modular and its mdadm support is supplied by the > mdadm package. > > Dracut isn't modular, and its mdadm support is

Re: policy for shipping sysctl.d snippets in packages?

On Sun, Apr 30, 2017 at 2:22 PM, Wouter Verhelst <wou...@debian.org> wrote: > On Sat, Apr 29, 2017 at 03:48:09PM -0400, Tom H wrote: >> On Thu, Apr 27, 2017 at 3:18 AM, Wouter Verhelst <wou...@debian.org> wrote: >>> >>> I didn't say RPM *doesn't* deal wi

Re: policy for shipping sysctl.d snippets in packages?

On Fri, Apr 28, 2017 at 12:08 PM, Wouter Verhelst <wou...@debian.org> wrote: > On Fri, Apr 28, 2017 at 04:21:17AM -0400, Tom H wrote: >> >> Did Linux development move as quickly as it does now? >> Did users experience more problems or failures when running those >&g

Re: policy for shipping sysctl.d snippets in packages?

On Thu, Apr 27, 2017 at 3:18 AM, Wouter Verhelst <wou...@debian.org> wrote: > On Wed, Apr 26, 2017 at 07:53:57AM -0400, Tom H wrote: >> On Sun, Apr 23, 2017 at 3:00 PM, Wouter Verhelst <wou...@debian.org> wrote: >>> >>> The "packages drop file

Re: policy for shipping sysctl.d snippets in packages?

On Thu, Apr 27, 2017 at 2:34 AM, Brian May wrote: > On 2017-04-27 16:19, Andrey Rahmatullin wrote: >> >> It seems you've missed the point (which was about 4 years between RHEL >> releases). > > There was almost three years between Woody (July 19th 2002) and Sarge (June >

Re: policy for shipping sysctl.d snippets in packages?

On Wed, Apr 26, 2017 at 8:12 PM, Luca Capello <l...@pca.it> wrote: > On Wed, 26 Apr 2017 08:05:10 -0400, Tom H wrote: >> >> You can't dist-upgrade RHEL from 6 to 7 and you can't dist-upgrade >> Debian from 6 to 8 in one leap. > > Debian *does* support dist-upgra

Re: policy for shipping sysctl.d snippets in packages?

On Wed, Apr 26, 2017 at 2:55 PM, Ben Hutchings <b...@decadent.org.uk> wrote: > On Wed, 2017-04-26 at 07:53 -0400, Tom H wrote: >>> On Sun, Apr 23, 2017 at 3:00 PM, Wouter Verhelst <wou...@debian.org> wrote: >>> The "packages drop files in /usr/*, sysadm

Re: policy for shipping sysctl.d snippets in packages?

On Mon, Apr 24, 2017 at 9:10 AM, Adam Borowski wrote: > > All of this is caused by Red Hat having no support for upgrades: > > https://access.redhat.com/solutions/21964 > > # Red Hat does not support in-place upgrades between major versions 4, 5 and > # 6 of Red Hat

Re: policy for shipping sysctl.d snippets in packages?

On Sun, Apr 23, 2017 at 3:00 PM, Wouter Verhelst wrote: > > The "packages drop files in /usr/*, sysadmins override in /etc" way of > doing things is prevalent in the RPM world; in Debian, however, we > traditionally have packages drop files in /etc, and let the maintainer >

Re: Can we kill net-tools, please?

On Sun, Jan 8, 2017 at 10:55 AM, Andrey Rahmatullin <w...@debian.org> wrote: > On Sun, Jan 08, 2017 at 10:49:23AM -0500, Tom H wrote: >> >> You can use >> >> ip a sh lo (if you have bash-completion installed, "a" will >> complete to "addr&q

Re: Can we kill net-tools, please?

On Fri, Jan 6, 2017 at 7:58 PM, Toni Mueller wrote: > On Thu, Dec 29, 2016 at 09:01:51PM +0500, Andrey Rahmatullin wrote: >> On Thu, Dec 29, 2016 at 10:30:26AM -0500, Theodore Ts'o wrote: >>> Ifconfig has been deprecated; you should probably use "ip a show >>> dev lo" instad of

Re: Can we kill net-tools, please?

On Fri, Dec 30, 2016 at 2:32 AM, Andrey Rahmatullin wrote: > > Do you really think that > > wlp3s0: flags=4163 mtu 1500 > inet 192.168.** netmask 255.255.255.0 broadcast 192.168.** > inet6 fe80::** prefixlen 64 scopeid 0x20 >

Re: support for merged /usr in Debian

On Sun, Jan 10, 2016 at 12:09 PM, Marc Haber <mh+debian-de...@zugschlus.de> wrote: > On Sun, 10 Jan 2016 09:53:52 +0100, Tom H <tomh0...@gmail.com> wrote: >> >> Lennart didn't even say that he wanted to get rid of "EnvironmentFile=". >> >>> From

Re: support for merged /usr in Debian

On Wed, Jan 6, 2016 at 12:03 AM, Philipp Kern wrote: > On 2016-01-04 11:30, Marc Haber wrote: >> >> Please also notice that this is the only option for ExecStart in >> systemd units. Well played, Lennart. > > Similarly skeleton-based init scripts use the full path as well. It

Re: support for merged /usr in Debian

Sorry. Not meant for list. :( On Sun, Jan 10, 2016 at 9:59 AM, Tom H <tomh0...@gmail.com> wrote: > Off-list. > > On Wed, Jan 6, 2016 at 1:38 PM, Ansgar Burchardt <ans...@debian.org> wrote: >> >> What is the advantage of having a optional-merged-/usr? > >

Re: support for merged /usr in Debian

Off-list. On Wed, Jan 6, 2016 at 1:38 PM, Ansgar Burchardt wrote: > > What is the advantage of having a optional-merged-/usr? Imagine the opposition if this had been proposed as a non-optional change! (BTW, I'll take this opportunity to thank you for two of your recent

Re: support for merged /usr in Debian

On Sun, Jan 3, 2016 at 6:17 PM, Iustin Pop <ius...@debian.org> wrote: > On 2016-01-03 12:59:01, Tom H wrote: >> >> I don't like usr-merge because it goes against my historical >> expectation that "/{,s}bin" be separate from their /usr namesakes and >> con

Re: support for merged /usr in Debian

On Sat, Jan 2, 2016 at 6:42 PM, Geert Stappers wrote: > On Fri, Jan 01, 2016 at 03:53:03PM +0100, Marco d'Itri wrote: >> On Jan 01, Ian Jackson wrote: >> With a merged /usr you would be able to serve the whole OS over NFS (and >> even share it among multiple systems

Re: support for merged /usr in Debian

On Sun, Jan 3, 2016 at 11:04 AM, Daniel Reurich wrote: > On 03/01/16 22:33, Philip Hands wrote: >> Daniel Reurich writes: >>> Because systemd doesn't work without /usr on the root partition isn't a >>> good reason either. >> >> You are right

Re: Putting default config files in /usr [was; (newbie) Disruptive LIRC package update.]

On Wed, Nov 11, 2015 at 10:37 AM, Marc Haber wrote: > > I violently disagree. We have always done it the other way, and had > the advantage that our conffile handling (which used to be and IMO > still is far superior to everything else other distributions have) >

Re: Putting default config files in /usr [was; (newbie) Disruptive LIRC package update.]

On Wed, Nov 11, 2015 at 4:16 PM, Bjørn Mork <bj...@mork.no> wrote: > Tom H <tomh0...@gmail.com> writes: >> >> systemd isn't the first package to allow/promote shipping distro >> settings in "/lib" or "/usr/lib" and overriding them via &

Re: Putting default config files in /usr [was; (newbie) Disruptive LIRC package update.]

On Wed, Nov 11, 2015 at 4:23 PM, Bjørn Mork wrote: > Bjørn Mork writes: >> >> "/usr/lib/sysctl.d/" is systemd specific. Dropping files there won't do >> anything unless you run the systemd-sysctl service. > > Sorry, should have researched this better first.

Re: Q: why binary-log by systemd-journald is not enabled by default?

On Tue, May 12, 2015 at 7:10 AM, Piotr Ożarowski pi...@debian.org wrote: [Hideki Yamane, 2015-05-10] On Sun, 10 May 2015 00:56:43 -0300 Henrique de Moraes Holschuh h...@debian.org wrote: And I wish it would keep /var/log/dmesg (and its rotation). That thing is really useful for user support

default init on non-Linux platforms

On Thu, 20 Feb 2014 22:28:56 +0800, Thomas Goirand wrote: On 02/20/2014 09:02 PM, Tom H wrote: Thanks for your answer and apologies for the delay in responding but my $dayjob's been keeping me very busy. What features does sysvinit+openrc have that sysvinit+sysv-rc+insserv doesn't have

default init on non-Linux platforms

On Thu, 20 Feb 2014 14:19:30 +0900, hero...@gentoo.org wrote: Tollef Fog Heen tfh...@err.no writes: It's probably better to just contribute your changes to the sysv-rc version and so make that one able to manage openrc in addition to the others it already knows how to. No point in forking

Bug#727708: tech-ctte: Decide which init system to default to in Debian.

On Wed, 30 Oct 2013 21:50:53 -0400, Theodore Ts'o wrote: It's not necessarily the init script author who might want the degrees of freedom, but the local system administrator. The most basic is the idea that whether you can control (via shell scrpit fragments) whether or not a service

Re: Fwd: /etc/hosts and resolving of the local host/domainname - 127.0.0.1 vs. 127.0.1.1

On Mon, 5 Aug 2013 13:08:28 -0400, Thomas Hood wrote: (I had an exchange of emails with Thomas off-list and he suggested that I reply on-list.) With the nsswitch configuration hosts: files ... dns ... myhostname myhostname resolves the system hostname if nothing else does so first. So

Accepted googlecl 0.9.12-1 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 21 Jan 2011 20:43:40 -0700 Source: googlecl Binary: googlecl Architecture: source all Version: 0.9.12-1 Distribution: unstable Urgency: low Maintainer: Tom H. Miller tom.h.mil...@gmail.com Changed-By: Tom H. Miller tom.h.mil

Accepted googlecl 0.9.9-1 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 1 Aug 2010 19:54:00 -0400 Source: googlecl Binary: googlecl Architecture: source all Version: 0.9.9-1 Distribution: unstable Urgency: low Maintainer: Tom H. Miller tom.h.mil...@gmail.com Changed-By: Tom H. Miller tom.h.mil

Accepted googlecl 0.9.8-1 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Jun 2010 3:50:00 -0400 Source: googlecl Binary: googlecl Architecture: source all Version: 0.9.8-1 Distribution: unstable Urgency: low Maintainer: Tom H. Miller tom.h.mil...@gmail.com Changed-By: Tom H. Miller tom.h.mil