slackware.ru
http://www.slackware.ru/forum/

Slackware GNU/Linux Current (x86, x86_64)
http://www.slackware.ru/forum/viewtopic.php?f=8&t=1573
Страница 2 из 2

Автор:  bormant [ 23 апр 2015 22:02 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Если б меня спрашивали, сказал бы, что всякие дополнения к оригинальному комплекту имеет смысл класть в отдельный каталог, ежели только нет желания делать свой дистрибутив/сборку на базе Slackware.

Автор:  Ne01eX [ 23 апр 2015 23:27 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Ладно, тогда только с минимум рассинхрона.

Автор:  Ne01eX [ 26 апр 2015 02:22 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

25.04.2015 было очередное обновление в current.

Цитата:
Sat Apr 25 02:37:47 UTC 2015
a/aaa_elflibs-14.1-i486-6.txz: Rebuilt.
Added libstdc++.so.6.0.20.
a/cxxlibs-6.0.18-i486-1.txz: Removed.
a/mkinitrd-1.4.8-i486-4.txz: Rebuilt.
In mkinitrd_command_generator.sh: fixed the kernel version detection, and
muted the error about missing /sys hcd module directories.
Blacklisted iphone-set-info to prevent the initrd from uselessly bloating.
Thanks to Ryan P.C. McQuen, Eric Hameleers, and Dan Church.
d/gcc-4.9.2-i486-2.txz: Rebuilt.
Recompiled with --enable-install-libiberty. Thanks to fskmh.
d/gcc-g++-4.9.2-i486-2.txz: Rebuilt.
d/gcc-gfortran-4.9.2-i486-2.txz: Rebuilt.
d/gcc-gnat-4.9.2-i486-2.txz: Rebuilt.
d/gcc-go-4.9.2-i486-2.txz: Rebuilt.
d/gcc-java-4.9.2-i486-2.txz: Rebuilt.
d/gcc-objc-4.9.2-i486-2.txz: Rebuilt.
d/llvm-3.6.0-i486-2.txz: Rebuilt.
Fixed overly restrictive permissions on c++-analyzer, ccc-analyzer,
scan-build, set-xcode-analyzer, and scan-view.
Thanks to Ricardo Nabinger Sanchez.
l/gc-7.4.2-i486-2.txz: Rebuilt.
Patched to fix "undefined reference to `GC_setup_mark_lock'", noticed while
building inkscape. Thanks to Matteo Bernardini.
l/libmpc-1.0.3-i486-1.txz: Upgraded.
Thanks to fskmh.
l/lzo-2.09-i486-1.txz: Upgraded.
l/netpbm-10.66.02-i486-2.txz: Rebuilt.
Fixed libnetpbm.so symlink. Thanks to Matteo Bernardini.
n/crda-3.18-i486-2.txz: Rebuilt.
Ensure libreg.so is installed in the proper lib directory.
Thanks to Robby Workman.
n/iproute2-3.18.0-i486-2.txz: Rebuilt.
Properly handle /etc/iproute2/nl_protos.new config file.
Thanks to Wim Speekenbrink.
n/libgpg-error-1.18-i486-2.txz: Rebuilt.
Compress info file, and remove /usr/info/dir from package.
Thanks to Edward Trumbo.
Don't build static library.
n/php-5.6.8-i486-2.txz: Rebuilt.
Fixed permissions on /etc/httpd/. Thanks to Francisco Ambrozio.
n/rsync-3.1.1-i486-1.txz: Upgraded.


Цитата:
Sat Apr 25 02:37:47 UTC 2015
a/aaa_elflibs-14.1-x86_64-6.txz: Rebuilt.
Added libstdc++.so.6.0.20.
a/cxxlibs-6.0.18-x86_64-1.txz: Removed.
a/mkinitrd-1.4.8-x86_64-4.txz: Rebuilt.
In mkinitrd_command_generator.sh: fixed the kernel version detection, and
muted the error about missing /sys hcd module directories.
Blacklisted iphone-set-info to prevent the initrd from uselessly bloating.
Thanks to Ryan P.C. McQuen, Eric Hameleers, and Dan Church.
d/gcc-4.9.2-x86_64-2.txz: Rebuilt.
Recompiled with --enable-install-libiberty. Thanks to fskmh.
d/gcc-g++-4.9.2-x86_64-2.txz: Rebuilt.
d/gcc-gfortran-4.9.2-x86_64-2.txz: Rebuilt.
d/gcc-gnat-4.9.2-x86_64-2.txz: Rebuilt.
d/gcc-go-4.9.2-x86_64-2.txz: Rebuilt.
d/gcc-java-4.9.2-x86_64-2.txz: Rebuilt.
d/gcc-objc-4.9.2-x86_64-2.txz: Rebuilt.
d/llvm-3.6.0-x86_64-2.txz: Rebuilt.
Fixed overly restrictive permissions on c++-analyzer, ccc-analyzer,
scan-build, set-xcode-analyzer, and scan-view.
Thanks to Ricardo Nabinger Sanchez.
l/gc-7.4.2-x86_64-2.txz: Rebuilt.
Patched to fix "undefined reference to `GC_setup_mark_lock'", noticed while
building inkscape. Thanks to Matteo Bernardini.
l/libmpc-1.0.3-x86_64-1.txz: Upgraded.
Thanks to fskmh.
l/lzo-2.09-x86_64-1.txz: Upgraded.
l/netpbm-10.66.02-x86_64-2.txz: Rebuilt.
Fixed libnetpbm.so symlink. Thanks to Matteo Bernardini.
n/crda-3.18-x86_64-2.txz: Rebuilt.
Ensure libreg.so is installed in the proper lib directory.
Thanks to Robby Workman.
n/iproute2-3.18.0-x86_64-2.txz: Rebuilt.
Properly handle /etc/iproute2/nl_protos.new config file.
Thanks to Wim Speekenbrink.
n/libgpg-error-1.18-x86_64-2.txz: Rebuilt.
Compress info file, and remove /usr/info/dir from package.
Thanks to Edward Trumbo.
Don't build static library.
n/php-5.6.8-x86_64-2.txz: Rebuilt.
Fixed permissions on /etc/httpd/. Thanks to Francisco Ambrozio.
n/rsync-3.1.1-x86_64-1.txz: Upgraded.


На данный момент остаются поломанными:

n/NetworkManager - Не подымает автоматом конфиги из /etc/NetworkManager/system-connections/
xap/MPlayer - Не работает. Совсем. Как следствие, - не работает kmplayer.

Пока не разбирался толком, почему и что отломалось.

Автор:  bormant [ 26 апр 2015 10:48 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Оф.форум про -current и MPlayer:
http://www.linuxquestions.org/questions ... ?p=5352207


Тема про последствия обновления 21-03-2015:
http://www.linuxquestions.org/questions ... 175540515/
Есть смысл отписаться про проблемы с NM там.
Вечерком попробую воспроизвести ситуацию у себя.


Тема про то, что еще неплохо обновить в -current:
http://www.linuxquestions.org/questions ... 175540375/

Автор:  bormant [ 26 апр 2015 21:58 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Цитата:
n/NetworkManager - Не подымает автоматом конфиги из /etc/NetworkManager/system-connections/

не могу воспроизвести в Slackware64, давайте подробностей.

Тестировал в VB на проводном соединении. Соединение было создано в 14.1, netconfig, NetworkManager, в интерфейсе создано системное проводное соединение.

Произведено обновление до -current. После обновления соединение поднято без замечаний.

Как обновлялись до -current? Правильная последовательность
Код:
# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system


PS. Если ставили отдельные серии, вместо slackpkg install-new можно использовать установку набора серий:
Код:
# slackpkg install a ap l n x xap xfce y d k

Автор:  Ne01eX [ 27 апр 2015 09:34 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Некорректная работа NM проявляется только на 32-битной сборке. И хорошо воспроизводится. На 64 битах у меня такого тоже нет.

В обоих случаях имеет место свежая полная установка на соседних разделах. И там и там конфиги брал из одного бэкапа. На одном интерфейсе поднята внутрисеть, на втором - интернет. Настройки самые тривиальные.

Автор:  bormant [ 27 апр 2015 12:57 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Ne01eX,
ок, тогда рассказывайте, как воспроизвести.

Slackware-current 14.1+, 32 бита:
Код:
# for o in g n r c d; do nmcli $o; done
STATE      CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN   
connected  full          enabled  enabled  enabled  enabled
enabled
WIFI-HW  WIFI     WWAN-HW  WWAN   
enabled  enabled  enabled  enabled
NAME  UUID                                  TYPE            DEVICE
eth0  35978bf9-8fbb-4458-a253-353bffdc3f91  802-3-ethernet  eth0   
DEVICE  TYPE      STATE      CONNECTION
eth0    ethernet  connected  eth0       
lo      loopback  unmanaged  --     
Код:
grep NetworkManager /var/log/messages
Apr 27 12:26:37 w7-swc NetworkManager[666]: <info>  NetworkManager (version 1.0.0) is starting...
Apr 27 12:26:37 w7-swc NetworkManager[666]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf
Apr 27 12:26:37 w7-swc NetworkManager[666]: <info>  WEXT support is enabled
Apr 27 12:26:38 w7-swc NetworkManager[666]: <info>  Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Apr 27 12:26:38 w7-swc NetworkManager[666]: <info>  new connection /etc/NetworkManager/system-connections/eth0
Apr 27 12:26:39 w7-swc NetworkManager[666]: <info>  monitoring kernel firmware directory '/lib/firmware'.
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  WiFi enabled by radio killswitch; enabled by state file
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  WWAN enabled by radio killswitch; enabled by state file
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  WiMAX enabled by radio killswitch; enabled by state file
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  Networking is enabled by state file
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (lo): link connected
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (lo): carrier is ON
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (lo): new Generic device (driver: 'unknown' ifindex: 1)
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): carrier is OFF
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): new Ethernet device (driver: 'e1000' ifindex: 2)
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): link connected
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): preparing device
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  Auto-activating connection 'eth0'.
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: starting connection 'eth0'
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  NetworkManager state is now CONNECTING
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 2 of 5 (Device Configure) successful.
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 3 of 5 (IP Configure Start) started...
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 27 12:26:40 w7-swc NetworkManager[666]: <info>  Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 27 12:26:41 w7-swc NetworkManager[666]: <info>  dhcpcd started with pid 694
Apr 27 12:26:41 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 3 of 5 (IP Configure Start) complete.
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>  ModemManager disappeared from bus
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>  ModemManager available in the bus
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>    address 10.0.2.15
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>    plen 24 (255.255.255.0)
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>    gateway 10.0.2.2
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>    server identifier 10.0.2.2
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>    lease time 86400
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>    nameserver '192.168.1.1'
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>    domain name 'home.loc'
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>  (eth0): DHCPv4 state changed unknown -> bound
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 27 12:26:42 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  NetworkManager state is now CONNECTED_LOCAL
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  NetworkManager state is now CONNECTED_GLOBAL
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  Policy set 'eth0' (eth0) as default for IPv4 routing and DNS.
Apr 27 12:26:43 w7-swc NetworkManager[666]: <info>  (eth0): Activation: successful, device activated.
Apr 27 12:26:45 w7-swc NetworkManager[666]: <info>  startup complete
Apr 27 12:27:13 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Apr 27 12:27:13 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started...
Apr 27 12:27:13 w7-swc NetworkManager[666]: <info>  (eth0): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete.
Код:
# cat /etc/NetworkManager/system-connections/eth0
[ethernet]
duplex=full
mac-address=xx:xx:xx:xx:xx:xx
mac-address-blacklist=

[connection]
id=eth0
uuid=35978bf9-8fbb-4458-a253-353bffdc3f91
type=ethernet
permissions=
timestamp=1430126466
secondaries=

[ipv6]
method=auto
dns-search=
ip6-privacy=0

[ipv4]
method=auto
dns-search=

Ничего крамольного (если не считать номера процесса ;) )...

Автор:  Ne01eX [ 28 апр 2015 08:53 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Часть первая:

Цитата:
Apr 28 10:30:50 duo NetworkManager[887]: <info> NetworkManager (version 1.0.0) is starting...
Apr 28 10:30:50 duo NetworkManager[887]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Apr 28 10:30:50 duo NetworkManager[887]: <info> WEXT support is enabled
Apr 28 10:30:50 duo NetworkManager[887]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Apr 28 10:30:50 duo NetworkManager[887]: <info> keyfile: ipv4.addresses1: Deprecated semicolon at the end of value.
Apr 28 10:30:50 duo NetworkManager[887]: <info> new connection /etc/NetworkManager/system-connections/Внутрисеть
Apr 28 10:30:50 duo NetworkManager[887]: <info> keyfile: ipv4.addresses1: Deprecated semicolon at the end of value.
Apr 28 10:30:50 duo NetworkManager[887]: <info> new connection /etc/NetworkManager/system-connections/Проводное соединение 1
Apr 28 10:30:50 duo NetworkManager[887]: <info> monitoring kernel firmware directory '/lib/firmware'.
Apr 28 10:30:50 duo NetworkManager[887]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
Apr 28 10:30:50 duo NetworkManager[887]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
Apr 28 10:30:50 duo NetworkManager[887]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
Apr 28 10:30:50 duo NetworkManager[887]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
Apr 28 10:30:50 duo NetworkManager[887]: <info> WiFi enabled by radio killswitch; enabled by state file
Apr 28 10:30:50 duo NetworkManager[887]: <info> WWAN enabled by radio killswitch; enabled by state file
Apr 28 10:30:50 duo NetworkManager[887]: <info> WiMAX enabled by radio killswitch; enabled by state file
Apr 28 10:30:50 duo NetworkManager[887]: <info> Networking is enabled by state file
Apr 28 10:30:50 duo NetworkManager[887]: <info> (lo): link connected
Apr 28 10:30:50 duo NetworkManager[887]: <info> (lo): carrier is ON
Apr 28 10:30:50 duo NetworkManager[887]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Apr 28 10:30:50 duo NetworkManager[887]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): link connected
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): carrier is ON
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): new Ethernet device (driver: 'via-rhine' ifindex: 2)
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Apr 28 10:30:50 duo NetworkManager[887]: <info> startup complete
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: starting connection 'eth0'
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): link connected
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): carrier is ON
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): new Ethernet device (driver: 'r8169' ifindex: 3)
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/2
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: starting connection 'eth1'
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) successful.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) successful.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) started...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv6 Commit) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) complete.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) started...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv6 Commit) scheduled...
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) complete.
Apr 28 10:30:50 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv6 Commit) started...
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv6 Commit) complete.
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv6 Commit) started...
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv6 Commit) complete.
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 28 10:30:52 duo NetworkManager[887]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:30:52 duo NetworkManager[887]: <info> NetworkManager state is now CONNECTED_LOCAL
Apr 28 10:30:53 duo NetworkManager[887]: <info> NetworkManager state is now CONNECTED_GLOBAL
Apr 28 10:30:53 duo NetworkManager[887]: <info> Policy set 'eth0' (eth0) as default for IPv4 routing and DNS.
Apr 28 10:30:53 duo NetworkManager[887]: <info> (eth0): Activation: successful, device activated.
Apr 28 10:30:53 duo NetworkManager[887]: <info> (eth1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:30:54 duo NetworkManager[887]: <info> (eth1): Activation: successful, device activated.
Apr 28 10:30:55 duo NetworkManager[887]: <info> ModemManager disappeared from bus
Apr 28 10:30:55 duo NetworkManager[887]: <info> ModemManager available in the bus


Здесь я гашу ненужные мне соединения eth1 и eth0 тыкая мышкой в апплете NM:

Цитата:
Apr 28 10:36:04 duo NetworkManager[887]: <info> (eth1): device state change: activated -> deactivating (reason 'user-requested') [100 110 39]
Apr 28 10:36:04 duo NetworkManager[887]: <info> (eth1): device state change: deactivating -> disconnected (reason 'user-requested') [110 30 39]
Apr 28 10:36:04 duo NetworkManager[887]: <info> (eth1): deactivating device (reason 'user-requested') [39]
Apr 28 10:36:09 duo NetworkManager[887]: <info> (eth0): device state change: activated -> deactivating (reason 'user-requested') [100 110 39]
Apr 28 10:36:09 duo NetworkManager[887]: <info> NetworkManager state is now DISCONNECTED
Apr 28 10:36:09 duo NetworkManager[887]: <info> (eth0): device state change: deactivating -> disconnected (reason 'user-requested') [110 30 39]
Apr 28 10:36:09 duo NetworkManager[887]: <info> (eth0): deactivating device (reason 'user-requested') [39]


И также тыкая мышкой подымаю то, что нужно мне:

Цитата:
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: starting connection 'Проводное соединение 1'
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 28 10:36:12 duo NetworkManager[887]: <info> NetworkManager state is now CONNECTING
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) successful.
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) started...
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) complete.
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:36:12 duo NetworkManager[887]: <info> NetworkManager state is now CONNECTED_LOCAL
Apr 28 10:36:12 duo NetworkManager[887]: <info> NetworkManager state is now CONNECTED_GLOBAL
Apr 28 10:36:12 duo NetworkManager[887]: <info> Policy set 'Проводное соединение 1' (eth1) as default for IPv4 routing and DNS.
Apr 28 10:36:12 duo NetworkManager[887]: <info> (eth1): Activation: successful, device activated.
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: starting connection 'Внутрисеть'
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) successful.
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) started...
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) complete.
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:36:17 duo NetworkManager[887]: <info> (eth0): Activation: successful, device activated.


Сейчас покажу, как это должно быть на самом деле:

Автор:  Ne01eX [ 28 апр 2015 09:01 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Часть 2. Когда всё работает сразу:
Цитата:
Apr 28 10:51:14 duo NetworkManager[829]: <info> NetworkManager (version 1.0.0) is starting...
Apr 28 10:51:14 duo NetworkManager[829]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
Apr 28 10:51:14 duo NetworkManager[829]: <info> WEXT support is enabled
Apr 28 10:51:14 duo NetworkManager[829]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Apr 28 10:51:14 duo NetworkManager[829]: <info> keyfile: ipv4.addresses1: Deprecated semicolon at the end of value.
Apr 28 10:51:14 duo NetworkManager[829]: <info> new connection /etc/NetworkManager/system-connections/Внутрисеть
Apr 28 10:51:14 duo NetworkManager[829]: <info> keyfile: ipv4.addresses1: Deprecated semicolon at the end of value.
Apr 28 10:51:14 duo NetworkManager[829]: <info> new connection /etc/NetworkManager/system-connections/Проводное соединение 1
Apr 28 10:51:14 duo NetworkManager[829]: <info> monitoring kernel firmware directory '/lib/firmware'.
Apr 28 10:51:14 duo NetworkManager[829]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-adsl.so
Apr 28 10:51:14 duo NetworkManager[829]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wifi.so
Apr 28 10:51:14 duo NetworkManager[829]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-wwan.so
Apr 28 10:51:14 duo NetworkManager[829]: <info> Loaded device plugin: /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so
Apr 28 10:51:14 duo NetworkManager[829]: <info> WiFi enabled by radio killswitch; enabled by state file
Apr 28 10:51:14 duo NetworkManager[829]: <info> WWAN enabled by radio killswitch; enabled by state file
Apr 28 10:51:14 duo NetworkManager[829]: <info> WiMAX enabled by radio killswitch; enabled by state file
Apr 28 10:51:14 duo NetworkManager[829]: <info> Networking is enabled by state file
Apr 28 10:51:14 duo NetworkManager[829]: <info> (lo): link connected
Apr 28 10:51:14 duo NetworkManager[829]: <info> (lo): carrier is ON
Apr 28 10:51:14 duo NetworkManager[829]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
Apr 28 10:51:14 duo NetworkManager[829]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): carrier is OFF
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): new Ethernet device (driver: 'via-rhine' ifindex: 2)
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/1
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): link connected
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): preparing device
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): link connected
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): carrier is ON
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 3)
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/2
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: starting connection 'eth0'
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 28 10:51:14 duo NetworkManager[829]: <info> Auto-activating connection 'Внутрисеть'.
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) successful.
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) started...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 5 of 5 (IPv6 Commit) scheduled...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 3 of 5 (IP Configure Start) complete.
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): Activation: starting connection 'Внутрисеть'
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 10:51:14 duo NetworkManager[829]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth0): Activation: Stage 5 of 5 (IPv6 Commit) started...
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth0): Activation: Stage 5 of 5 (IPv6 Commit) complete.
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) started...
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 28 10:51:15 duo NetworkManager[829]: <info> NetworkManager state is now CONNECTING
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) scheduled...
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): Activation: Stage 1 of 5 (Device Prepare) complete.
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) starting...
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) successful.
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): Activation: Stage 2 of 5 (Device Configure) complete.
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
Apr 28 10:51:15 duo NetworkManager[829]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:51:16 duo NetworkManager[829]: <info> NetworkManager state is now CONNECTED_GLOBAL
Apr 28 10:51:16 duo NetworkManager[829]: <info> Policy set 'eth0' (eth0) as default for IPv4 routing and DNS.
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth0): Activation: successful, device activated.
Apr 28 10:51:16 duo NetworkManager[829]: <info> ModemManager disappeared from bus
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) started...
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): Activation: Stage 3 of 5 (IP Configure Start) complete.
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Commit) started...
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): Activation: Stage 5 of 5 (IPv4 Commit) complete.
Apr 28 10:51:16 duo NetworkManager[829]: <info> ModemManager available in the bus
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 28 10:51:16 duo NetworkManager[829]: <info> (eth1): Activation: successful, device activated.
Apr 28 10:51:20 duo NetworkManager[829]: <info> startup complete
Apr 28 10:51:48 duo NetworkManager[829]: <info> (eth1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Apr 28 10:51:48 duo NetworkManager[829]: <info> (eth1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) started...
Apr 28 10:51:48 duo NetworkManager[829]: <info> (eth1): Activation: Stage 4 of 5 (IPv6 Configure Timeout) complete.

Автор:  Ne01eX [ 28 апр 2015 09:54 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

P.S. Пересборка NM результата не дала. :-):

Автор:  bormant [ 28 апр 2015 11:47 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

То есть, разница только в том, какая карта из eth0, eth1 первой оживает?
Можно увидеть маршруты в обоих случаях, когда работает и когда нет?

Возможно не связано с, тем не менее, файлы конфигурации правильно обновлены? Об использовании старого синтаксиса говорят, в частности, строки вроде:
Код:
<info> keyfile: ipv4.addresses1: Deprecated semicolon at the end of value.

Автор:  Ne01eX [ 08 май 2015 10:33 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Торрент перезалит 08.05.2015

Подробности и ChangeLog здесь: http://rutracker.org/forum/viewtopic.php?t=4927939

Автор:  Ne01eX [ 12 май 2015 19:52 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Обновление на slackware.com:

Цитата:
Tue May 12 07:17:33 UTC 2015
ap/mariadb-10.0.18-i586-1.txz: Upgraded.
This update contains security fixes and improvements.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-0501
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-2571
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-0505
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-0499
(* Security fix *)
n/wpa_supplicant-2.4-i486-2.txz: Rebuilt.
This update fixes potential denial of service issues.
For more information, see:
http://w1.fi/security/2015-1/wpa_suppli ... erflow.txt
http://w1.fi/security/2015-2/wps-upnp-h ... coding.txt
http://w1.fi/security/2015-3/integer-un ... -frame.txt
http://w1.fi/security/2015-4/eap-pwd-mi ... dation.txt
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-1863
(* Security fix *)
ap/terminus-font-4.39-noarch-1.txz: Upgraded.
l/libcanberra-0.30-i486-1.txz: Upgraded.
l/qt-4.8.6-i586-4.txz: Rebuilt.
QNAM: Fix upload corruptions when server closes connection
This patch fixes several upload corruptions if the server closes the
connection while/before we send data into it.
cherry picked from commit: qtbase/cff39fba10ffc10ee4dcfdc66ff6528eb
d/slacktrack-2.17-i486-1.txz: Upgraded.
Thanks to Stuart Winter.


Цитата:
Tue May 12 07:17:33 UTC 2015
ap/mariadb-10.0.18-x86_64-1.txz: Upgraded.
This update contains security fixes and improvements.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-0501
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-2571
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-0505
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-0499
(* Security fix *)
ap/terminus-font-4.39-noarch-1.txz: Upgraded.
d/slacktrack-2.17-x86_64-1.txz: Upgraded.
Thanks to Stuart Winter.
l/libcanberra-0.30-x86_64-1.txz: Upgraded.
l/qt-4.8.6-x86_64-4.txz: Rebuilt.
QNAM: Fix upload corruptions when server closes connection
This patch fixes several upload corruptions if the server closes the
connection while/before we send data into it.
cherry picked from commit: qtbase/cff39fba10ffc10ee4dcfdc66ff6528eb
n/wpa_supplicant-2.4-x86_64-2.txz: Rebuilt.
This update fixes potential denial of service issues.
For more information, see:
http://w1.fi/security/2015-1/wpa_suppli ... erflow.txt
http://w1.fi/security/2015-2/wps-upnp-h ... coding.txt
http://w1.fi/security/2015-3/integer-un ... -frame.txt
http://w1.fi/security/2015-4/eap-pwd-mi ... dation.txt
http://cve.mitre.org/cgi-bin/cvename.cg ... -2015-1863
(* Security fix *)

Автор:  Ne01eX [ 16 июл 2015 20:55 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

Итак, рад представить вашему вниманию свежий разрабатываемый выпуск S.C.R. GNU/Linux для платформ x86 и x86_64 (amd64).

Изображение

Буду краток. В данный выпуск было добавлено/обновлено/пересобрано около 170 пакаджей разнообразной тематики. В первую очередь, это, конечно, пользовательское ПО для работы с фото, графикой и мультимедиа. Например, теперь не составляет какого-либо труда организовать, используя Slackware Current Ru работу домашней или даже профессиональной фотостудии. И это не единственное применение нового выпуска S.C.R ;-).

Подробности в Changelog2.txt на любом из установочных дисков S.C.R.

Помимо новых пакаджей в свежем выпуске S.C.R. был слегка переработан установочный образ RAM-диска. Впервую очередь это касается модулей ядра, - теперь они вынесены в отдельные squash-образы (так, как это было сделано в крайних выпусках RTK GNU/Linux). Это позволило не только снизить системные требования (по оперативной памяти) S.C.R., но и даже слегка ускорить загрузку.

Так же данное решение позволило разместить на установочном образе утилиты из комплектов ddrescue, testdisk, cmospwd, заменить некоторые утилиты из комплекта busybox их полноценными аналогами, разместить файловый менеджер mc и текстовый редактор le. Другими словами, - в случае возникновения проблем с железом, S.C.R. теперь поможет решить некоторые из них, не прибегая к стороннему ПО.

И, да, - данный выпуск Slackware Current Ru синхронизирован с выпуском Slackware от 12.06.2015. История изменений Slackware отражена в файле Changelog.txt.

Вкратце, - это всё. Повторюсь, - подробности в файлах ChangeLog на установочных дисках S.C.R.

Официальный анонс
Скачать S.C.R. GNU/Linux для платформ x86 и x86_64 можно здесь.

Ваш Штандартенфюрер S, - Ne01eX.

Автор:  sunjob [ 24 янв 2016 17:20 ]
Заголовок сообщения:  Re: Slackware GNU/Linux Current (x86, x86_64)

добрый день

есть сопутствующая проблема, буду благодарен, если поможете
спасибо

п.с. надеюсь не нарушаю правила форума

http://www.slackware.ru/forum/viewtopic.php?f=8&t=1773

Страница 2 из 2 Часовой пояс: UTC + 3 часа
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/