Re: Free TCP/IP port numbers?

[Gene Heskett]

On Saturday 30 September 2017 22:28:45 Alexander V. Makartsev wrote:

> Ok, I will not waste my time to argue over obvious things.
> You won't get ports more "default" than from this list. Protocols,
> ports and service names are registered for a reason.
> Ex: If you install MySQL server it will be configured to listen on
> port 3306\tcp by default on any OS, be it Debian, RHEL, or Windows.
>
Thats a bit of a stiff attitude.  If his network is an isolated private 
network, there isn't any port police going to come and rip it up or 
prosecute for reconfiguring that install to use any of the ports that 
aren't in the services list. In fact I'd recommend that none of them run 
as root on a day to day basis.

> On 01.10.2017 06:40, Victor Porton wrote:
> > Alexander V. Makartsev wrote:
> >> There is official list of all registered port numbers:
> >> https://www.iana.org/assignments/service-names-port-numbers/service
> >>-names-port-numbers.txt
> >>
> >> You can choose any port that is not in the list, to be sure they
> >> won't clash.
> >
> > The list of port numbers you pointed to me is a subset (or at least
> > not a superset) of the full list used by Debian packages.
> >
> > Assuring that my port is not in this IANA list is not enough to
> > ensure that my port number will not clash with a port number used by
> > a Debian package (by default).
> >
> > So your answer to my question is wrong.
> >
In which case debian should publish the unlisted ports they do use, if 
for no other reason than to "stake a claim".

> >> On 01.10.2017 06:04, Victor Porton wrote:
> >>> We are going to install a range of software on a Debian Linux
> >>> installation. Because we run the same software (such as Celery)
> >>> several times, we need to use port numbers different than the
> >>> standard Debian port numbers chosen by default (because we can't
> >>> run more than one instance of a server with the same port, and
> >>> thus using the standard port number for all servers would fail).
> >>>
> >>> How to choose TCP/IP port numbers for server software we run in
> >>> such a way that they don't clash with "standard" Debian port
> >>> numbers?
> >>>
> >>> In Debian are there any ranges of port numbers dedicated (so that
> >>> they wouldn't clash with "standard" that is used by default port
> >>> numbers) for servers configured by users?
> >>>
> >>> Note that we run (at least some of) our software not as root, so
> >>> we can't use ports below 1024.


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

installer une instance mastodon

[bernard . schoenacker]

bonjour,

j'ai suivi ce tutoriel :
angristan.fr/installer-instance-mastodon-debian-8/

et j'ai le problème suivant:


To see why this extension failed to compile, please check the mkmf.log which 
can be found here:

  
/home/mastodon/live/vendor/bundle/ruby/2.4.0/extensions/x86_64-linux/2.4.0-static/idn-ruby-0.1.0/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in 
/home/mastodon/live/vendor/bundle/ruby/2.4.0/gems/idn-ruby-0.1.0 for inspection.
Results logged to 
/home/mastodon/live/vendor/bundle/ruby/2.4.0/extensions/x86_64-linux/2.4.0-static/idn-ruby-0.1.0/gem_make.out

An error occurred while installing idn-ruby (0.1.0), and Bundler cannot 
continue.
Make sure that `gem install idn-ruby -v '0.1.0'` succeeds before bundling.

In Gemfile:
  idn-ruby


le fichier (mkmf.log) :

cat  
/home/mastodon/live/vendor/bundle/ruby/2.4.0/extensions/x86_64-linux/2.4.0-static/idn-ruby-0.1.0/mkmf.log
have_library: checking for -lidn...  no

"gcc -o conftest 
-I/home/mastodon/.rbenv/versions/2.4.1/include/ruby-2.4.0/x86_64-linux 
-I/home/mastodon/.rbenv/versions/2.4.1/include/ruby-2.4.0/ruby/backward 
-I/home/mastodon/.rbenv/versions/2.4.1/include/ruby-2.4.0 -I. 
-I/home/mastodon/.rbenv/versions/2.4.1/include-O3 -fno-fast-math -ggdb3 
-Wall -Wextra -Wno-unused-parameter -Wno-parentheses -Wno-long-long 
-Wno-missing-field-initializers -Wno-tautological-compare 
-Wno-parentheses-equality -Wno-constant-logical-operand -Wno-self-assign 
-Wunused-variable -Wimplicit-int -Wpointer-arith -Wwrite-strings 
-Wdeclaration-after-statement -Wimplicit-function-declaration 
-Wdeprecated-declarations -Wno-packed-bitfield-compat 
-Wsuggest-attribute=noreturn -Wsuggest-attribute=format 
-Wimplicit-fallthrough=0 conftest.c  -L. 
-L/home/mastodon/.rbenv/versions/2.4.1/lib 
-Wl,-R/home/mastodon/.rbenv/versions/2.4.1/lib -L. 
-L/home/mastodon/.rbenv/versions/2.4.1/lib  -fstack-protector -rdynamic 
-Wl,-export-dynamic -Wl,-R/home/mastodon/.rbenv/versions/2.4.1/lib 
-L/home/mastodon/.rbenv/versions/2.4.1/lib -lruby-static  -lpthread -ldl 
-lcrypt -lm   -lc"
checked program was:
/* begin */
1: #include "ruby.h"
2: 
3: int main(int argc, char **argv)
4: {
5:   return 0;
6: }
/* end */

"gcc -o conftest 
-I/home/mastodon/.rbenv/versions/2.4.1/include/ruby-2.4.0/x86_64-linux 
-I/home/mastodon/.rbenv/versions/2.4.1/include/ruby-2.4.0/ruby/backward 
-I/home/mastodon/.rbenv/versions/2.4.1/include/ruby-2.4.0 -I. 
-I/home/mastodon/.rbenv/versions/2.4.1/include-O3 -fno-fast-math -ggdb3 
-Wall -Wextra -Wno-unused-parameter -Wno-parentheses -Wno-long-long 
-Wno-missing-field-initializers -Wno-tautological-compare 
-Wno-parentheses-equality -Wno-constant-logical-operand -Wno-self-assign 
-Wunused-variable -Wimplicit-int -Wpointer-arith -Wwrite-strings 
-Wdeclaration-after-statement -Wimplicit-function-declaration 
-Wdeprecated-declarations -Wno-packed-bitfield-compat 
-Wsuggest-attribute=noreturn -Wsuggest-attribute=format 
-Wimplicit-fallthrough=0 conftest.c  -L. 
-L/home/mastodon/.rbenv/versions/2.4.1/lib 
-Wl,-R/home/mastodon/.rbenv/versions/2.4.1/lib -L. 
-L/home/mastodon/.rbenv/versions/2.4.1/lib  -fstack-protector -rdynamic 
-Wl,-export-dynamic -Wl,-R/home/mastodon/.rbenv/versions/2.4.1/lib 
-L/home/mastodon/.rbenv/versions/2.4.1/lib -lruby-static -lidn  -lpthread -ldl 
-lcrypt -lm   -lc"
/usr/bin/ld : ne peut trouver -lidn
collect2: error: ld returned 1 exit status
checked program was:
/* begin */
 1: #include "ruby.h"
 2: 
 3: /*top*/
 4: extern int t(void);
 5: int main(int argc, char **argv)
 6: {
 7:   if (argc > 100) {
 8: printf("%p", );
 9:   }
10: 
11:   return 0;
12: }
13: 
14: int t(void) { ; return 0; }
/* end */




comment finir en beauté ?

slt
bernard

Re: Free TCP/IP port numbers?

[shawn wilson]

The answer is correct - IANA maintains the list of ports. You may also look
at the services file nmap maintains or ask showdan what it's seen publicly
if you want a public popularity contest of ports.

As it is, I'm pretty sure you're over engineering this. Have a config file
that has a port range option and be done with it. Also, you didn't mention
needing <1024 so pick a port and be done with it (what everyone else does).

Lastly, certain ports are so old, their intended services shouldn't be
online anymore (see the first 20 ports or 90-110 - off the top of my head -
not sitting here and going through them) or if the service probably won't
be used in ICS or on a box designed to be an internet backbone, use one of
those.

On Sep 30, 2017 21:50, "Victor Porton"  wrote:

> Alexander V. Makartsev wrote:
>
> > There is official list of all registered port numbers:
> > https://www.iana.org/assignments/service-names-
> port-numbers/service-names-port-numbers.txt
> >
> > You can choose any port that is not in the list, to be sure they won't
> > clash.
>
> The list of port numbers you pointed to me is a subset (or at least not a
> superset) of the full list used by Debian packages.
>
> Assuring that my port is not in this IANA list is not enough to ensure that
> my port number will not clash with a port number used by a Debian package
> (by default).
>
> So your answer to my question is wrong.
>
> > On 01.10.2017 06:04, Victor Porton wrote:
> >> We are going to install a range of software on a Debian Linux
> >> installation. Because we run the same software (such as Celery) several
> >> times, we need to use port numbers different than the standard Debian
> >> port numbers chosen by default (because we can't run more than one
> >> instance of a server with the same port, and thus using the standard
> port
> >> number for all servers would fail).
> >>
> >> How to choose TCP/IP port numbers for server software we run in such a
> >> way that they don't clash with "standard" Debian port numbers?
> >>
> >> In Debian are there any ranges of port numbers dedicated (so that they
> >> wouldn't clash with "standard" that is used by default port numbers) for
> >> servers configured by users?
> >>
> >> Note that we run (at least some of) our software not as root, so we
> can't
> >> use ports below 1024.
>
> --
> Victor Porton - http://portonvictor.org
>
>

Re: Free TCP/IP port numbers?

[Alexander V. Makartsev]

Ok, I will not waste my time to argue over obvious things.
You won't get ports more "default" than from this list. Protocols, ports
and service names are registered for a reason.
Ex: If you install MySQL server it will be configured to listen on port
3306\tcp by default on any OS, be it Debian, RHEL, or Windows.



On 01.10.2017 06:40, Victor Porton wrote:
> Alexander V. Makartsev wrote:
>
>> There is official list of all registered port numbers:
>> https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
>>
>> You can choose any port that is not in the list, to be sure they won't
>> clash.
> The list of port numbers you pointed to me is a subset (or at least not a 
> superset) of the full list used by Debian packages.
>
> Assuring that my port is not in this IANA list is not enough to ensure that 
> my port number will not clash with a port number used by a Debian package 
> (by default).
>
> So your answer to my question is wrong.
>
>> On 01.10.2017 06:04, Victor Porton wrote:
>>> We are going to install a range of software on a Debian Linux
>>> installation. Because we run the same software (such as Celery) several
>>> times, we need to use port numbers different than the standard Debian
>>> port numbers chosen by default (because we can't run more than one
>>> instance of a server with the same port, and thus using the standard port
>>> number for all servers would fail).
>>>
>>> How to choose TCP/IP port numbers for server software we run in such a
>>> way that they don't clash with "standard" Debian port numbers?
>>>
>>> In Debian are there any ranges of port numbers dedicated (so that they
>>> wouldn't clash with "standard" that is used by default port numbers) for
>>> servers configured by users?
>>>
>>> Note that we run (at least some of) our software not as root, so we can't
>>> use ports below 1024.

Re: ralentissement ssh -X

[Pierre Meurisse]

On Mon, Aug 28, 2017 at 09:33:39AM +0200, Thierry Despeyroux wrote:
> Bonjour,
> 
> j'avais l'habitude dans les versions précédentes de Debian de me
> connecter par ssh -X à mon portable pro depuis ma station perso, et tout
> marchait nikel. Sauf pour les videos dans firefox, je ne remarquais
> aucun ralentissement notable par rapport à aller directement sur
> l'écran du portable.
> 
> Depuis que je suis passé à Debian 9 (sur les 2 machines) le
> ralentissement est devenu insupportable...
> 
> Avez-vous une idée du côté où il faut que je regarde ?
> 

Tu peux essayer ssh -CX qui compresse les données avant de les envoyer.


-- 
Pierre Meurisse

Re: Free TCP/IP port numbers?

[Victor Porton]

Alexander V. Makartsev wrote:

> There is official list of all registered port numbers:
> https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
> 
> You can choose any port that is not in the list, to be sure they won't
> clash.

The list of port numbers you pointed to me is a subset (or at least not a 
superset) of the full list used by Debian packages.

Assuring that my port is not in this IANA list is not enough to ensure that 
my port number will not clash with a port number used by a Debian package 
(by default).

So your answer to my question is wrong.

> On 01.10.2017 06:04, Victor Porton wrote:
>> We are going to install a range of software on a Debian Linux
>> installation. Because we run the same software (such as Celery) several
>> times, we need to use port numbers different than the standard Debian
>> port numbers chosen by default (because we can't run more than one
>> instance of a server with the same port, and thus using the standard port
>> number for all servers would fail).
>>
>> How to choose TCP/IP port numbers for server software we run in such a
>> way that they don't clash with "standard" Debian port numbers?
>>
>> In Debian are there any ranges of port numbers dedicated (so that they
>> wouldn't clash with "standard" that is used by default port numbers) for
>> servers configured by users?
>>
>> Note that we run (at least some of) our software not as root, so we can't
>> use ports below 1024.

-- 
Victor Porton - http://portonvictor.org

Re: Supper slow USB disk

[Mostafa Shahverdy]

> It seems pretty clearly to be operating at USB 2 speed. Are there any
> error messages in your dmesg output?

​I couldn't find any errors in my dmesg log, as I'm sending it as an
attachment. ​


> Can you quantify the performance

​Using my own system, it copies at most 200kps while using a live cd it
copies up to 4Mps

​
[0.00] microcode: microcode updated early to revision 0x60f, date = 
2010-09-29
[0.00] Linux version 4.12.0-2-amd64 (debian-ker...@lists.debian.org) 
(gcc version 6.4.0 20170915 (Debian 6.4.0-6) ) #1 SMP Debian 4.12.13-1 
(2017-09-19)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.0-2-amd64 
root=UUID=c4ab4daf-0aff-4dd5-a4a1-e9098803f0a6 ro quiet
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009fbff] usable
[0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xdff7] usable
[0.00] BIOS-e820: [mem 0xdff8-0xdff8dfff] ACPI data
[0.00] BIOS-e820: [mem 0xdff8e000-0xdffc] ACPI NVS
[0.00] BIOS-e820: [mem 0xdffd-0xdfff] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xfff0-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00011fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.5 present.
[0.00] DMI: System manufacturer System Product Name/P5QL-ASUS-SE, BIOS 
040210/09/2008
[0.00] tsc: Fast TSC calibration using PIT
[0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x12 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR fixed ranges enabled:
[0.00]   0-9 write-back
[0.00]   A-B uncachable
[0.00]   C-D3FFF write-protect
[0.00]   D4000-D uncachable
[0.00]   E-E write-through
[0.00]   F-F write-protect
[0.00] MTRR variable ranges enabled:
[0.00]   0 base 0 mask F write-back
[0.00]   1 base 1 mask FE000 write-back
[0.00]   2 base 0E000 mask FE000 uncachable
[0.00]   3 disabled
[0.00]   4 disabled
[0.00]   5 disabled
[0.00]   6 disabled
[0.00]   7 disabled
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: update [mem 0xe000-0x] usable ==> reserved
[0.00] e820: last_pfn = 0xdff80 max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at 
[905bc00ff780]
[0.00] Base memory trampoline at [905bc0099000] 99000 size 24576
[0.00] BRK [0x3b954000, 0x3b954fff] PGTABLE
[0.00] BRK [0x3b955000, 0x3b955fff] PGTABLE
[0.00] BRK [0x3b956000, 0x3b956fff] PGTABLE
[0.00] BRK [0x3b957000, 0x3b957fff] PGTABLE
[0.00] BRK [0x3b958000, 0x3b958fff] PGTABLE
[0.00] RAMDISK: [mem 0x35479000-0x36a33fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000FB800 14 (v00 ACPIAM)
[0.00] ACPI: RSDT 0xDFF8 3C (v01 A_M_I_ OEMRSDT  
1809 MSFT 0097)
[0.00] ACPI: FACP 0xDFF80200 84 (v02 A_M_I_ OEMFACP  
1809 MSFT 0097)
[0.00] ACPI: DSDT 0xDFF80440 006941 (v01 A1099  A1099000 
 INTL 20051117)
[0.00] ACPI: FACS 0xDFF8E000 40
[0.00] ACPI: APIC 0xDFF80390 6C (v01 A_M_I_ OEMAPIC  
1809 MSFT 0097)
[0.00] ACPI: MCFG 0xDFF80400 3C (v01 A_M_I_ OEMMCFG  
1809 MSFT 0097)
[0.00] ACPI: OEMB 0xDFF8E040 89 (v01 A_M_I_ AMI_OEM  
1809 MSFT 0097)
[0.00] ACPI: HPET 0xDFF86D90 38 (v01 A_M_I_ OEMHPET  
1809 MSFT 0097)
[0.00] ACPI: SSDT 0xDFF8EBA0 000A7C (v01 DpgPmm CpuPm
0012 INTL 20051117)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] No NUMA configuration found
[0.00] Faking a node at [mem 0x-0x00011fff]
[0.00] NODE_DATA(0) allocated [mem 0x11fff7000-0x11fffbfff]
[0.00] Zone ranges:
[0.00]   DMA  [mem 0x1000-0x00ff]
[0.00]   DMA32[mem 0x0100-0x]
[0.00]   Normal   [mem 0x0001-0x00011fff]
[0.00]   Device   empty
[0.00] Movable zone start for each node
[0.00] Early memory node 

Re: Free TCP/IP port numbers?

[Alexander V. Makartsev]

There is official list of all registered port numbers:
https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt

You can choose any port that is not in the list, to be sure they won't
clash.


On 01.10.2017 06:04, Victor Porton wrote:
> We are going to install a range of software on a Debian Linux installation. 
> Because we run the same software (such as Celery) several times, we need to 
> use port numbers different than the standard Debian port numbers chosen by 
> default (because we can't run more than one instance of a server with the 
> same port, and thus using the standard port number for all servers would 
> fail).
>
> How to choose TCP/IP port numbers for server software we run in such a way 
> that they don't clash with "standard" Debian port numbers?
>
> In Debian are there any ranges of port numbers dedicated (so that they 
> wouldn't clash with "standard" that is used by default port numbers) for 
> servers configured by users?
>
> Note that we run (at least some of) our software not as root, so we can't 
> use ports below 1024.
>

Free TCP/IP port numbers?

[Victor Porton]

We are going to install a range of software on a Debian Linux installation. 
Because we run the same software (such as Celery) several times, we need to 
use port numbers different than the standard Debian port numbers chosen by 
default (because we can't run more than one instance of a server with the 
same port, and thus using the standard port number for all servers would 
fail).

How to choose TCP/IP port numbers for server software we run in such a way 
that they don't clash with "standard" Debian port numbers?

In Debian are there any ranges of port numbers dedicated (so that they 
wouldn't clash with "standard" that is used by default port numbers) for 
servers configured by users?

Note that we run (at least some of) our software not as root, so we can't 
use ports below 1024.

-- 
Victor Porton - http://portonvictor.org

Nettoyage du spam : septembre 2017

[jean-pierre giraud]

Bonjour,
Comme nous sommes en octobre, il est désormais possible de
traiter les archives du mois de septembre 2017 des listes francophones.

N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs
pour que nous sachions où nous en sommes.

Détails du processus de nettoyage du spam sur :

https://wiki.debian.org/I18n/FrenchSpamClean

Re: origem do logo Debian - Ian

[Helio Loureiro]

Se foi suicidio, assassinato ou unha encravada, isso muda alguma coisa?
Ele morreu e o software livre perdeu uma grande força, uma personalidade
ímpar.

Que ele seja inspiração para muitos mais quanto ao software livre e
liberdade.

./helio

-= sent via Android =-

On Sep 30, 2017 16:47, "Gilberto F da Silva"  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, Sep 26, 2017 at 05:54:45PM +0200, Helio Loureiro wrote:
> > http://helio.loureiro.eng.br/index.php/debian/269-sabia-
> que-o-logo-do-debian-podia-ter-sido-uma-formiga
> >
> > O logo do Debian era um piguim estilizado que eu particularmente gostava.
> > A proposta de mudança do logo foi pelo motivo de ter se tornado uma
> distro
> > mais GNU que Linux, podendo rodar Hurd e kFreeBSD.  Nessa época o
> Stallman
> > tinha prazer de dizer que Debian era a única distro realmente GNU.
> >
> > Por ironia, a maior parte do trabalho feito no Debian pra tornar o
> sistema
> > desacoplado entre binários, bibliotecas e kernel foi o que possibilitou
> > rodar Linux sem GNU depois.  Por mais ironia ainda, com systemd o Debian
> > matou Hurd e kFreeBSD, que não tem cgroups pra rodar com o mesmo.  Ian
> deve
> > ter se revirado no túmulo quando escolheram o systemd.
>
>
>   Nessa lista foi notificada a morte do criador do Debian.  Mas não
>   fiquei sabendo  de mais coisas.  Se foi suicídio ou o que a causa
>   morte.
>
> - --
>
> Gilberto F da Silva - gfs1...@gmx.net - ICQ 136.782.571
> Stela dato:2.458.027,113  Loka tempo:2017-09-30 11:43:32 Sabato
> - -==-
> A terra há de comer - já que eu não comi
> -- Falcão
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iEYEARECAAYFAlnPrnEACgkQJxugWtMhGw51xACfXQZrIMRrWIpG4ijez1RPXUV6
> jzYAn2/vz9Xz4mVWr9svQdqacCoHHrv1
> =EQPb
> -END PGP SIGNATURE-
>

Re: conflit entre init et unbound

[François TOURDE]

Le 17439ième jour après Epoch,
Ph. Gras écrivait:

> Salut,
>
>> Le 09/30/17 à 18:06, bernard.schoenac...@free.fr a écrit :
>>> bonjour,
>>> 
>>> comment faire pour débloquer la situation afin que unbound puisse prendre
>>> la main sur le port 53 ?
>>> 
>>> netstat -antp | grep :53
>>> |
>>> tcp0  0 127.0.2.1:530.0.0.0:*   LISTEN  
>>> 1/init 
>>> 
>>> merci pour vos lumières
>>> 
>>> slt
>>> bernard
>>> 
>> 
>> Euh pour quelle mauvaise raison init écouterait sur 53/tcp
>> Voire même écoute sur le réseau ?
>> 
>
> C'est quoi init ?

L'origine du monde. C'est le premier process lancé en userspace par le
noyau. Et c'est lui qui lance tout le reste.

Du coup, init est père de tous les process et c'est lui qui récupère au
final un process dont la parenté se serait cassé la figure.

De là à récupérer les fichiers/tubes/ports qui seraient laissés à
l'abandon, il n'y a qu'un pas, hein?

Re: virtualbox - missing packages

[Patrick Bartek]

On Sat, 30 Sep 2017 07:33:50 +0200 Tamas Hegedus 
wrote:

> Hi,
> 
> A few weeks ago I could install virtualbox on stretch w/o any problem.
> Now I try to install on a different computer and have the broken 
> packages error shown below.
> 
> At the same time I have installed:
> i   libssl1.0.2   -
> Secure Sockets Layer toolkit - shared libraries
> i   libssl1.1 -
> Secure Sockets Layer toolkit - shared libraries
> 
> I also installed vpx-tools
> 
> I also have
> 
> i   linux-image-amd64 - Linux 
> for 64-bit PCs (meta-package)
> 
> What can I do?
> Thanks a lot for your help in advance.
> 
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'virtualbox-5.1' instead of 'virtualbox'
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   virtualbox-5.1 : Depends: libssl1.0.0 (>= 1.0.0) but it is not
> installable Depends: libvpx3 (>= 1.5.0) but it is not installable
>Recommends: linux-image but it is not installable
> E: Unable to correct problems, you have held broken packages.
> 

I got similar errors last week or so after upgrading to Virtualbox
5.1.28 from 5.1.22 on my Wheezy 64-bit host.  None of my VMs would run
either. Turned out it was due to a mismatched VirtualBox Extension
Pack.  The new one (5.1.28) was downloaded, but not installed.  I was
still running 5.1.22.  I manually installed .28 and all is working.  I
also checked I had the correct matching Guest Additions installed,
too.

NOTE:  I use ONLY the VB versions from the VirtualBox repo.  NOT the
versions from the Debian repos or backports.

B

Re: Supper slow USB disk

[Michael Stone]

On Sat, Sep 30, 2017 at 08:49:27PM +0330, Mostafa Shahverdy wrote:

I have an issue with the speed of my USB3 Trancend disk, while I am using my 
motherboard with USB2 ports (and also
some usb1 ports). It seems it is using usb1 driver for my usb disk, and

[...]

/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
   |__ Port 4: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M


It seems pretty clearly to be operating at USB 2 speed. Are there any 
error messages in your dmesg output? Can you quantify the performance?


Mike Stone

Re: lynis & adding hidepid to /proc?

[Dan Ritter]

On Sat, Sep 30, 2017 at 04:53:23PM -, miz...@elude.in wrote:
> selinux & grc do that automatically.
> lynis give 'suggestion' & tweaking without know what you do , break the
> security/anonymity/privacy.

Lynis is a security auditing tool. Are you complaining about
Debian's default policy, or about Lynis not being sufficiently
clear?

-dsr-

Supper slow USB disk

[Mostafa Shahverdy]

Hi everyone

I have an issue with the speed of my USB3 Trancend disk, while I am using my 
motherboard with USB2 ports (and also
some usb1 ports). It seems it is using usb1 driver for my usb disk, and
because of that, I am expericing a very slow speed. I have to mention
that using an Ubuntu live CD I can have the normal speed. Any kind of
help would be really appreciated.


here is the output of my `lsusb`:

Bus 004 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n 
Wireless Network Adapter
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 8564:1000 Transcend Information, Inc. JetFlash
Bus 003 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 24ae:2000  
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


here is the output of my `lsbusb -t`:

/:  Bus 08.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 2: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8188eu, 480M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 4: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M

and this is the output of `lsmod | grep hci`:

ehci_pci   16384  0
uhci_hcd   45056  0
ehci_hcd   81920  1 ehci_pci
usbcore   245760  7 
usbhid,usb_storage,ehci_hcd,uhci_hcd,uas,8188eu,ehci_pci

-- 
Regards,
Mostafa Shahverdy 


signature.asc
Description: PGP signature

lynis & adding hidepid to /proc?

[mizett]

selinux & grc do that automatically.
lynis give 'suggestion' & tweaking without know what you do , break the
security/anonymity/privacy.

Re: conflit entre init et unbound

[Ph. Gras]

Salut,

> Le 09/30/17 à 18:06, bernard.schoenac...@free.fr a écrit :
>> bonjour,
>> 
>> comment faire pour débloquer la situation afin que unbound puisse prendre
>> la main sur le port 53 ?
>> 
>> netstat -antp | grep :53 
>>|
>> tcp0  0 127.0.2.1:530.0.0.0:*   LISTEN   
>>1/init 
>> 
>> merci pour vos lumières
>> 
>> slt
>> bernard
>> 
> 
> Euh pour quelle mauvaise raison init écouterait sur 53/tcp
> Voire même écoute sur le réseau ?
> 

C'est quoi init ?

Ph. Gras

Re: conflit entre init et unbound

[Erwan David]

Le 09/30/17 à 18:06, bernard.schoenac...@free.fr a écrit :
> bonjour,
> 
> comment faire pour débloquer la situation afin que unbound puisse prendre
> la main sur le port 53 ?
> 
> netstat -antp | grep :53  
>   |
> tcp0  0 127.0.2.1:530.0.0.0:*   LISTEN
>   1/init 
> 
> merci pour vos lumières
> 
> slt
> bernard
> 

Euh pour quelle mauvaise raison init écouterait sur 53/tcp
Voire même écoute sur le réseau ?

conflit entre init et unbound

[bernard . schoenacker]

bonjour,

comment faire pour débloquer la situation afin que unbound puisse prendre
la main sur le port 53 ?

netstat -antp | grep :53
|
tcp0  0 127.0.2.1:530.0.0.0:*   LISTEN  
1/init 

merci pour vos lumières

slt
bernard

Re: virtualbox - missing packages

[Tamas Hegedus]

Hi,

Thanks all the feed-backs, they helped in solving the problem.
A few weeks ago, when my virtualbox install was successful, it was an 
upgrade and not fresh debian 9 install.


Actually, finally I ended up to download the deb from virtualbox.org and 
it worked. However, it was only the install, I can not test it in the 
next days, since it is on a remote computer.


Thanks,
Tamas

On 09/30/2017 07:33 AM, Tamas Hegedus wrote:

Hi,

A few weeks ago I could install virtualbox on stretch w/o any problem.
Now I try to install on a different computer and have the broken
packages error shown below.

At the same time I have installed:
i   libssl1.0.2   - Secure
Sockets Layer toolkit - shared libraries
i   libssl1.1 - Secure
Sockets Layer toolkit - shared libraries

I also installed vpx-tools

I also have

i   linux-image-amd64 - Linux
for 64-bit PCs (meta-package)

What can I do?
Thanks a lot for your help in advance.

Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'virtualbox-5.1' instead of 'virtualbox'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 virtualbox-5.1 : Depends: libssl1.0.0 (>= 1.0.0) but it is not installable
  Depends: libvpx3 (>= 1.5.0) but it is not installable
  Recommends: linux-image but it is not installable
E: Unable to correct problems, you have held broken packages.

Re: System hardening: adding hidepid to /proc?

[Reco]

Hi.

On Thu, Sep 28, 2017 at 10:22:10AM +0200, Brent Clark wrote:
> Good day Guys
> 
> I came across this document:
> 
> https://linux-audit.com/linux-system-hardening-adding-hidepid-to-proc/
> 
> The idea is to increase security by hiding the display of running
> processes, and their arguments, which belong to other users. This helps
> avoid problems if users enter passwords on the command-line, and similar.
> 
> Its suggesting mount /proc with the option hidepid=2.
> 
> I would like to ask:
> 
> 1) is it safe?

Did not prevent boot for me (stretch, amd64, sysvinit).
Which means even if it breaks something - it should be possible to fix
without resorting to LiveCD booting and/or having console access.


> 2) did you incur any issues?

Nothing that catched my eye.


> 3) what are your thoughts

If that measure is your only defence against users that "enter passwords
on the commandline" (meaning actually that said users pass
usernames/passwords as commandline arguments so they are visible via
ps(1)) - you're doing it wrong as it's those commandline tools are
broken, not OS itself.
One should not tweak OS in such radical way without attempting to fix
those tools first. Or educating users. Or both.


> The security audit tool, Lynis, also checks to see if /proc is mounted
> hidepid?

I'm not familiar with this tool. Yet another thing I should research
once I have free time.

Reco

Re: origem do logo Debian - Ian

[Gilberto F da Silva]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Sep 26, 2017 at 05:54:45PM +0200, Helio Loureiro wrote:
> http://helio.loureiro.eng.br/index.php/debian/269-sabia-que-o-logo-do-debian-podia-ter-sido-uma-formiga
> 
> O logo do Debian era um piguim estilizado que eu particularmente gostava.
> A proposta de mudança do logo foi pelo motivo de ter se tornado uma distro
> mais GNU que Linux, podendo rodar Hurd e kFreeBSD.  Nessa época o Stallman
> tinha prazer de dizer que Debian era a única distro realmente GNU.
> 
> Por ironia, a maior parte do trabalho feito no Debian pra tornar o sistema
> desacoplado entre binários, bibliotecas e kernel foi o que possibilitou
> rodar Linux sem GNU depois.  Por mais ironia ainda, com systemd o Debian
> matou Hurd e kFreeBSD, que não tem cgroups pra rodar com o mesmo.  Ian deve
> ter se revirado no túmulo quando escolheram o systemd.  


  Nessa lista foi notificada a morte do criador do Debian.  Mas não
  fiquei sabendo  de mais coisas.  Se foi suicídio ou o que a causa
  morte.  

- -- 

Gilberto F da Silva - gfs1...@gmx.net - ICQ 136.782.571
Stela dato:2.458.027,113  Loka tempo:2017-09-30 11:43:32 Sabato   
- -==-
A terra há de comer - já que eu não comi 
-- Falcão
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlnPrnEACgkQJxugWtMhGw51xACfXQZrIMRrWIpG4ijez1RPXUV6
jzYAn2/vz9Xz4mVWr9svQdqacCoHHrv1
=EQPb
-END PGP SIGNATURE-

Re: Restore backup to KVM

[Reco]

Hi.

On Sat, Sep 30, 2017 at 03:42:03PM +0200, solitone wrote:
> This is serious hacking :^)

That's what they paying me for at office ☺.


> On 30/09/17 13:04, Reco wrote:
> > the next thing I have to suspect is that your backup misses
> > /dev directory (possibly /proc and /sys). The contents for those are
> > irrelevant. You simply do not have /dev, /proc, /sys in your root
> > filesystem.
> 
> No, I don't, you're perfectly right! Now I've made /dev, /proc, /sys, as
> well as /run and now it boots right.
> 
> I still have several error messages complaining about the floppy disk (?),

QEMU emulates floppy drive by default. Empty one, that is (unless you
pass -fda option to QEMU).
Initrd merely probes the drive (which means you have "floppy" module
inside initrd), the drive says "I have no floppy". Annoying, but harmless.

Reco

Re: Re : origem do logo Debian

[Gilberto F da Silva]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Sep 28, 2017 at 10:37:19AM +0200, Helio Loureiro wrote:
> Na verdade não são distro livres.  Elas usam o linux-libre que é um patch
> em cima do linux que bloqueia o uso de firmware proprietário.  Cercear a
> escolha do usuário não é liberdade.  O Debian por padrão vai sem firmwares
> e sem o repositório non-free.  Dá ao usuário a liberdade de escolha.
> 
> Essa bolsonoragem da FSF de enfiar liberdade - segundo ela - goela abaixo é
> algo novo.  Eu particularmente acho deplorável e fiz uma reclamação a ela
> sobre isso.  Eles respoderam que é recomendação, não obrigação.  Ainda
> assim achei que Debian merecia estar ali.

  O ideal de ser tudo livre é até legal. Quando você vai comprar um
  notebook existe uma meia dúzia de marcas.  Não há muito o que fazer
  em relação ao firmware.  
 
- -- 

Gilberto F da Silva - gfs1...@gmx.net - ICQ 136.782.571
Stela dato:2.458.027,094  Loka tempo:2017-09-30 11:15:41 Sabato   
- -==-
Quem se gaba de cagar cheiroso nunca peida em público.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlnPqFoACgkQJxugWtMhGw5hOQCfRqEPncsa1HBVDScldd5vcCNL
xnsAn3qT+5p73uGRrHJ8KOUUnht7D+Ji
=r228
-END PGP SIGNATURE-

Re: Restore backup to KVM

[solitone]

This is serious hacking :^)

On 30/09/17 13:04, Reco wrote:

the next thing I have to suspect is that your backup misses
/dev directory (possibly /proc and /sys). The contents for those are
irrelevant. You simply do not have /dev, /proc, /sys in your root
filesystem.


No, I don't, you're perfectly right! Now I've made /dev, /proc, /sys, as 
well as /run and now it boots right.


I still have several error messages complaining about the floppy disk 
(?), which slow booting, but everything seems to end well. Now I'll try 
to correct grub. Thanks!


===
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top 
... done.
Begin: Running /scripts/local-premount ... [1.688631] 
blk_update_request: I/O error, dev fd0, sector 0

[1.689678] floppy: error -5 while reading block 0
[1.699913] random: fast init done
[1.760666] blk_update_request: I/O error, dev fd0, sector 0
[1.762276] floppy: error -5 while reading block 0
Begin: Waiting for suspend/resume device ... Begin: Running 
/scripts/local-block ... done.

[2.828592] blk_update_request: I/O error, dev fd0, sector 0
[2.829812] floppy: error -5 while reading block 0
[2.13] blk_update_request: I/O error, dev fd0, sector 0
[2.890727] floppy: error -5 while reading block 0
Begin: Running /scripts/local-block ... done.
[3.964558] blk_update_request: I/O error, dev fd0, sector 0
[3.966112] floppy: error -5 while reading block 0
[4.024658] blk_update_request: I/O error, dev fd0, sector 0
[4.027035] floppy: error -5 while reading block 0
[...]
Begin: Running /scripts/local-block ... done.
[   32.404669] blk_update_request: I/O error, dev fd0, sector 0
[   32.406074] floppy: error -5 while reading block 0
[   32.464656] blk_update_request: I/O error, dev fd0, sector 0
[   32.465880] floppy: error -5 while reading block 0
done.
[   32.536758] blk_update_request: I/O error, dev fd0, sector 0
[   32.539140] floppy: error -5 while reading block 0
[   32.600728] blk_update_request: I/O error, dev fd0, sector 0
[   32.603490] floppy: error -5 while reading block 0
Gave up waiting for suspend/resume device
done.
Begin: Will now check root file system ... fsck from util-linux 2.29.2
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1
/dev/sda1: clean, 434185/5898240 files, 15163985/23592711 blocks
done.
[   33.183454] EXT4-fs (sda1): mounted filesystem with ordered data 
mode. Opts: (null)

done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
root@(none):/#
===

Re: virtualbox - missing packages

[Cindy-Sue Causey]

On 9/30/17, Cindy-Sue Causey  wrote:
> On 9/30/17, Sven Hoexter  wrote:
>> On Sat, Sep 30, 2017 at 09:16:59AM +0200, Hans wrote:
>>
>>> maybe you need to add this entry in sources.list:
>>>
>>> deb http://download.virtualbox.org/virtualbox/debian stretch contrib
>>
>> Or you just use the packages from stretch-backports? Those should be the
>> best fit for now.
>> https://backports.debian.org/Instructions/
>>
>> The original error message looked a bit like OP tried to use the
>> packages from testing/unstable in stretch which actually worked for
>> some time.
>
>
> I've unfortunately lost track of my personal notes on this so I'm
> winging it. There's this option:
>
> apt-get install --fix-missing
>
> You run it generically just like that. I'm encountering references to
> something like "dpkg-reconfigure --all" and dpkg-reconfigure
> [package-name].
>
> "dpkg-reconfigure --all" that pops up in search engine inquiries
> didn't work at all *for me*. Instead, it kept suggesting other
> options.
>
> "dpkg-reconfigure [package-name]" appeared to function. Was tested on
> a normally functioning package so there wasn't much to learn from that
> beyond that it *appeared* to be the right command (because it didn't
> complain and offer alternative flags).
>
> "dpkg-reconfigure --force [package-name] is rolling around out there,
> too. Feels like I've tried that one, but it's a go at your own risk
> kind of thing. In cases like this thread, I like the sound of that
> "--force" flag. :)
>
> It feels like I'm missing one that I've even shared on this list, but
> it's not coming to mind this morning *if* there is another one.


*heh!* While closing out this thread's tab in my browser, the word
"broken" said let's try one more thing so I winged it again:

apt-get install --fix-broken

IT WORKS! I had checked "man dpkg" and "man dpkg-reconfigure" but
never thought to check "man apt-get". You might find yet more
possibilities by searching the output of "man apt-get", e.g. this one:

apt-get install --ignore-missing

I don't like that last one because it sounds like avoidance, sounds
like it's leaving a problem lingering. BUT something like that might
at least open the door to then fixing things as the NEXT step after
that one...

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

* runs with duct tape *

Re: virtualbox - missing packages

[Cindy-Sue Causey]

On 9/30/17, Sven Hoexter  wrote:
> On Sat, Sep 30, 2017 at 09:16:59AM +0200, Hans wrote:
>
>> maybe you need to add this entry in sources.list:
>>
>> deb http://download.virtualbox.org/virtualbox/debian stretch contrib
>
> Or you just use the packages from stretch-backports? Those should be the
> best fit for now.
> https://backports.debian.org/Instructions/
>
> The original error message looked a bit like OP tried to use the
> packages from testing/unstable in stretch which actually worked for
> some time.


I've unfortunately lost track of my personal notes on this so I'm
winging it. There's this option:

apt-get install --fix-missing

You run it generically just like that. I'm encountering references to
something like "dpkg-reconfigure --all" and dpkg-reconfigure
[package-name].

"dpkg-reconfigure --all" that pops up in search engine inquiries
didn't work at all *for me*. Instead, it kept suggesting other
options.

"dpkg-reconfigure [package-name]" appeared to function. Was tested on
a normally functioning package so there wasn't much to learn from that
beyond that it *appeared* to be the right command (because it didn't
complain and offer alternative flags).

"dpkg-reconfigure --force [package-name] is rolling around out there,
too. Feels like I've tried that one, but it's a go at your own risk
kind of thing. In cases like this thread, I like the sound of that
"--force" flag. :)

It feels like I'm missing one that I've even shared on this list, but
it's not coming to mind this morning *if* there is another one.

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

* runs with duct tape *

Firefox och Linuxfika / öl i Stockholm + IRC Oktober + November 2017

[Luna Jernberg]

http://linuxportalen.se/articles/2017/09/18/suse-linux-l-mozilla-fika-i-oktober-november-2017-i-stockholm#comments

SUSE Linux/OpenSuSE folket kör öl i Stockholm 3:e Oktober:
https://docs.google.com/forms/d/e/1FAIpQLSdnklyHnmbe7hq_xd03h_CJsVFRYkDKBxtthKT3j7rGTOilHw/viewform?c=0=1
http://www.suse.com http://opensuse.org

och Mozilla Sverige kör IRC möte i #mozilla.se på irc.mozilla.org
(IRC) 20:00-21:30 16:e Oktober

och i mitten av November i Stockholm är det Mozilla Firefox (57)
Quantum Mozfika 14:e November för att fira releasen av helt nya
Firefox efter 17:00 plats inte bestämmd 100% än och 15:e November är
det http://linuxpodden.nu öl och burgare på RoQ 15:e November
18:00-23:00

Alla 3/4 events är till självkostnadspris förutom SUSEs Event

Re: Can't find the DNS Servers

[Curt]

On 2017-09-30, Gary Roach  wrote:
>>
> Well the philosophy and stories are nice but my access to the internet 
> is still among the missing. I have a Debian Stretch system installed and 
> am using NetworkManager. This worked until I installed qemu virtual 
> machine over the host OS. Since then the host system does not seem able 
> to find a DNS server. The really strange thing is that I installed 
> Kubuntu as the guest OS and that works fine. I suspect that qemu has 
> glommed onto the eth0 device and won't let the host in. I have gone
> over and over the NetworkManager documentation and have found no way
> to fix this. The situation is getting critical. I need to load some
> software into the host system and can't, I also can't upgrade the
> system and can't.

You're in good hands with Reco and Hambourg, however I read that libvirt
creates iptable rules, uses dnsmasq, but actually I don't understand any
of this--had I understood something I probably would have said to turn
that stuff off to troubleshoot, if you haven't already.


> I really need some help here.
>
> Gary R
>
>


-- 
"A simpering Bambi narcissist and a thieving, fanatical Albanian dwarf."
Christopher Hitchens, commenting shortly after the nearly concurrent deaths 
of Lady Diana and Mother Theresa.

Re: Restore backup to KVM

[Reco]

Hi.

On Fri, Sep 29, 2017 at 06:30:21AM +0200, solitone wrote:
> On 28/09/17 08:58, Reco wrote:
> > It's initrd that first tries to mount tmpfs filesystems on /root (and
> > fails), and only *then* mounts your root filesystem to /root (with the
> > intention to switch to it as /).

> Also, I don't understand why it needs to mount the root filesystem to /root.

So, I did some tests. Results are somewhat unexpected.

First things first, either I'm missing something, or MODULES=most does
not work as advertised. It did not put "all harddrive drivers" into
initrd for me.

Second, once I convinced update-initramfs to put missing kernel modules
into initrd, QEMU booted successfully with "init=/bin/bash".

If I understand what's written in /usr/share/initramfs-tools/script
correctly, the way it should work is the following:

1) Unpack initrd, load kernel modules, etc.

2) Mount root filesystem to /root (and that's initrd's /root!).

3) Re-mount /dev into /root/dev (that's init-bootom/udev, and that's
where it fails for you).

4) Mount procfs, sysfs (and several others) into appropriate directories
of /root.

5) Mount everything appropriate from /etc/fstab.

6) Execute pivot_root(8) to switch root filesystem, start init.

Therefore the next thing I have to suspect is that your backup misses
/dev directory (possibly /proc and /sys). The contents for those are
irrelevant. You simply do not have /dev, /proc, /sys in your root
filesystem.

Reco

Re: virtualbox - missing packages

[Sven Hoexter]

On Sat, Sep 30, 2017 at 09:16:59AM +0200, Hans wrote:

Hi,

> maybe you need to add this entry in sources.list:
> 
> deb http://download.virtualbox.org/virtualbox/debian stretch contrib

Or you just use the packages from stretch-backports? Those should be the
best fit for now.
https://backports.debian.org/Instructions/

The original error message looked a bit like OP tried to use the
packages from testing/unstable in stretch which actually worked for
some time.

Sven

Re: virtualbox - missing packages

[Hans]

Am Samstag, 30. September 2017, 07:33:50 CEST schrieb Tamas Hegedus:
Hi,

maybe you need to add this entry in sources.list:

deb http://download.virtualbox.org/virtualbox/debian stretch contrib

See this doku:

https://wiki.debian.org/VirtualBox#Debian_9_.22Stretch.22

Hope this helps.
Good luck!

Best

Hans
> Hi,
> 
> A few weeks ago I could install virtualbox on stretch w/o any problem.
> Now I try to install on a different computer and have the broken
> packages error shown below.
> 
> At the same time I have installed:
> i   libssl1.0.2   - Secure
> Sockets Layer toolkit - shared libraries
> i   libssl1.1 - Secure
> Sockets Layer toolkit - shared libraries
> 
> I also installed vpx-tools
> 
> I also have
> 
> i   linux-image-amd64 - Linux
> for 64-bit PCs (meta-package)
> 
> What can I do?
> Thanks a lot for your help in advance.
> 
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'virtualbox-5.1' instead of 'virtualbox'
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   virtualbox-5.1 : Depends: libssl1.0.0 (>= 1.0.0) but it is not installable
> Depends: libvpx3 (>= 1.5.0) but it is not installable Recommends:
> linux-image but it is not installable E: Unable to correct problems, you
> have held broken packages.

Re: Can't find the DNS Servers

[Pascal Hambourg]

Le 30/09/2017 à 04:18, Gary Roach a écrit :


Well the philosophy and stories are nice but my access to the internet 
is still among the missing.


We are waiting for the information asked by Reco several days ago :

ip address list

ip route list

cat /etc/resolv.conf

tcpdump -nvi any udp port 53 or tcp port 53
run while doing
getent hosts www.debian.org