Re: Set resolution options without xrandr

[Ric Moore]

On 02/04/2017 11:28 PM, John Hasler wrote:

Tony writes:

In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and
edited it, but there is no such file on this system (Jessie).


Create one.


+
...and which video card do you have?? Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: upgrade failed debian 8.7

[Ric Moore]

On 02/04/2017 03:25 PM, Mike Nunn wrote:

Please don't top post. Thanx, Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: Set resolution options without xrandr

[Felix Miata]

Tony Baldwin composed on 2017-02-04 21:55 (UTC-0500):


In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and
edited it, but there is no such file on this system (Jessie).


/etc/X11/xorg.conf became an optional file many releases ago. It usually can be 
created and used to override problems with automagic configuration like you 
appear to be having.


/etc/X11/xorg.conf.d/ can also be used for the same purposes. Anything in 
/etc/X11/xorg.conf.d/ that conflicts with anything in /etc/X11/xorg.conf will 
override to the extent of conflict.



I've been trying to use xrandr, but I'm clearly missing something that
the instructions I'm finding on superuser isn't giving me.
(http://superuser.com/questions/716795/how-to-adjust-the-screen-resolution-in-debian
)


That particular URI is trying to use a sledge hammer to drive a brad. Only 
rarely are CVT or GTF heroics necessary with modern versions of Xorg and its 
video drivers. I cannot recall ever in the past decade needing CVT or GTF to 
calculate and configure a modeline. Xorg knows how to and does do that 
automatically based on EDID, or if the display has defective EDID, any 
overriding HorizSync and VertRefresh specifications along with PreferredMode 
configured section Monitor in /etc/X11/xorg.conf* for Xorg to calculate them 
automatically.



The worst thing is that it WAS on the proper resolution, then I had a
PSU go south, so powered everything (including the monitor) down, while
I went out to acquire a new PSU, and, upon rebooting after installing


It's entirely possible creating a mode with xrandr could override some sort of 
filesystem corruption that resulted from the powerdown. Have you tried forcing 
fsck on the / filesystem since the power failure was cured?



said new PSU, my screen res has gone from a beautiful 1680 x1050 to
1280x768 of some such crap, and looks awful, in my opinion.
I didn't do anything to mess with it, so have no idea why it changed.,
and now the actual default for the monitor ( the 1680 x 1050 ) appears
unavailable to xrandr


Something must have become corrupted to cause what is happening to you. Jessie 
should automatically use 1680x1050 on a display whose native resolution is 
1680x1050.


I currently have host big31 connected to a native 1680x1050 LCD booted to Jessie 
with no xrandr commands configured and no /etc/X11/xorg.conf* configured to 
affect display output, and its running TDE @1680x1050.


What follows are things you can try that should work, once you've examined 
/var/log/Xorg.0.log to determine:


A-which driver is in use
B-which video device is connected to your display

If you cannot determine these on your own by examining Xorg.0.log, post it to 
http://paste.debian.net/ so someone here can. Also post output from 'lspci -nnk 
| grep -A6 VGA', and/or 'inxi -c0 -v6 | head -n20'. Include output of 'cat 
/proc/cmdline' in your reply.


The video driver in use should not be FBDEV(0) or VESA(0). Neither support any 
widescreen modes. What you want to see are lots of lines containing intel(0), 
nouveau(0) or radeon(0), according to which gfxchip you have, or modeset(0) or 
modesetting(0) without regard to which gfxchip you have. Something you can try 
if your gfxchip is neither ancient nor newer than Jessie is forcing use of the 
modesetting driver by ensuring xserver-xorg-video-modesetting is installed, and 
purging the xserver-xorg-video-[ati,intel,nouveau] driver matching your gfxchip.


To configure your display manually:

1-create a script in /etc/X11/Xsession.d/ containing the xrandr command you wish 
applied when X starts. http://fm.no-ip.com/Share/setup contains a long list of 
xrandr commands that have worked for me with various hardware at various times; or


2-create /etc/X11/xorg.conf.
http://fm.no-ip.com/Share/Linux/xorg.conf-1680x1050x108-mini can be used as a 
starting skeleton. Comment or remove the DisplaySize line if you don't wish DPI 
forced to 108. If your gfxcard has multiple outputs, xorg.conf may require an 
uncommented line in the device section similar one of those contained in:

http://fm.no-ip.com/Share/Linux/50-device.conf , e.g.:
Option  "monitor-VGA-0"   "DefaultMonitor"
You shouldn't need to specify the driver to use, but if 1680x1050 continues to 
fail to result you can try putting one in the device section, e.g.:

'Driver "nouveau"'.
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

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

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

Re: Set resolution options without xrandr

[John Hasler]

Tony writes:
> In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and
> edited it, but there is no such file on this system (Jessie).

Create one.  
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Set resolution options without xrandr

[Tony Baldwin]

In the past, of course I'd have dug up /etc/X11/xorg.conf with vi, and 
edited it, but there is no such file on this system (Jessie).
I've been trying to use xrandr, but I'm clearly missing something that 
the instructions I'm finding on superuser isn't giving me.
(http://superuser.com/questions/716795/how-to-adjust-the-screen-resolution-in-debian 
)


The worst thing is that it WAS on the proper resolution, then I had a 
PSU go south, so powered everything (including the monitor) down, while 
I went out to acquire a new PSU, and, upon rebooting after installing 
said new PSU, my screen res has gone from a beautiful 1680 x1050 to 
1280x768 of some such crap, and looks awful, in my opinion.
I didn't do anything to mess with it, so have no idea why it changed., 
and now the actual default for the monitor ( the 1680 x 1050 ) appears 
unavailable to xrandr


Thanks in Advance,
Tony


--
http://tonybaldwin.me
all tony, all the time

Re: PROBLEMAS CON DEBIAN 8 64 BITS

[Cyril Brulebois]

Hi,

Abraham Coiman  (2017-01-26):
> Buen día
> 
> Tengo problemas con Debian 8
> 
> Lo he instalo dos veces y presenta el mismo problema
> 
> He asignado lo siguiente:
> 
> 9 Gb /
> 5 Gb /home
> 6 Gb intercambio
> 200 mb /boot
> 
> Al inicio funciona bien, pero cuando arreglo el sudo y la hora
> 
> la partición / para de 4 gb de espacio libre a 0 Gb
> 
> Todo colapsa y no funciona más

You're expected to post in English on debian-boot@; I'm adding
debian-user-spanish to cc since someone there might help.


KiBi.


signature.asc
Description: Digital signature

Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su

[Roba]

Thank you very much Gene,
You are the first person to ever mention that "the line was removed" for
security paranoia, not that I mistakenly removed it by mistake over the
past few months of it running under jessie and not running under
stretch.  This is what I wanted to find out, why did this happen.
Now it DOES make sense.

I arrest my case!

You can have the pickles I am allergic and you must have a craving for
them for mentioning them, save one for Brian!

Gene Heskett:
> 
> Do you want it fixed, or do you just want to whine about it? I don't know 
> why the paranoia over security has caused that to be removed some years 
> ago, but those of us with well isolated home networks have been putting 
> that line back in our /etc/cups/cupsd.conf for years. If you refuse to 
> do it, take your whine on down the hall where there might be some cheese  
> and maybe some pickles to go with it.
> 
>> So for me the puzzle remains, for Brian the explanation maybe I
>> sleepwalk and change things unconsciously.
> 
> 
> Cheers, Gene Heskett
> 

Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su

[Brian]

On Sat 04 Feb 2017 at 18:44:04 -0500, Gene Heskett wrote:

> On Saturday 04 February 2017 18:04:00 Roba wrote:
> 
> > Brian:
> > > On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote:
> > >> Indulge us, and add a line to your cupsd.conf as follows:
> > >>
> > >> Listen localhost:631
> > >>
> > >> and restart CUPS and see what happens.
> > >
> > > It would solve his problem.
> > >
> > > There is nothing in the postinst script for cups which would replace
> > > a "Listen localhost:631" line. Easily tested with
> > >
> > >  apt-get --reinstall install cups
> >
> > Are you repeatedly denying what I have repeatedly said or is it that
> > you just don't know and can't guess?  For the rest of the people
> > following the thread I can assure you that neither I or has there been
> > anybody "physically" that has touched this pc and omitted this line.
> > I have no idea whether the update from jessie to stretch would replace
> > this file, I assume it is not the same as the packages are different
> > so the conf I suspect it might be different, I don't know.  That would
> > put this change within the past 2-3 weeks.
> >
> > Unless I read specific instructions form a reliable source to edit a
> > conf. file I don't go about messing with them, I know that much.
> 
> Do you want it fixed, or do you just want to whine about it? I don't know 
> why the paranoia over security has caused that to be removed some years 
> ago, but those of us with well isolated home networks have been putting 
> that line back in our /etc/cups/cupsd.conf for years. If you refuse to 
> do it, take your whine on down the hall where there might be some cheese  
> and maybe some pickles to go with it.

A problem was stated and diagnosed and a solution offered. Up to now,
the OP hasn't even had the grace to say what the solution did for him.

-- 
Brian.

Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su

[Gene Heskett]

On Saturday 04 February 2017 18:04:00 Roba wrote:

> Brian:
> > On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote:
> >> Indulge us, and add a line to your cupsd.conf as follows:
> >>
> >> Listen localhost:631
> >>
> >> and restart CUPS and see what happens.
> >
> > It would solve his problem.
> >
> > There is nothing in the postinst script for cups which would replace
> > a "Listen localhost:631" line. Easily tested with
> >
> >  apt-get --reinstall install cups
>
> Are you repeatedly denying what I have repeatedly said or is it that
> you just don't know and can't guess?  For the rest of the people
> following the thread I can assure you that neither I or has there been
> anybody "physically" that has touched this pc and omitted this line.
> I have no idea whether the update from jessie to stretch would replace
> this file, I assume it is not the same as the packages are different
> so the conf I suspect it might be different, I don't know.  That would
> put this change within the past 2-3 weeks.
>
> Unless I read specific instructions form a reliable source to edit a
> conf. file I don't go about messing with them, I know that much.

Do you want it fixed, or do you just want to whine about it? I don't know 
why the paranoia over security has caused that to be removed some years 
ago, but those of us with well isolated home networks have been putting 
that line back in our /etc/cups/cupsd.conf for years. If you refuse to 
do it, take your whine on down the hall where there might be some cheese  
and maybe some pickles to go with it.

> So for me the puzzle remains, for Brian the explanation maybe I
> sleepwalk and change things unconsciously.


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

Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su

[Roba]

Brian:
> On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote:

>> Indulge us, and add a line to your cupsd.conf as follows:
>>
>> Listen localhost:631
>>
>> and restart CUPS and see what happens.
>
> It would solve his problem.
>
> There is nothing in the postinst script for cups which would replace a
> "Listen localhost:631" line. Easily tested with
>
>  apt-get --reinstall install cups

Are you repeatedly denying what I have repeatedly said or is it that you
just don't know and can't guess?  For the rest of the people following
the thread I can assure you that neither I or has there been anybody
"physically" that has touched this pc and omitted this line.
I have no idea whether the update from jessie to stretch would replace
this file, I assume it is not the same as the packages are different so
the conf I suspect it might be different, I don't know.  That would put
this change within the past 2-3 weeks.

Unless I read specific instructions form a reliable source to edit a
conf. file I don't go about messing with them, I know that much.

So for me the puzzle remains, for Brian the explanation maybe I
sleepwalk and change things unconsciously.

Re: [OFF] Filosofia e TI

[Jack Jr.]

As questões filosóficas existem independentes de serem estudadas 
formalmente.


Em 04-02-2017 20:03, Rodolfo escreveu:
A epistemologia está ligada ao conhecimento científico, e não em 
questões abstratas do que é e do que não é. Para mim a importância da 
filosofia no campo científico de TI é ínfimo, pois a especificidade 
das ciências exatas são as mais necessárias visto que no trabalho da 
TI a nossa necessidade se diz ao uso do melhor conceito para atribuir 
uma melhora, o desenvolvimento e/ou inovação, uma descoberta que não 
precisa ser medida e nem comparada com outras pois a resolução do 
problema é o objetivo de todas as pesquisas nessa área. Agora é 
possível obter um resultado revolucionário com o uso da filosofia na 
nossa área? Acho que essa resposta está mais ligada a física, química 
e semelhantes do que na nossa área, pra mim à área de TI é nada mais 
do que o uso do conhecimento adquirido com as pesquisas dos conceitos 
naturais para resolver problemas especificamente de matriz auxiliar ao 
trabalho do homem. Bom, é a minha impressão sobre o tema.


Em 4 de fevereiro de 2017 17:17, Rodrigo Cunha 
> escreveu:


Não me aprofundarei no tema: O que é a filosofia para mim, pois é
massante e desgastante, envolve perguntas complexas como: "O que é
verdade" ou "O que é a realidade".

Porém, o oficio de TI, que nos traz a necessidade de estudar
linguagens, conceitos, boas praticas, etc.Me remete a um dos
campos de estudos da filosofia : a "epistemologia" ou mesmo a
filosofia analítica(filosofia da linguagem).

Dito isso, pergunto aos meus companheiros de oficio: Qual é a
importância, para vocês, da filosofia para o avanço e para a
epistemologia dentro do campo da informática ou do tratamento da
informação.Seria seu estudo mais um peso ou uma necessidade humana
frente a questão "homem x maquina".

-- 
Atenciosamente,

Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

Re: Some x-terminals do not compose unicode characters

[Jonathan Dowland]

On Fri, Feb 03, 2017 at 11:07:39AM +0100, Alessandro T. wrote:
> echo -e '1\u0336'
> 
> and with mlterm, pterm, rxvt and xterm I got, rightly, strikethrough 1.
> Instead with evilvte, gnome-terminal, lilyterm, lxterminal, sakura,
> terminator, terminix, termit, vala-terminal and xfce4-terminal (my
> default) I got 1-.
> 
> This is caused by incorrect configuration? So where should I intervene?
> Or is it a bug? So what package should I report?

Are you using the same shell in each terminal? Do you have TERM set to
something unusual by mistake?


signature.asc
Description: Digital signature

Re: [OFF] Filosofia e TI

[Rodolfo]

A epistemologia está ligada ao conhecimento científico, e não em questões
abstratas do que é e do que não é. Para mim a importância da filosofia no
campo científico de TI é ínfimo, pois a especificidade das ciências exatas
são as mais necessárias visto que no trabalho da TI a nossa necessidade se
diz ao uso do melhor conceito para atribuir uma melhora, o desenvolvimento
e/ou inovação, uma descoberta que não precisa ser medida e nem comparada
com outras pois a resolução do problema é o objetivo de todas as pesquisas
nessa área. Agora é possível obter um resultado revolucionário com o uso da
filosofia na nossa área? Acho que essa resposta está mais ligada a física,
química e semelhantes do que na nossa área, pra mim à área de TI é nada
mais do que o uso do conhecimento adquirido com as pesquisas dos conceitos
naturais para resolver problemas especificamente de matriz auxiliar ao
trabalho do homem. Bom, é a minha impressão sobre o tema.

Em 4 de fevereiro de 2017 17:17, Rodrigo Cunha 
escreveu:

> Não me aprofundarei no tema: O que é a filosofia para mim, pois é massante
> e desgastante, envolve perguntas complexas como: "O que é verdade" ou "O
> que é a realidade".
>
> Porém, o oficio de TI, que nos traz a necessidade de estudar linguagens,
> conceitos, boas praticas, etc.Me remete a um dos campos de estudos da
> filosofia : a "epistemologia" ou mesmo a filosofia analítica(filosofia da
> linguagem).
>
> Dito isso, pergunto aos meus companheiros de oficio: Qual é a importância,
> para vocês, da filosofia para o avanço e para a epistemologia dentro do
> campo da informática ou do tratamento da informação.Seria seu estudo mais
> um peso ou uma necessidade humana frente a questão "homem x maquina".
>
> --
> Atenciosamente,
> Rodrigo da Silva Cunha
> São Gonçalo, RJ - Brasil
>
>

Ass: Re: Fails a l'arrancar un Debian Jessie 64 bits

[danielal...@mailcat.cat]

L'error està al mail, no al bootlog.d. Ho he de mirar amb més calma;  alguna de 
les suggerències que he trobat per internet no m'han funcionat.De totes 
maneres, gràcies.
Enviat des del meu mòbil LG
-- Missatge original--De:Josep LladonosaData:ds., 4 febr. 2017 20:07Per 
a: Daniel;Cc: debian usuaris en CATALA;Assumpte:Re: Re: Fails a l'arrancar un 
Debian Jessie 64 bits


2017-02-04 17:57 GMT+01:00 Daniel :
  Resolt gairebé tot: 

El Failed to start load Kernel modules s'ha resolt instalant elkernel 
que no sé perquè no estava instalat. 

  Els problemes amb l'array s'han resolt amb:
  
   mdadm --manage /dev/md[XXX] --add /dev/sdc[X]. 
  
  Efectivament, els discos estaven connectats, i el que no sabré mai  
és perquè un dels dos discos de l'array s'ha "desconnectat"  -status 
removed-, i quan ho ha fet. Hauré de vigilar que no torni  a passar.
  
  Falta aclarir:
  
  Invalid PBLK length
  
  I perquè no funciona el log d'inici (/var/log/boot). L'he activat  al 
/etc/default/bootlog.d (BOOTLODG_ENABLED=yes) però no hi ha  manera. 


Que no sigui perquè hagi de ser  (BOOTLOGD_ENABLE=yes).
   
  
  
  
   Missatge reenviat 
Assumpte:Re: Fails a l'arrancar un Debian Jessie 64 
bitsReenviat-Data:Thu, 
2 Feb 2017 10:58:54 + (UTC)Reenviat-De: 
   debian-user-catalan@lists.debian.org 
   Data: Thu, 2 Feb 2017 11:57:32 +0100 
   De: Daniel  
   A: debian usuaris en CATALA  
  
  
He trobat el fitxer /etc/modules-load,d/modules.conf. No hi ha cap  
línia activa:
  
  daniel@Daniel-Debian:/etc/modules-load.d$  pg modules.conf
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that  should 
be loaded
# at boot time, one per line. Lines beginning with "#"  are 
ignored.

(EOF):
  
  
  
  
  El 02/02/17 a les 11:42, Daniel haescrit:
Hola:

Avui, mentre el sistema feia el check list a un disc, he
advertit la presència d'uns errors certament preocupants:
En primer lloc, just després d'engegar la càrrega del Debian,
apareix en pantalla:

Invalid PBLK length [7]

He estat buscant per Internet i trobo alguna cosa però no està
clara.

Després apareix dues vegades un Failed to start load Kernel
modules. Va acompanyat d'una suggerència d'execució:

root@Daniel-Debian:/home/daniel# systemctl status -l 
systemd-modules-load● systemd-modules-load.service - Load Kernel Modules   
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)   
Active: failed (Result: exit-code) since dj 2017-02-02 08:54:14 CET; 2h 21min 
ago Docs: man:systemd-modules-load.service(8)   
man:modules-load.d(5)  Process: 297 ExecStart=/lib/systemd/systemd-modules-load 
(code=exited, status=1/FAILURE) Main PID: 297 (code=exited, 
status=1/FAILURE)feb 02 08:54:14 Daniel-Debian systemd[1]: Starting Load Kernel 
Modules...feb 02 08:54:14 Daniel-Debian systemd[1]: 
systemd-modules-load.service: main process exited, code=exited, 
status=1/FAILUREfeb 02 08:54:14 Daniel-Debian systemd[1]: Failed to start Load 
Kernel Modules.feb 02 08:54:14 Daniel-Debian systemd[1]: Unit 
systemd-modules-load.service entered failed 
state.root@Daniel-Debian:/home/danielI per fi, apareix un altre fail 
absolutament terrorífic sobrel'
 array que tinc innstalat. He anat a repassar les funcions delmdadm i 
he pogut trobar el següent:


root@Daniel-Debian:/etc/mdadm#  mdadm --detail /dev/md125   
  /dev/md125:  Version : 0.90  Creation 
Time : Wed Oct 6 09:35:45  2010  Raid Level : raid1 
 Array Size : 224548416 (214.15 GiB  229.94 GB) 
 Used Dev Size : 224548416 (214.15  GiB 229.94 GB)  
Raid Devices : 2  Total Devices : 1 
Preferred Minor : 125  Persistence : Superblock is  
persistent 
   Update Time : Thu Feb 2 09:48:25  
2017  State : clean, degraded   Active Devices 
: 1 

[OFF] Filosofia e TI

[Rodrigo Cunha]

Não me aprofundarei no tema: O que é a filosofia para mim, pois é massante
e desgastante, envolve perguntas complexas como: "O que é verdade" ou "O
que é a realidade".

Porém, o oficio de TI, que nos traz a necessidade de estudar linguagens,
conceitos, boas praticas, etc.Me remete a um dos campos de estudos da
filosofia : a "epistemologia" ou mesmo a filosofia analítica(filosofia da
linguagem).

Dito isso, pergunto aos meus companheiros de oficio: Qual é a importância,
para vocês, da filosofia para o avanço e para a epistemologia dentro do
campo da informática ou do tratamento da informação.Seria seu estudo mais
um peso ou uma necessidade humana frente a questão "homem x maquina".

-- 
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

Ass: Fails a l'arrancar un Debian Jessie 64 bits

[danielal...@mailcat.cat]

El disc dona alguns errors. Podrien ser-ne la causa. Passaré el smartctl a 
veure si la cosa ha empitjorat. Gràcies.
Enviat des del meu mòbil LG
-- Missatge original--De:Alex MuntadaData:ds., 4 febr. 2017 20:52Per a: 
Daniel;Cc: Llista debian català;Assumpte:Re: Fails a l'arrancar un Debian 
Jessie 64 bits
Hola Daniel,no és gaire normal que els discos es treguin del raid sense motiu. 
Jo comprovaria amb smartctl si els discos estan bé de salut, per si de cas. 
Especialment el que havia estat eliminat del raid.
Salut,Alex

[(fwd): Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1]

[Ennio-Sr]

Hi all!
I'm forwarding to the list this message which didn't reach the original
destination. I would have to get through bugzilla to report a bug, bat
this is not a bug. Although, I think it might help some onlookers...

Regards, Ennio


- Forwarded message from ennio -


Subject: Debian/Stretch - network-manager_1.4.4-1 and libbluetooth3_5.43-1
Reply-To: Ennio-Sr 
Date: Sat, 4 Feb 2017 20:27:00 +0100
To: Debian Bluetooth Maintainers 

Cc: Utopia Maintenance Team 

Hi!
As you certainly know (and I learnt recently), in the oncoming
Debian/Stretch version, the network-manager pkg depends on libbluetooth3
so that when this package is removed network-manager will be removed as
well. 
Now, considering that - if I understand well - the Stretch default
policy will be to delete all downloaded packages once they have beeen
installed (unless you modify default), a newby could have problems to reconnect.

AAMOF it happened to me a few days ago when, while struggling to pair an
apple wireless keyboard, I removed all bluetooth related packages and
remained 'isolated' from the world. Luckily enough I had a
network-manager package in the /var/cache/apt/archives and could solve
my problem.

Of course, the deletion of network-manager is announced when you remove
libbluetooth3 but I think it should be stressed by a stronger axplicit warning,
also considering that while removing bluetooth one would not expect that
network-manager will vanish altogether and could not notice the weak
'Remv network-manager ...' amon others.

Thank you for the nice result of your work. 
Best regards,
   Ennio

- End forwarded message -

-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

Re: upgrade failed debian 8.7

[Mike Nunn]

update-initramfs pid 1373

sudo lsof -p 1373
COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
update-in 1373 root  cwdDIR9,2 4096 16515073 /root
update-in 1373 root  rtdDIR9,2 40962 /
update-in 1373 root  txtREG9,2   125400 23461891 /bin/dash
update-in 1373 root  memREG9,2  1738176 26869908
/lib/x86_64-linux-gnu/libc-2.19.so
update-in 1373 root  memREG9,2   140928 26869905
/lib/x86_64-linux-gnu/ld-2.19.so
update-in 1373 root0u   CHR  136,4  0t07 /dev/pts/4
update-in 1373 root1u   CHR  136,4  0t07 /dev/pts/4
update-in 1373 root2u   CHR  136,4  0t07 /dev/pts/4
update-in 1373 root   10r   REG9,2 8974 19546736
/usr/sbin/update-initramfs

Re: upgrade failed debian 8.7

[Mike Nunn]

df
Filesystem 1K-blocksUsed Available Use% Mounted on
/dev/md2   458453504 6569528 428572808   2% /
udev   10240   0 10240   0% /dev
tmpfs   13187516  320656  12866860   3% /run
tmpfs   32968784 504  32968280   1% /dev/shm
tmpfs   5120   0  5120   0% /run/lock
tmpfs   32968784   0  32968784   0% /sys/fs/cgroup
/dev/md1  498980   52528420267  12% /boot
tmpfs6593760   0   6593760   0% /run/user/1000
none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/bce41dd5773c817aea6e833cf53e43a1679c29e3d73c20c09ad3040bca57d573

shm65536   0 65536   0%
/var/lib/docker/containers/e9c96303b37e485c0990ac5c0b60e75009c2663b4bba9310867e73ec22c71401/shm

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/bbe023c51a117696a4cf8cf9770ca7bfdb47e79a8b65d7a733afaba6d2b15839

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/a238b58eeb33998d8adbeefa3b82d129d1cc5d9990667cafec8d818399cf6f03

shm65536   0 65536   0%
/var/lib/docker/containers/97a599c4375ce06d3df465529851f20fd6c63dae5da25221abce1e768d25a215/shm

shm65536   0 65536   0%
/var/lib/docker/containers/f839ffd572eb8d2a9e5059012227e06778bf491da83b0058c115be724f857e66/shm

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/d0fe269d720b17579a9939bfa9d64b0d1607f35140f0dfd593cc7f9f20bc7f9e

shm65536   0 65536   0%
/var/lib/docker/containers/13e5125d33b80f5a54dcaeddb078ce093b27f8fa19797359166b32be9b122a7d/shm

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/4e773bf15bc02540a2478aef0fffec0b83879712557d4985c31d0a80c3bbc498

none   458453504 6569528 428572808   2%
/var/lib/docker/aufs/mnt/91ebefd722e8aab74b1037511bdbc22ce8366b98fd4f081695116cbecd40c992

shm65536   0 65536   0%
/var/lib/docker/containers/e7f8c5eccb175562c2a7941be220790d36240f0e9e38d96311166fd25a91d368/shm

shm65536   0 65536   0%
/var/lib/docker/containers/4fff1f2b2b141846488d39aede964a2629b16f0d97913f7207841cd4ca69/shm

df -i
Filesystem   Inodes  IUsedIFree IUse% Mounted on
/dev/md2   29122560 270014 288525461% /
udev8239770310  82394601% /dev
tmpfs   8242196685  82415111% /run
tmpfs   8242196 22  82421741% /dev/shm
tmpfs   8242196  7  82421891% /run/lock
tmpfs   8242196 13  82421831% /sys/fs/cgroup
/dev/md1 131072329   1307431% /boot
tmpfs   8242196  4  82421921% /run/user/1000
none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/bce41dd5773c817aea6e833cf53e43a1679c29e3d73c20c09ad3040bca57d573

shm 8242196  1  82421951%
/var/lib/docker/containers/e9c96303b37e485c0990ac5c0b60e75009c2663b4bba9310867e73ec22c71401/shm

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/bbe023c51a117696a4cf8cf9770ca7bfdb47e79a8b65d7a733afaba6d2b15839

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/a238b58eeb33998d8adbeefa3b82d129d1cc5d9990667cafec8d818399cf6f03

shm 8242196  1  82421951%
/var/lib/docker/containers/97a599c4375ce06d3df465529851f20fd6c63dae5da25221abce1e768d25a215/shm

shm 8242196  1  82421951%
/var/lib/docker/containers/f839ffd572eb8d2a9e5059012227e06778bf491da83b0058c115be724f857e66/shm

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/d0fe269d720b17579a9939bfa9d64b0d1607f35140f0dfd593cc7f9f20bc7f9e

shm 8242196  1  82421951%
/var/lib/docker/containers/13e5125d33b80f5a54dcaeddb078ce093b27f8fa19797359166b32be9b122a7d/shm

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/4e773bf15bc02540a2478aef0fffec0b83879712557d4985c31d0a80c3bbc498

none   29122560 270014 288525461%
/var/lib/docker/aufs/mnt/91ebefd722e8aab74b1037511bdbc22ce8366b98fd4f081695116cbecd40c992

shm 8242196  1  82421951%
/var/lib/docker/containers/e7f8c5eccb175562c2a7941be220790d36240f0e9e38d96311166fd25a91d368/shm

shm 8242196  1  82421951%
/var/lib/docker/containers/4fff1f2b2b141846488d39aede964a2629b16f0d97913f7207841cd4ca69/shm

cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,relatime 0 0
udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=8239770,mode=755 0 0
devpts /dev/pts devpts
rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=13187516k,mode=755 0 0
/dev/md2 / ext4 rw,relatime,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime
0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup 

Re: upgrade failed debian 8.7

[Sven Hartge]

Mike Nunn  wrote:

> can't install strace as apt suggests running dpkg --configure -a , prob due
> to the failure of the upgrade

> with update-initramfs -u -v -k 3.16.0-4-amd64 hung there doesn't seem to be
> a cpio process running

Strange.

If it hangs at "Building cpio /boot/initrd.img-3.16.0-4-amd64.new
initramfs" then there should be a cpio process.

Could then please share the full output of "df", "df -i" and "cat
/proc/mounts", each done as user "root"?

Grüße,
S°

-- 
Sigmentation fault. Core dumped.

Re: upgrade failed debian 8.7

[Mike Nunn]

can't install strace as apt suggests running dpkg --configure -a , prob due
to the failure of the upgrade

with update-initramfs -u -v -k 3.16.0-4-amd64 hung there doesn't seem to be
a cpio process running

On 4 February 2017 at 19:02, Sven Hartge  wrote:

> Mike Nunn  wrote:
> > Sven Hartge  wrote:
>
> >> Hmm. How long did you wait for it to complete? Is "/boot" full?
> >> Or is the disk /boot is on just abysmally slow?
>
> > It's still stuck, been over an hour now. Everything else seems fast,
> > no obvious slowdown.
>
> > Filesystem Size  Used Avail Use% Mounted on
> > /dev/md1   488M   52M  411M  12% /boot
>
> > Disks are NVMe Gen3 x4 SSD (Software-RAID 1)
>
> Please do
>
> a) lsof -p `pidof cpio`
> b) strace -f -p `pidof cpio`
>
> (If those tools are not installed, please install them.)
>
> Grüße,
> Sven.
>
> --
> Sigmentation fault. Core dumped.
>
>

Re: upgrade failed debian 8.7

[Sven Hartge]

Henrique de Moraes Holschuh  wrote:
> On Sat, 04 Feb 2017, Mike Nunn wrote:

>> /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable

> Is /tmp mounted "noexec"?  Just Don't Do It[tm].  The system will break
> in hideously crazy, suprising ways.  BTW, this is also valid for the
> filesystem hosting whatever directory $TMPDIR (and $TEMP, $TMP...)
> points to.

The above output seems to be normal, I get the same on my system.
Besides, the files mentioned ...

,
| /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not 
executable
| /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
| /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable
`

... don't even exist on those directories:

,
| # ls -l /usr/share/initramfs-tools/scripts/*
| -rw-r--r-- 1 root root 9394 Dec 15 22:34 
/usr/share/initramfs-tools/scripts/functions
| -rw-r--r-- 1 root root 4457 Apr 17  2016 
/usr/share/initramfs-tools/scripts/local
| -rw-r--r-- 1 root root 3050 Feb 20  2016 
/usr/share/initramfs-tools/scripts/nfs
|
| /usr/share/initramfs-tools/scripts/init-bottom:
| total 8
| -rwxr-xr-x 1 root root 147 Dec 18 11:50 plymouth
| -rwxr-xr-x 1 root root 572 Feb  1 22:45 udev
|
| /usr/share/initramfs-tools/scripts/init-premount:
| total 4
| -rwxr-xr-x 1 root root 464 Dec 18 11:50 plymouth
|
| /usr/share/initramfs-tools/scripts/init-top:
| total 16
| -rwxr-xr-x 1 root root 351 Dec  9  2015 all_generic_ide
| -rwxr-xr-x 1 root root 295 Dec  9  2015 blacklist
| -rwxr-xr-x 1 root root 358 Dec  9  2015 keymap
| -rwxr-xr-x 1 root root 501 Feb  1 22:45 udev
|
| /usr/share/initramfs-tools/scripts/local-block:
| total 8
| -rwxr-xr-x 1 root root  689 Dec 16 12:56 lvm2
| -rwxr-xr-x 1 root root 1206 Jul 28  2016 mdadm
|
| /usr/share/initramfs-tools/scripts/local-bottom:
| total 4
| -rwxr-xr-x 1 root root 46 Jul 28  2016 mdadm
|
| /usr/share/initramfs-tools/scripts/local-premount:
| total 8
| -rwxr-xr-x 1 root root  270 Sep 22 15:48 btrfs
| -rwxr-xr-x 1 root root 1041 Dec  9  2015 resume
|
| /usr/share/initramfs-tools/scripts/local-top:
| total 4
| -rwxr-xr-x 1 root root 970 Dec 16 12:56 lvm2
|
| /usr/share/initramfs-tools/scripts/panic:
| total 4
| -rwxr-xr-x 1 root root 151 Dec 18 11:50 plymouth
`

I think the error message is misleading in this case.

> Mounting /tmp "noexec" is not really supported, regardless of whether it
> used to work in the past or not.

Looking at "lsof -p `pidof cpio` it looks like the initramfs is build
inside /var/tmp and not /tmp.

Grüße,
S°

-- 
Sigmentation fault. Core dumped.

Re: Fails a l'arrancar un Debian Jessie 64 bits

[Alex Muntada]

Hola Daniel,
no és gaire normal que els discos es treguin del raid sense motiu. Jo
comprovaria amb smartctl si els discos estan bé de salut, per si de cas.
Especialment el que havia estat eliminat del raid.

Salut,
Alex

Re: upgrade failed debian 8.7

[Henrique de Moraes Holschuh]

On Sat, 04 Feb 2017, Mike Nunn wrote:
> /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable

Is /tmp mounted "noexec"?  Just Don't Do It[tm].  The system will break
in hideously crazy, suprising ways.  BTW, this is also valid for the
filesystem hosting whatever directory $TMPDIR (and $TEMP, $TMP...)
points to.

Mounting /tmp "noexec" is not really supported, regardless of whether it
used to work in the past or not.


If that's the case, here's a rough idea on how to fix the breakage:

1. fix the /tmp definiton on /etc/fstab, it must not be "noexec".

2. assuming you actually managed to boot, run as root:

   mount /tmp -o remount,exec
   update-initramfs -u

   that should create a working initramfs for the next boot.

-- 
  Henrique Holschuh

Re: logrotate - got compressed log

[Joe]

On Sat, 04 Feb 2017 18:04:12 +0100
kjo...@poczta.onet.pl (Kamil Jońca) wrote:

> Andy Smith  writes:
> 
> > Hi Kamil,
> >
> > On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:  
> >> I have logrotate with config (excerpt)
> >> --8<---cut here---start->8---
> >> compress  
> >
> > […]
> >  
> >> And since some days I started to receive *compressed* old syslog
> >> files :( instead uncompressed ones.   
> >
> > If you have the "compress" directive there you should expect to get
> > compressed logs.  
> Sorry, I did not write precisely.
> I started to receive compressed old logs by *mail*.
> So far, there were simple text in mail.
> 
> I understand, that old files on disk are compressed.
> 

Presumably you should be emailed the file after rotation, when it has
been closed, i.e. the version you should get is .1 which if
originating with rsyslog, should not be compressed. .2 and
subsequent should be compressed.

-- 
Joe

Re: logrotate - got compressed log

[Joe]

On Sat, 4 Feb 2017 16:12:50 +
Andy Smith  wrote:

> Hi Kamil,
> 
> On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
> > I have logrotate with config (excerpt)
> > --8<---cut here---start->8---
> > compress  
> 
> […]
> 
> > And since some days I started to receive *compressed* old syslog
> > files :( instead uncompressed ones.   
> 
> If you have the "compress" directive there you should expect to get
> compressed logs.
> 
> > Nothing has happen in configuration.
> > The only change was logrotate upgrade, from 3.8.7 to 3.11.0
> > Can anyboty confirm that there is difference between these
> > versions?  
> 
> I can't. As far as I can see you should expect compressed rotated
> files with your config, both in 3.8.7 and 3.11.0.
> 

I'm on 3.11.0 on sid, behaviour appears unchanged. Compression options
for rsyslog are compress and delaycompress, meaning that the open
logfile and the previous one are uncompressed, earlier ones are
compressed. I'm fairly sure this has been the Debian default for years.

-- 
Joe

Re: How to fix I/O errors?

[David Christensen]

On 02/04/17 07:18, Ric Moore wrote:

I'm looking at a Seagate 750 gig drive that went south on me with a pile
of errors. Good luck getting Seagate to give a good gosh darn. In the
past I have had mixed results replacing the drive motherboard. I saved
two out of three. I doubt I will buy anything Seagate makes in the
future.


Everything electrical and mechanical fails.  It's just a question of 
when, followed by whether or not you're prepared.



I've found (and heard) that the worst thing I can do to a HDD is put it 
on the shelf and let it rot.  I've had more than a few that failed 
shortly after being put into a computer.



David

Re: Re: Fails a l'arrancar un Debian Jessie 64 bits

[Josep Lladonosa]

2017-02-04 17:57 GMT+01:00 Daniel :

> Resolt gairebé tot:
>
> El Failed to start load Kernel modules s'ha resolt instalant el kernel que
> no sé perquè no estava instalat.
>
> Els problemes amb l'array s'han resolt amb:
>
>  mdadm --manage /dev/md[XXX] --add /dev/sdc[X].
>
> Efectivament, els discos estaven connectats, i el que no sabré mai és
> perquè un dels dos discos de l'array s'ha "desconnectat" -status removed-,
> i quan ho ha fet. Hauré de vigilar que no torni a passar.
>
> Falta aclarir:
>
> Invalid PBLK length
>
> I perquè no funciona el log d'inici (/var/log/boot). L'he activat al
> /etc/default/bootlog.d (BOOTLODG_ENABLED=yes) però no hi ha manera.
>


Que no sigui perquè hagi de ser (BOOTLOGD_ENABLE=yes).



>
>
>
>
>  Missatge reenviat 
> Assumpte: Re: Fails a l'arrancar un Debian Jessie 64 bits
> Reenviat-Data: Thu, 2 Feb 2017 10:58:54 + (UTC)
> Reenviat-De: debian-user-catalan@lists.debian.org
> Data: Thu, 2 Feb 2017 11:57:32 +0100
> De: Daniel  
> A: debian usuaris en CATALA 
> 
>
>
> He trobat el fitxer /etc/modules-load,d/modules.conf. No hi ha cap línia
> activa:
>
> *daniel@Daniel-Debian:/etc/modules-load.d$
>  pg modules.conf*
> *# /etc/modules: kernel modules to load at boot time.*
> *#*
> *# This file contains the names of kernel modules that should be loaded*
> *# at boot time, one per line. Lines beginning with "#" are ignored.*
>
> *(EOF):*
>
>
>
>
> El 02/02/17 a les 11:42, Daniel ha escrit:
>
> Hola:
>
> Avui, mentre el sistema feia el check list a un disc, he advertit la
> presència d'uns errors certament preocupants:
> En primer lloc, just després d'engegar la càrrega del Debian, apareix en
> pantalla:
>
> Invalid PBLK length [7]
>
> He estat buscant per Internet i trobo alguna cosa però no està clara.
>
> Després apareix dues vegades un Failed to start load Kernel modules. Va
> acompanyat d'una suggerència d'execució:
>
> root@Daniel-Debian:/home/daniel# systemctl status -l systemd-modules-load
> ● systemd-modules-load.service - Load Kernel Modules
>Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
>Active: failed (Result: exit-code) since dj 2017-02-02 08:54:14 CET; 2h 
> 21min ago
>  Docs: man:systemd-modules-load.service(8)
>man:modules-load.d(5)
>   Process: 297 ExecStart=/lib/systemd/systemd-modules-load (code=exited, 
> status=1/FAILURE)
>  Main PID: 297 (code=exited, status=1/FAILURE)
>
> feb 02 08:54:14 Daniel-Debian systemd[1]: Starting Load Kernel Modules...
> feb 02 08:54:14 Daniel-Debian systemd[1]: systemd-modules-load.service: main 
> process exited, code=exited, status=1/FAILURE
> feb 02 08:54:14 Daniel-Debian systemd[1]: Failed to start Load Kernel Modules.
> feb 02 08:54:14 Daniel-Debian systemd[1]: Unit systemd-modules-load.service 
> entered failed state.
> root@Daniel-Debian:/home/daniel
>
> I per fi, apareix un altre fail absolutament terrorífic sobre l'array que
> tinc innstalat. He anat a repassar les funcions del mdadm i he pogut trobar
> el següent:
>
> *root@Daniel-Debian:/etc/mdadm# mdadm --detail /dev/md125*
>
> */dev/md125:*
>
> * Version : 0.90*
>
> * Creation Time : Wed Oct 6 09:35:45 2010*
>
> * Raid Level : raid1*
>
> * Array Size : 224548416 (214.15 GiB 229.94 GB)*
>
> * Used Dev Size : 224548416 (214.15 GiB 229.94 GB)*
>
> * Raid Devices : 2*
>
> * Total Devices : 1*
>
> *Preferred Minor : 125*
>
> * Persistence : Superblock is persistent*
>
>
> * Update Time : Thu Feb 2 09:48:25 2017*
>
> * State : clean, degraded *
>
> * Active Devices : 1*
>
> *Working Devices : 1*
>
> * Failed Devices : 0*
>
> * Spare Devices : 0*
>
>
> * UUID : 3455ddc1:1d300587:216ebfe7:79edd7b7*
>
> * Events : 0.45652*
>
>
> * Number Major Minor RaidDevice State*
>
> * 00   0  0removed*
>
> * 18 17  1active sync /dev/sdb1*
>
> *root@Daniel-Debian:/etc/mdadm# *
>
> Em passa exactament el mateix amb l'altre disc de l'array, el /dev/md126.
> Removed vol dir que el disc no hi és, oi? Ara miraré si el disc està ben
> connectat...
>
> Qualsevol ajuda serà molt benvinguda... Me'n vaig a fer mentrestant còpia
> de totes les fotos per si de cas. Gràcies.
>
> --
> Daniel Elias
> Usuari de Linux nº 461584
>
>
> --
> Daniel Elias
> Usuari de Linux nº 461584
>
>
>
>


-- 
--
Salutacions...Josep
--

Re: upgrade failed debian 8.7

[Sven Hartge]

Mike Nunn  wrote:
> Sven Hartge  wrote:

>> Hmm. How long did you wait for it to complete? Is "/boot" full?
>> Or is the disk /boot is on just abysmally slow?

> It's still stuck, been over an hour now. Everything else seems fast,
> no obvious slowdown.

> Filesystem Size  Used Avail Use% Mounted on
> /dev/md1   488M   52M  411M  12% /boot

> Disks are NVMe Gen3 x4 SSD (Software-RAID 1)

Please do

a) lsof -p `pidof cpio`
b) strace -f -p `pidof cpio`

(If those tools are not installed, please install them.)

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

upgrade failed debian 8.7

[Mike Nunn]

Sven Hartge  wrote:

> Hmm. How long did you wait for it to complete? Is "/boot" full?
> Or is the disk /boot is on just abysmally slow?

It's still stuck, been over an hour now. Everything else seems fast,
no obvious slowdown.

Filesystem Size  Used Avail Use% Mounted on
/dev/md1   488M   52M  411M  12% /boot

Disks are NVMe Gen3 x4 SSD (Software-RAID 1)

Thanks

Mike

Re: upgrade failed debian 8.7

[Sven Hartge]

Mike Nunn  wrote:

> It seems to stop after the last line shown below.

>  Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs

Hmm. How long did you wait for it to complete? Is "/boot" full? Or is
the disk /boot is on just abysmally slow?

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

upgrade failed debian 8.7

[Mike Nunn]

Thanks for the reply,

It seems to stop after the last line shown below.

 update-initramfs -u -v -k 3.16.0-4-amd64
 Keeping /boot/initrd.img-3.16.0-4-amd64.dpkg-bak
 update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
 Copying module directory kernel/drivers/hid


 Calling hook zz-busybox
 Adding binary /bin/busybox
 Calling hook dmsetup
 /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not
executable
 /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not
executable
 /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not
executable
 /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
 /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not
executable
 /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
 Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs

Thanks

Mike

upgrade failed debian 8.7

[Mike Nunn]

Thanks for the reply,

It seems to stop after the last line shown below.

update-initramfs -u -v -k 3.16.0-4-amd64
Keeping /boot/initrd.img-3.16.0-4-amd64.dpkg-bak
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
Copying module directory kernel/drivers/hid


Calling hook zz-busybox
Adding binary /bin/busybox
Calling hook dmsetup
/usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not
executable
/usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not
executable
/usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable
/usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable
Building cpio /boot/initrd.img-3.16.0-4-amd64.new initramfs

Thanks

Mike

Re: debconf

[paulo bruck]

Se você quer fazer  a instalação de pacotes automatica, vc pode ver estes 2
links:

https://www.debian.org/releases/stable/amd64/apb.html.en

https://wiki.debian.org/Simple-CDD/Howto

[]s

Em 4 de fevereiro de 2017 10:08, Paulo Roberto Evangelista <
shellcl...@gmail.com> escreveu:

> Adriano, muito obrigado!
>
> Estava lendo a lista devel agora mesmo! :D
>
> Encontrei esse link aqui   nf-doc/tutorial.html#AEN34>  e me ajudou bastante!
>
> Em 4 de fevereiro de 2017 09:03, Adriano Rafael Gomes <
> adrian...@debian.org> escreveu:
>
>> On Sat, Feb 04, 2017 at 08:23:09AM -0300, Paulo Roberto Evangelista wrote:
>> > olá, todo mundo!
>> >
>> > Alguém sabe onde encontro uma documentação que detalhe o uso de debconf?
>> > Quero automatizar a instalação de um pacote mas durante a instalação ele
>> > faz algumas perguntas,  penso em utilizar o debconf para que eu não
>> precise
>> > de nenhuma entrada via teclado para as perguntas durante a instalação.
>>
>> Você pode tentar isto:
>>
>> https://lists.debian.org/debian-devel-portuguese/
>> https://www.debian.org/doc/debian-policy/ch-binary.html#s-ma
>> intscriptprompt
>> https://www.debian.org/doc/packaging-manuals/debconf_specification.html
>> http://www.fifi.org/doc/debconf-doc/tutorial.html
>> https://packages.debian.org/sid/debconf-doc
>> https://wiki.debian.org/debconf
>>
>
>


-- 
Paulo Ricardo Bruck consultor
tel 011 3596-4881/4882  011 98140-9184 (TIM)
http://www.contatogs.com.br
http://www.protejasuarede.com.br
gpg AAA59989 at wwwkeys.us.pgp.net

Re: logrotate - got compressed log

[Kamil Jońca]

Andy Smith  writes:

> Hi Kamil,
>
> On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
>> I have logrotate with config (excerpt)
>> --8<---cut here---start->8---
>> compress
>
> […]
>
>> And since some days I started to receive *compressed* old syslog files
>> :( instead uncompressed ones. 
>
> If you have the "compress" directive there you should expect to get
> compressed logs.
Sorry, I did not write precisely.
I started to receive compressed old logs by *mail*.
So far, there were simple text in mail.

I understand, that old files on disk are compressed.

KJ

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
The average nutritional value of promises is roughly zero.

Re: Dolphin symlink previews

[Glenn Holmer]

On 02/04/2017 11:13 AM, Glenn Holmer wrote:
> Debian testing with KDE here, all patches applied.
> 
> I've got a directory full of images, some of which are symlinks. I have
> Dolphin set to display previews for image files, but previews aren't
> showing up for symlinks. How can I get previews for them?

Ha! Never mind, I'd broken the symlinks by moving the originals.

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

Dolphin symlink previews

[Glenn Holmer]

Debian testing with KDE here, all patches applied.

I've got a directory full of images, some of which are symlinks. I have
Dolphin set to display previews for image files, but previews aren't
showing up for symlinks. How can I get previews for them?

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

Re: Some x-terminals do not compose unicode characters

[Darac Marjal]

Just to note, I have tried this same command in xfce-terminal 0.8.3
(which is in testing and unstable and depends on libvte-2.91-1 version
0.46.1-1) and I /do/ get a struckthrough 1.

So, if you're using stable (you don't actually say which versions of the
packages you tries), then the bug may already be fixed. If you're on
testing or newer, then it might be a configuration issue.


On 03/02/17 10:07, Alessandro T. wrote:
> Hi,
> I would get the strikethrough text in x-terminal-emulator. So I tried
>
> echo -e '1\u0336'
>
> and with mlterm, pterm, rxvt and xterm I got, rightly, strikethrough 1.
> Instead with evilvte, gnome-terminal, lilyterm, lxterminal, sakura,
> terminator, terminix, termit, vala-terminal and xfce4-terminal (my
> default) I got 1-.
>
> This is caused by incorrect configuration? So where should I intervene?
> Or is it a bug? So what package should I report?
>
> Thanks
>



signature.asc
Description: OpenPGP digital signature

Re: upgrade failed debian 8.7

[Sven Hartge]

Mike Nunn  wrote:

> uname -a 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64
> GNU/Linux

> I ran sudo apt update followed by upgrade

> it hangs at the following point:

> Setting up linux-image-3.16.0-4-amd64 (3.16.39-1) ...
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64

> Progress: [  0%]

> Any advice very gratefully received.

Please interrupt the currently running process (STRG+C) and do it in two
steps: 

a) sudo -i 
   to get a genuine root shell

b) apt upgrade

With this I want to check if there is anything funny happening with the
terminal when using just "sudo apt upgrade".

If this does not change anything, interrupt the process again and just
issue "update-initramfs -u -v -k 3.16.0-4-amd64" to see if anything
strange happens during the generation of the initramfs.

S°

-- 
Sigmentation fault. Core dumped.

Re: can not set time

[Matthias Bodenbinder]

Am 04.02.2017 um 17:43 schrieb Jude DaShiell:

On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:


Date: Sat, 4 Feb 2017 09:07:00
From: Matthias Bodenbinder 
To: debian-user@lists.debian.org
Subject: Re: can not set time
Resent-Date: Sat,  4 Feb 2017 14:07:22 + (UTC)
Resent-From: debian-user@lists.debian.org

Am 04.02.2017 um 14:36 schrieb Jude DaShiell:

please check that other box and see if it has
systemd-timesyncd.service on it.
You can probably start that service up and solve that problem.
Then try timedatectl set-ntp true.
That should make timesync happen on boot.
On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:



timedatectl set-ntp true
did not help. It is not changing the time.

My reference PC has debian testing running with systemd-timesyncd. But
the broken PC is MINT LMDE which is still on init.d.

Matthias


Okay, since you have ntp, ntpd -qg and then hwclock --systohc --utc may
get this working for you.  We probably don't need to do anything with
your timezone setting link to /etc/localtime by now.


Hello Jude,

I tried it all. I googled almost every command related to time setting 
and tried it out. But it did not work. I am still not sure why.


But now, after switching to systemd and systemd-timesyncd it works. See 
my other post.


Thank you for help anyways.
Matthias

Fwd: Re: Fails a l'arrancar un Debian Jessie 64 bits

[Daniel]

Resolt gairebé tot:

El Failed to start load Kernel modules s'ha resolt instalant el kernel 
que no sé perquè no estava instalat.


Els problemes amb l'array s'han resolt amb:

 mdadm --manage /dev/md[XXX] --add /dev/sdc[X].

Efectivament, els discos estaven connectats, i el que no sabré mai és 
perquè un dels dos discos de l'array s'ha "desconnectat" -status 
removed-, i quan ho ha fet. Hauré de vigilar que no torni a passar.


Falta aclarir:

Invalid PBLK length

I perquè no funciona el log d'inici (/var/log/boot). L'he activat al 
/etc/default/bootlog.d (BOOTLODG_ENABLED=yes) però no hi ha manera.





 Missatge reenviat 
Assumpte:   Re: Fails a l'arrancar un Debian Jessie 64 bits
Reenviat-Data:  Thu, 2 Feb 2017 10:58:54 + (UTC)
Reenviat-De:debian-user-catalan@lists.debian.org
Data:   Thu, 2 Feb 2017 11:57:32 +0100
De: Daniel 
A:  debian usuaris en CATALA 



He trobat el fitxer /etc/modules-load,d/modules.conf. No hi ha cap línia 
activa:


/daniel@Daniel-Debian:/etc/modules-load.d$ pg modules.conf//
//# /etc/modules: kernel modules to load at boot time.//
//#//
//# This file contains the names of kernel modules that should be loaded//
//# at boot time, one per line. Lines beginning with "#" are ignored.//
//
//(EOF):/




El 02/02/17 a les 11:42, Daniel ha escrit:

Hola:

Avui, mentre el sistema feia el check list a un disc, he advertit la 
presència d'uns errors certament preocupants:
En primer lloc, just després d'engegar la càrrega del Debian, apareix 
en pantalla:


Invalid PBLK length [7]

He estat buscant per Internet i trobo alguna cosa però no està clara.

Després apareix dues vegades un Failed to start load Kernel modules. 
Va acompanyat d'una suggerència d'execució:


root@Daniel-Debian:/home/daniel# systemctl status -l systemd-modules-load
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)
Active: failed (Result: exit-code) since dj 2017-02-02 08:54:14 CET; 2h 
21min ago
  Docs:man:systemd-modules-load.service(8)
man:modules-load.d(5)
   Process: 297 ExecStart=/lib/systemd/systemd-modules-load (code=exited, 
status=1/FAILURE)
  Main PID: 297 (code=exited, status=1/FAILURE)

feb 02 08:54:14 Daniel-Debian systemd[1]: Starting Load Kernel Modules...
feb 02 08:54:14 Daniel-Debian systemd[1]: systemd-modules-load.service: main 
process exited, code=exited, status=1/FAILURE
feb 02 08:54:14 Daniel-Debian systemd[1]: Failed to start Load Kernel Modules.
feb 02 08:54:14 Daniel-Debian systemd[1]: Unit systemd-modules-load.service 
entered failed state.
root@Daniel-Debian:/home/daniel
I per fi, apareix un altre fail absolutament terrorífic sobre l'array 
que tinc innstalat. He anat a repassar les funcions del mdadm i he 
pogut trobar el següent:


/root@Daniel-Debian:/etc/mdadm# mdadm --detail /dev/md125/

//dev/md125:/

/Version : 0.90/

/Creation Time : Wed Oct 6 09:35:45 2010/

/Raid Level : raid1/

/Array Size : 224548416 (214.15 GiB 229.94 GB)/

/Used Dev Size : 224548416 (214.15 GiB 229.94 GB)/

/Raid Devices : 2/

/Total Devices : 1/

/Preferred Minor : 125/

/Persistence : Superblock is persistent/

/
/

/Update Time : Thu Feb 2 09:48:25 2017/

/State : clean, degraded /

/Active Devices : 1/

/Working Devices : 1/

/Failed Devices : 0/

/Spare Devices : 0/

/
/

/UUID : 3455ddc1:1d300587:216ebfe7:79edd7b7/

/Events : 0.45652/

/
/

/Number Major Minor RaidDevice State/

/00   0  0 removed/

/18 17  1active sync /dev/sdb1/

/root@Daniel-Debian:/etc/mdadm# /


Em passa exactament el mateix amb l'altre disc de l'array, el 
/dev/md126. Removed vol dir que el disc no hi és, oi? Ara miraré si el 
disc està ben connectat...


Qualsevol ajuda serà molt benvinguda... Me'n vaig a fer mentrestant 
còpia de totes les fotos per si de cas. Gràcies.


--
Daniel Elias
Usuari de Linux nº 461584


--
Daniel Elias
Usuari de Linux nº 461584

Re: Advice / recommendations on Inexpensive Managed Ethernet Switches

[solitone]

On sabato 4 febbraio 2017 11:02:12 CET Dan Ritter wrote:
> If, on the other hand, you have a bunch of potential bandwidth
> consumers, yes, you'll need a capable switch.

Yes, this is my scenario.

> EBay says that you can get a used Juniper EX2200-24 (24 gigabit
> ports) for $110 or so -- that's a great piece of hardware, very
> capable,
> 
> For about the same price, you can get a used Juniper SRX110h or
> SRX220h, which are 8 port firewall/routers: but they can also do
> LACP on any set of ports. If you have a small network, that
> could be really nice.

Nice, thanks! SRX220h could be an option, since it has Gigabit eth ports, 
while 110h hasn't. Considering my current router is pretty limited, it might 
be the way to go, rather than a switch. 8 ports would be enough for my home 
LAN.

upgrade failed debian 8.7

[Mike Nunn]

uname -a 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64
GNU/Linux

I ran sudo apt update followed by upgrade

it hangs at the following point:

Setting up linux-image-3.16.0-4-amd64 (3.16.39-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64

Progress: [  0%]

Any advice very gratefully received.

Thanks

Mike

Re: can not set time

[Matthias Bodenbinder]

Am 04.02.2017 um 15:49 schrieb Matthias Bodenbinder:

More info:

I switched to systemd and systemd-timesyncd. During boot the time is synced 
back and forth multiple times and in the end it stays wrong.

Look at this. See the timestamps for each line. Going back and forth.

Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 
78.46.253.198:123 (2.debian.pool.ntp.org).
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.


The switch to systemd and systemd-timesyncd did the trick. But it takes 
very long. Its obvious from the journal messages but I did not get it at 
first: timesyncd changes the time in small increments of only 0.01 seconds.


I just had to wait and now the time is correct.

Matthias

Re: can not set time

[Jude DaShiell]

On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:


Date: Sat, 4 Feb 2017 09:07:00
From: Matthias Bodenbinder 
To: debian-user@lists.debian.org
Subject: Re: can not set time
Resent-Date: Sat,  4 Feb 2017 14:07:22 + (UTC)
Resent-From: debian-user@lists.debian.org

Am 04.02.2017 um 14:36 schrieb Jude DaShiell:

please check that other box and see if it has systemd-timesyncd.service on it.
You can probably start that service up and solve that problem.
Then try timedatectl set-ntp true.
That should make timesync happen on boot.
On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:



timedatectl set-ntp true
did not help. It is not changing the time.

My reference PC has debian testing running with systemd-timesyncd. But the 
broken PC is MINT LMDE which is still on init.d.

Matthias

Okay, since you have ntp, ntpd -qg and then hwclock --systohc --utc may 
get this working for you.  We probably don't need to do anything with 
your timezone setting link to /etc/localtime by now.






--

Re: Advice / recommendations on Inexpensive Managed Ethernet Switches

[rhkramer]

On Saturday, February 04, 2017 09:43:13 AM solitone wrote:
> I'm just curious, but I cannot understand how you can have Internet access
> from all your devices, considering you just have a modem plus some
> switches, but you don't have a router that does Network Address
> Translation. Perhaps the modem is in fact a modem/router combo, rather
> than a modem-only device?

Sorry, yes, the modem is a modem/router combo.  And it is from that that I 
currently get the statistics I mentioned (re used bandwidth).

Re: Boot fails after stretch upgrade to linux 4.9.0

[Francesco Montanari]

Hi,

I may have not copied the correct error message when the system
freezes after passing lspci in recovery mode (unless
the message changed). I report below the corrected message.

To sum up:
- using linux 4.8.0. I notice no problem.
- When I first booted linux 4.9.0, I got a TPM error message that I never
  had before. Disabling the security chip from BIOS solved it.
- The system does not boot as it gets stucked after loading some
  service (e.g., network manager).
- It boots in recovery mode, but freezes when passing the lspci
  command. It also freezes if I pass "systemctl reboot"
- Logs show error messages related to acpi, drivers, remount error of
  EXT4 partition (fsck did not find problems), and segfault related to
  gnome-session-f (https://is.gd/fMGaPr).

Do you have any hint to identify and understand better the origin of
the issue (please let me know if you need more info)?




Here is the message before the system gets stucked:
# lspci -nn | grep VGA
[   111.290008] thinkpad_acpi: EC reports that Thermal Table has changed
[   111.290185] nouveau :01:00.0: DRM: resuming kernel object
tree..
[   111.477119] nouveau :01:00.0: DRM: resuming client object trees...
[   111.478199] nouveau :01:00.0: DRM: resuming display...
[   111.479289] nouveau :01:00.0: DRM: resuming console...




Thanks,
Francesco


On Sat, Jan 28, 2017 at 02:35:24PM +0200, Francesco Montanari wrote:
> Hi,
>
> With a recent Stretch update, linux 4.9.0-1-amd64 was installed. I got:
>   A TPM error (6) occurred attempting to read a pcr value
>
> Disabling the security chip from BIOS solved the error. Still, 4.9.0
> does not boot. It manages to start some service (e.g., network
> manager), but then it gets stuck before displaying the login screen.
>
> I managed to boot in recovery mode. I collect here some grep of errors
> and warnings:
>
> - From dmesg:
>   [ 0.773426] acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM
>
> - From journalctl -xb:
>   Jan 28 10:05:08 debian-francesco kernel: acpi PNP0A08:00: _OSC failed 
> (AE_SUPPORT); disabling ASPM
>   -- The process /bin/plymouth could not be executed and failed.
>   Jan 28 10:05:17 debian-francesco bluetoothd[512]: Sap driver initialization 
> failed.
>   Jan 28 10:05:08 debian-francesco kernel: EXT4-fs (sda3): re-mounted. Opts: 
> errors=remount-ro
>   -- The error number returned by this process is 2.
>
> - From syslog:
>   https://is.gd/fMGaPr
>
> When rebooting from recovery mode (i.e., executing 'systemctl
> reboot'), it also gets stuck.
>
> Finally, If I pass the following command in recovery mode
>   # lspci -nn | grep VGA
> it gets stuck (ctrl-c/d/z have no effect) right after displaying this
> message:
> [   19.948099] nouveau :01:00.0: DRM: suspending console...
> [   19.951782] nouveau :01:00.0: DRM: suspending display...
> [   19.955032] nouveau :01:00.0: DRM: evicting buffers...
> [   19.958215] nouveau :01:00.0: DRM: waiting for kernel channels to 
> go idle...
> [   19.961380] nouveau :01:00.0: DRM: suspending client object 
> trees...
> [   19.964738] nouveau :01:00.0: DRM: suspending kernel object tree...
>
> I successfully booted with the old 4.8.0 kernel (normal mode). In that
> case:
>   $ lspci -nn | grep VGA
>   00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation 
> Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
>   01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M [Quadro 
> NVS 4200M] [10de:1057] (rev a1)
>
>
> Not sure if it is related to some configuration I may have modified in
> the past, to graphics drivers or, e.g., to old BIOS? Maybe something
> else?
>
> I have a Thinkpad T420.
>
> Thanks,
> Francesco
>

Re: logrotate - got compressed log

[Andy Smith]

Hi Kamil,

On Sat, Feb 04, 2017 at 10:11:00AM +0100, Kamil Jońca wrote:
> I have logrotate with config (excerpt)
> --8<---cut here---start->8---
> compress

[…]

> And since some days I started to receive *compressed* old syslog files
> :( instead uncompressed ones. 

If you have the "compress" directive there you should expect to get
compressed logs.

> Nothing has happen in configuration.
> The only change was logrotate upgrade, from 3.8.7 to 3.11.0
> Can anyboty confirm that there is difference between these versions?

I can't. As far as I can see you should expect compressed rotated
files with your config, both in 3.8.7 and 3.11.0.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Advice / recommendations on Inexpensive Managed Ethernet Switches

[Dan Ritter]

On Sat, Feb 04, 2017 at 04:29:39PM +0100, solitone wrote:
> I take advantage of this thread to ask for advice on this topic. My need is a 
> managed switch with Gigabit ports that supports port trunking (Link 
> Aggregation Control Protocol, LACP, 802.3ad Dynamic Link Aggregation), to 
> increase the bandwith to my Network Access Storage. Is there anything on the 
> marketplace that doesn't cost way too much?

Depending on your usage scenario, maybe you don't need one at
all.

If you have a single Linux box that wants lots of bandwidth to
the NAS, you could do this:

   switch  NAS
|  |||
--Linux box

This shows a NAS and a Linux box with four NICs each. One is
used to connect to the general network via the switch, and
the other three on each device are connected straight across
to the companion.

You would want to set extra IP addresses on each device so that
they can see each other directly through the triple NICs, which
can speak LACP without going through a switch.

If, on the other hand, you have a bunch of potential bandwidth
consumers, yes, you'll need a capable switch.

EBay says that you can get a used Juniper EX2200-24 (24 gigabit
ports) for $110 or so -- that's a great piece of hardware, very
capable,

For about the same price, you can get a used Juniper SRX110h or
SRX220h, which are 8 port firewall/routers: but they can also do
LACP on any set of ports. If you have a small network, that
could be really nice.

-dsr-

Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su

[Brian]

On Sat 04 Feb 2017 at 14:55:18 +0900, Mark Fletcher wrote:

> On Sat, Feb 04, 2017 at 01:42:00AM +, Roba wrote:
> > /etc/cups/cupsd.conf  (I thought whereis would have found it, I am wrong)
> > 
> > # Show general information in error_log.
> > LogLevel warn
> > MaxLogSize 0
> > Listen /var/run/cups/cups.sock
> > Listen /var/run/cups/cups.sock
> > Browsing On
> > BrowseLocalProtocols dnssd
> 
> In my _working_ CUPS on Jessie, I have :
> 
> Listen /var/run/cups/cups.sock
> Listen 192.168.11.5:631
> 
> which I find fascinating, as 192.168.11.5 is _NOT_ the IP address of my 
> computer, yet somehow it works anyway. The port scan you did a reply or

You don't mean localhost:631 works, surely? What is 192.168.11.5? Does
cupsd run on it?

> two ago showed you had something listening on UDP port 631, but nothing 
> on TCP port 631, which is why printing is not working. 

Exactly.

> Indulge us, and add a line to your cupsd.conf as follows:
> 
> Listen localhost:631
> 
> and restart CUPS and see what happens.

It would solve his problem.
 
> Assuming that works, you are going to want to know why it was necessary 
> to add it, and I am afraid I have no idea. I can tell you though, for 
> what use this is, it is _NOT_ a direct cause of the wheezy --> jessie 
> upgrade. I performed that upgrade (a good while ago, to be fair) and did 
> not experience this problem. So in the absence of better information I'd 
> have to guess something you did or something else you installed resulted 
> in this happening to your conf file. I really have no idea what that 
> could be though.

There is nothing in the postinst script for cups which would replace a
"Listen localhost:631" line. Easily tested with

 apt-get --reinstall install cups

-- 
Brian.

Re: Advice / recommendations on Inexpensive Managed Ethernet Switches

[solitone]

I take advantage of this thread to ask for advice on this topic. My need is a 
managed switch with Gigabit ports that supports port trunking (Link 
Aggregation Control Protocol, LACP, 802.3ad Dynamic Link Aggregation), to 
increase the bandwith to my Network Access Storage. Is there anything on the 
marketplace that doesn't cost way too much?

Re: How to fix I/O errors?

[Ric Moore]

On 02/03/2017 04:47 PM, Marc Shapiro wrote:

On 02/02/2017 10:23 PM, David Christensen wrote:


Have you downloaded and run the manufacturer diagnostic utilities for
all your drives?  What do they say?


I have now downloaded and run Seagate's tools and it does show a does
show a disk error.  Since it stops on the first error I do not know if
this is an isolated error, or a more systematic problem.


I'm looking at a Seagate 750 gig drive that went south on me with a pile 
of errors. Good luck getting Seagate to give a good gosh darn. In the 
past I have had mixed results replacing the drive motherboard. I saved 
two out of three. I doubt I will buy anything Seagate makes in the 
future. Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: can not set time

[Matthias Bodenbinder]

More info:

I switched to systemd and systemd-timesyncd. During boot the time is synced 
back and forth multiple times and in the end it stays wrong. 

Look at this. See the timestamps for each line. Going back and forth.

Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 
78.46.253.198:123 (2.debian.pool.ntp.org).
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp
Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.874s/0.016s/560.321s/+0pp
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.864s/0.015s/457.500s/+0pp
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.854s/0.015s/323.501s/+0pp
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.844s/0.015s/0.036s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.834s/0.015s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.824s/0.016s/0.029s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.814s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.804s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.794s/0.015s/0.029s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.784s/0.015s/0.036s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.774s/0.016s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.764s/0.016s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.754s/0.015s/0.045s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.744s/0.015s/0.037s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.733s/0.016s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.723s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.713s/0.015s/0.025s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: 
interval/delta/delay/jitter/drift 32s/-855.702s/0.017s/0.030s/+0ppm
Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. 
Resyncing.
Feb 04 

Re: Advice / recommendations on Inexpensive Managed Ethernet Switches

[solitone]

On giovedì 2 febbraio 2017 11:19:59 CET rhkra...@gmail.com wrote:
> Layout of the network (for background):
> 
> The Earthlink DSL modem (Westell) is followed by an Ethernet (unmanaged}
> switch.
> 
> From that switch there are three cables:
> 
>* One to a WiFi hotspot that is almost always on (but only used by my son
> playing games while watching TV)
> 
>* One to my desk [...] There is
> an unmanaged Ethernet switch here to connect the various devices.
> 
>* One to my son's desk [...] There is an
> unmanaged Ethernet switch here to connect the various devices.

I'm just curious, but I cannot understand how you can have Internet access 
from all your devices, considering you just have a modem plus some switches, 
but you don't have a router that does Network Address Translation. Perhaps the 
modem is in fact a modem/router combo, rather than a modem-only device?

Re: can not set time

[Matthias Bodenbinder]

Am 04.02.2017 um 14:36 schrieb Jude DaShiell:
> please check that other box and see if it has systemd-timesyncd.service on it.
> You can probably start that service up and solve that problem.
> Then try timedatectl set-ntp true.
> That should make timesync happen on boot.
> On Sat, 4 Feb 2017, Matthias Bodenbinder wrote:


timedatectl set-ntp true
did not help. It is not changing the time.

My reference PC has debian testing running with systemd-timesyncd. But the 
broken PC is MINT LMDE which is still on init.d.

Matthias

Partition alignment

[Thomas Hungenberg]

Hi,

I have a 4TB HDD with 4k sectors:

Disk /dev/sdb: 976754642 sectors, 3.6 TiB
Logical sector size: 4096 bytes

I would like to set up a single partition using GPT.

gdisk sets up the partition to start at sector 8 by default:

Number  Start (sector)End (sector)  Size   Code  Name
   1   8   976754636   3.6 TiB 8300  Linux filesystem

gdisk then is fine with the alignment:

No problems found. 2 free sectors (8.0 KiB) available in 1
segments, the largest of which is 2 (8.0 KiB) in size.

However, parted says the partition is not aligned:

# parted /dev/sdb align-check opt 1
1 not aligned


According to this howto


the first partition should start at sector 65535 with my HDD's parameters:

# cat /sys/block/sdb/queue/optimal_io_size
268431360
# cat /sys/block/sdb/queue/physical_block_size
4096

268431360 / 4096 = 65535

So I changed the start sector accordingly:

Number  Start (sector)End (sector)  Size   Code  Name
   1   65535   976733639   3.6 TiB 8300  Linux filesystem

Now parted is fine with the alignment:

# parted /dev/sdb align-check opt 1
1 aligned

But gdisk complains:

Caution: Partition 1 doesn't begin on a 8-sector boundary. This may
result in degraded performance on some modern (2009 and later) hard disks.


So I wonder which start sector I should choose for optimal alignment?


Thanks,
Thomas

Re: can not set time

[Jude DaShiell]

please check that other box and see if it has systemd-timesyncd.service 
on it.

You can probably start that service up and solve that problem.
Then try timedatectl set-ntp true.
That should make timesync happen on boot.
On Sat, 4 
Feb 2017, Matthias Bodenbinder wrote:



Date: Sat, 4 Feb 2017 08:07:16
From: Matthias Bodenbinder 
To: debian-user@lists.debian.org
Subject: can not set time
Resent-Date: Sat,  4 Feb 2017 13:07:40 + (UTC)
Resent-From: debian-user@lists.debian.org

Hi,

I have a weird issue with one of my debian boxes (LMDE): I can not set the 
time. The time is off by ca. 14 min and whatever I try to fix it is failing. I 
tried ntp, ntpdate, date and rdate. Nothing helps.

ntpdate shows the offset but is not fixing it.

91# ntpdate 0.debian.pool.ntp.org
4 Feb 14:03:55 ntpdate[8159]: step time server 85.114.132.52 offset -855.296824 
sec


rdate is showing some interesting behaviour. If I run a command like "date && rdate -v  
ptbtime1.ptb.de && date" to see the time before and after rdate, the output suggests that 
rdate was successful:

81# date && rdate -v  ptbtime1.ptb.de && date
Sat Feb  4 14:16:04 CET 2017
Sat Feb  4 14:01:49 CET 2017
rdate: adjust local clock by -855 seconds
Sat Feb  4 14:01:49 CET 2017

But in fact 1 second later the time is back to old values again:

82# date
Sat Feb  4 14:16:06 CET 2017


timedatectl is showing wrong time as well:

93# timedatectl
 Local time: Sat 2017-02-04 14:20:39 CET
 Universal time: Sat 2017-02-04 13:20:39 UTC
   RTC time: Sat 2017-02-04 13:20:39
  Time zone: Europe/Berlin (CET, +0100)


But is should be:
 Local time: Sa 2017-02-04 14:06:25 CET
 Universal time: Sa 2017-02-04 13:06:25 UTC
   RTC time: Sa 2017-02-04 13:06:25
  Time zone: Europe/Berlin (CET, +0100)


I am lost.

Matthias









--

Re: installing knoppix or debian on hard list

[Richard Owlett]

On 02/03/2017 02:53 PM, John Culleton wrote:

I have my existing OS on /sda3. I want to leave it untouched. > I also have an 
OS on /sda4 that I am willing to overwrite.
The easiest path for me is to fire up Knoppix 7.6 and write
it to hard disk. But I need assurance that I won't disturb
/sda3 in any way.



I think you have omitted relevant information.
What is on /sda1 and /sda2?
What OS is on on /sda3? on /sda4?
What is your bootloader?

Technically correct answers can be given without this 
information. However, suitability to *YOUR* goals/preferences ???


My current used laptop resembles your setup. /sda1 and /sda2 are 
the Windows installation installed by the seller. They are being 
left untouched until the end of my warranty. /sda3 is an extended 
partition and /sda6 is swap.


/sda5 has Debian Jessie with Mate desktop. This is my primary OS 
which I take pains not to mess-up - {comparable to your /sda3}.

/sda7 has Jessie with Xfce that someone had suggested I try.
/sda8,/sda9,/sda10 are several identical installs of Jessie being 
used to chase down a possible bug.

The above occupies only ~1/2 of available space.

To avoid disturbing in *ANY* way the Windows install or my 
primary Debian install I do the following:

1. make the additional installs of Debian using "expert mode"
   to give me maximum control.
2. at the partitioning menu I chose manual to:
   a. chose destination partition of current install.
   b. flag the current swap partition as "Do Not Use"
  [The Jessie installer automatically reformats
   any existing swap partition, changing its UUID
   which can cause problems with other installs]. It suits
   me to not use any swap for my secondary installs. The
   installer will warn, but accept]
3. chose to install neither GRUB not LILO. That allows me to
   keep my existing GRUB menu. On reboot I run update-grub
   from my primary Debian install to add the latest install at
   the bottom of the menu.

I have never had any contact with Knoppix so do not know if a 
similar procedure could be followed. In any case remember to do a 
backup first.


HTH

can not set time

[Matthias Bodenbinder]

Hi,

I have a weird issue with one of my debian boxes (LMDE): I can not set the 
time. The time is off by ca. 14 min and whatever I try to fix it is failing. I 
tried ntp, ntpdate, date and rdate. Nothing helps.

ntpdate shows the offset but is not fixing it.

91# ntpdate 0.debian.pool.ntp.org
 4 Feb 14:03:55 ntpdate[8159]: step time server 85.114.132.52 offset 
-855.296824 sec


rdate is showing some interesting behaviour. If I run a command like "date && 
rdate -v  ptbtime1.ptb.de && date" to see the time before and after rdate, the 
output suggests that rdate was successful:

81# date && rdate -v  ptbtime1.ptb.de && date
Sat Feb  4 14:16:04 CET 2017
Sat Feb  4 14:01:49 CET 2017
rdate: adjust local clock by -855 seconds
Sat Feb  4 14:01:49 CET 2017

But in fact 1 second later the time is back to old values again:

82# date
Sat Feb  4 14:16:06 CET 2017


timedatectl is showing wrong time as well:

93# timedatectl
  Local time: Sat 2017-02-04 14:20:39 CET
  Universal time: Sat 2017-02-04 13:20:39 UTC
RTC time: Sat 2017-02-04 13:20:39
   Time zone: Europe/Berlin (CET, +0100)


But is should be:
  Local time: Sa 2017-02-04 14:06:25 CET
  Universal time: Sa 2017-02-04 13:06:25 UTC
RTC time: Sa 2017-02-04 13:06:25
   Time zone: Europe/Berlin (CET, +0100)


I am lost.

Matthias

Re: CUPS in stretch does NOT WORK - Ricoh printer SP112 SP112-su

[Roba]

Yes, this worked without specifying an ip just localhost:631

The upgrade was from jessie to stretch and I had never edited this file,
yesterday I didn't even know where it was.
If this line is by default in this file and this file pre-existed on
jessie how could that line be omitted?  Or was the upgrade from cups 1.7
to 2.2??  replacing this file?

My frustration as I recommend to others to leave their non-open non-free
systems and trying debian is that after a successful installation their
basic utilities (of an average Win7 user) are there.  No shell command
writing or editing script files.  It seems as this is not the case as it
is with 20% of packages installed not working with a particular desktop,
etc.

In the case of a near-sighted person leading the blind some experience
is not very confidence inspiring.  Most of the manuals have an extensive
administration and programmer experience as a prerequisite.  In other
words I have yet to find ONE debian manual page that explains one thing
without knowledge of many other things that appear as common knowledge
but are a foreign language to many of us mortals.  And it is getting
more complex instead of being simplified.

>In my _working_ CUPS on Jessie, I have :

>Listen /var/run/cups/cups.sock
>Listen 192.168.11.5:631

>which I find fascinating, as 192.168.11.5 is _NOT_ the IP address of my
>computer, yet somehow it works anyway. The port scan you did a reply or
>two ago showed you had something listening on UDP port 631, but nothing
>on TCP port 631, which is why printing is not working.

>Indulge us, and add a line to your cupsd.conf as follows:

>Listen localhost:631

>and restart CUPS and see what happens.

>Assuming that works, you are going to want to know why it was necessary
>to add it, and I am afraid I have no idea. I can tell you though, for
>what use this is, it is _NOT_ a direct cause of the wheezy --> jessie
>upgrade. I performed that upgrade (a good while ago, to be fair) and >did
>not experience this problem. So in the absence of better information >I'd
>have to guess something you did or something else you installed >resulted
>in this happening to your conf file. I really have no idea what that
>could be though.

>Mark


Mark Fletcher:
>In my _working_ CUPS on Jessie, I have :

Listen /var/run/cups/cups.sock
Listen 192.168.11.5:631

which I find fascinating, as 192.168.11.5 is _NOT_ the IP address of my
computer, yet somehow it works anyway. The port scan you did a reply or
two ago showed you had something listening on UDP port 631, but nothing
on TCP port 631, which is why printing is not working.

Indulge us, and add a line to your cupsd.conf as follows:

Listen localhost:631

and restart CUPS and see what happens.

Assuming that works, you are going to want to know why it was necessary
to add it, and I am afraid I have no idea. I can tell you though, for
what use this is, it is _NOT_ a direct cause of the wheezy --> jessie
upgrade. I performed that upgrade (a good while ago, to be fair) and did
not experience this problem. So in the absence of better information I'd
have to guess something you did or something else you installed resulted
in this happening to your conf file. I really have no idea what that
could be though.

Mark

Re: debconf

[Paulo Roberto Evangelista]

Adriano, muito obrigado!

Estava lendo a lista devel agora mesmo! :D

Encontrei esse link aqui  <
http://www.fifi.org/doc/debconf-doc/tutorial.html#AEN34>  e me ajudou
bastante!

Em 4 de fevereiro de 2017 09:03, Adriano Rafael Gomes 
escreveu:

> On Sat, Feb 04, 2017 at 08:23:09AM -0300, Paulo Roberto Evangelista wrote:
> > olá, todo mundo!
> >
> > Alguém sabe onde encontro uma documentação que detalhe o uso de debconf?
> > Quero automatizar a instalação de um pacote mas durante a instalação ele
> > faz algumas perguntas,  penso em utilizar o debconf para que eu não
> precise
> > de nenhuma entrada via teclado para as perguntas durante a instalação.
>
> Você pode tentar isto:
>
> https://lists.debian.org/debian-devel-portuguese/
> https://www.debian.org/doc/debian-policy/ch-binary.html#
> s-maintscriptprompt
> https://www.debian.org/doc/packaging-manuals/debconf_specification.html
> http://www.fifi.org/doc/debconf-doc/tutorial.html
> https://packages.debian.org/sid/debconf-doc
> https://wiki.debian.org/debconf
>

Re: debconf

[Adriano Rafael Gomes]

On Sat, Feb 04, 2017 at 08:23:09AM -0300, Paulo Roberto Evangelista wrote:
> olá, todo mundo!
> 
> Alguém sabe onde encontro uma documentação que detalhe o uso de debconf?
> Quero automatizar a instalação de um pacote mas durante a instalação ele
> faz algumas perguntas,  penso em utilizar o debconf para que eu não precise
> de nenhuma entrada via teclado para as perguntas durante a instalação.

Você pode tentar isto:

https://lists.debian.org/debian-devel-portuguese/
https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintscriptprompt
https://www.debian.org/doc/packaging-manuals/debconf_specification.html
http://www.fifi.org/doc/debconf-doc/tutorial.html
https://packages.debian.org/sid/debconf-doc
https://wiki.debian.org/debconf


signature.asc
Description: Digital signature

Re: 7->8: inexplicable difficulty discovering available package versions

[Martin Read]

On 04/02/17 07:30, David Christensen wrote:

On 02/03/17 11:04, Felix Miata wrote:

I just did an apt-get dist-upgrade to reach Jessie 8.7 from Wheezy.


I am of the opinion that attempting an in-place major version upgrade of
an operating system or a service is folly.


Perhaps - and yet, one of the requirements for Debian packages is that 
you should be able to do in-place upgrades in reasonable safety, and 
that if there are any substantial caveats to such an action when going 
from oldstable to stable, they need to be documented in the release notes.

Re: debconf

[Paulo Roberto Evangelista]

Realizei pesquisas no Google mas em nenhuma delas encontrei maiores
detalhes sobre a utilização do debconf.

Em 4 de fevereiro de 2017 08:23, Paulo Roberto Evangelista <
shellcl...@gmail.com> escreveu:

> olá, todo mundo!
>
> Alguém sabe onde encontro uma documentação que detalhe o uso de debconf?
> Quero automatizar a instalação de um pacote mas durante a instalação ele
> faz algumas perguntas,  penso em utilizar o debconf para que eu não precise
> de nenhuma entrada via teclado para as perguntas durante a instalação.
>

debconf

[Paulo Roberto Evangelista]

olá, todo mundo!

Alguém sabe onde encontro uma documentação que detalhe o uso de debconf?
Quero automatizar a instalação de um pacote mas durante a instalação ele
faz algumas perguntas,  penso em utilizar o debconf para que eu não precise
de nenhuma entrada via teclado para as perguntas durante a instalação.

Re: Advice / recommendations on Inexpensive Managed Ethernet Switches

[Mark Fletcher]

On Sat, Feb 04, 2017 at 10:56:50AM +0100, to...@tuxteam.de wrote:
> 
> On the contrary: I'd be ready to flame back. But I don't think anyone here
> would be willing to go beyond a little candle :)
> 
That gives me the mental picture of a "candle-war" -- 

"I think you are not completely correct!"

"Well, I think you are not quite thinking about the problem the right way!"

...

Mark

Re: 7->8: inexplicable difficulty discovering available package versions

[Eduardo M KALINOWSKI]

On 04-02-2017 05:30, David Christensen wrote:
> I am of the opinion that attempting an in-place major version upgrade
> of an operating system or a service is folly.  The only reliable
> method is to do a fresh install on another computer, and then migrate.

Whatever works for you. But keep in mind that debian does support in
place upgrades and offers support for that. I and many others have done
that successfully several times.


-- 
What one fool can do, another can.
-- Ancient Simian Proverb

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: How to enable SSH root access with password in jessie or stretch?

[Pierre Couderc]

On 02/04/2017 10:08 AM, Joe wrote:

On Sat, 4 Feb 2017 09:18:34 +0100
Pierre Couderc  wrote:


I know it is not secure.

I have soon set "PermitRootLogin yes" and restarted. In fact
PermitRootLogin was not soon present in my ssh_config file.

Thank you.


I think that ought to be enough, but clearly it isn't. It's a long time
since I used passwords in ssh.

One thing: is that a typo? The file you should have modified is
sshd_config, ssh_config is for connections from that machine to others.


Thank you very much...
It is not a typo : it is my mistake and the problem I have been looking 
from months

Re: Advice / recommendations on Inexpensive Managed Ethernet Switches

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, Feb 03, 2017 at 05:21:30PM -0300, Eike Lantzsch wrote:
> On Thursday, 2 February 2017 11:19:59 PYST rhkra...@gmail.com wrote:
> > I'm sending this to the Debian user list first, even though it is probably
> > somewhat OT.
> > 
> > Background: Recently I started monitoring how many packets are going through
> > my LAN to my ISP (Earthlink (DSL)).  I have (or maybe had) some thought
> > about considering a switch to HughesNet satelite service, which has some
> > low limits (before slowdown) on how many bytes you can download per month
> > (without looking, I think the limits are like 5, 10, and 15 GB).
> > 
> Excuse me please for writing this on a Debian list, but ... I see the flame 
> war 
> coming ...

Not from me. OpenBSD is free software, and while some might see me as GNU
zealot, free software is -- um -- free, and that is a Good Thing.

Technically, BSD is a very respectable choice too and a community to which
we, the Debian community owe a lot, especially in the realm of networking.
Just think SSH for one prominent (but not the only) example.

On the contrary: I'd be ready to flame back. But I don't think anyone here
would be willing to go beyond a little candle :)

- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliVpWIACgkQBcgs9XrR2kZjjQCeLgWjphoALR5V0UQoyfaCpaX2
McAAn2CGOz4ZT9tTjuIXTiGPAZlCqTJa
=W1gn
-END PGP SIGNATURE-

logrotate - got compressed log

[Kamil Jońca]

I have logrotate with config (excerpt)
--8<---cut here---start->8---
compress
delaycompress
dateext
mail root
compresscmd /usr/bin/xz
uncompresscmd /usr/bin/unxz
compressext .xz
compressoptions -9
tabooext +.dpkg-bak
minsize 1M
[...]
--8<---cut here---end--->8---

And since some days I started to receive *compressed* old syslog files
:( instead uncompressed ones. 

Nothing has happen in configuration.
The only change was logrotate upgrade, from 3.8.7 to 3.11.0
Can anyboty confirm that there is difference between these versions?
KJ


-- 
http://wolnelektury.pl/wesprzyj/teraz/
Since a politician never believes what he says, he is surprised
when others believe him.
-- Charles DeGaulle

Re: How to enable SSH root access with password in jessie or stretch?

[Joe]

On Sat, 4 Feb 2017 09:18:34 +0100
Pierre Couderc  wrote:

> I know it is not secure.
> 
> I have soon set "PermitRootLogin yes" and restarted. In fact 
> PermitRootLogin was not soon present in my ssh_config file.
> 
> Thank you.


I think that ought to be enough, but clearly it isn't. It's a long time
since I used passwords in ssh.

One thing: is that a typo? The file you should have modified is
sshd_config, ssh_config is for connections from that machine to others.

-- 
Joe 

How to enable SSH root access with password in jessie or stretch?

[Pierre Couderc]

I know it is not secure.

I have soon set "PermitRootLogin yes" and restarted. In fact 
PermitRootLogin was not soon present in my ssh_config file.


Thank you.


PC

Re: 7->8: inexplicable difficulty discovering available package versions

[Felix Miata]

David Christensen composed on 2017-02-03 23:30 (UTC-0800):


Felix Miata wrote:



I just did an apt-get dist-upgrade to reach Jessie 8.7 from Wheezy.



I am of the opinion that attempting an in-place major version upgrade of
an operating system or a service is folly.  The only reliable method is
to do a fresh install on another computer, and then migrate.


That sounds pretty much the opposite of the recommended installation method 
forSid - install prior release or unstable, then upgrade it to Sid.



This means you need at least three computers -- one that you are
migrating off, one that you are migrating onto, and one (or more) for
everything else you need to keep operational while you do the migration.
  Mobile racks and spare drives will help immensely.


I have lots of functioning computers, and a fair sized stash of extra HDs. All 
except one machine are multiboot. Installations average >10 per machine. I find 
upgrades are generally less painful that all the re-customization that fresh 
installs entail (especially when Zypper is the available upgrade tool). Clone 
partition, apply new UUID and label, reconfigure bootloader, fstab and sources, 
then upgrade. If there's a major malfunction, just re-clone and start over, not 
that big a deal. YMMV. :-D

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

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

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