Re: [gentoo-user] Choice of TLD for internal network

[Adam Carter]

On Mon, Dec 18, 2017 at 1:05 PM, Peter Humphrey 
wrote:

> Hello list,
>
> I've been running Linux systems since 1994, calling my private LAN mynet
> (bowdlerised). Now I come to install neth server on one machine, it insists
> that I tell it a domain name with at least two dots in it.


That's dumb, and may be an omen on what the rest of it is like.

You can add dotted hostnames to your mynet zone file.

Re: [gentoo-user] Choice of TLD for internal network

[Peter Humphrey]

On Monday, 18 December 2017 09:49:41 GMT Adam Carter wrote:
> On Mon, Dec 18, 2017 at 1:05 PM, Peter Humphrey 
> 
> wrote:
> > Hello list,
> > 
> > I've been running Linux systems since 1994, calling my private LAN mynet
> > (bowdlerised). Now I come to install neth server on one machine, it
> > insists that I tell it a domain name with at least two dots in it.
> 
> That's dumb, and may be an omen on what the rest of it is like.

Yes, I've been forming a similar impression while wrestling with the 
installation. I found I couldn't even touch the partitioning setup without 
causing it to fail - and so I couldn't see what it was going to do; I just 
had to give it the whole disk to play with, with no others present like USB. 
The progress bar stayed static throughout each installation phase, switching 
back and forth at the end of each phase. Then, the initial config has to be 
done in a browser on another box, after signing in to the web page as root. 
The docs don't say that.

I'd been encouraged to try Neth by a score of 9/10 in a certain magazine 
known to one of our contributors here.

> You can add dotted hostnames to your mynet zone file.

That's a good idea, but it doesn't matter any more: I've evicted Neth and 
reverted to good ol' Gentoo. Coincidentally, I'd recently also ended my 
subscription to the magazine.

-- 
Regards,
Peter.

Re: [gentoo-user] Choice of TLD for internal network

[Michael Orlitzky]

On 12/18/2017 09:31 AM, Peter Humphrey wrote:
>>
>> You should probably buy a TLD. It's stupid, but there are no reserved
>> top-level domain names for internal use.
> 
> What, for $185,000 plus quarterly fees[1]? No thanks.
> 
> --->8
> 

I meant "buy a domain" there =)

If somebody were to shell out 200k for a TLD for internal use, I would
try to talk him into letting me use it.

Re: [gentoo-user] Choice of TLD for internal network

[R0b0t1]

On Mon, Dec 18, 2017 at 4:45 AM, Peter Humphrey  wrote:
> On Monday, 18 December 2017 09:49:41 GMT Adam Carter wrote:
>> On Mon, Dec 18, 2017 at 1:05 PM, Peter Humphrey 
>>
>> wrote:
>> > Hello list,
>> >
>> > I've been running Linux systems since 1994, calling my private LAN mynet
>> > (bowdlerised). Now I come to install neth server on one machine, it
>> > insists that I tell it a domain name with at least two dots in it.
>>
>> That's dumb, and may be an omen on what the rest of it is like.
>
> Yes, I've been forming a similar impression while wrestling with the
> installation. I found I couldn't even touch the partitioning setup without
> causing it to fail - and so I couldn't see what it was going to do; I just
> had to give it the whole disk to play with, with no others present like USB.
> The progress bar stayed static throughout each installation phase, switching
> back and forth at the end of each phase. Then, the initial config has to be
> done in a browser on another box, after signing in to the web page as root.
> The docs don't say that.
>

That is unfortunate. I've been having a bear of a time with Ubuntu and
its mail packages, and hoped I could try something less offensive.

> I'd been encouraged to try Neth by a score of 9/10 in a certain magazine
> known to one of our contributors here.
>

Are there any others? I find I keep experiencing issues with the
existing configuration, but I still keep looking.

Cheers,
 R0b0t1

Re: [gentoo-user] Choice of TLD for internal network

[Michael Orlitzky]

On 12/17/2017 09:05 PM, Peter Humphrey wrote:
> Hello list,
> 
> I've been running Linux systems since 1994, calling my private LAN mynet 
> (bowdlerised). Now I come to install neth server on one machine, it insists 
> that I tell it a domain name with at least two dots in it. But I don't have 
> a standard TLD.
> 
> What do you all call your local LANs? Following Google hints, it looks as 
> though I may have to change all .mynet references to .mynet.internal.

You should probably buy a TLD. It's stupid, but there are no reserved
top-level domain names for internal use. There used to be four[0],

  * test
  * example
  * invalid
  * localhost

There was no proscribed behavior for those TLDs, so you were free to use
them for your internal network. Then along came rfc6761[1], which tells
people how to treat those four names. In particular,

  * anything.localhost is out, because users may assume that all
addresses resolve back to the loopback interface (e.g. 127.0.0.1)

  * anything.invalid is out, because users may assume that the domain
does not exist.

  * anything.example is out, because it's reserved for documentation.

And that leaves you with "test." Using "test" isn't perfect, because
caching resolvers may not support it: "Caching DNS servers SHOULD offer
a configuration option..." But more importantly, having "test" on the
end of all your production hostnames is stupid.

So that really leaves you with... nothing. Don't use ".internal" or any
other name that isn't reserved or that you don't own[2].

For now, your best option is to buy a domain.


[0] https://tools.ietf.org/html/rfc2606
[1] https://tools.ietf.org/html/rfc6761
[2]
https://isc.sans.edu/forums/diary/Stop+Using+internal+Top+Level+Domain+Names/21095/

Re: [gentoo-user] Choice of TLD for internal network

[Peter Humphrey]

On Monday, 18 December 2017 13:56:52 GMT Michael Orlitzky wrote:
> On 12/17/2017 09:05 PM, Peter Humphrey wrote:
> > Hello list,
> > 
> > I've been running Linux systems since 1994, calling my private LAN mynet
> > (bowdlerised). Now I come to install neth server on one machine, it
> > insists that I tell it a domain name with at least two dots in it. But
> > I don't have a standard TLD.
> > 
> > What do you all call your local LANs? Following Google hints, it looks
> > as
> > though I may have to change all .mynet references to .mynet.internal.
> 
> You should probably buy a TLD. It's stupid, but there are no reserved
> top-level domain names for internal use.

What, for $185,000 plus quarterly fees[1]? No thanks.

--->8

> So that really leaves you with... nothing. Don't use ".internal" or any
> other name that isn't reserved or that you don't own[2].
> 
> For now, your best option is to buy a domain.

Come to think of it, I have a .me.uk domain registered. I wonder if I can 
use that...

1.  
https://webmasters.stackexchange.com/questions/24460/how-can-i-buy-my-own-personalized-top-level-domain-tld

-- 
Regards,
Peter.

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[John Blinka]

On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards
 wrote:
>
> How do I skip grub and continue?
>

emerge --skipfirst --resume

I had to do that several times in my 17.0 upgrades.

John Blinka

Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?

[Dale]

Grant Edwards wrote:
> On 2017-12-18, John Blinka  wrote:
>> On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards
>>  wrote:
>>> How do I skip grub and continue?
>>
>> emerge --skipfirst --resume
> Thanks, I just seconds ago finally tumbled across that in Google.
>
> Oddly, the failing package (grub:0) wasn't the first one: it was about
> 5-6 packags down the list.  So I used --exclude instead.  We'll see
> how far that gets...
>
> --
> Grant
>

You tried it and it does work with --exclude.  lol  Now we know.  ;-)

Dale

:-)  :-) 

[gentoo-user] CHOST missing in no-multilib stage3 make.conf

[Walter Dnes]

  Beginning the install (AMD64 no-multilib).  I downloaded
stage3-amd64-nomultilib-20171215T184104Z.tar.bz2 and extracted.  Here's
make.conf...

=
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-O2 -pipe"

# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C
=

  I tried a couple of different mirrors.  No CHOST line. The example
file usr/share/portage/config/make.conf.example shows...

===
CHOST="x86_64-pc-linux-gnu"
===

  I could insert that, but I wonder if anything else is screwed up.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] CHOST missing in no-multilib stage3 make.conf

[Michael Orlitzky]

On 12/18/2017 10:00 AM, Walter Dnes wrote:
> 
>   I tried a couple of different mirrors.  No CHOST line. The example
> file usr/share/portage/config/make.conf.example shows...
> 
> ===
> CHOST="x86_64-pc-linux-gnu"
> ===
> 
>   I could insert that, but I wonder if anything else is screwed up.

This silently disappeared some time ago. It's set in the profiles now;
for example, the file "profiles/arch/amd64/make.defaults" sets

  CHOST="x86_64-pc-linux-gnu"

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Dale]

Grant Edwards wrote:
> I tried following the profile 17 upgrade instructions but now I'm
> stuck.  After running for a day or so, the 'emerge -e @world' command
> stopped when grub-0.97 failed to build.
>
> How do I skip grub and continue?
>
> Or do I have to tell emerge to start over from the beginning (skipping
> grub)?  Assuming there are other packages that are going to fail also,
> that could take weeks...
>


emerge --resume --skipfirst 

That should work.  If forced, using --exclude grub might could be
added.  I've never tried that with the --resume command tho. 

Dale

:-)  :-) 

[gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Grant Edwards]

I tried following the profile 17 upgrade instructions but now I'm
stuck.  After running for a day or so, the 'emerge -e @world' command
stopped when grub-0.97 failed to build.

How do I skip grub and continue?

Or do I have to tell emerge to start over from the beginning (skipping
grub)?  Assuming there are other packages that are going to fail also,
that could take weeks...

-- 
Grant

[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?

[Grant Edwards]

On 2017-12-18, John Blinka  wrote:
> On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards
> wrote:
>>
>> How do I skip grub and continue?
>
>
> emerge --skipfirst --resume

Thanks, I just seconds ago finally tumbled across that in Google.

Oddly, the failing package (grub:0) wasn't the first one: it was about
5-6 packags down the list.  So I used --exclude instead.  We'll see
how far that gets...

--
Grant

Re: [gentoo-user] Choice of TLD for internal network

[Neil Bothwick]

On Mon, 18 Dec 2017 10:45:30 +, Peter Humphrey wrote:

> I'd been encouraged to try Neth by a score of 9/10 in a certain
> magazine known to one of our contributors here.

I reviewed it for one of those magazines a couple of years ago in a 5 way
round up where it narrowly beat ClearOS for top spot. I don't recall any
of those issues, but I do have a dotted domain name.

> > You can add dotted hostnames to your mynet zone file.  
> 
> That's a good idea, but it doesn't matter any more: I've evicted Neth
> and reverted to good ol' Gentoo.

Server distros are like any other binary distro, they provide a quick way
to get such a system up and running. If you are used to the control Gentoo
provides, you will soon find any of them frustrating.

> Coincidentally, I'd recently also ended my subscription to the magazine.

 :-(


-- 
Neil Bothwick

"I need your clothes, your boots, and your tagline!"


pgpqgVGEJ0jKs.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Dale]

David Haller wrote:
> Hello,
>
> On Mon, 18 Dec 2017, Dale wrote:
>> The key thing, remembering to force it to be added to world, which is a
>> lot easier than remembering to use -1 for ALL those things I don't want
>> in the world file.  Before I added the -1 option, my world file was full
>> of all sorts of things that have no business being there at all.  It was
>> causing huge problems with upgrades and such. 
> Hm.
>
> # wc -l /var/lib/portage/world
> 1140 /var/lib/portage/world
>
> Am I doing something wrong? Looking it over, it looks right though.
> And --depclean is hopelessly overeager here.
>
> 
> Packages installed:   3511
> Packages in world:1140
> Packages in system:   43
> Required packages:2581
> Number to remove: 930
> 
>
> Hm. I guess there's stuff missing from world (linux-gazette*?) or
> something's broke. I guess I should quickpkg stuff, run a depclean and
> go figure what's missing ;) adding to world/pruning whatever ;) I know
> a lot of those "depcleaned" pkgs are wanted/needed, so I missed adding
> stuff to world or deps are lacking... Oh well. Not while I'm cleaning
> up after the profile-13/gcc-5.4 -> profile-17/gcc-7.2 stuff (I'd
> already compiled most with gcc 6.4, with "std=c++14" for C++ stuff. So
> not much change there besides pie/no-pie.
>
> -dnh
>

I have KDE installed here plus other desktops as well.  While I use some
meta packages, I do some on their own as needed.  I have a lot of things
installed since I have a digital camera, burn CD/DVDs and all sorts of
other weird things.  Here is mine.

root@fireball / # wc -l /var/lib/portage/world
201 /var/lib/portage/world
root@fireball / #

The way I've done in the past and read others have done as well, make a
backup copy of world, go through the world file and remove anything you
didn't install directly for your use.  If you see anything that is a lib
package, odds are you don't need that in the world file because whatever
needs it will pull it in as a dependency.  What you can do, remove say
ten entries that you didn't install yourself directly, you can just put
a # in front to comment out that entry as well, then run --depclean -a
to see what it shows.  If you see something you use listed, add that to
the world file to keep it.  If not, then let it remove them.  Keep doing
that with whatever number you are comfy with until you get a clean world
file.  This could take a while.  The biggest thing, don't let it remove
any system packages.  It shouldn't but depending on what your system
requires, it could.  If in doubt, use eix to see what the package is. 

Also, it is rare that I install anything with a specific version.  I
actually found one listed in my world file and removed it.  No idea how
or why it was there.  The only exception to that, kernels.  Some of
those are done by version.  If you see a entry with a version, may want
to try to recall why because it could make that version stick and not
upgrade.  It's been a while since I did that.

There is a command that may help with this.  I've never used it and
would strongly recommend backing up your world file first.  There is no
help or options for it that show up here.

regenworld

Either way, doing it manually or using that command, you should end up
with a clean world file after some effort.  I would guess that updates
would be much easier.  Most of mine work first time with no problems. 
Any failures are usually from the build itself. 

Hope that helps.

Dale

:-)  :-) 

Re: [gentoo-user] Re: Upgrading kernel with gcc6... use mrproper and not clean

[Dale]

Daniel Frey wrote:
> On 12/18/17 18:46, Daniel Frey wrote:
>> I just thought I'd send this out in case others aren't aware...
>>
>> I've updated some seven machines now to the new profile and gcc6. Out
>> of the seven, four of them had problems rebuilding the kernel which
>> led to an outright hang during booting (black screen, no kernel
>> panic, just hang.)
>>
>> I found out `make clean` is not enough, I had to backup my .config,
>> use `make mrproper`, restore the .config and run `make
>> silentoldconfig` before compiling the kernel and modules.
>>
>> I am thinking `make clean` didn't remove everything made during the
>> compile process and caused some strange race condition somewhere
>> while booting (completely guessing here.)
>>
>> I went back to the three that seemed to be working fine and did the
>> mrproper process on them, because if something happens down the line
>> I probably won't remember what caused the boot issue.
>>
>> Dan
>
> Sigh... from the kernel Makefile:
>
> # clean - Delete most, but leave enough to build external modules
>
> The computers in question that were hanging were using external
> modules such as nvidia, open-vm-tools modules, vmware modules, etc...
>
> *smacks head against wall*
>
> I guess I answered my own question now, and I'll bet that everyone
> here knew this already!
>
> Dan
>
>


I never can remember which is which so I run them both.  If that ever
starts to fail, I may see how me using that rm command does with
cleaning out stuff.  ROFL 

Thanks for the heads up tho. 

Dale

:-)  :-) 

Re: [gentoo-user] No Sound After Reboot, or, More Troubles with Firmware?

[eric]

On 12/18/2017 08:18 PM, Hunter Jozwiak wrote:
> Hello again,
> 
> While fixing my wifi card issues, I came across yet another issue. I
> set the snd-hda-intel PCH as my default soundcard, but I have no sound
> whatsoever, which renders the system pretty much inoperable to me. I
> tried the following:
> amixer set Master unmute
> amixer set Speaker unmute
> amixer set Headphone unmute
> These all went to no evail; no speech from espeakup, and nothing from
> speaker-test. Am I missing something here? Is there an amixer set All
> unmute or something? configlessnd_hda_intel is enabled as a module, as
> is the Realtek codec; the system picked up on the device fine.
> 
> Thanks,
> 
> Hunter
> 
> 



Hunter,

I am a new gentoo user and had trouble getting my sound card to work.
It took me a lot of head scratching and I was able to finally get it to
be recognized.

I don't know what the statement below means or where you set this
configuration.

> set the snd-hda-intel PCH as my default soundcard


On my system

$ lspci | grep Audio

00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
01:00.1 Audio device: NVIDIA Corporation Device 10f1 (rev a1)

and

$ lsmod

Module  Size  Used by
nvidia_drm 40960  1
nvidia_modeset864256  4 nvidia_drm
nvidia  13398016  170 nvidia_modeset
snd_hda_codec_hdmi 45056  0
xhci_pci   16384  0
xhci_hcd  139264  1 xhci_pci
x86_pkg_temp_thermal16384  0
i2c_hid20480  0

My kernel config file shows

# cat .config | grep SND_HDA

CONFIG_SND_HDA=y
CONFIG_SND_HDA_INTEL=y
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_RECONFIG=y
# CONFIG_SND_HDA_INPUT_BEEP is not set
CONFIG_SND_HDA_PATCH_LOADER=y
CONFIG_SND_HDA_CODEC_REALTEK=m
CONFIG_SND_HDA_CODEC_ANALOG=m
# CONFIG_SND_HDA_CODEC_SIGMATEL is not set
CONFIG_SND_HDA_CODEC_VIA=m
CONFIG_SND_HDA_CODEC_HDMI=m
# CONFIG_SND_HDA_CODEC_CIRRUS is not set
# CONFIG_SND_HDA_CODEC_CONEXANT is not set
# CONFIG_SND_HDA_CODEC_CA0110 is not set
# CONFIG_SND_HDA_CODEC_CA0132 is not set
# CONFIG_SND_HDA_CODEC_CMEDIA is not set
# CONFIG_SND_HDA_CODEC_SI3054 is not set
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDA_CORE=y
CONFIG_SND_HDA_I915=y
CONFIG_SND_HDA_PREALLOC_SIZE=2048


What are you using for your sound?  ALSA or PulseAudio?

I ended up going with PulseAudio myself to get my sound working.

Hope any of this helps you,

Eric

Re: [gentoo-user] No Sound After Reboot, or, More Troubles with Firmware?

[Dale]

Hunter Jozwiak wrote:
> Hello again,
>
> While fixing my wifi card issues, I came across yet another issue. I
> set the snd-hda-intel PCH as my default soundcard, but I have no sound
> whatsoever, which renders the system pretty much inoperable to me. I
> tried the following:
> amixer set Master unmute
> amixer set Speaker unmute
> amixer set Headphone unmute
> These all went to no evail; no speech from espeakup, and nothing from
> speaker-test. Am I missing something here? Is there an amixer set All
> unmute or something? configlessnd_hda_intel is enabled as a module, as
> is the Realtek codec; the system picked up on the device fine.
>
> Thanks,
>
> Hunter
>
>


It's been a loong time since I had to deal with this.  I recall
unmuting the ones you listed but there is another one that I had to
unmute and I can't recall what it was for sure.  I want to say it was
Kmix, since I use KDE, but not sure.  If it's loading correctly, I bet
something somewhere is muted.  I sort of wish that wasn't the default.

I might add, I once plugged the speakers into the wrong plug too.  It
looked like the right one.  lol 

Dale

:-)  :-) 

Re: [gentoo-user] No Sound After Reboot, or, More Troubles with Firmware?

[Adam Carter]

On Tue, Dec 19, 2017 at 2:18 PM, Hunter Jozwiak 
wrote:

> Hello again,
>
> While fixing my wifi card issues, I came across yet another issue. I
> set the snd-hda-intel PCH as my default soundcard, but I have no sound
> whatsoever, which renders the system pretty much inoperable to me. I
> tried the following:
> amixer set Master unmute
> amixer set Speaker unmute
> amixer set Headphone unmute
> These all went to no evail; no speech from espeakup, and nothing from
> speaker-test. Am I missing something here? Is there an amixer set All
> unmute or something? configlessnd_hda_intel is enabled as a module, as
> is the Realtek codec; the system picked up on the device fine.
>
>
Did you setup /etc/asound.conf or .asoundrc ?
https://wiki.gentoo.org/wiki/ALSA

I was under the impression that pulse uses the lower level ALSA stuff, so
you can use ALSA without pulse but not pulse without ALSA

Re: [gentoo-user] No Sound After Reboot, or, More Troubles with Firmware?

[Walter Dnes]

On Mon, Dec 18, 2017 at 10:18:06PM -0500, Hunter Jozwiak wrote
> Hello again,
> 
> While fixing my wifi card issues, I came across yet another issue. I
> set the snd-hda-intel PCH as my default soundcard, but I have no sound
> whatsoever, which renders the system pretty much inoperable to me. I
> tried the following:
> amixer set Master unmute
> amixer set Speaker unmute
> amixer set Headphone unmute
> These all went to no evail; no speech from espeakup, and nothing from
> speaker-test. Am I missing something here? Is there an amixer set All
> unmute or something? configlessnd_hda_intel is enabled as a module, as
> is the Realtek codec; the system picked up on the device fine.

  Did you run "alsamixer" and check if sound is muted?

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Loading a Firmware Module By hand?

[Mick]

On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote:
> Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version
> 9 as well, but that didn't help matters, either. Nor did
> compiling the firmware into the kernel; either 4.14 is too old, or it
> is too new. 

I'd think they are both too new?

> I tried copying the firmware my live iso was using, but
> that didn't help either.

If the live iso works, start with using the same kernel release and linux-
firmware version, to see if this works as expected on your installation.  Then 
update kernel sources and firmware to the latest stable and see if this works 
too.

>From there on you can move into ~arch to find the version at which things 
break.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] CHOST missing in no-multilib stage3 make.conf

[Walter Dnes]

On Mon, Dec 18, 2017 at 10:20:48AM -0500, Michael Orlitzky wrote
> On 12/18/2017 10:00 AM, Walter Dnes wrote:
> > 
> >   I tried a couple of different mirrors.  No CHOST line. The example
> > file usr/share/portage/config/make.conf.example shows...
> > 
> > ===
> > CHOST="x86_64-pc-linux-gnu"
> > ===
> > 
> >   I could insert that, but I wonder if anything else is screwed up.
> 
> This silently disappeared some time ago. It's set in the profiles now;
> for example, the file "profiles/arch/amd64/make.defaults" sets
> 
>   CHOST="x86_64-pc-linux-gnu"

  Thanks.  That's good to know.  This could've used a brief news item to
avoid scaring people.  I'll file a documentation bug because
usr/share/portage/config/make.conf.example still shows an explicit CHOST
setting line.  While I'm at it, I'll ask them to mention "-march=native"
in CFLAGS/CXXFLAGS.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Francisco Ares]

2017-12-18 17:02 GMT-02:00 David Haller :

> Hello,
>
> On Mon, 18 Dec 2017, Mick wrote:
> >On Monday, 18 December 2017 16:14:42 GMT Dale wrote:
> >> Grant Edwards wrote:
> >> > I tried following the profile 17 upgrade instructions but now I'm
> >> > stuck.  After running for a day or so, the 'emerge -e @world' command
> >> > stopped when grub-0.97 failed to build.
> >> >
> >> > How do I skip grub and continue?
> >> >
> >> > Or do I have to tell emerge to start over from the beginning (skipping
> >> > grub)?  Assuming there are other packages that are going to fail also,
> >> > that could take weeks...
> >>
> >> emerge --resume --skipfirst
> >>
> >> That should work.  If forced, using --exclude grub might could be
> >> added.  I've never tried that with the --resume command tho.
> >>
> >> Dale
> >>
> >Let's not forget the '--keep-going y' option too.  At the end it will
> print a
> >list of all the packages that failed to emerge.
>
> Well, there's a catch though. I did:
>
> $ emerge -e --keep-going @world
> [some failed pkg(s)]
> [Ctrl-C due to going to sleep etc.]
> $ emerge -e --keep-going --resume @world
> [Ctrl-C due to going to sleep etc.]
> [some failed pkg(s)]
> $ emerge -e --keep-going --resume @world
> [Ctrl-C due to going to sleep etc.]
> [2 more failed pkg(s)]
> [emerge prints just those two failed pkgs that failed since the last
> resume]
>
> And no "failed pgks" were printed at those Ctrl-C...
>
> Only trace was probably deep in the emerge logs and the leftovers in
> /var/tmp/portage (-> you should not these down before you shut down if
> that's a tmpfs ...)
>
> I think something about this should be done / documented.
>
> Luckily, it was no big deal, as I did a switch to gcc-7.2 / -pie at
> the same time, so I ran my "check-pie" script (pie-only check
> extracted from checksec) to find the packages that (might) need a
> recompile. I've just a few biggies leftover to compile and a couple I
> want to mess with. But those have updates pending anyway. So, I'm
> about done.
>
> BTW: in the process, I've collected binaries/packages that won't get
> compiled as pie... e.g. gcc itself, grub and most (all?) haskell
> stuff. ATM, it's a pretty badly ad-hoc script, but I could amend that.
> Or at least share the list of "known non-pie-able" binaries, I guess.
> Hm. One could also add an output that can be fed to emerge via xargs.
>
> -dnh
>
> --
> "As a sysadmin, I suppose you're familiar with something called a
>   'worst-case scenario'?"
> "Isn't that what we call, "having a good day for a change"?"
>(Rik Steenwinkel and Graham Reed)
>
>

I have a script for "-e" :


#! /bin/bash
LOG=/tmp/update.log
date > $LOG
echo   Starting... >> $LOG

#looking for active gcc
N=1
A=`gcc-config -c`
B=$A
while [ $B != `echo $B | sed s/-//` ]
do
   N=$(( $N + 1 ))
   B=`echo $B | sed s/-//`
done
A=`echo $A | cut -d- -f$N-`
GCC_VER=`equery l sys-devel/gcc | grep $A`

nice -n 10 emerge -1v --keep-going --quiet-build =$GCC_VER
sys-devel/libtool 1>> $LOG 2>> $LOG && \
nice -n 10 emerge -1v --keep-going --quiet-build dev-libs/glib
sys-libs/glibc 1>> $LOG 2>> $LOG && \
nice -n 10 emerge -1vb --keep-going --quiet-build =$GCC_VER
sys-devel/libtool 1>> $LOG 2>> $LOG && \
nice -n 10 emerge -vbe --keep-going --quiet-build world 1>> $LOG 2>> $LOG
echo   Resuming... >> $LOG
nice -n 10 emerge -vb --resume --keep-going --quiet-build 1>> $LOG 2>> $LOG
echo   Resuming... >> $LOG
nice -n 10 emerge -vb --resume --keep-going --quiet-build 1>> $LOG 2>> $LOG
echo   Resuming... >> $LOG
nice -n 10 emerge -vb --resume --skip-first --keep-going --quiet-build 1>>
$LOG 2>> $LOG
echo   Resuming... >> $LOG
nice -n 10 emerge -vb --resume --keep-going --quiet-build 1>> $LOG 2>> $LOG
echo   Resuming... >> $LOG
nice -n 10 emerge -vb --resume --skip-first --keep-going --quiet-build 1>>
$LOG 2>> $LOG
echo   Finishing. >> $LOG
date >> $LOG
echo -n  >> $LOG
cat $LOG | mail -b -c -s "emerge -e results" your-email@your-domain



This usually ends up with too many resumes, but at least it gets to the end
of the builds as deep as possible.

Please note the "-b" flag, as I keep binary packages for an emergency.

Hope this helps,
Francisco

Re: [gentoo-user] Choice of TLD for internal network

[Wol's lists]

On 18/12/17 13:56, Michael Orlitzky wrote:

On 12/17/2017 09:05 PM, Peter Humphrey wrote:

Hello list,

I've been running Linux systems since 1994, calling my private LAN mynet
(bowdlerised). Now I come to install neth server on one machine, it insists
that I tell it a domain name with at least two dots in it. But I don't have
a standard TLD.

What do you all call your local LANs? Following Google hints, it looks as
though I may have to change all .mynet references to .mynet.internal.


You should probably buy a TLD. It's stupid, but there are no reserved
top-level domain names for internal use. There used to be four[0],

   * test
   * example
   * invalid
   * localhost

There was no proscribed behavior for those TLDs, so you were free to use
them for your internal network. Then along came rfc6761[1], which tells
people how to treat those four names. In particular,

My router defaults, iirc, to .local. And I thought .home also did the 
same sort of thing.


See RFCs 7788 for .home, and 8244 for .local

It seems to me that 7788 defines .home, although it appears it did not 
do it properly.


I think .local was correctly added to 6761, so that domain CAN be used 
as your private network's TLD.


Cheers,
Wol

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[David Haller]

Hello,

On Mon, 18 Dec 2017, Francisco Ares wrote:
>2017-12-18 17:02 GMT-02:00 David Haller :
>> On Mon, 18 Dec 2017, Mick wrote:
[..]
>> >Let's not forget the '--keep-going y' option too.  At the end it will
>> print a
>> >list of all the packages that failed to emerge.
>>
>> Well, there's a catch though. I did:
>>
>> $ emerge -e --keep-going @world
>> [some failed pkg(s)]
>> [Ctrl-C due to going to sleep etc.]
>> $ emerge -e --keep-going --resume @world
>> [Ctrl-C due to going to sleep etc.]
>> [some failed pkg(s)]
>> $ emerge -e --keep-going --resume @world
>> [Ctrl-C due to going to sleep etc.]
>> [2 more failed pkg(s)]
>> [emerge prints just those two failed pkgs that failed since the last
>> resume]
>>
>> And no "failed pgks" were printed at those Ctrl-C...
>>
>> Only trace was probably deep in the emerge logs and the leftovers in
>> /var/tmp/portage (-> you should not these down before you shut down if
>> that's a tmpfs ...)
>>
>> I think something about this should be done / documented.
[..]
>I have a script for "-e" :
>
>#! /bin/bash
[..]
>nice -n 10 emerge -1v --keep-going --quiet-build =$GCC_VER
>sys-devel/libtool 1>> $LOG 2>> $LOG && \
>nice -n 10 emerge -1v --keep-going --quiet-build dev-libs/glib
>sys-libs/glibc 1>> $LOG 2>> $LOG && \

I think you've got those reversed. glib depends on glibc. And, besides
being a lib that more and more (basic) packages depend on for utility,
has nothing to do with (g)libc. It's started as a basic utility lib
for the Gimp Toolkit (gtk) ... ;)

>nice -n 10 emerge -1vb --keep-going --quiet-build =$GCC_VER
>sys-devel/libtool 1>> $LOG 2>> $LOG && \

Is this rebuild of gcc / libtool intentional? And what about binutils?
Those are quite critical, IMO.

>nice -n 10 emerge -vbe --keep-going --quiet-build world 1>> $LOG 2>> $LOG
>echo   Resuming... >> $LOG

Ah, yeah. Logging. I should've done that. But, as I said, I noticed
too late about that "problem" with resume and failed packages.

BTW: your script will be much easier to maintain if you rewrite is as
such:


exec 1>>$LOG
exec 2>>$LOG
# more redirs, e.g. for console output possible


and instead of all those


foo && \
bar && ...


write


foo || exit 1
bar || exit 2
...


or some such. And this stuff:

>nice -n 10 emerge -vb --resume --keep-going --quiet-build 1>> $LOG 2>> $LOG
>echo   Resuming... >> $LOG
>nice -n 10 emerge -vb --resume --keep-going --quiet-build 1>> $LOG 2>> $LOG
>echo   Resuming... >> $LOG
[..]
>echo   Finishing. >> $LOG

could be wrapped in a loop... I don't know, but I'd hope emerge exits
with a status != 0 if packages failed. And if so, you could use


while ! nice -n 10 emerge ... ; do
echo   Resuming...
done
echo   Finishing.


(assuming you've redirected fd1 to $LOG as mentioned above ;)

[..]
>Please note the "-b" flag, as I keep binary packages for an emergency.

So do I. And I keep a /stage3 dir around. If python/portage breaks,
I just need to point PATH & LD_LIBRARY_PATH and stuff to /stage3/bla
and can restart. BTDT when pulling 4-years abandoned gentoo up to date
last year...

>Hope this helps,

Yeah. Logging ;) And,

HTH, too,
-dnh

-- 
Sheridan: "I'll tell you one thing. If the primates that we came from had
known that some day politicians would come out of the gene pool, they'd have
stayed up in the trees and written evolution off as a bad idea!"
 -- Babylon 5, 2x04 - A Distant Star

Re: [gentoo-user] Colorized output when piping to tee

[David Haller]

Hello,

On Mon, 18 Dec 2017, Ramon Fischer wrote:
>I am looking for a way to have a colorized output when piping to tee, e.g.:
>
>/usr/bin/emerge --ask --update --deep --newuse --tree --verbose @world | 
> tee --append nom.txt
>
>I already tried installing "dev-tcltk/expect" which should actually contain 
>"unbuffer" which can help me out. But there is no unbuffer command.

# qfile `which unbuffer`
app-misc/unbuffer (/usr/bin/unbuffer)

>Am I missing something or is there any other way to do that?

unbuffer won't help you there anyway. That only changes when stuff is
written to the pipe.

You're actually looking for:


   --color < y | n >
  Enable  or  disable  color  output.   This  option will override
  NOCOLOR (see make.conf(5)) and may also be used to  force  color
  output  when  stdout is not a tty (by default, color is disabled
  unless stdout is a tty).
=

BTW: if you don't want that colorized output in the log, add

app-text/ansifilter (/usr/bin/ansifilter)

for reading the log.

HTH,
-dnh

-- 
MCSE: "Microsoft Certified Stupidity enclosed"-- A. Spengler

Re: [gentoo-user] Colorized output when piping to tee

[Walter Dnes]

On Mon, Dec 18, 2017 at 07:46:16PM +, Ramon Fischer wrote
> Hi there,
> 
> I am looking for a way to have a colorized output when piping to tee, e.g.:
> 
> /usr/bin/emerge --ask --update --deep --newuse --tree --verbose @world | 
> tee --append nom.txt
> 
> I already tried installing "dev-tcltk/expect" which should actually contain 
> "unbuffer" which can help me out. But there is no unbuffer command.
> 
> Am I missing something or is there any other way to do that?

  From "man emerge"

   --color < y | n >
  Enable  or  disable  color  output.   This  option will override
  NOCOLOR (see make.conf(5)) and may also be used to  force  color
  output  when  stdout is not a tty (by default, color is disabled
  unless stdout is a tty).

  So you'd want...

/usr/bin/emerge --color y --ask --update --deep --newuse --tree --verbose 
@world | tee --append nom.txt

  Insert "--color y" into the command.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Choice of TLD for internal network

[David Haller]

Hello,

On Mon, 18 Dec 2017, Peter Humphrey wrote:
>Come to think of it, I have a .me.uk domain registered. I wonder if I can 
>use that...

Of course you can. Just add a third/fourth level subdomain and put
your stuff under this. E.g. I have a domain example.de registered to
me, resolving from-da-induhned. With hosts such as
{www,mail}.example.de and example.de redirected to www.

Now then, internally, I chose hostnames. And then use those, not
resolvable via DNS, via /etc/hosts and dnsmasq. From my /etc/hosts:

127.0.0.1   ${hostname}.example.de  ${hostname} localhost
127.0.0.1   news.${hostname}.example.de news
127.0.0.2   docs.${hostname}.example.de docsdocs.example.de
127.0.0.3   www.${hostname}.example.de  www
127.0.0.1   irc.${hostname}.example.de  irc
127.0.0.1   ftp.${hostname}.example.de  ftp

So, just replace example.de by ${yourprefix}.me.uk and have fun, and
use ${hostname}.${yourprefix}.me.uk, www.${hostname}.${yourprefix}.me.uk.

HTH,
-dnh

-- 
"Ford had his own code of ethics. It wasn't much of one, but it was
his and he stuck by it, more or less. One rule he made was never to
buy his own drinks. He wasn't sure if that counted as an ethic, but
you have to go with what you've got. "

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[David Haller]

Hello,

On Mon, 18 Dec 2017, Mick wrote:
>On Monday, 18 December 2017 16:14:42 GMT Dale wrote:
>> Grant Edwards wrote:
>> > I tried following the profile 17 upgrade instructions but now I'm
>> > stuck.  After running for a day or so, the 'emerge -e @world' command
>> > stopped when grub-0.97 failed to build.
>> > 
>> > How do I skip grub and continue?
>> > 
>> > Or do I have to tell emerge to start over from the beginning (skipping
>> > grub)?  Assuming there are other packages that are going to fail also,
>> > that could take weeks...
>> 
>> emerge --resume --skipfirst 
>> 
>> That should work.  If forced, using --exclude grub might could be
>> added.  I've never tried that with the --resume command tho. 
>> 
>> Dale
>> 
>Let's not forget the '--keep-going y' option too.  At the end it will print a 
>list of all the packages that failed to emerge.

Well, there's a catch though. I did:

$ emerge -e --keep-going @world
[some failed pkg(s)]
[Ctrl-C due to going to sleep etc.]
$ emerge -e --keep-going --resume @world
[Ctrl-C due to going to sleep etc.]
[some failed pkg(s)]
$ emerge -e --keep-going --resume @world
[Ctrl-C due to going to sleep etc.]
[2 more failed pkg(s)]
[emerge prints just those two failed pkgs that failed since the last
resume]

And no "failed pgks" were printed at those Ctrl-C...

Only trace was probably deep in the emerge logs and the leftovers in
/var/tmp/portage (-> you should not these down before you shut down if
that's a tmpfs ...)

I think something about this should be done / documented.

Luckily, it was no big deal, as I did a switch to gcc-7.2 / -pie at
the same time, so I ran my "check-pie" script (pie-only check
extracted from checksec) to find the packages that (might) need a
recompile. I've just a few biggies leftover to compile and a couple I
want to mess with. But those have updates pending anyway. So, I'm
about done.

BTW: in the process, I've collected binaries/packages that won't get
compiled as pie... e.g. gcc itself, grub and most (all?) haskell
stuff. ATM, it's a pretty badly ad-hoc script, but I could amend that.
Or at least share the list of "known non-pie-able" binaries, I guess.
Hm. One could also add an output that can be fed to emerge via xargs.

-dnh

-- 
"As a sysadmin, I suppose you're familiar with something called a
  'worst-case scenario'?"
"Isn't that what we call, "having a good day for a change"?"
   (Rik Steenwinkel and Graham Reed)

[gentoo-user] Colorized output when piping to tee

[Ramon Fischer]

Hi there,

I am looking for a way to have a colorized output when piping to tee, e.g.:

/usr/bin/emerge --ask --update --deep --newuse --tree --verbose @world | 
tee --append nom.txt

I already tried installing "dev-tcltk/expect" which should actually contain 
"unbuffer" which can help me out. But there is no unbuffer command.

Am I missing something or is there any other way to do that?

-Ramon

Re: [gentoo-user] Choice of TLD for internal network

[Michael Orlitzky]

On 12/18/2017 02:55 PM, Wol's lists wrote:
>
> My router defaults, iirc, to .local. And I thought .home also did the 
> same sort of thing.

Both are reserved: the ".home" TLD is reserved for the Home Networking
Control Protocol in the RFC 7788 that you cited, and ".local" is
reserved for some multicast DNS mumbo jumbo in RFC 6762.

(There is no good choice, and out of the bad ones, ".local" is OK I guess.)


> See RFCs 7788 for .home, and 8244 for .local

I didn't know about RFC 8244 (it's from October), but it looks like it
only points out the existing problems. I'll go read it.


> I think .local was correctly added to 6761, so that domain CAN be used 
> as your private network's TLD.

local doesn't appear in RFC 6761, you might be thinking of localhost?
For ".localhost", the RFC more or less states that your users can assume
that all addresses resolve to 127.0.0.1, which makes it unsuitable for a
network with more than one machine.

Re: [gentoo-user] Choice of TLD for internal network

[David Haller]

Hello,

On Mon, 18 Dec 2017, Michael Orlitzky wrote:
>On 12/18/2017 02:55 PM, Wol's lists wrote:
>> My router defaults, iirc, to .local. And I thought .home also did the 
>> same sort of thing.
>
>Both are reserved: the ".home" TLD is reserved for the Home Networking
>Control Protocol in the RFC 7788 that you cited, and ".local" is
>reserved for some multicast DNS mumbo jumbo in RFC 6762.
>
>(There is no good choice, and out of the bad ones, ".local" is OK I guess.)
>
>> See RFCs 7788 for .home, and 8244 for .local
>
>I didn't know about RFC 8244 (it's from October), but it looks like it
>only points out the existing problems. I'll go read it.
>
>> I think .local was correctly added to 6761, so that domain CAN be used 
>> as your private network's TLD.
>
>local doesn't appear in RFC 6761, you might be thinking of localhost?
>For ".localhost", the RFC more or less states that your users can assume
>that all addresses resolve to 127.0.0.1, which makes it unsuitable for a
>network with more than one machine.

ISTR, .localdomain is the new .local...

BTW: I hate it how .local got ursurped by zeroconf/mDNS.

-dnh

-- 
[the role of government] is not taking over the health care system, that has
existed for a long long time and has produced the best health records in the
world ... -- Mitt Romney, 2012, first presidential candidate debate,
 who clearly never has seen "Sicko" by Michael Moore

Re: [gentoo-user] CHOST missing in no-multilib stage3 make.conf

[Mike Gilbert]

On Mon, Dec 18, 2017 at 3:20 PM, Walter Dnes  wrote:
> On Mon, Dec 18, 2017 at 10:20:48AM -0500, Michael Orlitzky wrote
>> On 12/18/2017 10:00 AM, Walter Dnes wrote:
>> >
>> >   I tried a couple of different mirrors.  No CHOST line. The example
>> > file usr/share/portage/config/make.conf.example shows...
>> >
>> > ===
>> > CHOST="x86_64-pc-linux-gnu"
>> > ===
>> >
>> >   I could insert that, but I wonder if anything else is screwed up.
>>
>> This silently disappeared some time ago. It's set in the profiles now;
>> for example, the file "profiles/arch/amd64/make.defaults" sets
>>
>>   CHOST="x86_64-pc-linux-gnu"
>
>   Thanks.  That's good to know.  This could've used a brief news item to
> avoid scaring people.  I'll file a documentation bug because
> usr/share/portage/config/make.conf.example still shows an explicit CHOST
> setting line.  While I'm at it, I'll ask them to mention "-march=native"
> in CFLAGS/CXXFLAGS.

CHOST is still a valid setting in make.conf, so removing it from the
example is not necessary.

Setting CHOST is still necessary for archs like x86, on which you have
i486, i586 and i686 variants.

Re: [gentoo-user] Loading a Firmware Module By hand?

[Floyd Anderson]

On Mon, 18 Dec 2017 19:15:04 +
Hunter Jozwiak  wrote:

On 12/18/17, Mick  wrote:

On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote:

Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version
9 as well, but that didn't help matters, either. Nor did
compiling the firmware into the kernel; either 4.14 is too old, or it
is too new.


I'd think they are both too new?


I tried copying the firmware my live iso was using, but
that didn't help either.


If the live iso works, start with using the same kernel release and linux-
firmware version, to see if this works as expected on your installation.
Then
update kernel sources and firmware to the latest stable and see if this
works
too.

From there on you can move into ~arch to find the version at which things
break.
--
Regards,
Mick

Okay, here are the dmesg messages:
https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/
The present kernel configuration, as of yesterday evening:
https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/
Make and model of the offending card: Qualcomm 6174 revision 20.
Not exactly what the -2 error means, but I will try as Mick suggested
and work my way forwards to see what I can get working.



Hi,

I was a little bit confused from your earlier mentioned

   /lib/firmware/ath10k/QCABLEFAGD/HW3.0

I wonder where this firmware come from. I cannot find it, neither with 
the identifier ‘QCABLEFAGD’ nor an upper cased ‘HW3.0’ directory in 
[1][2][3][4].


Your log tells an other story now. As far as I can tell:

   “Direct firmware load for […] failed with error -2”

comes from _request_firmware and fw_get_filesystem_firmware functions in 
file [5]. The symbolic error name ENOENT, see `man 3 errno`, means 
something like ‘No such element’ or ‘No such file or directory’.


Even CONFIG_EXTRA_FIRMWARE_DIR defaults to ‘/lib/firmware’, there should 
be whether an entry ‘# CONFIG_EXTRA_FIRMWARE_DIR is not set’ or 
something like ‘CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"’ in your 
config. Its unclear to me why it is not there.


If you want to build into the kernel again, check 
‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set:


   CONFIG_FIRMWARE_IN_KERNEL=y
   CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin"
   CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

Hope that helps.


[1] 

[2] 

[3] 
[4] 
[5] 




--
Regards,
floyd

Re: [gentoo-user] Loading a Firmware Module By hand?

[Floyd Anderson]

If you want to build into the kernel again, check 
‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set:


  CONFIG_FIRMWARE_IN_KERNEL=y
  CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin"
  CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"



I must correct myself. I’ve seen that the file ‘firmware-6.bin’ is 
located in ‘/lib/firmware/ath10k/QCA6174/hw3.0’ and ‘firmware-5.bin’ 
lives in ‘/lib/firmware/ath10k/QCA6174/hw2.1’, see [1].


That is where your firmware loading error comes from (and my wrong 
example for the CONFIG_EXTRA_FIRMWARE). So, the correct kernel 
configuration should be:


   CONFIG_FIRMWARE_IN_KERNEL=y
   CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-5.bin"
   CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

or

   CONFIG_FIRMWARE_IN_KERNEL=y
   CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw3.0/firmware-6.bin"
   CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"


[1] 



--
Regards,
floyd

Re: [gentoo-user] Choice of TLD for internal network

[Bill Kenworthy]

On 19/12/17 04:25, David Haller wrote:
> Hello,
> 
> On Mon, 18 Dec 2017, Michael Orlitzky wrote:
>> On 12/18/2017 02:55 PM, Wol's lists wrote:
>>> My router defaults, iirc, to .local. And I thought .home also did the 
>>> same sort of thing.
>>
>> Both are reserved: the ".home" TLD is reserved for the Home Networking
>> Control Protocol in the RFC 7788 that you cited, and ".local" is
>> reserved for some multicast DNS mumbo jumbo in RFC 6762.
>>
>> (There is no good choice, and out of the bad ones, ".local" is OK I guess.)
>>
>>> See RFCs 7788 for .home, and 8244 for .local
>>
>> I didn't know about RFC 8244 (it's from October), but it looks like it
>> only points out the existing problems. I'll go read it.
>>
>>> I think .local was correctly added to 6761, so that domain CAN be used 
>>> as your private network's TLD.
>>
>> local doesn't appear in RFC 6761, you might be thinking of localhost?
>> For ".localhost", the RFC more or less states that your users can assume
>> that all addresses resolve to 127.0.0.1, which makes it unsuitable for a
>> network with more than one machine.
> 
> ISTR, .localdomain is the new .local...
> 
> BTW: I hate it how .local got ursurped by zeroconf/mDNS.
> 
> -dnh
> 

I have used .localdomain for years without issue.  VLANS
(wifi.localdomain, lan.localdomain etc.) are great if you have the
hardware to do it.

Using non-official TLD internally shouldn't cause any problems (unless
someone is "stupid").

BillK

Re: [gentoo-user] Loading a Firmware Module By hand?

[Hunter Jozwiak]

On 12/18/17, Floyd Anderson  wrote:
> On Mon, 18 Dec 2017 19:15:04 +
> Hunter Jozwiak  wrote:
>>On 12/18/17, Mick  wrote:
>>> On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote:
 Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version
 9 as well, but that didn't help matters, either. Nor did
 compiling the firmware into the kernel; either 4.14 is too old, or it
 is too new.
>>>
>>> I'd think they are both too new?
>>>
 I tried copying the firmware my live iso was using, but
 that didn't help either.
>>>
>>> If the live iso works, start with using the same kernel release and
>>> linux-
>>> firmware version, to see if this works as expected on your installation.
>>> Then
>>> update kernel sources and firmware to the latest stable and see if this
>>> works
>>> too.
>>>
>>> From there on you can move into ~arch to find the version at which
>>> things
>>> break.
>>> --
>>> Regards,
>>> Mick
>>Okay, here are the dmesg messages:
>>https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/
>>The present kernel configuration, as of yesterday evening:
>>https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/
>>Make and model of the offending card: Qualcomm 6174 revision 20.
>>Not exactly what the -2 error means, but I will try as Mick suggested
>>and work my way forwards to see what I can get working.
>>
>
> Hi,
>
> I was a little bit confused from your earlier mentioned
>
> /lib/firmware/ath10k/QCABLEFAGD/HW3.0
>
> I wonder where this firmware come from. I cannot find it, neither with
> the identifier ‘QCABLEFAGD’ nor an upper cased ‘HW3.0’ directory in
> [1][2][3][4].
>
> Your log tells an other story now. As far as I can tell:
>
> “Direct firmware load for […] failed with error -2”
>
> comes from _request_firmware and fw_get_filesystem_firmware functions in
> file [5]. The symbolic error name ENOENT, see `man 3 errno`, means
> something like ‘No such element’ or ‘No such file or directory’.
>
> Even CONFIG_EXTRA_FIRMWARE_DIR defaults to ‘/lib/firmware’, there should
> be whether an entry ‘# CONFIG_EXTRA_FIRMWARE_DIR is not set’ or
> something like ‘CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"’ in your
> config. Its unclear to me why it is not there.
>
> If you want to build into the kernel again, check
> ‘/lib/firmware/ath10k/QCA6174/hw2.1/firmware-6.bin’ exists and set:
>
> CONFIG_FIRMWARE_IN_KERNEL=y
> CONFIG_EXTRA_FIRMWARE="ath10k/QCA6174/hw2.1/firmware-6.bin"
> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
>
> Hope that helps.
>
>
> [1]
> 
> [2]
> 
> [3] 
> [4] 
> [5]
> 
>
>
>
> --
> Regards,
> floyd
>
>
>
That particular firmware does not exist. I am trying to figure how far
back I need to rollback the kernel. Sabayon's live ISO is using
4.13.0, but that is no longer in the tree. Not sure if I need to go
back to the 4.12 ebuilds, or if 4.13.5 will suit my needs; perhaps
there is a bit of source code that I can look at to see what is being
used for the firmware?

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Dale]

Mick wrote:
> On Monday, 18 December 2017 16:14:42 GMT Dale wrote:
>> Grant Edwards wrote:
>>> I tried following the profile 17 upgrade instructions but now I'm
>>> stuck.  After running for a day or so, the 'emerge -e @world' command
>>> stopped when grub-0.97 failed to build.
>>>
>>> How do I skip grub and continue?
>>>
>>> Or do I have to tell emerge to start over from the beginning (skipping
>>> grub)?  Assuming there are other packages that are going to fail also,
>>> that could take weeks...
>> emerge --resume --skipfirst 
>>
>> That should work.  If forced, using --exclude grub might could be
>> added.  I've never tried that with the --resume command tho. 
>>
>> Dale
>>
>> :-)  :-) 
> Let's not forget the '--keep-going y' option too.  At the end it will print a 
> list of all the packages that failed to emerge.
>


I have to confess, I set most of this as defaults in make.conf.  The
most often commands I use, eix-sync and emerge -uaDN world.  Everything
else is in make.conf.  Listy for those who may be curious.

EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j5
--quiet-build=n -1 --unordered-display"

FEATURES="-usersync userpriv usersandbox buildpkg sandbox parallel-fetch"

Each of those were added as I noticed I needed them more often than
not.  The backtrack option started out at 50 but sometimes that wasn't
enough so I increased it to 100.  That has worked well so far.  The
--oneshot, (-1), option was to keep unneeded things from being added to
my world file.  Each option has some reason for being there. 

If someone reading this wants to copy that, may solve some problems at
least.  ;-) 

Dale

:-)  :-) 

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Mick]

On Monday, 18 December 2017 16:14:42 GMT Dale wrote:
> Grant Edwards wrote:
> > I tried following the profile 17 upgrade instructions but now I'm
> > stuck.  After running for a day or so, the 'emerge -e @world' command
> > stopped when grub-0.97 failed to build.
> > 
> > How do I skip grub and continue?
> > 
> > Or do I have to tell emerge to start over from the beginning (skipping
> > grub)?  Assuming there are other packages that are going to fail also,
> > that could take weeks...
> 
> emerge --resume --skipfirst 
> 
> That should work.  If forced, using --exclude grub might could be
> added.  I've never tried that with the --resume command tho. 
> 
> Dale
> 
> :-)  :-) 

Let's not forget the '--keep-going y' option too.  At the end it will print a 
list of all the packages that failed to emerge.

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] xinput_calibrator on ARM (Odroid XU4) refuses to output to xinput

[R0b0t1]

On Mon, Dec 18, 2017 at 12:30 PM, Francisco Ares  wrote:
> Hi,
>
> I'm trying to use an eGalax touch screen in this Odroid, using
> xinput_calibrator like this:
>
> $DEVICE_NAME=`xinput_calibrator --list | grep "eGalax" | cut -d\" -f2`
> /usr/bin/xinput_calibrator --misclick 0 --device "$DEVICE_NAME"
> --output-type xinput
>
> doesnt work, xinput_calibrator outputs an error after the apparently
> successful calibration screen:
>
> ERROR: XorgPrint Calibrator does not support the supplied --output-type
> Error: unable to apply or save configuration values
>
> Any hints?  Is it expected on an ARM CPU?  I use it the same way in a x86
> machine, and it works perfectly...
>

Are the versions the same? What happens if you try the xorg.conf.d output type?

Nothing seems like it should be related to your architecture, but the
package may be older or newer.

Cheers,
 R0b0t1.

Re: [gentoo-user] Loading a Firmware Module By hand?

[Hunter Jozwiak]

On 12/18/17, Mick  wrote:
> On Monday, 18 December 2017 05:11:20 GMT Hunter Jozwiak wrote:
>> Hmm. I have kernel 4.14.7 and linux-firmware 20171206. I tried version
>> 9 as well, but that didn't help matters, either. Nor did
>> compiling the firmware into the kernel; either 4.14 is too old, or it
>> is too new.
>
> I'd think they are both too new?
>
>> I tried copying the firmware my live iso was using, but
>> that didn't help either.
>
> If the live iso works, start with using the same kernel release and linux-
> firmware version, to see if this works as expected on your installation.
> Then
> update kernel sources and firmware to the latest stable and see if this
> works
> too.
>
> From there on you can move into ~arch to find the version at which things
> break.
> --
> Regards,
> Mick
Okay, here are the dmesg messages:
https://paste.pound-python.org/show/nrNfBAEPfh9W7ZIeItJC/
The present kernel configuration, as of yesterday evening:
https://paste.pound-python.org/show/NmNB8nzLuEjmsz74kRVE/
Make and model of the offending card: Qualcomm 6174 revision 20.
Not exactly what the -2 error means, but I will try as Mick suggested
and work my way forwards to see what I can get working.

[gentoo-user] xinput_calibrator on ARM (Odroid XU4) refuses to output to xinput

[Francisco Ares]

Hi,

I'm trying to use an eGalax touch screen in this Odroid, using
xinput_calibrator like this:

$DEVICE_NAME=`xinput_calibrator --list | grep "eGalax" | cut -d\" -f2`
/usr/bin/xinput_calibrator --misclick 0 --device "$DEVICE_NAME" --output-type
xinput

doesnt work, xinput_calibrator outputs an error after the apparently
successful calibration screen:

ERROR: XorgPrint Calibrator does not support the supplied --output-type
Error: unable to apply or save configuration values

Any hints?  Is it expected on an ARM CPU?  I use it the same way in a x86
machine, and it works perfectly...

Thanks a lot!
Francisco

[gentoo-user] Re: Choice of TLD for internal network

[Ian Zimmerman]

On 2017-12-19 00:10, Peter Humphrey wrote:

> Maybe not. See the debate at
> https://community.nethserver.org/t/i-fell-at-the-first-hurdle/8563/4

"You can't simply edit configuration files."

I stopped reading there. {8-P

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

[gentoo-user] Upgrading kernel with gcc6... use mrproper and not clean

[Daniel Frey]

I just thought I'd send this out in case others aren't aware...

I've updated some seven machines now to the new profile and gcc6. Out of 
the seven, four of them had problems rebuilding the kernel which led to 
an outright hang during booting (black screen, no kernel panic, just hang.)


I found out `make clean` is not enough, I had to backup my .config, use 
`make mrproper`, restore the .config and run `make silentoldconfig` 
before compiling the kernel and modules.


I am thinking `make clean` didn't remove everything made during the 
compile process and caused some strange race condition somewhere while 
booting (completely guessing here.)


I went back to the three that seemed to be working fine and did the 
mrproper process on them, because if something happens down the line I 
probably won't remember what caused the boot issue.


Dan

[gentoo-user] Re: Upgrading kernel with gcc6... use mrproper and not clean

[Daniel Frey]

On 12/18/17 18:46, Daniel Frey wrote:

I just thought I'd send this out in case others aren't aware...

I've updated some seven machines now to the new profile and gcc6. Out of 
the seven, four of them had problems rebuilding the kernel which led to 
an outright hang during booting (black screen, no kernel panic, just hang.)


I found out `make clean` is not enough, I had to backup my .config, use 
`make mrproper`, restore the .config and run `make silentoldconfig` 
before compiling the kernel and modules.


I am thinking `make clean` didn't remove everything made during the 
compile process and caused some strange race condition somewhere while 
booting (completely guessing here.)


I went back to the three that seemed to be working fine and did the 
mrproper process on them, because if something happens down the line I 
probably won't remember what caused the boot issue.


Dan


Sigh... from the kernel Makefile:

# clean - Delete most, but leave enough to build external modules

The computers in question that were hanging were using external modules 
such as nvidia, open-vm-tools modules, vmware modules, etc...


*smacks head against wall*

I guess I answered my own question now, and I'll bet that everyone here 
knew this already!


Dan

[gentoo-user] No Sound After Reboot, or, More Troubles with Firmware?

[Hunter Jozwiak]

Hello again,

While fixing my wifi card issues, I came across yet another issue. I
set the snd-hda-intel PCH as my default soundcard, but I have no sound
whatsoever, which renders the system pretty much inoperable to me. I
tried the following:
amixer set Master unmute
amixer set Speaker unmute
amixer set Headphone unmute
These all went to no evail; no speech from espeakup, and nothing from
speaker-test. Am I missing something here? Is there an amixer set All
unmute or something? configlessnd_hda_intel is enabled as a module, as
is the Realtek codec; the system picked up on the device fine.

Thanks,

Hunter

Re: [gentoo-user] Loading a Firmware Module By hand?

[Adam Carter]

That particular firmware does not exist. I am trying to figure how far

> back I need to rollback the kernel. Sabayon's live ISO is using
> 4.13.0, but that is no longer in the tree. Not sure if I need to go
> back to the 4.12 ebuilds, or if 4.13.5 will suit my needs; perhaps
> there is a bit of source code that I can look at to see what is being
> used for the firmware?
>

Are you thinking that there's some interoperability issues between kernel
versions and firmwares? My impression is that's generally not a problem, so
wouldn't be too worried about trying different kernel versions.

So the steps are just;
- identify the correct firmware
- verify its in /lib/firmware (typically just emerge linux-firmware, but
sometimes others from /usr/portage/sys-firmware/ )
- configure the kernel to load it (in this case follow Floyd's instructions)
- build and install new kernel
- reboot

FYI on one of my systems;
$ zgrep ^C.*FIRM /proc/config.gz
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="i915/skl_dmc_ver1_26.bin i915/skl_guc_ver6_1.bin
intel-ucode/06-4e-03"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
CONFIG_FIRMWARE_MEMMAP=y
$ dmesg | egrep '(firm|microcode)'
[0.300096] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_26.bin
(v1.26)
[0.321592] microcode: sig=0x406e3, pf=0x80, revision=0xba
[0.321679] microcode: Microcode Update Driver: v2.2.
$

Re: [gentoo-user] Choice of TLD for internal network

[Adam Carter]

On Tue, Dec 19, 2017 at 11:10 AM, Peter Humphrey 
wrote:

> On Monday, 18 December 2017 09:49:41 GMT Adam Carter wrote:
> > On Mon, Dec 18, 2017 at 1:05 PM, Peter Humphrey 
> > wrote:
> > > I've been running Linux systems since 1994, calling my private LAN
> mynet
> > > (bowdlerised). Now I come to install neth server on one machine, it
> > > insists that I tell it a domain name with at least two dots in it.
> >
> > That's dumb, and may be an omen on what the rest of it is like.
>
> Maybe not. See the debate at
> https://community.nethserver.org/t/i-fell-at-the-first-hurdle/8563/4
>
>
I can't see any concrete info on why your original config was a problem,
but a charitable read could amount to "given the interdependencies of the
various components, the requirement for two dots in the FQDN was deemed the
best compromise *for neth*".

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[David Haller]

Hello,

On Mon, 18 Dec 2017, Dale wrote:
>The key thing, remembering to force it to be added to world, which is a
>lot easier than remembering to use -1 for ALL those things I don't want
>in the world file.  Before I added the -1 option, my world file was full
>of all sorts of things that have no business being there at all.  It was
>causing huge problems with upgrades and such. 

Hm.

# wc -l /var/lib/portage/world
1140 /var/lib/portage/world

Am I doing something wrong? Looking it over, it looks right though.
And --depclean is hopelessly overeager here.


Packages installed:   3511
Packages in world:1140
Packages in system:   43
Required packages:2581
Number to remove: 930


Hm. I guess there's stuff missing from world (linux-gazette*?) or
something's broke. I guess I should quickpkg stuff, run a depclean and
go figure what's missing ;) adding to world/pruning whatever ;) I know
a lot of those "depcleaned" pkgs are wanted/needed, so I missed adding
stuff to world or deps are lacking... Oh well. Not while I'm cleaning
up after the profile-13/gcc-5.4 -> profile-17/gcc-7.2 stuff (I'd
already compiled most with gcc 6.4, with "std=c++14" for C++ stuff. So
not much change there besides pie/no-pie.

-dnh

-- 
Shin - Device for finding furniture in the dark.

Re: [gentoo-user] Re: Choice of TLD for internal network

[R0b0t1]

On Mon, Dec 18, 2017 at 8:06 PM, Ian Zimmerman  wrote:
> On 2017-12-19 00:10, Peter Humphrey wrote:
>
>> Maybe not. See the debate at
>> https://community.nethserver.org/t/i-fell-at-the-first-hurdle/8563/4
>
> "You can't simply edit configuration files."
>
> I stopped reading there. {8-P
>

This is the point where I'd give up. If it doesn't work and can't be
fixed by editing the configuration directly, the only other option is
developing for neth. That's back to square 1, if you switched to neth
to save time.

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Adam Carter]

>
> I have to confess, I set most of this as defaults in make.conf.  The
> most often commands I use, eix-sync and emerge -uaDN world.  Everything
> else is in make.conf.  Listy for those who may be curious.
>
> EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j5
> --quiet-build=n -1 --unordered-display"
>
> FEATURES="-usersync userpriv usersandbox buildpkg sandbox parallel-fetch"
>
> Each of those were added as I noticed I needed them more often than
> not.  The backtrack option started out at 50 but sometimes that wasn't
> enough so I increased it to 100.  That has worked well so far.  The
> --oneshot, (-1), option was to keep unneeded things from being added to
> my world file.  Each option has some reason for being there.
>
>
Won't the -1 mean that --depclean will remove packages that you want?

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Dale]

Adam Carter wrote:
>
> I have to confess, I set most of this as defaults in make.conf.  The
> most often commands I use, eix-sync and emerge -uaDN world. 
> Everything
> else is in make.conf.  Listy for those who may be curious.
>
> EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going
> -v -j5
> --quiet-build=n -1 --unordered-display"
>
> FEATURES="-usersync userpriv usersandbox buildpkg sandbox
> parallel-fetch"
>
> Each of those were added as I noticed I needed them more often than
> not.  The backtrack option started out at 50 but sometimes that wasn't
> enough so I increased it to 100.  That has worked well so far.  The
> --oneshot, (-1), option was to keep unneeded things from being
> added to
> my world file.  Each option has some reason for being there.
>
>
> Won't the -1 mean that --depclean will remove packages that you want?
>

If I emerge something and want to keep around, I use the --select y
option which overrides the -1 option in make.conf.  Sometimes I install
something, play with it and don't like it and then let --depclean remove
it.  If I emerge something and like it, I can use --select y -n to add
it to world, without compiling it again. 

The key thing, remembering to force it to be added to world, which is a
lot easier than remembering to use -1 for ALL those things I don't want
in the world file.  Before I added the -1 option, my world file was full
of all sorts of things that have no business being there at all.  It was
causing huge problems with upgrades and such. 

I just use what works for me.  Some may not like doing it this way but
some might. 

Dale

:-)  :-) 

Re: [gentoo-user] Choice of TLD for internal network

[Peter Humphrey]

On Monday, 18 December 2017 09:49:41 GMT Adam Carter wrote:
> On Mon, Dec 18, 2017 at 1:05 PM, Peter Humphrey 
> wrote:
> > I've been running Linux systems since 1994, calling my private LAN mynet
> > (bowdlerised). Now I come to install neth server on one machine, it
> > insists that I tell it a domain name with at least two dots in it.
> 
> That's dumb, and may be an omen on what the rest of it is like.

Maybe not. See the debate at
https://community.nethserver.org/t/i-fell-at-the-first-hurdle/8563/4

-- 
Regards,
Peter.

Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?

[Adam Carter]

>
> Hm.
>
> # wc -l /var/lib/portage/world
> 1140 /var/lib/portage/world
>
> Am I doing something wrong?


If you're emerging dependencies without -1, then yes, otherwise, no.


> Looking it over, it looks right though.
> And --depclean is hopelessly overeager here.
>

What makes you think that?


> 
> Packages installed:   3511
> Packages in world:1140
> Packages in system:   43
> Required packages:2581
> Number to remove: 930
> 
>
> Hm. I guess there's stuff missing from world (linux-gazette*?) or
> something's broke. I guess I should quickpkg stuff, run a depclean and
> go figure what's missing ;) adding to world/pruning whatever ;) I know
> a lot of those "depcleaned" pkgs are wanted/needed, so I missed adding
> stuff to world or deps are lacking...


Yeah reviewing the output of a --pv --depclean sounds like a good idea.
Then you can add anything that's obviously missing to world before a real
--depclean. When i depclean i use -av --depclean --exclude gcc --exclude
gentoo-sources, since i like keep 2 gcc's around and I look after sources
manually.

AFAIK missing dependencies are rare as they are quickly identified by the
breakage.


> Oh well. Not while I'm cleaning
> up after the profile-13/gcc-5.4 -> profile-17/gcc-7.2 stuff (I'd
> already compiled most with gcc 6.4, with "std=c++14" for C++ stuff. So
> not much change there besides pie/no-pie.
>

I ended up rebuilding two machines, partly due to self induced
hardened/PIE/PIC pain, and also to start with empty USE and
/etc/portage/package.* files which were full of crap after many years. I
now have;
$ wc -l /var/lib/portage/world
63 /var/lib/portage/world

and emerge -pe says "Total: 1024 packages"