Re: Wheezy to Stretch

[deloptes]

Jimmy Johnson wrote:

> I never said that!  But I do know what I'm talking about because I do
> what I'm talking about constantly.
> 

you have said that, because in the official upgrade notes, as Roberto
pointed out, it says you can go only one level up at a time.
Perhaps your setup has nothing special and you have not hit the fan (yet),
but it does not mean that what is working for you may work for everybody,
while what Debian has recommended works indeed for everybody.

> I have a question for you.  Why do your emails wind up in my spam box
> where I have to fish them out? I have never black-listed you or marked
> your email as spam yet you keep going to my spam box, maybe my system
> knows something about you that I don't know.

I have no influence either on the communication channel, or on your spam
filter(s). I really have no idea. It might be your mail server does not
like me much

regards

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 07:02 PM, rhkra...@gmail.com wrote:

On Wednesday, February 21, 2018 03:40:51 PM Jimmy Johnson wrote:

On 02/21/2018 10:47 AM, Roberto C. S�nchez wrote:

Note that upgrades skipping a release (e.g., wheezy -> stretch instead
of wheezy -> jessie -> stretch) are not supported. A fresh install
sounds like the better route in this case.




I know what I'm talking about and if I can do it anybody can do it,
Debian has given us all the tools we need to upgrade any stable release
to current stable release or higher for that matter, thank about it.
Just start with a simple upgrade first before tackling the other things,
it's not rocket science after all.


And what if their system has slightly different hardware or some other
difference such that your advice doesn't work?  (AFAICT, the fact that Debian
does not support an upgrade skipping a release means that little or no testing
has been done and there is an indeterminate amount of risk.)



First off you're quoting something you have read and not from any real 
experience.  I can say this, I run 5 laptops and two desktops, one 
laptop is reaching it's end of life for kde plasma upstream, it's an 
older real IBM Thinkpad, while all the others are different makes and 
models, AMD and Intel, none are the same but they are running Wheezy, 
Jessie, Stretch, Buster, Sid, 14.04 lts, 16.04 lts, 18.04 lts and I test 
other systems of interest too and it keeps me busy, these are not 
virtual installs, they are real hardware installs and I fix my problems, 
that's how I learn, I've been doing this for more than 20 years, it's 
called experience, real experience. My main testing desktop has sid on 
sda15 and its probably broken with every release, been moved to more 
computers than I care to remember, but I fix it, clean it and keep 
going, so far this release, knock on wood and thinks to Debian upstream 
repairs have been minimal. Outside of machine language I'm not a coder, 
nor do I use machine language any longer.



Will you stand behind the upgrade, and fix his system if there is a problem?
(Site visits are usually not cheap.)
No more or less than anybody else here, I don't know the OP or what his 
capabilities are and my time is limited, but when I see a post where I 
can help I will, what else can you ask from a fellow Linux User.  Just 
one other thing, I'm not a joiner and I won't get held back. I'm done 
discussing this tread, unless the OP has a question for me. Your like a 
pack of wolf's ready to pounce on anything different than what you have 
read and some of you have not changed in the 20+ years I've been using 
Linux, you are bullies and mean to anyone different than you, and I am 
different than you period.


Cheers,
--
Jimmy Johnson - The Linux Tester

Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

Re: Wheezy to Stretch

[rhkramer]

On Wednesday, February 21, 2018 03:40:51 PM Jimmy Johnson wrote:
> On 02/21/2018 10:47 AM, Roberto C. Sánchez wrote:
> > Note that upgrades skipping a release (e.g., wheezy -> stretch instead
> > of wheezy -> jessie -> stretch) are not supported. A fresh install
> > sounds like the better route in this case.

> 
> I know what I'm talking about and if I can do it anybody can do it,
> Debian has given us all the tools we need to upgrade any stable release
> to current stable release or higher for that matter, thank about it.
> Just start with a simple upgrade first before tackling the other things,
> it's not rocket science after all.

And what if their system has slightly different hardware or some other 
difference such that your advice doesn't work?  (AFAICT, the fact that Debian 
does not support an upgrade skipping a release means that little or no testing 
has been done and there is an indeterminate amount of risk.)

Will you stand behind the upgrade, and fix his system if there is a problem?  
(Site visits are usually not cheap.)

Re: Wheezy to Stretch

[Patrick Bartek]

On Wed, 21 Feb 2018 17:45:51 + "Kleene, Steven (kleenesj)"
 wrote:

> I am running Wheezy (v7 = oldoldstable) and intend to replace it with
> a fresh install of Stretch (v9 = stable) before Wheezy's support runs
> out on May 31st.  I will try the default systemd installation and see
> how I like it.
> 
> After the installation, I will want to build my system from my
> favorite window manager (fvwm).  With sysvinit, I would set
> initdefault to runlevel 3 in /etc/inittab.  In /etc/rc3.d, I would
> rename gdm3 so that I would boot into a terminal interface (command
> line) instead of Gnome.  Then I would quickly install fvwm, call
> startx, and happily finish building.

Just install a "terminal only" system first.  That is no X, no display
manager, no window manager, etc. I used the Netinstall ISO. Then
install what you want piece by piece. This is what I did with both
Wheezy and Stretch.

For Stretch, the init conversion -- systemd to sysvinit -- is a simple,
as root,  'apt-get install sysvinit-core sysvinit-utils' IIRC.  You
don't have to "uninstall" systemd.  The sysvinit-core install takes care
of everything so systemd won't run, but the systemd libraries remain for
those apps that have them as dependencies.

These are the instructions I used.  Just the Required Steps:

   http://without-systemd.org/wiki/index.php/Debian_Stretch

> I know systemd doesn't have inittab.  Will the default installation
> leave me with a terminal interface whenever I boot?  If not, how will
> I accomplish that?

With both my systems, I boot directly to a terminal by default which was
what I wanted.  Didn't have to do anything special.

> I also thought I had read about some problem with window
> authentication in Stretch, but I can't find any such posts now.

I've never had any problems, but I use Openbox instead of fvwm.

B

Re: Were is gapcmon?

[Roberto C . Sánchez]

On Thu, Feb 22, 2018 at 02:04:12AM +, Juan R. de Silva wrote:
> 
> Ups, I've totaly missed that Marc said 'apcupsd'. In this case here are 
> my deep appologies to Marc and everybody Being over busy last couple of 
> days I was quite hasty in this case. Sorry.
> 
No problem. I certainly was not offended. It was an honest mistake.

> BTW. about apcupsd-cgi. I found that in order to use it I need to install 
> appache2. I never needed to run a server on my home desktop before. 
> Wouldn't it be a little overkill to install appache server only to use 
> apcupsd web interface? 
> 
The dependency is 'apache2 | httpd', so you can use just about any web
server since they all support CGI. You might find lighttpd simpler than
apache2.

> I'm realy not sure I want to spend a lot of time on securing and then 
> maintaning the server. However I'm not realy familiar with the matter. Is 
> it over complicated or I'd rather use CLI to control apcuspd daemon?
> 
That is a choice you have to make. If you run a firewall on your machine
and you do not expose the ports (3551 for apcupsd and 80 for httpd),
then there is no real concern. That said, if you do not want to worry
about a webserver, you can probably script something that retrieves that
data from the apcupsd process on port 3551. It should not require very
much effort at all.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Were is gapcmon?

[Juan R. de Silva]

On Wed, 21 Feb 2018 20:36:03 -0500, Roberto C. Sánchez wrote:

> On Thu, Feb 22, 2018 at 01:30:40AM +, Juan R. de Silva wrote:
>> On Tue, 20 Feb 2018 14:03:01 -0500, Marc Auslander wrote:
>> 
>> > "Juan R. de Silva"  writes:
>> > 
>> >>I've been using gapcmon GUI to control my APC UPS backup units for
>> >>years.
>> >>I cannot find it in Debian Stretch repos. Was the package removed?
>> >>For what reason? What can I use in its stead?
>> >>
>> >>Thanks.
>> > 
>> > I've always use apcupsd which still works in stretch.  My use is
>> > pretty
> ^^^
>> > trivial - just reports - I don't do anything automatic on power fail
>> > since I can't figure out how to do anything that will always wind up
>> > with my machine running when the power comes back!
>> 
>> So you shared with my your joy using it but spared the where you get
>> it.
>> Well, enjoy your little secret. :-)
>> 
>> 
> Juan,
> 
> He was saying that he uses apcupsd, not gapcmon. There is no secret. As
> you know, gapcmon really is gone and apcupsd is available in all current
> Debian releases.

Ups, I've totaly missed that Marc said 'apcupsd'. In this case here are 
my deep appologies to Marc and everybody Being over busy last couple of 
days I was quite hasty in this case. Sorry.

BTW. about apcupsd-cgi. I found that in order to use it I need to install 
appache2. I never needed to run a server on my home desktop before. 
Wouldn't it be a little overkill to install appache server only to use 
apcupsd web interface? 

I'm realy not sure I want to spend a lot of time on securing and then 
maintaning the server. However I'm not realy familiar with the matter. Is 
it over complicated or I'd rather use CLI to control apcuspd daemon?

Thanks.

Re: Were is gapcmon?

[Roberto C . Sánchez]

On Thu, Feb 22, 2018 at 01:30:40AM +, Juan R. de Silva wrote:
> On Tue, 20 Feb 2018 14:03:01 -0500, Marc Auslander wrote:
> 
> > "Juan R. de Silva"  writes:
> > 
> >>I've been using gapcmon GUI to control my APC UPS backup units for years. 
> >>I cannot find it in Debian Stretch repos. Was the package removed? For 
> >>what reason? What can I use in its stead?
> >>
> >>Thanks.
> > 
> > I've always use apcupsd which still works in stretch.  My use is pretty
^^^
> > trivial - just reports - I don't do anything automatic on power fail
> > since I can't figure out how to do anything that will always wind up
> > with my machine running when the power comes back!
> 
> So you shared with my your joy using it but spared the where you get it. 
> Well, enjoy your little secret. :-)
> 

Juan,

He was saying that he uses apcupsd, not gapcmon. There is no secret. As
you know, gapcmon really is gone and apcupsd is available in all current
Debian releases.

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: Were is gapcmon?

[Juan R. de Silva]

On Tue, 20 Feb 2018 14:03:01 -0500, Marc Auslander wrote:

> "Juan R. de Silva"  writes:
> 
>>I've been using gapcmon GUI to control my APC UPS backup units for years. 
>>I cannot find it in Debian Stretch repos. Was the package removed? For 
>>what reason? What can I use in its stead?
>>
>>Thanks.
> 
> I've always use apcupsd which still works in stretch.  My use is pretty
> trivial - just reports - I don't do anything automatic on power fail
> since I can't figure out how to do anything that will always wind up
> with my machine running when the power comes back!

So you shared with my your joy using it but spared the where you get it. 
Well, enjoy your little secret. :-)

Re: System crash (gpu hang?)

[Ben Caradoc-Davies]

On 22/02/18 09:50, Ben Caradoc-Davies wrote:

On 22/02/18 04:19, Pétùr wrote:

I recently experimented some crashes on debian sid.
The system becomes unresponsive and falls back to the login (lightdm)
window after few minutes.
Here is the dmesg log if someone has the time to help me figure out what
is going on:
https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU= 
Petur
I have also seen this GPU hang on sid. It started occurring every time I 
opened Eclipse Oxygen.2 with export SWT_GTK3=0 so I had to unset this 
environment variable. I am using Intel HD Graphics 630.


I reported the bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891056

I found another workaround, which was to disable xfwm4 compositing (I am 
using XFCE).


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: BIOS Can Not Find Disk

[Dan Norton]

On Wed, 21 Feb 2018 23:19:04 +0100
Pascal Hambourg  wrote:

> Le 21/02/2018 à 03:53, Dan Norton a écrit :
> > 
> > In contrast, with GPT and LVM, for the second and subsequent
> > installations, the partitioning and defining of PVs, VGs, and LVs
> > needs to be done before installation using gdisk and the LVM tools
> > in /sbin. Then, the installer with manual partitioning can succeed
> > by defining the mount points of the various LVs.  
> 
> No, all this can be done during the installation.
> 

Interesting. Via manual partitioning? Changing what's there? Bare disk?

Re: BeMyStreet devient gratuit pour les pros

[Abdullah Ramazanoglu]

On Mon, 06 Feb 2017 16:20:30 +0100
BeMyStreet  wrote:

> BeMyStreet devient gratuit pour les pros.

Spam?

-- 
Abdullah Ramazanoglu

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 02:10 PM, Karol Augustin wrote:

On 2018-02-21 21:42, Jimmy Johnson wrote:

On 02/21/2018 01:31 PM, deloptes wrote:

Jimmy Johnson wrote:


For all the "Na" Sayers here, nothing lost except for sometime and
something to gan the system you want and if you can't make it work
format and do a new system, but remember there is no "sysvinit" in
Stretch.


OK, I have a question:
Why do you think you are smarter than all Debian developers?


I never said that!  But I do know what I'm talking about because I do
what I'm talking about constantly.

I have a question for you.  Why do your emails wind up in my spam box
where I have to fish them out? I have never black-listed you or marked
your email as spam yet you keep going to my spam box, maybe my system
knows something about you that I don't know.


Its because Deloptes is using an e-mail to news gateway with his gmail
address. As you are also using gmail it is marked as spam/phishing as
DMARC fails because the mail is sent using third party servers to reach
Debian mailing list instead of Google's.


I'm using my gmail account's smtp.gmail server. But thanks.


Even though gmail DMARC policy is "none" i think they mark messages
without DKIM from gmail domain as spam to protect themselves. It might
be hard to fix as even if you repeatedly mark Deloptes' emails as not
spam it probably won't help.

You can try adding him to contacts if you desire. If you are using
Android you will also have his e-mail address on your phone for quick
access anytime you might need to reach him...

k.


Cheers,
--
Jimmy Johnson

Debian Wheezy - KDE 4.8.4 - Intel i7-3540M - EXT4 at sda10
Registered Linux User #380263

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 02:18 PM, Sven Joachim wrote:

On 2018-02-21 16:49 -0500, Greg Wooledge wrote:


On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote:

Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
Stretch is that there is no _package_ named sysvinit in Stretch, so you
will be left with the old sysvinit from Wheezy and have to do a manual
upgrade, e.g. like this:


Moot argument.  You don't *DO* a direct upgrade from wheezy to stretch
in the first place.  You go wheezy->jessie, and then jessie->stretch.


Certainly.  I only mentioned this because Jimmy had suggested the
reckless method of directly upgrading from Wheezy to Stretch, and I was
curious how badly it would break.



It's sicking the people who talk with authority about things they have 
never done and I don't care if they read something somewhere, doing is 
knowing.


Cheers,
--
Jimmy Johnson

Debian Wheezy - KDE 4.8.4 - Intel i7-3540M - EXT4 at sda10
Registered Linux User #380263

Re: System crash (gpu hang?)

[Cindy-Sue Causey]

On 2/21/18, Ben Caradoc-Davies  wrote:
> On 22/02/18 04:19, Pétùr wrote:
>> I recently experimented some crashes on debian sid.
>> The system becomes unresponsive and falls back to the login (lightdm)
>> window after few minutes.
>> Here is the dmesg log if someone has the time to help me figure out what
>> is going on:
>> https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU=
>> Petur
>
> I have also seen this GPU hang on sid. It started occurring every time I
> opened Eclipse Oxygen.2 with export SWT_GTK3=0 so I had to unset this
> environment variable. I am using Intel HD Graphics 630.


Mine locked up last night worse than it has in a very long time. It
took a long time, but I was able to break out of it by PATIENTLY
shutting down programs tab by tab, window by window.

Trying to shut entire programs down just seems to clog things up worse
and faster. I've had to do the hardware power off button number a
couple times in response. I HATE that route because it's when you see
that orphan something or other deal during the next bootup.

Something was running that I tried to track down. I figured out what
it might be once a while back, but I forget what it is now. Didn't
have the cognitive togetherness to be able to figure out again last
night

It may fall under "cron" or something. I'm pretty sure it's something
that runs regularly. I have no idea why it locked up that bad last
night, but it sure did.

I heard it kick in just a split second before my computer locked up.
Sometime just after midnight as has been its pattern.

By heard it, I mean I could hear hardware take on an extra load when I
hadn't clicked anything. There was basically about 200MB of breathing
room out of ~9GB total in "mem" and "swap" k/t "free -m".

Just sharing because someone with a fancier quiet system or in a noisy
work environment might not have that advantage of hearing whatever I'm
hearing kick in

PS I just encountered "kworker" two days ago during an accidentally
issued (wide open) "ps aux". If I understand the chatter across the
Net, that looks like something that might have potential as a useful
check point when tracking down memory issues.

Or not. if I didn't understand correctly. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: BIOS Can Not Find Disk

[Pascal Hambourg]

Le 21/02/2018 à 03:53, Dan Norton a écrit :


In contrast, with GPT and LVM, for the second and subsequent
installations, the partitioning and defining of PVs, VGs, and LVs needs
to be done before installation using gdisk and the LVM tools in /sbin.
Then, the installer with manual partitioning can succeed by defining
the mount points of the various LVs.


No, all this can be done during the installation.

Re: Wheezy to Stretch

[Sven Joachim]

On 2018-02-21 16:49 -0500, Greg Wooledge wrote:

> On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote:
>> Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
>> Stretch is that there is no _package_ named sysvinit in Stretch, so you
>> will be left with the old sysvinit from Wheezy and have to do a manual
>> upgrade, e.g. like this:
>
> Moot argument.  You don't *DO* a direct upgrade from wheezy to stretch
> in the first place.  You go wheezy->jessie, and then jessie->stretch.

Certainly.  I only mentioned this because Jimmy had suggested the
reckless method of directly upgrading from Wheezy to Stretch, and I was
curious how badly it would break.

Cheers,
   Sven

Re: Problem with suspend-to-disk

[Pascal Hambourg]

Le 21/02/2018 à 14:07, Louis Wust a écrit :


Is your swap partition large enough to hold the contents of your RAM? It
doesn't need to match (or exceed) the system memory capacity, but it
should be reasonably large. Suspend-to-disk won't work if it is too
small, but I'm not sure whether it would fail in the way that you have
described.


I don't think so. It would fail during suspend, not resume.


You can also test the swap partition directly using badblocks(8):

swapoff /dev/sda2  (assuming that swap is on sda2, for example)
badblocks -vw /dev/sda2


Note that this destroys the swap metadata, including the UUID used to 
identify it in /etc/fstab and in the initramfs. You will have to 
recreate the swap with the same UUID using mkswap.

Re: Wheezy to Stretch

[Karol Augustin]

On 2018-02-21 21:42, Jimmy Johnson wrote:
> On 02/21/2018 01:31 PM, deloptes wrote:
>> Jimmy Johnson wrote:
>>
>>> For all the "Na" Sayers here, nothing lost except for sometime and
>>> something to gan the system you want and if you can't make it work
>>> format and do a new system, but remember there is no "sysvinit" in
>>> Stretch.
>>
>> OK, I have a question:
>> Why do you think you are smarter than all Debian developers?
> 
> I never said that!  But I do know what I'm talking about because I do
> what I'm talking about constantly.
> 
> I have a question for you.  Why do your emails wind up in my spam box
> where I have to fish them out? I have never black-listed you or marked
> your email as spam yet you keep going to my spam box, maybe my system
> knows something about you that I don't know.

Its because Deloptes is using an e-mail to news gateway with his gmail
address. As you are also using gmail it is marked as spam/phishing as
DMARC fails because the mail is sent using third party servers to reach
Debian mailing list instead of Google's.

Even though gmail DMARC policy is "none" i think they mark messages
without DKIM from gmail domain as spam to protect themselves. It might
be hard to fix as even if you repeatedly mark Deloptes' emails as not
spam it probably won't help.

You can try adding him to contacts if you desire. If you are using
Android you will also have his e-mail address on your phone for quick
access anytime you might need to reach him...

k.


-- 
Karol Augustin
ka...@augustin.pl
http://karolaugustin.pl/
+353 85 775 5312

Re: Wheezy to Stretch

[Greg Wooledge]

On Wed, Feb 21, 2018 at 10:39:15PM +0100, Sven Joachim wrote:
> Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
> Stretch is that there is no _package_ named sysvinit in Stretch, so you
> will be left with the old sysvinit from Wheezy and have to do a manual
> upgrade, e.g. like this:

Moot argument.  You don't *DO* a direct upgrade from wheezy to stretch
in the first place.  You go wheezy->jessie, and then jessie->stretch.

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 01:31 PM, deloptes wrote:

Jimmy Johnson wrote:


For all the "Na" Sayers here, nothing lost except for sometime and
something to gan the system you want and if you can't make it work
format and do a new system, but remember there is no "sysvinit" in
Stretch.


OK, I have a question:
Why do you think you are smarter than all Debian developers?


I never said that!  But I do know what I'm talking about because I do 
what I'm talking about constantly.


I have a question for you.  Why do your emails wind up in my spam box 
where I have to fish them out? I have never black-listed you or marked 
your email as spam yet you keep going to my spam box, maybe my system 
knows something about you that I don't know.


Cheers,
--
Jimmy Johnson - The Linux Tester

Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

Re: Wheezy to Stretch

[Sven Joachim]

On 2018-02-21 16:01 -0500, Greg Wooledge wrote:

> On Wed, Feb 21, 2018 at 12:58:11PM -0800, Jimmy Johnson wrote:
>> For all the "Na" Sayers here, nothing lost except for sometime and something
>> to gan the system you want and if you can't make it work format and do a new
>> system, but remember there is no "sysvinit" in Stretch.
>
> There is.  It's just not the default.

Speaking of sysvinit, one problem with a direct upgrade from Wheezy to
Stretch is that there is no _package_ named sysvinit in Stretch, so you
will be left with the old sysvinit from Wheezy and have to do a manual
upgrade, e.g. like this:

# apt-get install sysvinit-core
# dpkg --purge --force-remove-essential sysvinit

Other than that, on a fairly minimal chroot this worked surprisingly
well.  However, on a system with ~2000 packages I would rather not try
it.  There are certainly many other cases where you will be left with
old packages without an obvious upgrade path, obsolete conffiles,
directories which should be symlinks or vice versa and other issues
which are not immediately obvious but may bite you many months later.

Cheers,
   Sven

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 01:01 PM, Greg Wooledge wrote:

On Wed, Feb 21, 2018 at 12:58:11PM -0800, Jimmy Johnson wrote:

For all the "Na" Sayers here, nothing lost except for sometime and something
to gan the system you want and if you can't make it work format and do a new
system, but remember there is no "sysvinit" in Stretch.


There is.  It's just not the default.\


I had to boot stretch to double check my memory and there is no 
"sysvinit", you do have sysv-rc, sysv-rc-conf, sysvinit-core and 
sysvinit-utils and yes I do know that you can run a sysvinit system with 
those files or so it seems.


I'll let the OP choose what he wants to do.

Cheers,
--
Jimmy Johnson - "The Linux Tester"

Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

Re: Wheezy to Stretch

[deloptes]

Jimmy Johnson wrote:

> For all the "Na" Sayers here, nothing lost except for sometime and
> something to gan the system you want and if you can't make it work
> format and do a new system, but remember there is no "sysvinit" in
> Stretch.

OK, I have a question:
Why do you think you are smarter than all Debian developers?

Re: troubleshooting Kmail

[Cindy-Sue Causey]

On 2/21/18, Curt  wrote:
> On 2018-02-21, rhkra...@gmail.com  wrote:
>> On Tuesday, February 20, 2018 08:57:27 PM Gene Heskett wrote:
>>> Not so good. The woof is back in the shop.
>>
>> Woof?  The dog?
>
> I think the woof fell in maybe.


Da woof, da woof

Da woof is on da house.

Re: Unknown URL

[Reco]

Hi.

On Wed, Feb 21, 2018 at 03:41:08PM -0500, Stephen P. Molnar wrote:
> I have just installed Stretch and have what, to me at least, is an unknown
> URL when I do apt update (as root).
> 
> [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

That's because you have this in your sources.list:

> deb http://security.debian.org/debian-security/ stretch/updates main contrib

security.debian.org tries to redirect you to the mirrors that are
nearest to you.

It just so happens that your host has IPv6 address from somewhere, so
apt tries IPv6 first, then another, and finally falls back to IPv4.

For example, from here it looks like this:

$ wget -S --spider http://security.debian.org
Spider mode enabled. Check if remote file exists.
--2018-02-21 23:56:33--  http://security.debian.org/
Resolving security.debian.org (security.debian.org)...
2001:a78:5:1:216:35ff:fe7f:6ceb, 2a02:16a8:dc41:100::233,
217.196.149.233, ..
.
Connecting to security.debian.org
(security.debian.org)|2001:a78:5:1:216:35ff:fe7f:6ceb|:80
...

$ getent hosts 2001:a78:5:1:216:35ff:fe7f:6ceb
2001:a78:5:1:216:35ff:fe7f:6ceb lobos.debian.org

Therefore here security.debian.org = lobos.debian.org


Since prod.debian.map.fastly.net is reachable from here, I suggest you
to fix your IPv6 setup, or squash it altogether in case you don't
control it.

Reco

Re: Wheezy to Stretch

[Greg Wooledge]

On Wed, Feb 21, 2018 at 12:58:11PM -0800, Jimmy Johnson wrote:
> For all the "Na" Sayers here, nothing lost except for sometime and something
> to gan the system you want and if you can't make it work format and do a new
> system, but remember there is no "sysvinit" in Stretch.

There is.  It's just not the default.

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 10:39 AM, Jimmy Johnson wrote:

On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:
I am running Wheezy (v7 = oldoldstable) and intend to replace it with 
a fresh

install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st.  I will try the default systemd installation and see how I like it.


Okay, but I suggest instead you keep your wheezy system and your wheezy 
sources and do a upgrade using package upgrade-system, it will clean 
your system and then add the stretch sources including backports and run 
apt update & apt-upgrade and then run upgrade-system until your system 
is upgraded and clean, careful that sysvinit is not removed cause that 
package is not in stretch. You can also use apt dist-upgrade and deborphan.



After the installation, I will want to build my system from my favorite
window manager (fvwm).  With sysvinit, I would set initdefault to 
runlevel 3

in /etc/inittab.  In /etc/rc3.d, I would rename gdm3 so that I would boot
into a terminal interface (command line) instead of Gnome.  Then I would
quickly install fvwm, call startx, and happily finish building.

I know systemd doesn't have inittab.  Will the default installation 
leave me

with a terminal interface whenever I boot?  If not, how will I accomplish
that?

I also thought I had read about some problem with window 
authentication in

Stretch, but I can't find any such posts now.


I don't know of any current problems in stretch.



For all the "Na" Sayers here, nothing lost except for sometime and 
something to gan the system you want and if you can't make it work 
format and do a new system, but remember there is no "sysvinit" in Stretch.


Cheers,
--
Jimmy Johnson - "The Linux-Tester"

Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

Re: Unknown URL

[Brian]

On Wed 21 Feb 2018 at 15:41:08 -0500, Stephen P. Molnar wrote:

> I have just installed Stretch and have what, to me at least, is an unknown
> URL when I do apt update (as root).
> 
> [Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

Is this this the unknown URL you are talking about? What's the problem?

> 
> apt hangs for a couple of minutes and finally finishes without any errors.

That's good.

-- 
Brian.

Re: Wheezy to Stretch

[Roberto C . Sánchez]

On Wed, Feb 21, 2018 at 12:40:51PM -0800, Jimmy Johnson wrote:
> I know what I'm talking about

Same here.

> and if I can do it anybody can do it,

There is a big difference between *can* and *should*.

> Debian
> has given us all the tools we need to upgrade any stable release to current
> stable release or higher for that matter, thank about it.

>From the release notes [0]:

Direct upgrades from Debian releases older than 8 (jessie) are not
supported. Please follow the instructions in the Release Notes for
Debian 8 to upgrade to 8 first. 

> Just start with a
> simple upgrade first before tackling the other things, it's not rocket
> science after all.
> 

Correct. It is not rocket science. However, the suggestion you made is
far more likely to encounter problems, perhaps even very difficult to
recover problems, than the supported and *tested* upgrade path. There
are so many packages in Debian that you have no way of being certain
that any given upgrade will work without issues.

I have even done in place 32-bit -> 64-bit migrations. However, I would
not recommend that anyone try that without understanding the potential
risks. Your recommendation had a conspicuous lack of warnings concerning
the potential provblems associated with it.

Regards,

-Roberto

[0]
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#system-status

-- 
Roberto C. Sánchez

Re: System crash (gpu hang?)

[Ben Caradoc-Davies]

On 22/02/18 04:19, Pétùr wrote:

I recently experimented some crashes on debian sid.
The system becomes unresponsive and falls back to the login (lightdm)
window after few minutes.
Here is the dmesg log if someone has the time to help me figure out what
is going on:
https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU=
Petur


I have also seen this GPU hang on sid. It started occurring every time I 
opened Eclipse Oxygen.2 with export SWT_GTK3=0 so I had to unset this 
environment variable. I am using Intel HD Graphics 630.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:

I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st.  I will try the default systemd installation and see how I like it.


Okay, but I suggest instead you keep your wheezy system and your wheezy 
sources and do a upgrade using package upgrade-system, it will clean 
your system and then add the stretch sources including backports and run 
apt update & apt-upgrade and then run upgrade-system until your system 
is upgraded and clean, careful that sysvinit is not removed cause that 
package is not in stretch. You can also use apt dist-upgrade and deborphan.



After the installation, I will want to build my system from my favorite
window manager (fvwm).  With sysvinit, I would set initdefault to runlevel 3
in /etc/inittab.  In /etc/rc3.d, I would rename gdm3 so that I would boot
into a terminal interface (command line) instead of Gnome.  Then I would
quickly install fvwm, call startx, and happily finish building.

I know systemd doesn't have inittab.  Will the default installation leave me
with a terminal interface whenever I boot?  If not, how will I accomplish
that?

I also thought I had read about some problem with window authentication in
Stretch, but I can't find any such posts now.


I don't know of any current problems in stretch.


Thanks.


Cheers,
--
Jimmy Johnson

Debian Buster - KDE Plasma 5.12.0 - AMD A8-7600 - EXT4 at sda7
Registered Linux User #380263

Re: Lancer un script shell linux lors de la fermeture du terminal, avec la croix

[Basile Starynkevitch]

On 02/20/2018 06:48 PM, Raphaël POITEVIN wrote:

G2PC  writes:


Comment lancer un script shell linux lors de la fermeture du terminal,
avec la croix. ... ?

L’appeler dans .bash_logout ?


Moi j'aimerais comprendre pourquoi on veut faire ça. Je n'en vois pas la 
raison. Un emulateur de terminal peut
disparaître à tout moment (par exemple avec xkill), indépendamment du 
shell (ou du programme) qui y est executé.


Une possibilité (peut-être) serait de choisir puis configurer un window 
manager convenable pour ça.


A mon avis la question initiale est une instance de problème XY 
http://xyproblem.info/ et mériterait une motivation poussée.


Librement

--
Basile STARYNKEVITCH   == http://starynkevitch.net/Basile
opinions are mine only - les opinions sont seulement miennes
Bourg La Reine, France

Re: Wheezy to Stretch

[john doe]

On 2/21/2018 7:47 PM, Roberto C. Sánchez wrote:

On Wed, Feb 21, 2018 at 10:39:54AM -0800, Jimmy Johnson wrote:

On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:

I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st.  I will try the default systemd installation and see how I like it.


Okay, but I suggest instead you keep your wheezy system and your wheezy
sources and do a upgrade using package upgrade-system, it will clean your
system and then add the stretch sources including backports and run apt
update & apt-upgrade and then run upgrade-system until your system is
upgraded and clean, careful that sysvinit is not removed cause that package
is not in stretch. You can also use apt dist-upgrade and deborphan.


Note that upgrades skipping a release (e.g., wheezy -> stretch instead
of wheezy -> jessie -> stretch) are not supported. A fresh install
sounds like the better route in this case.

Also, adding backports sources for the target version during an upgrade
is a terrible idea. Packages in backports have not received upgrade
testing, so who knows what sort of a mess it could create.

For Steven, the best thing is to read the release notes and/or
installation manual and follow the instructions found there.



I agree with Roberto for both advices.

--
John Doe

[Debian Sid] Upgrade of ppp package breaks connection

[Maxim Karpenko]

Running Debian Sid quite long and never had such "unstable" issue.

After upgrading package ppp from 2.4.7-1+4 to 2.4.7-2+1 cannot start ppp-oe
connection, requests to my ISP are failing with: MS-CHAP authentication
failed: Authentication failure

Nothing was changed in config/connection settings. After I removed new
package and installed previous version (with several dependencies) - ppp is
back to normal.

Did anyone face the same issue?

Regards.

Re: Problem withj dd

[Reco]

Hi.

On Wed, Feb 21, 2018 at 11:39:42AM -0600, Richard Owlett wrote:
> I've downloaded the netinst iso with intention of copying it to a flash
> drive. I've done it before without problem.
> 
> > root@debian-jan13:/home/richard# dd bs=64k 
> > if=/home/richard/Downloads/debian-9.3.0-amd64-netinst.iso of=/dev/sdc
> > dd: failed to open '/dev/sdc': No medium found
> > root@debian-jan13:/home/richard# ls /dev/sdc
> > /dev/sdc
> > root@debian-jan13:/home/richard#
> 
> What's happening?
> [or perhaps "What have I forgotten?"]

That's a legitimate question, but a better one(s) would be:

1) What's the output of "parted /dev/sdc"?

2) If the flash drive has a filesystem, is it mounted somewhere, or not?

3) What's the output of "smartctl -a /dev/sdc"?

4) What does show

strace dd if=.../debian-9.3.0-amd64-netinst.iso of=/dev/sdc bs=64k

5) Can one be really sure that "/dev/sdc" is a flash drive?

Reco

Re: Wheezy to Stretch

[Roberto C . Sánchez]

On Wed, Feb 21, 2018 at 08:12:56PM +0100, deloptes wrote:
> Roberto C. Sánchez wrote:
> 
> > Note that upgrades skipping a release (e.g., wheezy -> stretch instead
> > of wheezy -> jessie -> stretch) are not supported. A fresh install
> > sounds like the better route in this case.
> 
> Roberto, OP said he want to replace wheezy with fresh install. Just FYI.
> 
Right. Then Jimmy made the rather unwise suggestion of upgrading
directly from wheezy to stretch and than also something about adding
backports source prior to upgrading.

I was simply reinforcing the OP's original position that a fresh install
is the right way to go.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Wheezy to Stretch

[Jimmy Johnson]

On 02/21/2018 10:47 AM, Roberto C. Sánchez wrote:

On Wed, Feb 21, 2018 at 10:39:54AM -0800, Jimmy Johnson wrote:

On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:

I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st.  I will try the default systemd installation and see how I like it.


Okay, but I suggest instead you keep your wheezy system and your wheezy
sources and do a upgrade using package upgrade-system, it will clean your
system and then add the stretch sources including backports and run apt
update & apt-upgrade and then run upgrade-system until your system is
upgraded and clean, careful that sysvinit is not removed cause that package
is not in stretch. You can also use apt dist-upgrade and deborphan.


Note that upgrades skipping a release (e.g., wheezy -> stretch instead
of wheezy -> jessie -> stretch) are not supported. A fresh install
sounds like the better route in this case.

Also, adding backports sources for the target version during an upgrade
is a terrible idea. Packages in backports have not received upgrade
testing, so who knows what sort of a mess it could create.

For Steven, the best thing is to read the release notes and/or
installation manual and follow the instructions found there.

Regards,

-Roberto
I know what I'm talking about and if I can do it anybody can do it, 
Debian has given us all the tools we need to upgrade any stable release 
to current stable release or higher for that matter, thank about it. 
Just start with a simple upgrade first before tackling the other things, 
it's not rocket science after all.


Cheers,
--
Jimmy Johnson

Ubuntu 18.04 LTS - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda9
Registered Linux User #380263

Unknown URL

[Stephen P. Molnar]

I have just installed Stretch and have what, to me at least, is an 
unknown URL when I do apt update (as root).


[Connecting to prod.debian.map.fastly.net (2a04:4e42:b::204)]

apt hangs for a couple of minutes and finally finishes without any errors.

Here is /etc/apt/sources.list:


# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD 
Binary-1 20171209-12:11]/ stretch contrib main


# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 DVD 
Binary-1 20171209-12:11]/ stretch main contrib


deb http://debian.uchicago.edu/debian/ stretch main non-free contrib
deb-src http://debian.uchicago.edu/debian/ stretch main non-free contrib

deb http://security.debian.org/debian-security/ stretch/updates main 
contrib non-free
deb-src http://security.debian.org/debian-security/ stretch/updates main 
contrib non-free


# stretch-updates, previously known as 'volatile'
deb http://debian.uchicago.edu/debian/ stretch-updates main contrib 
non-free
deb-src http://debian.uchicago.edu/debian/ stretch-updates main contrib 
non-free


Pointers to a solution will be much appreciated.

Thanks in advance.

--
Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: Wheezy to Stretch

[deloptes]

Roberto C. Sánchez wrote:

> Right. Then Jimmy made the rather unwise suggestion of upgrading
> directly from wheezy to stretch and than also something about adding
> backports source prior to upgrading.
> 
> I was simply reinforcing the OP's original position that a fresh install
> is the right way to go.

Sorry and thanks for clarification.

Re: Wheezy to Stretch

[deloptes]

Roberto C. Sánchez wrote:

> Note that upgrades skipping a release (e.g., wheezy -> stretch instead
> of wheezy -> jessie -> stretch) are not supported. A fresh install
> sounds like the better route in this case.

Roberto, OP said he want to replace wheezy with fresh install. Just FYI.

regards

Re: Lancer un script shell linux lors de la fermeture du terminal, avec la croix

[Étienne Mollier]

On 02/20/2018 06:48 PM, Raphaël POITEVIN wrote:
> G2PC  writes:
> 
>> Comment lancer un script shell linux lors de la fermeture du terminal,
>> avec la croix. ... ?
> 
> L’appeler dans .bash_logout ?
> 

Bonsoir,

L'approche est intéressante, mais ne marcherait pas dans le cas
concernant les terminaux quittés via la croix pour deux raisons.
La première est que la plupart des terminaux ne lancent pas par
défaut des shells de login, et la seconde est que, dans le cas
d'une utilisation dans un script de login, le .bash_logout n'est
appelé qu'a l'appel de la commande « exit ».

Ceci dit, c'était bien pensé.  :-)

La section « INVOCATION » du manuel de Bash est assez détaillée
à ce sujet :

   When an interactive login shell exits, or a non-interac‐
   tive login shell executes the exit builtin command, bash
   readsandexecutescommands   from   the   file
   ~/.bash_logout, if it exists.


Il est toujours intéressant de noter que les terminaux des
divers environnements de bureau peuvent être configurés pour
être des shells de login via une option à cocher dans les
préférences.  Pour le terminal XTerm, vous pouvez le lancer avec
l'option -ls.

La morale de cette histoire est que, c'est mal de fermer ses
terminaux avec la croix : si un programme en cours d'exécution
avait eu besoin de faire du ménage, il y a de grandes chances
pour qu'il faille repasser derrière faire le ménage à la mimine.
Gérer ce cas proprement au sein des programmes n'est pas simple.

À plus,
-- 
Étienne Mollier 

[partial resolution] Re: Problem withj dd

[Richard Owlett]

On 02/21/2018 12:22 PM, Reco wrote:

Hi.

On Wed, Feb 21, 2018 at 11:39:42AM -0600, Richard Owlett wrote:

I've downloaded the netinst iso with intention of copying it to a flash
drive. I've done it before without problem.


root@debian-jan13:/home/richard# dd bs=64k 
if=/home/richard/Downloads/debian-9.3.0-amd64-netinst.iso of=/dev/sdc
dd: failed to open '/dev/sdc': No medium found
root@debian-jan13:/home/richard# ls /dev/sdc
/dev/sdc
root@debian-jan13:/home/richard#


What's happening?
[or perhaps "What have I forgotten?"]


That's a legitimate question, but a better one(s) would be:

1) What's the output of "parted /dev/sdc"?

2) If the flash drive has a filesystem, is it mounted somewhere, or not?

3) What's the output of "smartctl -a /dev/sdc"?

4) What does show

strace dd if=.../debian-9.3.0-amd64-netinst.iso of=/dev/sdc bs=64k

5) Can one be really sure that "/dev/sdc" is a flash drive?

Reco




A variation of the "device does not always get the same /dev/??? 
designation". I've got another problem. After giving dd the correct 
destination the install did not go as expected. I've an idea of what's 
wrong but I need to run some tests. More later. Thanks

Re: Need help debugging total system lockup, probably notebook power saving related

[Ondřej Grover]

Hi Henning,
thanks for the tip.

However, I've been experiencing this issue already before the
spectre/meltdown bunch hit the fan.
It does sound like it a bit, but likely is some different HW stuff.
For now I'm experimenting with i915.enable_rc6=0. I hope it won't bog down
the battery run-time too much.

Ondrej G.

On Wed, Feb 21, 2018 at 3:55 PM, Henning Follmann  wrote:

> On Wed, Feb 21, 2018 at 09:51:58AM +0100, Ondřej Grover wrote:
> > Hello,
> >
> > I need help debugging random total system lock-ups.
> > This is a notebook Acer Aspire V3-572G-78A running Debian Stretch with
> > the 4.9.0-5-amd64 kernel.
> >
> > When running on battery (does not happen on AC power), usually after
> > resuming from RAM, after some rather random time (can be a few minutes to
> > hours) the system suddenly locks up, the screen freezes, keyboard and the
> > click-pad don't react, sound keeps playing a ~2 second loop. The computer
> > does not react to magic SysRq combos (probably because the keyboard
> doesn't
> > react), or to pressing the power key. I cannot ping it nor ssh into it.
> The
> > notebook appears to stay in this state indefinitely (the screen does not
> > blank). Only a ~10-sec power-key hold or removing the battery does a hard
> > reset.
> >
> > I believe this is a kernel-level lock-up in some hardware driver.
> > Unfortunately, I haven't been able to find out which one, because the log
> > files (tried both syslog and journald) contain nothing out of the
> ordinary
> > just before the lock-up. Probably the IO locks-up as well.
> >
> > Netconsole isn't really an easy option, because I cannot reliably
> reproduce
> > this in a suitable controlled environment, which is further complicated
> by
> > the lack of polling support (required for netconsole) on the wireless
> > interface.
> >
> > My suspects:
> > - The integrated Intel graphics card with the i915 driver: always had
> > issues with it (on linux-3.16 it used to crash/hang a lot), maybe the gpu
> > hangs are not properly detected anymore.
> > - The hard disk sometimes loses APM levels after suspend (have to use
> > pm_async == 0 to prevent errors after each suspend). Maybe this points
> to a
> > larger suspend/power-mgmt issue.
> > - My iwlwifi interface sometimes crashes and only removing it from the
> PCI
> > bus and rescanning for it helps. But this procedure does not hang the
> whole
> > system.
> >
> > Any help, suggestions, pointers will be appreciated.
> >
>
> Hello,
> I do have some power management issues with 4.9.0-5-amd64. My issues seem
> different than yours ( I cannot boot up with power plugged in) but it is
> also a hard stop, no logs available. I really haven't figured out the exact
> cause however in my case they seem related to the spectre/meltdown fix in
> the newest kernel.
> You can switch that off by adding pti=off to
> GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and running update-grub.
>
> It is no ideal solution, but maybe it helps narrowing down the issue.
>
>
> -H
>
>
> --
> Henning Follmann   | hfollm...@itcfollmann.com
>
>

Re: Wheezy to Stretch

[Roberto C . Sánchez]

On Wed, Feb 21, 2018 at 10:39:54AM -0800, Jimmy Johnson wrote:
> On 02/21/2018 09:45 AM, Kleene, Steven (kleenesj) wrote:
> > I am running Wheezy (v7 = oldoldstable) and intend to replace it with a 
> > fresh
> > install of Stretch (v9 = stable) before Wheezy's support runs out on May
> > 31st.  I will try the default systemd installation and see how I like it.
> 
> Okay, but I suggest instead you keep your wheezy system and your wheezy
> sources and do a upgrade using package upgrade-system, it will clean your
> system and then add the stretch sources including backports and run apt
> update & apt-upgrade and then run upgrade-system until your system is
> upgraded and clean, careful that sysvinit is not removed cause that package
> is not in stretch. You can also use apt dist-upgrade and deborphan.
> 
Note that upgrades skipping a release (e.g., wheezy -> stretch instead
of wheezy -> jessie -> stretch) are not supported. A fresh install
sounds like the better route in this case.

Also, adding backports sources for the target version during an upgrade
is a terrible idea. Packages in backports have not received upgrade
testing, so who knows what sort of a mess it could create.

For Steven, the best thing is to read the release notes and/or
installation manual and follow the instructions found there.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Re: Is Debian Linux protected against the Meltdown and Spectre security flaws?

[Michael Fothergill]

On 21 February 2018 at 17:46, Julien Aubin  wrote:

> Hi,
>
> Do you have any clue on when the gcc fix for stretch is to be released ?
>
> Actually the retpoline-compliant kernel is ready, and gcc fixes for
> stretch seem to have already been implemented. So I dunno what is still
> blocking the release. :'(
>

​Ooooh! Tantalazing stuff

The solution is to collectively burst into song; singing e.g. the Climb
Every Mountain song from the sound of music
and "To Dream the Impossible Dream" etc. and then suggest we are going to
post it on the site here in some way.

Then we relent and say we are happy to forget all about that idea if the
fixes are released soon etc

That would persuade me.

Cheers

MF

​



>
> Thanks a lot.
>

Re: Wheezy to Stretch

[Felix Miata]

Greg Wooledge composed on 2018-02-21 13:11 (UTC-0500):

> If you simply want to boot *once* into multi-user.target without
> changing the default target, you can edit the kernel command line
> and add the option "systemd.unit=multi-user.target".

> Which is a whole lot more typing than adding the option "2" used to
> be, but is otherwise almost 100% equivalent. 

5 works to override multi-user.target.

3 works to override graphical.target.

Systemd aliases the old runlevels to its targets, so that 'init [S,1-6]' and
'telinit [S,1-6]' can more or less work like they used to with SysV.

With RedHat's rpm runlevels, 3 nominally meant everything except GUI, with 2
nominally meaning multiuser without networking, but a lot of rpm distros
included basic networking in 2 and 3 was distinguished to include most services
that depend on functioning network.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Wheezy to Stretch

[Greg Wooledge]

On Wed, Feb 21, 2018 at 05:45:51PM +, Kleene, Steven (kleenesj) wrote:
> With sysvinit, I would set initdefault to runlevel 3
> in /etc/inittab.  In /etc/rc3.d, I would rename gdm3 so that I would boot
> into a terminal interface (command line) instead of Gnome.  Then I would
> quickly install fvwm, call startx, and happily finish building.
> 
> I know systemd doesn't have inittab.  Will the default installation leave me
> with a terminal interface whenever I boot?  If not, how will I accomplish
> that?

Systemd does not have runlevels, but it is being developed primarily
by and for Red Hat systems, and therefore it *mimics* the Red Hat
runlevels remarkably.

Instead of runlevels, systemd has a "default target", which is the set
of services that should be brought up at boot time.  Which is basically
a runlevel by a different name.

The default target of systemd in Debian is "graphical.target", which
means that if you have installed a Display Manager (gdm3, lightdm,
etc.) it will be started at boot time.

If you don't want that, the other default target you can use is
named "multi-user.target".  This one will not run a Display Manager.

You can check your default target by running "systemctl get-default".

You can set your default target by running "systemctl set-default foo".

If you simply want to boot *once* into multi-user.target without
changing the default target, you can edit the kernel command line
and add the option "systemd.unit=multi-user.target".

Which is a whole lot more typing than adding the option "2" used to
be, but is otherwise almost 100% equivalent.

Another way you can achieve the goal of "not booting into a Display
Manager" is to remove your Display Manager package.  You can always
add it back later.

Re: Debian Sid spectre-meltdown

[Jimmy Johnson]

On 02/21/2018 08:30 AM, Michael Fothergill wrote:

On 21 February 2018 at 16:25, Jimmy Johnson 
wrote:


As reported by Linus kernel 4.15 would have the spectre-meltdown fix,
Debian Sid just got 4.15 and I installed it on both AMD and Intel and then
I ran the spectre-meltdown-checker and Sid is no longer vulnerable to
Spectre-1,2 or 3/meltdown. It should be in Buster soon.

Cheers,
--
Jimmy Johnson



​Heroic stuff...  Excellent news.


Cheers

MF




Debian Sid/Testing - KDE Plasma 5.12.1 - AMD A8-7600 - EXT4 at sda8



Buster, after making sure buster was up to date and clean I added sid 
sources and installed anything that was a new package or upgrade package 
with the name linux and then removed the sid sources, clean and upgraded 
I rebooted to the 4.15 kernel with no problem, ran the 
spectre-meltdown-checker and was not vulnerable.


The AMD A8-7600 needed 12 packages, it has non-free nvidia driver. Not 
vulnerable.

The Intel i7-3540 only needed 5 packages. Not vulnerable.
KDE Plasma 5.12 Desktop on both.

Cheers,
--
Jimmy Johnson

Debian Buster - KDE Plasma 5.12.0 - AMD A8-7600 - EXT4 at sda7
Registered Linux User #380263

Re: Re: Is Debian Linux protected against the Meltdown and Spectre security flaws?

[Julien Aubin]

Hi,

Do you have any clue on when the gcc fix for stretch is to be released ?

Actually the retpoline-compliant kernel is ready, and gcc fixes for stretch
seem to have already been implemented. So I dunno what is still blocking
the release. :'(

Thanks a lot.

Wheezy to Stretch

[Kleene, Steven (kleenesj)]

I am running Wheezy (v7 = oldoldstable) and intend to replace it with a fresh
install of Stretch (v9 = stable) before Wheezy's support runs out on May
31st.  I will try the default systemd installation and see how I like it.

After the installation, I will want to build my system from my favorite
window manager (fvwm).  With sysvinit, I would set initdefault to runlevel 3
in /etc/inittab.  In /etc/rc3.d, I would rename gdm3 so that I would boot
into a terminal interface (command line) instead of Gnome.  Then I would
quickly install fvwm, call startx, and happily finish building.

I know systemd doesn't have inittab.  Will the default installation leave me
with a terminal interface whenever I boot?  If not, how will I accomplish
that?

I also thought I had read about some problem with window authentication in
Stretch, but I can't find any such posts now.

Thanks.

Re: Problem withj dd

[Eduardo M KALINOWSKI]

On qua, 21 fev 2018, Richard Owlett wrote:

I've downloaded the netinst iso with intention of copying it to a  
flash drive. I've done it before without problem.


root@debian-jan13:/home/richard# dd bs=64k  
if=/home/richard/Downloads/debian-9.3.0-amd64-netinst.iso of=/dev/sdc

dd: failed to open '/dev/sdc': No medium found
root@debian-jan13:/home/richard# ls /dev/sdc
/dev/sdc
root@debian-jan13:/home/richard#


What's happening?


Your USB drive might have died.
--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Problem withj dd

[Richard Owlett]

I've downloaded the netinst iso with intention of copying it to a flash 
drive. I've done it before without problem.



root@debian-jan13:/home/richard# dd bs=64k 
if=/home/richard/Downloads/debian-9.3.0-amd64-netinst.iso of=/dev/sdc
dd: failed to open '/dev/sdc': No medium found
root@debian-jan13:/home/richard# ls /dev/sdc
/dev/sdc
root@debian-jan13:/home/richard# 


What's happening?
[or perhaps "What have I forgotten?"]
TIA

Re: troubleshooting Kmail

[Curt]

On 2018-02-21, rhkra...@gmail.com  wrote:
> On Tuesday, February 20, 2018 08:57:27 PM Gene Heskett wrote:
>> Not so good. The woof is back in the shop.
>
> Woof?  The dog?

I think the woof fell in maybe.

-- 
New York was no mere city. It was instead an infinitely romantic notion, the
mysterious nexus of all love and money and power, the shining and the
perishable dream itself. To think of 'living' there was to reduce the
miraculous to the mundane; one does not 'live' at Xanadu. --Joan Didion

Re: Debian Sid spectre-meltdown

[Michael Fothergill]

On 21 February 2018 at 16:25, Jimmy Johnson 
wrote:

> As reported by Linus kernel 4.15 would have the spectre-meltdown fix,
> Debian Sid just got 4.15 and I installed it on both AMD and Intel and then
> I ran the spectre-meltdown-checker and Sid is no longer vulnerable to
> Spectre-1,2 or 3/meltdown. It should be in Buster soon.
>
> Cheers,
> --
> Jimmy Johnson
>

​Heroic stuff...  Excellent news.


Cheers

MF


​


>
> Debian Sid/Testing - KDE Plasma 5.12.0 - AMD A8-7600 - EXT4 at sda8
> Registered Linux User #380263
>
>

Re: Supprimer docker de debian avec un script

[G2PC]

Résolu, mais, pas totalement.
J'arrive donc a supprimer une clé de dépôt, super !

Par contre, mon test conditionnel ne répond pas à mon attente.
Quand je lance la suppression de la clé de dépôt de docker, le message
retourné sera toujours OK sur le terminal.

Mon script, lui, me retournera toujours : Le clé a été supprimée ( Même
si elle n'existait plus. )

Ainsi, apt-key del proutprout me retournera OK , la clé a été supprimée,
hors, proutprout n'existait pas.


Mon script actuel :

sudo apt-key del 2C52609D
if [ "$?" = "0" ] ; then
echo "La clé de dépôt ajoutée pour Docker, si elle existait, a été
supprimée"
else
echo "La clé de dépôt ajoutée pour Docker n'a pas été supprimée"
fi


Le 20/02/2018 à 22:31, G2PC a écrit :
> Clés de dépôts
> Lister les clés : apt-key list
>
> pub rsa4096 2015-07-14 [SCEA] 5811 8E89 F3A9 1289 7C07 0ADB F762 2157
> 2C52 609D
> uid [ unknown] Docker Release Tool (releasedocker) 
>
> Supprimer une clé : apt-key del 
> Supprimer la clé du dépôt de Docker : apt-key del 2C52609D
>
> [Résolu]
>
> Le 15/02/2018 à 03:14, G2PC a écrit :
>> Effectivement, c'est bien la clé du dépôt de Docker que j'aimerais
>> identifier, pour retirer la clé, puisque je n'en ai plus besoin si je
>> désinstalle Docker.
>>
>> Par contre, pour le paquet dirmngr, je n'ai pas avancé, je ne sais
>> pas si je peux le supprimer, sans risque de voir d'autres clés
>> devenir inactives.
>>
>> Dans mon contexte, sur VM, Debian 9.3, je sais parfaitement que je
>> n'ai que installé Docker qui demande une clé. Ici, je peux tout
>> supprimer sans crainte.
>>
>> J'aimerais toute fois que mon script de désinstallation puisse être
>> utilisé de façon plus large, donc, je me demande comment ne pas faire
>> disparaître des configurations, clés, ou paquets d'importants.
>>
>> Le 14/02/2018 à 18:39, Olivier Bitsch a écrit :
>>> Hello,
>>>
>>> Est-ce qu'on parle des clés du dépôts de Docker ? Dans ce cas, je me
>>> tournerais vers la commande apt-key list qui permet de lister les
>>> clés, et apt-key del  pour supprimer la clé voulu.
>>>
>>>
>>>
>>> Le 12 février 2018 à 17:02, G2PC >> > a écrit :
>>>
>>> Bonjour.
>>>
>>> Je crée un script pour supprimer Docker sur Debian 9.
>>>
>>> Lors de l'installation de Docker, il faut valider la clé, et,
>>> j'avais eu
>>> un message qui indiquait que le paquet dirmngr n'est pas installé.
>>>
>>> Maintenant, je veux supprimer Docker mais je me demande comment sont
>>> gérées les clés à l'installation.
>>>
>>> Si je fais un autoremove du paquet dirmngr, est ce que le fichier
>>> contenant les clés sera supprimé, si il contient d'autres clés ?
>>>
>>> apt autoremove dirmngr
>>> if [ "$?" = "0" ] ; then
>>> echo "Le paquet dirmngr pour gérer les clés est supprimé."
>>> else
>>> echo "Le paquet dirmngr pour gérer les clés n'a pas été supprimé."
>>> fi
>>>
>>>
>>> D'ailleurs, voilà le script en entier, si vous voulez m'aider à
>>> l'améliorer, le compléter.
>>>
>>> #!/bin/bash
>>>
>>> apt autoremove docker docker-engine docker-compose
>>> if [ "$?" = "0" ] ; then
>>> echo "Docker a été supprimé."
>>> else
>>> echo "Docker n'a pas été supprimé."
>>> fi
>>>
>>> apt autoremove dirmngr
>>> if [ "$?" = "0" ] ; then
>>> echo "Le paquet dirmngr pour gérer les clés est supprimé."
>>> else
>>> echo "Le paquet dirmngr pour gérer les clés n'a pas été supprimé."
>>> fi
>>>
>>> apt autoremove
>>> if [ "$?" = "0" ] ; then
>>> echo "Les paquets qui ne sont plus nécessaires ont également été
>>> supprimés."
>>> else
>>> echo "Les paquets qui ne sont plus nécessaires n'ont pas été
>>> supprimé."
>>> fi
>>>
>>> apt clean
>>> if [ "$?" = "0" ] ; then
>>> echo "Les paquets présents dans /var/cache/apt/archives ont été
>>> supprimés."
>>> else
>>> echo "Les paquets présents dans /var/cache/apt/archives n'ont
>>> pas été
>>> supprimés."
>>> fi
>>>
>>> apt purge '~c'
>>> if [ "$?" = "0" ] ; then
>>> echo "Les fichiers de configuration des paquets désinstallés non
>>> purgés
>>> ont été supprimés."
>>> else
>>> echo "Les fichiers de configuration des paquets désinstallés non
>>> purgés
>>> n'ont pas été supprimés."
>>> fi
>>>
>>> rm /etc/apt/sources.list.d/docker.list
>>> if [ "$?" = "0" ] ; then
>>> echo "Le dépôt ajouté pour Docker a été supprimé."
>>> else
>>> echo "Le dépôt ajouté pour Docker n'a pas été supprimé."
>>>
>>>
>>
>

Debian Sid spectre-meltdown

[Jimmy Johnson]

As reported by Linus kernel 4.15 would have the spectre-meltdown fix, 
Debian Sid just got 4.15 and I installed it on both AMD and Intel and 
then I ran the spectre-meltdown-checker and Sid is no longer vulnerable 
to Spectre-1,2 or 3/meltdown. It should be in Buster soon.


Cheers,
--
Jimmy Johnson

Debian Sid/Testing - KDE Plasma 5.12.0 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263

Re: Were is gapcmon?

[Juan R. de Silva]

On Tue, 20 Feb 2018 14:03:01 -0500, Marc Auslander wrote:

> "Juan R. de Silva"  writes:
> 
>>I've been using gapcmon GUI to control my APC UPS backup units for
>>years.
>>I cannot find it in Debian Stretch repos. Was the package removed? For
>>what reason? What can I use in its stead?
>>
>>Thanks.
> 
> I've always use apcupsd which still works in stretch.  My use is pretty
> trivial - just reports - I don't do anything automatic on power fail
> since I can't figure out how to do anything that will always wind up
> with my machine running when the power comes back!

It's nice to here that it still works in Stretch but where did you get 
the package to install?  As I said it is not in repos any longer. Do you 
think you can share it with me? :-)

Re: domain names, was: hostname

[Curt]

On 2018-02-21, Reco  wrote:
>> > 
>> > ".local" is out too -- reserved for mDNS (bonjour / avahi ).
>> 
>> Oh, for gawd's sake. Is there not an RFC for local domains ?
>
> There is, see RFC 7788 and RFC 8244. ".home", while being controversial,
> is probably fine. And there's ".test", which is perfectly fine as far as
> RFC 6761 concerned.

https://icannwiki.org/.home

TLD;DR

Name Collision Concerns Impede Delegation

 ICANN hired firm Interisle Consulting to carry out an independent investigation
 on the issues that may arise from new gTLDs that are identical to TLDs being
 used on internal networks. The publishing of the report sparked a
 community-wide debate that later became known as the Name Collision issue. The
 firm reported at ICANN 47 that .home and .corp gTLDs were cause for serious
 concern since those strings are widely in use by internal naming systems. In
 response to the report, ICANN labeled the .home and .corp strings as "high
 risk" and proposed that neither of the strings be delegated until it could be
 proven that risk is low.[8] These two strings are currently severely delayed
 and some community members guess they may never be delegated.

They hired a consulting firm.



> Reco


-- 
New York was no mere city. It was instead an infinitely romantic notion, the
mysterious nexus of all love and money and power, the shining and the
perishable dream itself. To think of 'living' there was to reduce the
miraculous to the mundane; one does not 'live' at Xanadu. --Joan Didion

System crash (gpu hang?)

[Pétùr]

I recently experimented some crashes on debian sid.

The system becomes unresponsive and falls back to the login (lightdm)
window after few minutes.

Here is the dmesg log if someone has the time to help me figure out what
is going on:

https://paste.aperture-sc.net/?95de7f038710fd42#q18U+ujcdN+oYVKPkF8uHPCTWUehItZGtzvXYTsgHVU=

Petur

Re: Need help debugging total system lockup, probably notebook power saving related

[Henning Follmann]

On Wed, Feb 21, 2018 at 09:51:58AM +0100, Ondřej Grover wrote:
> Hello,
> 
> I need help debugging random total system lock-ups.
> This is a notebook Acer Aspire V3-572G-78A running Debian Stretch with
> the 4.9.0-5-amd64 kernel.
> 
> When running on battery (does not happen on AC power), usually after
> resuming from RAM, after some rather random time (can be a few minutes to
> hours) the system suddenly locks up, the screen freezes, keyboard and the
> click-pad don't react, sound keeps playing a ~2 second loop. The computer
> does not react to magic SysRq combos (probably because the keyboard doesn't
> react), or to pressing the power key. I cannot ping it nor ssh into it. The
> notebook appears to stay in this state indefinitely (the screen does not
> blank). Only a ~10-sec power-key hold or removing the battery does a hard
> reset.
> 
> I believe this is a kernel-level lock-up in some hardware driver.
> Unfortunately, I haven't been able to find out which one, because the log
> files (tried both syslog and journald) contain nothing out of the ordinary
> just before the lock-up. Probably the IO locks-up as well.
> 
> Netconsole isn't really an easy option, because I cannot reliably reproduce
> this in a suitable controlled environment, which is further complicated by
> the lack of polling support (required for netconsole) on the wireless
> interface.
> 
> My suspects:
> - The integrated Intel graphics card with the i915 driver: always had
> issues with it (on linux-3.16 it used to crash/hang a lot), maybe the gpu
> hangs are not properly detected anymore.
> - The hard disk sometimes loses APM levels after suspend (have to use
> pm_async == 0 to prevent errors after each suspend). Maybe this points to a
> larger suspend/power-mgmt issue.
> - My iwlwifi interface sometimes crashes and only removing it from the PCI
> bus and rescanning for it helps. But this procedure does not hang the whole
> system.
> 
> Any help, suggestions, pointers will be appreciated.
> 

Hello,
I do have some power management issues with 4.9.0-5-amd64. My issues seem
different than yours ( I cannot boot up with power plugged in) but it is
also a hard stop, no logs available. I really haven't figured out the exact
cause however in my case they seem related to the spectre/meltdown fix in
the newest kernel.
You can switch that off by adding pti=off to 
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and running update-grub.

It is no ideal solution, but maybe it helps narrowing down the issue.


-H


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: hostname

[Dan Purgert]

Greg Wooledge wrote:
> Why this is even being *discussed* is beyond me.  I still don't understand
> the OP's rants.  Maybe it's a Windows-user thing?

I think you were spot on with the mobile-user thing in your first or
second response.

-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: hostname

[Greg Wooledge]

On Wed, Feb 21, 2018 at 01:48:32PM +1300, Richard Hector wrote:
> On 20/02/18 05:32, Greg Wooledge wrote:
> > You appear to be concerned that your hostname contains secret information,
> > and that having your hostname "leaked" to the rest of the world will be
> > an issue for you?
> > 
> > If that's the case, try not putting secret information into your
> > hostname.  E.g. naming your machine my_mothers_maiden_name_is_johnson
> > might be a bad idea.
> 
> I haven't been following the thread, but to be fair hostnames could
> sometimes contain info that you might not want to spread around
> unnecessarily. Eg "pg1-linode-tx" might be a useful hostname for your
> first Texas DB VM, but you might not want to reveal that much info to
> the whole world.

Then don't choose that hostname.  That's the entire point I'm trying
to make.  In Debian, you get to choose what your hostname is.  If you
want it to be as meaningless as possible, use something like pwgen to
generate a random string for you.

Why this is even being *discussed* is beyond me.  I still don't understand
the OP's rants.  Maybe it's a Windows-user thing?

Re: Problem with suspend-to-disk

[Louis Wust]

On Tue, Feb 20, 2018, at 16:12, Hans wrote:
> Hi folks,
> I am working on a little problem. Just let me shortly describe:
>
> When I am running suspend-to-disk, I can see, that the RAM is saved to
> the partition (in my case I defined the swap partition).

Is your swap partition large enough to hold the contents of your RAM? It
doesn't need to match (or exceed) the system memory capacity, but it 
should be reasonably large. Suspend-to-disk won't work if it is too
small, but I'm not sure whether it would fail in the way that you have
described.

It might be valuable to check the health of your swap space. If there
are problems, then invalid data might be read back into RAM. A good
place to start is the S.M.A.R.T. report for the hard drive or SSD,
which can be retrieved with smartctl(8) from the smartmontools package:

smartctl -a /dev/sda   (if we assume that your swap partition is on sda)

You can also test the swap partition directly using badblocks(8):

swapoff /dev/sda2  (assuming that swap is on sda2, for example)
badblocks -vw /dev/sda2

On Tue, Feb 20, 2018, at 16:12, Hans wrote:
> Everything is working fine, after that writing to disk, the computer
> is shutting down. So far, so well.
>
> But when I wake it up, I can see, the computer is starting from BIOS,
> and the data is rewritten from the partition into ram.
>
> But then - the computer shuts down, and is starting from BIOS again.

Analogous to the last check, it might be good to check the health of
RAM, in case there are errors occurring while data is being read back.
You can install the memtest86+ package and then boot from the "Memory
test" option in GRUB.

On Tue, Feb 20, 2018, at 16:12, Hans wrote:
> Now my problem: Is there a way, to see, what happens, when the 
> computer writes its data from swap into memory and then crashes? I
> found no log entries, which showed me, why the computer resets after
> refilling the ram. Kernel logs are overwritten at next boot, and
> tricks, like cutting of power before the second boot, and then
> examining the log files with a second operating system like a livefile
> system gave me no further information, too.

I'd recommend testing the disk and system memory first, as described
above, but there are ways to retrieve kernel messages and so forth from
a crashed system. The traditional method is by string a null-modem
serial cable between this computer and another one, and then passing a
kernel parameter to enable writing kernel messages to the serial
console.

You might also have some luck with the kdump-tools package, which uses
the kdump and kexec kernel features to immediately transition from the
crashed kernel instance to a sane kernel instance, which then safely
collects and saves information about the crash (including kernel logs).
This resembles the approach which you attempted with the second OS but
is less likely to fail -- the second OS approach depended on the
crashed kernel having successfully written its kernel ring buffer out 
to disk before dying, which often does not happen.

- Louis

Re: domain names, was: hostname

[Reco]

Hi.

On Wed, Feb 21, 2018 at 10:23:51AM +, Darac Marjal wrote:
> On Wed, Feb 21, 2018 at 09:00:52AM +0300, Reco wrote:
> > Hi.
> > 
> > On Wed, Feb 21, 2018 at 01:05:41AM +, mick crane wrote:
> > > On 2018-02-21 00:33, Dan Purgert wrote:
> > > > mick crane wrote:
> > > > > On 2018-02-20 19:36, Jeremy Nicoll wrote:
> > > > > ,snipped>
> > > > > > Other than that, opinion seems divided on whether for a home LAN it
> > > > > > makes more sense to leave domain name unset, or to provide a value
> > > > > > (picked carefully, perhaps ending ".test"  or ".invalid").   In some
> > > > > > ways
> > > > > > I like the idea of providing a planned/known name, if only
> > > > > > because I'd
> > > > > > recognise it for what it is if I saw it in error messages, logs
> > > > > > etc in
> > > > > > future.
> > > > > >
> > > > > > I almost wonder if, to avoid any potential name conflict, one
> > > > > > would be
> > > > > > sensible to register a domain, and then NOT have it point at
> > > > > > one's own
> > > > > > home LAN - because unless a dynamic DNS service is used, how could
> > > > > > one keep that uptodate (my cable internet ISP does change my WAN
> > > > > > ip address occasionally) - and use its name on the home system.   
> > > > > > But
> > > > > > then again that might have unintended consequences.
> > > > >
> > > > > I think it used to be OK and was suggested to use ".home" for local
> > > > > network but then a cellphone company started using it. Now I think
> > > > > it is
> > > > > OK to use ".local"
> > > >
> > > >
> > > > ".local" is out too -- reserved for mDNS (bonjour / avahi ).
> > > 
> > > Oh, for gawd's sake. Is there not an RFC for local domains ?
> > 
> > There is, see RFC 7788 and RFC 8244. ".home", while being controversial,
> > is probably fine. And there's ".test", which is perfectly fine as far as
> > RFC 6761 concerned.
> 
> There is a solution to all of this, of course. Stump up the few
> dollars/pounds/euro per year to register your own public domain name. You
> don't necessarily need to to anything with it, but if you're registered as
> the owner of, say, DavesHomeLAN.fr, then you don't really need to worry
> about it clashing with someone else.

Or use free (as in "beer" free) DNS service such as freedns.afraid.org,
and get one for free.

Reco

Re: domain names, was: hostname

[Reco]

Hi.

On Wed, Feb 21, 2018 at 06:56:01AM -0500, Gene Heskett wrote:
> On Wednesday 21 February 2018 01:00:52 Reco wrote:
> 
> > Hi.
> >
> > On Wed, Feb 21, 2018 at 01:05:41AM +, mick crane wrote:
> > > On 2018-02-21 00:33, Dan Purgert wrote:
> > > > mick crane wrote:
> > > > > On 2018-02-20 19:36, Jeremy Nicoll wrote:
> > > > > ,snipped>
> > > > >
> > > > > > Other than that, opinion seems divided on whether for a home
> > > > > > LAN it makes more sense to leave domain name unset, or to
> > > > > > provide a value (picked carefully, perhaps ending ".test"  or
> > > > > > ".invalid").   In some ways
> > > > > > I like the idea of providing a planned/known name, if only
> > > > > > because I'd
> > > > > > recognise it for what it is if I saw it in error messages,
> > > > > > logs etc in
> > > > > > future.
> > > > > >
> > > > > > I almost wonder if, to avoid any potential name conflict, one
> > > > > > would be
> > > > > > sensible to register a domain, and then NOT have it point at
> > > > > > one's own
> > > > > > home LAN - because unless a dynamic DNS service is used, how
> > > > > > could one keep that uptodate (my cable internet ISP does
> > > > > > change my WAN ip address occasionally) - and use its name on
> > > > > > the home system.   But then again that might have unintended
> > > > > > consequences.
> > > > >
> > > > > I think it used to be OK and was suggested to use ".home" for
> > > > > local network but then a cellphone company started using it. Now
> > > > > I think it is
> > > > > OK to use ".local"
> > > >
> > > > ".local" is out too -- reserved for mDNS (bonjour / avahi ).
> > >
> > > Oh, for gawd's sake. Is there not an RFC for local domains ?
> >
> > There is, see RFC 7788 and RFC 8244. ".home", while being
> > controversial, is probably fine. And there's ".test", which is
> > perfectly fine as far as RFC 6761 concerned.
> 
> I don't think it matters as long as it does not resolve external to ones 
> home network. There's no domain ending in .den, so 30 years ago I picked 
> the smartest animal I ever met for my home domain. Zero problems.

Four years ago there was no TLD called ".dev". Then Google paid some
money, and ".dev" TLD now belongs to them. With appropriate NS records
and all the jazz.

The amount of pain and suffering this small step brought on countless
web-developers (who thought that using "fake" and "unused" TLD is a good
idea) cannot be measured by mere mortal.

Morale of the story is - don't use it unless it's in RFC. Or being "web
developer" sucks. Or both.

Reco

Re: domain names, was: hostname

[Dan Purgert]

Darac Marjal wrote:
>>> [...]
>>> Oh, for gawd's sake. Is there not an RFC for local domains ?
>>
>>There is, see RFC 7788 and RFC 8244. ".home", while being controversial,
>>is probably fine. And there's ".test", which is perfectly fine as far as
>>RFC 6761 concerned.
>
> There is a solution to all of this, of course. Stump up the few
> dollars/pounds/euro per year to register your own public domain name.
> You don't necessarily need to to anything with it, but if you're
> registered as the owner of, say, DavesHomeLAN.fr, then you don't really
> need to worry about it clashing with someone else.

Indeed.  Even gets you the benefit of being able to run TLS-enabled
services for yourself.  

When I worked it out for myself, given my usage and some fuzzy maths (as
I don't know the exact breakdown of "my servers use X% of my Y kWh/month
electricity bill"), I am spending approximately $25 to $30 per month to
run stuff like my OwnCloud instance, when considering the electricity
costs, tls cert, domain name / ddns service, etc.

While I could probably "get away with" the $8.25 per month tier of
Dropbox (the only one I checked when writing this), I know I don't
always catch accidental data deletions very quick, so I'd probably want
to use the $16.50 tier. (NB -- costs based on paying for a year in full,
month-to-month is $9.99 / 19.99, respectively).

Now, I wouldn't just throw away my domain name (and the associated ddns
service) if I was using a cloud provider, so we're right back at $19 /
month for it.  

I personally consider that $5 to $10 per month cost of "my data on my
hardware, and not subject to a service agreement that can change" to be
money well spent.


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: domain names, was: hostname

[Gene Heskett]

On Wednesday 21 February 2018 01:00:52 Reco wrote:

>   Hi.
>
> On Wed, Feb 21, 2018 at 01:05:41AM +, mick crane wrote:
> > On 2018-02-21 00:33, Dan Purgert wrote:
> > > mick crane wrote:
> > > > On 2018-02-20 19:36, Jeremy Nicoll wrote:
> > > > ,snipped>
> > > >
> > > > > Other than that, opinion seems divided on whether for a home
> > > > > LAN it makes more sense to leave domain name unset, or to
> > > > > provide a value (picked carefully, perhaps ending ".test"  or
> > > > > ".invalid").   In some ways
> > > > > I like the idea of providing a planned/known name, if only
> > > > > because I'd
> > > > > recognise it for what it is if I saw it in error messages,
> > > > > logs etc in
> > > > > future.
> > > > >
> > > > > I almost wonder if, to avoid any potential name conflict, one
> > > > > would be
> > > > > sensible to register a domain, and then NOT have it point at
> > > > > one's own
> > > > > home LAN - because unless a dynamic DNS service is used, how
> > > > > could one keep that uptodate (my cable internet ISP does
> > > > > change my WAN ip address occasionally) - and use its name on
> > > > > the home system.   But then again that might have unintended
> > > > > consequences.
> > > >
> > > > I think it used to be OK and was suggested to use ".home" for
> > > > local network but then a cellphone company started using it. Now
> > > > I think it is
> > > > OK to use ".local"
> > >
> > > ".local" is out too -- reserved for mDNS (bonjour / avahi ).
> >
> > Oh, for gawd's sake. Is there not an RFC for local domains ?
>
> There is, see RFC 7788 and RFC 8244. ".home", while being
> controversial, is probably fine. And there's ".test", which is
> perfectly fine as far as RFC 6761 concerned.
>
> Reco

I don't think it matters as long as it does not resolve external to ones 
home network. There's no domain ending in .den, so 30 years ago I picked 
the smartest animal I ever met for my home domain. Zero problems.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: ordi impossible a eteindre

[daniel huhardeaux]

Le 21/02/2018 à 11:03, hamster a écrit :

Le 19/02/2018 à 14:40, JF Straeten a écrit :

Hello,

On Mon, Feb 19, 2018 at 02:25:32PM +0100, hamster wrote:

Quand je lui fait "eteindre", il s'eteint, puis il se rallume 
immédiatement.

Quand je lui fait "mettre en veille", il se met en veille, puis il se
réveille immédiatement. Avez vous une idée d'ou viens le problème ? 
C'est un

lenovo yoga 2 11 modèle 20332

Ça pourrait sentir un driver qui ne freeze pas, à décharger alors
avant la veille...

Que dit un "dmesg -T" avant et pendant ?


Juste après avoir eteint l'ordi et qu'il se soit rallumé :
http://www.suna.fdn.fr/liens/dmesg-juste-demarre.txt

Juste après avoir mis l'ordi en veille et qu'il se soit réveillé :
http://www.suna.fdn.fr/liens/dmesg-apres-veille.txt


Bonjour,

ce que je vois des logs

[mar. févr. 20 14:01:43 2018] smpboot: CPU 3 is now offline
[sam. sept. 11 14:30:46 2602] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> 
-82917770. Restoring
[mar. févr. 20 14:01:43 2018] ACPI: Low-level resume complete
[mar. févr. 20 14:01:43 2018] ACPI: EC: EC started
[mar. févr. 20 14:01:43 2018] PM: Restoring platform NVS memory
[mar. févr. 20 14:01:43 2018] Suspended for 0.234 seconds

14:01:43 => 14:30:46 Restoring => 14:01:43 => ...

Dans juste-demarre, le FW bug apparait également

[mar. févr. 20 13:56:33 2018] [Firmware Bug]: TSC ADJUST differs: Reference 
CPU0: -82972266 CPU1: 0
[mar. févr. 20 13:56:33 2018]  #2
[mar. févr. 20 13:56:33 2018] [Firmware Bug]: TSC ADJUST differs: Reference 
CPU0: -82972266 CPU2: 0
[mar. févr. 20 13:56:33 2018]  #3
[mar. févr. 20 13:56:33 2018] [Firmware Bug]: TSC ADJUST differs: Reference 
CPU0: -82972266 CPU3: 0

Sur ce lien un problème équivalent, mise à jour du bios devrait être nécessaire 
ou dernier kernel mainline

https://rog.asus.com/forum/showthread.php?95900-TSC-Unstable-Asus-Strix-ROG-STRIX-X299-E-GAMING

--
Daniel

Re: domain names, was: hostname

[Darac Marjal]

On Wed, Feb 21, 2018 at 09:00:52AM +0300, Reco wrote:

Hi.

On Wed, Feb 21, 2018 at 01:05:41AM +, mick crane wrote:

On 2018-02-21 00:33, Dan Purgert wrote:
> mick crane wrote:
> > On 2018-02-20 19:36, Jeremy Nicoll wrote:
> > ,snipped>
> > > Other than that, opinion seems divided on whether for a home LAN it
> > > makes more sense to leave domain name unset, or to provide a value
> > > (picked carefully, perhaps ending ".test"  or ".invalid").   In some
> > > ways
> > > I like the idea of providing a planned/known name, if only
> > > because I'd
> > > recognise it for what it is if I saw it in error messages, logs
> > > etc in
> > > future.
> > >
> > > I almost wonder if, to avoid any potential name conflict, one
> > > would be
> > > sensible to register a domain, and then NOT have it point at
> > > one's own
> > > home LAN - because unless a dynamic DNS service is used, how could
> > > one keep that uptodate (my cable internet ISP does change my WAN
> > > ip address occasionally) - and use its name on the home system.   But
> > > then again that might have unintended consequences.
> >
> > I think it used to be OK and was suggested to use ".home" for local
> > network but then a cellphone company started using it. Now I think
> > it is
> > OK to use ".local"
>
>
> ".local" is out too -- reserved for mDNS (bonjour / avahi ).

Oh, for gawd's sake. Is there not an RFC for local domains ?


There is, see RFC 7788 and RFC 8244. ".home", while being controversial,
is probably fine. And there's ".test", which is perfectly fine as far as
RFC 6761 concerned.


There is a solution to all of this, of course. Stump up the few 
dollars/pounds/euro per year to register your own public domain name. 
You don't necessarily need to to anything with it, but if you're 
registered as the owner of, say, DavesHomeLAN.fr, then you don't really 
need to worry about it clashing with someone else.




Reco



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: ordi impossible a eteindre

[kaliderus]

Bonjour,

Le 21 février 2018 à 11:03, hamster  a écrit :
> Le 19/02/2018 à 14:40, JF Straeten a écrit :
>>
>> Hello,
>>
>> On Mon, Feb 19, 2018 at 02:25:32PM +0100, hamster wrote:
>>
>>> Quand je lui fait "eteindre", il s'eteint, puis il se rallume
>>> immédiatement.
>>> Quand je lui fait "mettre en veille", il se met en veille, puis il se
>>> réveille immédiatement. Avez vous une idée d'ou viens le problème ? C'est
>>> un
>>> lenovo yoga 2 11 modèle 20332
>>
>> Ça pourrait sentir un driver qui ne freeze pas, à décharger alors
>> avant la veille...
>>
Sans grande conviction, un problème matériel ?
J'ai eu un petit asus impossible à éteindre ou à sortir de veille car
le switch était défectueux (en fait tout le circuit de mise sous
tension, donc toute la carte mère).
Du coup => retour SAV 3 fois
Sinon un soucis de driver mais je pense que tu ne serai pas le seul à
t'en plaindre.

Bon courage.

Re: ordi impossible a eteindre

[hamster]

Le 19/02/2018 à 14:40, JF Straeten a écrit :

Hello,

On Mon, Feb 19, 2018 at 02:25:32PM +0100, hamster wrote:


Quand je lui fait "eteindre", il s'eteint, puis il se rallume immédiatement.
Quand je lui fait "mettre en veille", il se met en veille, puis il se
réveille immédiatement. Avez vous une idée d'ou viens le problème ? C'est un
lenovo yoga 2 11 modèle 20332

Ça pourrait sentir un driver qui ne freeze pas, à décharger alors
avant la veille...

Que dit un "dmesg -T" avant et pendant ?


Juste après avoir eteint l'ordi et qu'il se soit rallumé :
http://www.suna.fdn.fr/liens/dmesg-juste-demarre.txt

Juste après avoir mis l'ordi en veille et qu'il se soit réveillé :
http://www.suna.fdn.fr/liens/dmesg-apres-veille.txt

Need help debugging total system lockup, probably notebook power saving related

[Ondřej Grover]

Hello,

I need help debugging random total system lock-ups.
This is a notebook Acer Aspire V3-572G-78A running Debian Stretch with
the 4.9.0-5-amd64 kernel.

When running on battery (does not happen on AC power), usually after
resuming from RAM, after some rather random time (can be a few minutes to
hours) the system suddenly locks up, the screen freezes, keyboard and the
click-pad don't react, sound keeps playing a ~2 second loop. The computer
does not react to magic SysRq combos (probably because the keyboard doesn't
react), or to pressing the power key. I cannot ping it nor ssh into it. The
notebook appears to stay in this state indefinitely (the screen does not
blank). Only a ~10-sec power-key hold or removing the battery does a hard
reset.

I believe this is a kernel-level lock-up in some hardware driver.
Unfortunately, I haven't been able to find out which one, because the log
files (tried both syslog and journald) contain nothing out of the ordinary
just before the lock-up. Probably the IO locks-up as well.

Netconsole isn't really an easy option, because I cannot reliably reproduce
this in a suitable controlled environment, which is further complicated by
the lack of polling support (required for netconsole) on the wireless
interface.

My suspects:
- The integrated Intel graphics card with the i915 driver: always had
issues with it (on linux-3.16 it used to crash/hang a lot), maybe the gpu
hangs are not properly detected anymore.
- The hard disk sometimes loses APM levels after suspend (have to use
pm_async == 0 to prevent errors after each suspend). Maybe this points to a
larger suspend/power-mgmt issue.
- My iwlwifi interface sometimes crashes and only removing it from the PCI
bus and rescanning for it helps. But this procedure does not hang the whole
system.

Any help, suggestions, pointers will be appreciated.

Regards,
Ondrej G.

Re: Instalar python-nest

[Alberto Luaces]

Josu Lazkano writes:

> Buenas a todos,
>
> Quiero probar a utiliza la API de Nest mediante el paquete "python-nest".
>
> El problema es que no acierto a instalarlo al estilo Debian, que sea sencillo.
>
> He probado esto:
>
> apt-get install python3-pip
> pip install python-nest
> -bash: pip: no se encontró la orden
>
> Pero me dice que pip no es un ejecutable.
>
> ¿Algiuien con experiencia en modulos de pthon me puede ayudar?
>
> Lo estoy probando en un raspberrypi con Debian Stretch.

Hola, em tu caso lo primero que probaría es a ver qué hay en
"python3-pip":

$ dpkg -L python3-pip

Tal vez el ejecutable se llame "pip3" o algo así.

De todas formas, lo recomendable es no instalar los paquetes de pip
directamente en el sistema, sino hacer un entorno virtual, lo cual no
requiere permisos de "root".  En python2 había "virtualenv", y en python3
es el módulo "venv":

$ pyvenv --system-site-packages mi_entorno
$ cd mi_entorno
$ source bin/activate.sh

A partir de ahí, todos los comandos como "python" o "pip" se referirán
al entorno nuevo.

-- 
Alberto