Re: [gentoo-user] Set the alias of an interface with netifrc

[Alarig Le Lay]

On sam. 19 janv. 16:45:42 2019, J. Roeleveld wrote:
> Not sure if that is actually "supported" by netifrc.
> You could add these commands in a postup() block.

I did that, thanks!

> Is there a specific benefit for just setting an "alias" like this?

Yes, knowing what each interface is used for.

-- 
Alarig

Re: [gentoo-user] Re: minimal grub:2 install? [grub:0 being removed]

[Mick]

On Friday, 18 January 2019 20:57:45 GMT Grant Edwards wrote:
> On 2019-01-18, Grant Edwards  wrote:
> > On 2019-01-18, Daniel Frey  wrote:
> >> As someone else mentioned you can mask grub-mkconfig. I didn't bother,
> >> it isn't run automatically.
> > 
> > I should have known that on Gentoo it wouldn't be.  I ought to think
> > about starting to switch to grub2.  On one of my simpler installs, I
> > may try out the chainloading from grub to grub2 scheme documented at
> > 
> > https://wiki.gentoo.org/wiki/GRUB2_Migration
> 
> I had some spare time while watching a Windows 10 machine while away a
> few hours doing updates (WTF does it take so long?  Is it rebuilding
> everything from sources?). So, I decided to give the above migration
> scheme a try on one of my "simple" machines, and it worked swimmingly
> except the auto-generated grub.cfg file fell over.  I was not
> surprised. The kernel started to boot, but then locked up at the point
> where the video mode switches.
> 
> Fortunately, the chainloading scheme allows you to reboot into a
> working system via grub-0.97 and tweak things until grub-2 works. I
> manually created a grub.cfg file, and it worked fine.  Then I did a
> final 'grub2-install', uninstalled grub:0, and all that's left is to
> clean the grub:0 files out of /boot/grub.
> 
> I'm still amazed by the giant mess that grub2-mkconfig spits out.
> It's 90X larger than my manually generated config file:
> 
> # grub2-mkconfig 2>/dev/null | wc
> 4381661   17888
> 
> # wc boot/grub/grub.cfg
>  10  17 200 boot/grub/grub.cfg

There's also extlinux of the syslinux project.  I'm thinking of giving this a 
spin on an old system of mine.  It's pretty minimalist, doesn't need re-
installing after adding a new kernel[1] and it will boot FAT, NTFS, ext2/3/4, 
Btrfs, XFS, UFS/FFS, so it should cover my needs.

[1] I'm used to manually editing /boot/grub/grub.conf with legacy grub anyway, 
so extlinux is no different.
-- 
Regards,
Mick

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

Re: [gentoo-user] Re: bash upgrading problem

[Jacques Montier]

Thanks Jack,

Le sam. 19 janv. 2019 à 19:03, Jack  a
écrit :

>
> --quoted attachment
> “app-shells:bash-4.4_p23-r1:20190119-102517.log”--
> [snip much of emerge log]
> So the problem occurs at the end of the ./configure stage.  You did not
> include this in your original post.
> > checking which library has the termcap functions... (cached) using
> > libcurses
> > checking whether /dev/fd is available...
> > ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be
> > preloaded (cannot open shared object file): ignored.
> So this is the real error - portage can't (pre)load libsandbox.so.
> 1) When is the last time you did a full upgrade?  I'm now wondering if
> you have inconsistent versions of different packages installed.
> 2) Try re-emerging sys-apps/sandbox.
>

 - I just did a full upgrade by : emerge -auvDN --with-bdeps=y --keep-going
world => so i have to upgrade bash
[ebuild U  ] app-shells/bash-4.4_p23-r1::gentoo [4.4_p12::gentoo]
USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins"
0 KiB
- Then emerge sandbox => OK
- Then emerge bash => it stops asking for passwd. :-(

3) If that does not work, try running revdep-rebuild.  It should not
> normally be necessary, but there are times.  Did an emerge world ever
> get interrupted?
>
>
- revdep-rebuild done without any error


--
Jacques

Re: [gentoo-user] Re: bash upgrading problem

[Jack]

On 2019.01.19 05:51, Jacques Montier wrote:
Le ven. 18 janv. 2019 à 21:36, Nikos Chantziaras  a  
écrit :

> On 18/01/2019 13:29, Jacques Montier wrote:

[snip]

Thanks Jack and Nikos,

I did not have any problem with bash emerge so far.
It is not clear if you do not have any problem with the emerge, or if  
it is still failing.

Here is the attached log.

[snip]
The only thing i did some days ago, was to change my user jacques  
password. In the sudoers file, i have the row : jacques ALL=(ALL)  
NOPASSWD: ALL So with sudo, i don't have to write the root password.
Changing the password should not cause any problems, and that sudo  
entry look fine.


It is not version bash related as i tried to re-emerge the installed  
app-shells/bash and it fails.

So you DO still have the problem.
[snip]

--quoted attachment  
“app-shells:bash-4.4_p23-r1:20190119-102517.log”--

[snip much of emerge log]
So the problem occurs at the end of the ./configure stage.  You did not  
include this in your original post.
checking which library has the termcap functions... (cached) using  
libcurses

checking whether /dev/fd is available...
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be  
preloaded (cannot open shared object file): ignored.

So this is the real error - portage can't (pre)load libsandbox.so.
1) When is the last time you did a full upgrade?  I'm now wondering if  
you have inconsistent versions of different packages installed.

2) Try re-emerging sys-apps/sandbox.
3) If that does not work, try running revdep-rebuild.  It should not  
normally be necessary, but there are times.  Did an emerge world ever  
get interrupted?




We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

Sorry, try again.
sandbox:stop  caught signal 2 in pid 10364
sudo: 1 incorrect password attempt
sandbox:stop  Send signal 4 more times to force SIGKILL

[snipped repeated error]

Jack

Re: [gentoo-user] Why is no one discussing this anymore?

[malloc1337]

Thus spoke Peter Humphrey (pe...@prh.myzen.co.uk):
> On Thursday, 27 December 2018 20:32:29 GMT vsnsdua...@memeware.net wrote:
> > Why is no one discussing this anymore.
> 
> Welcome to my kill file.
> 

dito @vsndualce

-- 
m1440c

mailto: dis...@mm-no.de

Re: [gentoo-user] Set the alias of an interface with netifrc

[J. Roeleveld]

On Saturday, January 19, 2019 3:36:15 PM CET Alarig Le Lay wrote:
> Hi,
> 
> On sam. 19 janv. 12:02:20 2019, J. Roeleveld wrote:
> > Not sure if you can use spaces in the name, but I have the following:
> > 
> > $ cat /etc/conf.d/net
> > #config_eno1="dhcp"
> > 
> > config_eno1="null"
> > vlans_eno1="10 15"
> > vlan10_name="adm"
> > vlan15_name="str"
> > rc_net_adm_need="net.eno1"
> > rc_net_str_need="net.eno1"
> > config_adm="10.55.16.44 netmask 255.255.255.0 broadcast 10.55.16.255"
> > routes_adm="default gw 10.55.16.68"
> > config_str="10.30.15.44 netmask 255.255.255.0 broadcast 10.30.15.255"
> > 
> > For this to work, configured the init-scripts as:
> > 
> > $ ls -l /etc/init.d/net.*
> > lrwxrwxrwx 1 root root 6 Jun 16  2016 /etc/init.d/net.adm -> net.lo
> > lrwxrwxrwx 1 root root 6 Jun 15  2016 /etc/init.d/net.eno1 -> net.lo
> > -rwxr-xr-x 1 root root 18514 Mar  2  2018 /etc/init.d/net.lo
> > lrwxrwxrwx 1 root root 6 Jun 16  2016 /etc/init.d/net.str -> net.lo
> > 
> > And only have to add "net.adm" and "net.str" to the runlevel.
> 
> I don’t want to change the name of my interfaces, but the equivalent of
> `ip link set ${if} alias "${whatever}"`.

Not sure if that is actually "supported" by netifrc.
You could add these commands in a postup() block.

Is there a specific benefit for just setting an "alias" like this?

--
Joost

Re: [gentoo-user] Set the alias of an interface with netifrc

[Alarig Le Lay]

Hi,

On sam. 19 janv. 12:02:20 2019, J. Roeleveld wrote:
> Not sure if you can use spaces in the name, but I have the following:
> 
> $ cat /etc/conf.d/net
> #config_eno1="dhcp"
> 
> config_eno1="null"
> vlans_eno1="10 15"
> vlan10_name="adm"
> vlan15_name="str"
> rc_net_adm_need="net.eno1"
> rc_net_str_need="net.eno1"
> config_adm="10.55.16.44 netmask 255.255.255.0 broadcast 10.55.16.255"
> routes_adm="default gw 10.55.16.68"
> config_str="10.30.15.44 netmask 255.255.255.0 broadcast 10.30.15.255"
> 
> For this to work, configured the init-scripts as:
> 
> $ ls -l /etc/init.d/net.*
> lrwxrwxrwx 1 root root 6 Jun 16  2016 /etc/init.d/net.adm -> net.lo
> lrwxrwxrwx 1 root root 6 Jun 15  2016 /etc/init.d/net.eno1 -> net.lo
> -rwxr-xr-x 1 root root 18514 Mar  2  2018 /etc/init.d/net.lo
> lrwxrwxrwx 1 root root 6 Jun 16  2016 /etc/init.d/net.str -> net.lo
> 
> And only have to add "net.adm" and "net.str" to the runlevel.

I don’t want to change the name of my interfaces, but the equivalent of
`ip link set ${if} alias "${whatever}"`.

-- 
Alarig

Re: [gentoo-user] Set the alias of an interface with netifrc

[J. Roeleveld]

On Thursday, January 17, 2019 10:37:32 PM CET Alarig Le Lay wrote:
> Hi,
> 
> I would like to set the alias of my interfaces at boot (if possible with
> netifrc).
> 
> Here are the relevant parts of my configuration:
> config_enp3s0f0="null"
> vlans_enp3s0f0="20 21 22 50"
> config_enp3s0f0_22="185.1.89.13/24 2001:7f8:b1::d/64"
> 
> My interface is well created, but if I want an alias, I have to do it by
> hand:
> asbr02 ~ # ip addr show enp3s0f0.22
> 11: enp3s0f0.22@enp3s0f0:  mtu 1500 qdisc
> noqueue state UP group default qlen 1000 link/ether 00:1b:21:48:68:98 brd
> ff:ff:ff:ff:ff:ff
> inet 185.1.89.13/24 brd 185.1.89.255 scope global enp3s0f0.22
>valid_lft forever preferred_lft forever
> inet6 2001:7f8:b1::d/64 scope global
>valid_lft forever preferred_lft forever
> inet6 fe80::21b:21ff:fe48:6898/64 scope link
>valid_lft forever preferred_lft forever
> asbr02 ~ # ip link set enp3s0f0.22 alias "Peering: BreizhIX"
> asbr02 ~ # ip link show enp3s0f0.22
> 11: enp3s0f0.22@enp3s0f0:  mtu 1500 qdisc
> noqueue state UP mode DEFAULT group default qlen 1000 link/ether
> 00:1b:21:48:68:98 brd ff:ff:ff:ff:ff:ff
> alias Peering: BreizhIX
> 
> On FreeBSD, I did that with an /etc/start_if script:
> ifconfig igb0.22 create
> ifconfig igb0.22 description "Peering: BreizhIX"
> ifconfig igb0.22 vlan 22 vlandev igb0
> ifconfig igb0.22 inet 185.1.89.13/24
> ifconfig igb0.22 inet6 2001:7f8:b1::d/64
> 
> 
> I didn’t find any mention of this in
> /usr/share/doc/netifrc-0.5.1/net.example.bz2
> 
> Am I missing something?

Not sure if you can use spaces in the name, but I have the following:

$ cat /etc/conf.d/net
#config_eno1="dhcp"

config_eno1="null"
vlans_eno1="10 15"
vlan10_name="adm"
vlan15_name="str"
rc_net_adm_need="net.eno1"
rc_net_str_need="net.eno1"
config_adm="10.55.16.44 netmask 255.255.255.0 broadcast 10.55.16.255"
routes_adm="default gw 10.55.16.68"
config_str="10.30.15.44 netmask 255.255.255.0 broadcast 10.30.15.255"

For this to work, configured the init-scripts as:

$ ls -l /etc/init.d/net.*
lrwxrwxrwx 1 root root 6 Jun 16  2016 /etc/init.d/net.adm -> net.lo
lrwxrwxrwx 1 root root 6 Jun 15  2016 /etc/init.d/net.eno1 -> net.lo
-rwxr-xr-x 1 root root 18514 Mar  2  2018 /etc/init.d/net.lo
lrwxrwxrwx 1 root root 6 Jun 16  2016 /etc/init.d/net.str -> net.lo

And only have to add "net.adm" and "net.str" to the runlevel.

--
Joost Roeleveld

Re: [gentoo-user] Re: bash upgrading problem

[Jacques Montier]

*--*
*Jacques*

*https://sites.google.com/site/jacquesfr35/
*


Le ven. 18 janv. 2019 à 21:36, Nikos Chantziaras  a
écrit :

> On 18/01/2019 13:29, Jacques Montier wrote:
> > Hello all,
> >
> > I encounter some problem about upgrading app-shells/bash from 4.4_p12
> > to 4.4_p23-r1.
> > After the checking phase, it stops asking for password (attached file).
> > All passwords (root, user) are rejected, so i can't go further.
> >
> > Any idea ?
>
> Log in as root with:
>
> su -
>
> and then try emerging from there. Reboot.
>
>
>
Thanks Jack and Nikos,

I did not have any problem with bash emerge so far.
Here is the attached log.
As usual, i successfully logged with my root password (su -) and then
#emerge -uv bash

The only thing i did some days ago, was to change my user jacques password.
In the sudoers file, i have the row : jacques ALL=(ALL) NOPASSWD: ALL
So with sudo, i don't have to write the root password.

It is not version bash related as i tried to re-emerge the
installed app-shells/bash and it fails.

Thanks again,

Regards,

--
Jacques
 * Package:app-shells/bash-4.4_p23-r1
 * Repository: gentoo
 * Maintainer: base-sys...@gentoo.org
 * USE:abi_x86_64 amd64 elibc_glibc kernel_linux net nls readline userland_GNU
 * FEATURES:   preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking bash-4.4.tar.gz to /var/tmp/portage/app-shells/bash-4.4_p23-r1/work
>>> Source unpacked in /var/tmp/portage/app-shells/bash-4.4_p23-r1/work
>>> Preparing source in /var/tmp/portage/app-shells/bash-4.4_p23-r1/work/bash-4.4 ...
 * Applying bash44-001 ...
 [ ok ]
 * Applying bash44-002 ...
 [ ok ]
 * Applying bash44-003 ...
 [ ok ]
 * Applying bash44-004 ...
 [ ok ]
 * Applying bash44-005 ...
 [ ok ]
 * Applying bash44-006 ...
 [ ok ]
 * Applying bash44-007 ...
 [ ok ]
 * Applying bash44-008 ...
 [ ok ]
 * Applying bash44-009 ...
 [ ok ]
 * Applying bash44-010 ...
 [ ok ]
 * Applying bash44-011 ...
 [ ok ]
 * Applying bash44-012 ...
 [ ok ]
 * Applying bash44-013 ...
 [ ok ]
 * Applying bash44-014 ...
 [ ok ]
 * Applying bash44-015 ...
 [ ok ]
 * Applying bash44-016 ...
 [ ok ]
 * Applying bash44-017 ...
 [ ok ]
 * Applying bash44-018 ...
 [ ok ]
 * Applying bash44-019 ...
 [ ok ]
 * Applying bash44-020 ...
 [ ok ]
 * Applying bash44-021 ...
 [ ok ]
 * Applying bash44-022 ...
 [ ok ]
 * Applying bash44-023 ...
 [ ok ]
 * Applying bash-4.4-jobs_overflow.patch ...
 [ ok ]
 * Applying bash-4.4-set-SHOBJ_STATUS.patch ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-shells/bash-4.4_p23-r1/work/bash-4.4 ...
 * econf: updating bash-4.4/support/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating bash-4.4/support/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --docdir=/usr/share/doc/bash-4.4_p23-r1 --htmldir=/usr/share/doc/bash-4.4_p23-r1/html --libdir=/usr/lib64 --disable-profiling --docdir=$(datarootdir)/doc/bash-4.4_p23-r1 --htmldir=$(docdir)/html --with-curses --disable-mem-scramble --enable-net-redirections --enable-readline --enable-bang-history --enable-history --without-afs --without-bash-malloc --with-installed-readline=.
configure: loading site script /usr/share/config.site
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu

Beginning configuration for bash-4.4-release for x86_64-pc-linux-gnu

checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc