On Wed, Oct 25, 2017 at 11:35:20PM -0400, Stefan Monnier wrote:
> > If Debian developers who are responsible for resolvconf are reading this,
> > and if they actually CARE about making things work correctly and sensibly,
> > then here is yet another proposal: give us a way to QUICKLY and EASILY
> >
On Thu, Oct 26, 2017 at 04:19:42PM +1100, David Margerison wrote:
> On 26 October 2017 at 11:39, wrote:
> >
> > According to 'man mountpoint', it returns 0 if something is mounted.
> > So why the complaint from
> > if [ mountpoint $WorkingDirectory ] ?
>
> Answered here:
>
> http://mywiki.woo
On Thu, Oct 26, 2017 at 06:44:44AM -0400, Roberto C. Sánchez wrote:
On Wed, Oct 25, 2017 at 11:35:20PM -0400, Stefan Monnier wrote:
> If Debian developers who are responsible for resolvconf are reading this,
> and if they actually CARE about making things work correctly and sensibly,
> then here
On Thu, Oct 26, 2017 at 12:24:32PM +0100, Darac Marjal wrote:
>
> Actually, there's no need to duplicate the effort. As I understand it,
> resolvconf is basically an optional helper program. Software that
> automatically modifies /etc/resolv.conf should first test for the presence
> of resolvconf
I'm still running Debian 8 on all of my systems. Since it is time to
switch to Debian 9, I've tried to have a first look at it. So I've
installed the nonfree DVD-Image 9.2 within a VirtualBox container. All
went fine, until I've tried to update the APT database.
Both, apt and Synaptics updates
On Thu, Oct 26, 2017 at 11:50:05AM +, Joerg Desch wrote:
I'm still running Debian 8 on all of my systems. Since it is time to
switch to Debian 9, I've tried to have a first look at it. So I've
installed the nonfree DVD-Image 9.2 within a VirtualBox container. All
went fine, until I've tried t
On Thu, Oct 26, 2017 at 11:50:05AM +, Joerg Desch wrote:
> I'm still running Debian 8 on all of my systems. Since it is time to
> switch to Debian 9, I've tried to have a first look at it. So I've
> installed the nonfree DVD-Image 9.2 within a VirtualBox container. All
> went fine, until I'v
On 26 October 2017 at 21:59, Roberto C. Sánchez wrote:
> On Thu, Oct 26, 2017 at 04:19:42PM +1100, David Margerison wrote:
>> On 26 October 2017 at 12:23, Roberto C. Sánchez wrote:
>> >
>> > mountpoint -q $WorkingDirectory
>> > if [[ $? = 0 ]]
>>
>> That will work, but is ridiculous considering t
>> > If Debian developers who are responsible for resolvconf are reading this,
>> > and if they actually CARE about making things work correctly and sensibly,
>> > then here is yet another proposal: give us a way to QUICKLY and EASILY
>> > and RELIABLY tell resolvconf "never do anything".
>> `resol
On Thu, Oct 26, 2017 at 11:12:16PM +1100, David Margerison wrote:
>
> That's a fair point, but the documentation of the 'if' statement in 'man bash'
> will make that immediately clear to anyone who cares to read it.
>
You must regularly deal with different sorts of people than I do :-)
> The [[
On Wed, Oct 25, 2017 at 02:26:35PM -0400, Roberto C. Sánchez wrote:
>
> As an additional note, it is strange to me that none of the dhclient
> interactions are logged in syslog. When I ran dhclient directly and
> specified the verbose option, that resulted in the exhanges being logged
> to syslog
On Wed, Oct 25, 2017 at 11:35:20PM -0400, Stefan Monnier wrote:
> `resolvconf` only touches /etc/resolv.conf when it is installed/initialized.
> What it does to it is to replace it with a symlink.
> After that, it doesn't touch it any morel instead it only modifies the file
> that is the target of
On Thu, Oct 26, 2017 at 09:06:09AM -0400, Roberto C. Sánchez wrote:
> debian:/etc# systemctl status networking
> [...]
> Is this the new normal, for things to get captured in some systemd log
> that I cannot grep out of /var/log? I specifically recall in the past
> on older pre-systemd systems tha
On Thu, Oct 26, 2017 at 09:35:03AM -0400, Greg Wooledge wrote:
> On Thu, Oct 26, 2017 at 09:06:09AM -0400, Roberto C. Sánchez wrote:
> > debian:/etc# systemctl status networking
> > [...]
> > Is this the new normal, for things to get captured in some systemd log
> > that I cannot grep out of /var/l
On 10/25/17 22:19, David Christensen wrote:
On 10/25/17 21:23, Russell L. Carter wrote:
Greetings. Your reply is completely nonresponsive to
the zfs kernel upgrade situation as it is today on debian.
Why did you bother? It's weird.
I don't actually care very much. I'm going to go back to
du
On Thu, Oct 26, 2017 at 8:06 AM, Roberto C. Sánchez
wrote:
>
> Is this the new normal, for things to get captured in some systemd log
> that I cannot grep out of /var/log?
Unfortunately yes.
My experience with Debian 8/9 and more recent Ubuntu is that there is now no
escaping it. One could use
On Thu 26 Oct 2017 at 07:46:24 (-0400), Roberto C. Sánchez wrote:
> On Thu, Oct 26, 2017 at 12:24:32PM +0100, Darac Marjal wrote:
> >
> > Actually, there's no need to duplicate the effort. As I understand it,
> > resolvconf is basically an optional helper program. Software that
> > automatically m
On Thu, Oct 26, 2017 at 09:31:47AM -0500, David Wright wrote:
>
> Judging by your address and earlier comment, you're much closer to
> Debian's strategy than I am, but I thought the thrust of Debian was
> to coerce/persuade packages to cooperate on /etc/resolv.conf so that
> one package did not ov
On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone wrote:
> On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote:
>>
>> and made immutable. Particularly is the fact that /etc/resolv.conf isn't
>> a link to something else but contains:
>>
>> nameserver 192.168.XX.1
>> search hostdns
>> dom
On Thu, Oct 26, 2017 at 03:35:06PM +, Glenn English wrote:
> The 'search host dns' line? How do you set that order? I couldn't find
> that from a bit of surfing, and I'd like to have name lookups work in
> that order...
Gene's resolv.conf has this erroneous line that he has been maintaining
fo
On 2017-10-26 at 11:35, Glenn English wrote:
> On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone wrote:
>
>> On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote:
>>>
>>> and made immutable. Particularly is the fact that /etc/resolv.conf isn't
>>> a link to something else but contains:
>>>
>
An interesting, accidental FYI on the subject of the resolvconf package:
Just now I upgraded an Ubuntu 17.04 test machine which was fully upgraded
only ten days ago. I see in the pending upgrade details that resolvconf is
"No longer supported by Canonical" since the previous upgrade.
On Thu, Oct
On Thu, Oct 26, 2017 at 11:13 AM, Nicholas Geovanis
wrote:
> An interesting, accidental FYI on the subject of the resolvconf package:
> Just now I upgraded an Ubuntu 17.04 test machine which was fully upgraded
> only ten days ago. I see in the pending upgrade details that resolvconf is
> "No long
Hi,
I have installed Debian 9 onto an old laptop with an SSD disk.
Unfortunately the BIOS does not support booting from that SSD disk so
I would like to "abuse" of PXE in order to boot my installed Linux
from /dev/sda1.
For that purpose I setup a PXE server on another machine on the same
LAN usin
Roberto C. Sánchez:
Is this the new normal, for things to get captured in some systemd log
[...]?
* https://unix.stackexchange.com/a/294206/5132 Yes.
On Thu, Oct 26, 2017 at 1:46 PM, Jonathan de Boyne Pollard <
j.deboynepollard-newsgro...@ntlworld.com> wrote:
> Roberto C. Sánchez:
>
> Is this the new normal, for things to get captured in some systemd log
>> [...]?
>>
>> * https://unix.stackexchange.com/a/294206/5132 Yes.
>
Thanks for that. And
On Thu, Oct 26, 2017 at 07:46:12PM +0100, Jonathan de Boyne Pollard wrote:
> Roberto C. Sánchez:
>
> > Is this the new normal, for things to get captured in some systemd log
> > [...]?
> >
> * https://unix.stackexchange.com/a/294206/5132 Yes.
>
That is very informative. In particular:
| If it
On Thu, 26 Oct 2017, Roberto C. Sánchez wrote:
> I do have a syslog package installed and running. It is possible I
> misremembered what was previously logged where, but there is a clear
> discrepancy between what goes to syslog and what systemd captures:
[...]
> In particular, systemd appears to
On Thu, Oct 26, 2017 at 12:31:32PM -0700, Don Armstrong wrote:
> On Thu, 26 Oct 2017, Roberto C. Sánchez wrote:
> > I do have a syslog package installed and running. It is possible I
> > misremembered what was previously logged where, but there is a clear
> > discrepancy between what goes to syslog
bash has a comments syntax to document what may not necessarily be clear
with scripts. If I write a script at minimum just below the
#!/usr/bin/env bash line I have a # file: line giving the file name
followed by a dash and a little bit of a description what the script is
supposed to do. Each
Sent from my iPhone
On Thursday 26 October 2017 11:35:06 Glenn English wrote:
> On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone
wrote:
> > On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote:
> >> and made immutable. Particularly is the fact that /etc/resolv.conf
> >> isn't a link to something else but cont
On Thursday 26 October 2017 12:13:57 Nicholas Geovanis wrote:
> An interesting, accidental FYI on the subject of the resolvconf
> package: Just now I upgraded an Ubuntu 17.04 test machine which was
> fully upgraded only ten days ago. I see in the pending upgrade details
> that resolvconf is "No lo
On Thursday 26 October 2017 15:22:35 Nicholas Geovanis wrote:
> On Thu, Oct 26, 2017 at 1:46 PM, Jonathan de Boyne Pollard <
>
> j.deboynepollard-newsgro...@ntlworld.com> wrote:
> > Roberto C. Sánchez:
> >
> > Is this the new normal, for things to get captured in some systemd
> > log
> >
> >> [...
The perl list I subscribe to seems to be on the fritz or I would
take the question there. I want to write code that receives from
a RS-232 port and I just can't seem to get it to do anything.
The port I am reading is connected to a scanner radio and
produces generally short lines of text
On 27/10/17 13:02, Gene Heskett wrote:
On Thursday 26 October 2017 15:22:35 Nicholas Geovanis wrote:
" And there's also systemd, that is slowly phagocytosing the UNIX part
of Linux"
I'm old enough to have taken phonics in grade school, but that obviously
invented word could probably be repl
Hi Martin,
On Thu, Oct 26, 2017 at 07:37:07PM -0500, Martin McCormick wrote:
> If anybody has gotten the perl Device::SerialPort to
> work, I am interested to know what I am doing or not doing.
I have been using it successfully for a long time, but all I do is
read whole lines from the seri
Hi all,
Any place where this number exists? I would include those companies and
web professionals, using Linux servers as apart of their craft?
Thanks,
Karen
"No one is born hating another person because of the color of his
skin or his background or his religion ... People must learn to
hate,
On Thu, Oct 26, 2017 at 07:37:07PM -0500, Martin McCormick wrote:
> The perl list I subscribe to seems to be on the fritz or I would
> take the question there. I want to write code that receives from
> a RS-232 port and I just can't seem to get it to do anything.
>
> The port I am reading i
Gene Heskett writes:
> On Thursday 26 October 2017 15:22:35 Nicholas Geovanis wrote:
>
>> On Thu, Oct 26, 2017 at 1:46 PM, Jonathan de Boyne Pollard <
>>
>> j.deboynepollard-newsgro...@ntlworld.com> wrote:
>> > Roberto C. Sánchez:
>> >
>> > Is this the new normal, for things to get captured in so
On 10/26/2017 05:37 PM, Martin McCormick wrote:
The perl list I subscribe to seems to be on the fritz or I would
take the question there. I want to write code that receives from
a RS-232 port and I just can't seem to get it to do anything.
The port I am reading is connected to a scanner
On Thu, 26 Oct 2017 21:38:15 -0400 (EDT)
Karen Lewellen wrote:
> Hi all,
> Any place where this number exists? I would include those companies and
> web professionals, using Linux servers as apart of their craft?
https://www.linuxcounter.net/
I don't know how meaningful its data are.
> Thank
Andy Smith writes:
> Hi Martin,
> I have been using it successfully for a long time, but all I do is
> read whole lines from the serial device like:
>
> my $dev = '/dev/ttyUSB0';
> my $port = Device::SerialPort->new($dev);
>
> $port->baudrate(57600);
> $port->write_settings;
>
> open my $fh,
Celejar writes:
> https://www.linuxcounter.net/
> I don't know how meaningful its data are.
Utterly useless.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On 10/26/2017 09:38 PM, Karen Lewellen wrote:
Hi all,
Any place where this number exists? I would include those companies
and web professionals, using Linux servers as apart of their craft?
This isn't an easy question to answer, or probably even a meaningful
one, especially because it's easy
On 27/10/17 15:38, Martin McCormick wrote:
> A perldoc of Device::SerialPort says that lookfor is
> supposed to block or hold until a character string emerges from
> the port as in /dev/ttyUSB0 or /dev/ttyS1. When I trace the
> code, it just loops as fast as it can and never holds to wait fo
On Thursday 26 October 2017 21:21:37 Ben Caradoc-Davies wrote:
> On 27/10/17 13:02, Gene Heskett wrote:
> > On Thursday 26 October 2017 15:22:35 Nicholas Geovanis wrote:
> >> " And there's also systemd, that is slowly phagocytosing the UNIX
> >> part of Linux"
> >
> > I'm old enough to have ta
Am Thu, 26 Oct 2017 13:13:57 +0100 schrieb Darac Marjal:
> [Aside: The debian packaging tool is called "synaptic". "Synaptics" are
> a company producing touchpads. The two are not related]
I know, but I always make this mistake. ;-)
> I believe this is a known bug in synaptic: #864640 [1].
It i
48 matches
Mail list logo
