Re: gstreamer-1.0/libgstlame.so what is this?

[A_Man_Without_Clue]

On 04/30/2018 11:39 AM, Andy Smith wrote:
> Hello,
> 
> On Mon, Apr 30, 2018 at 11:34:13AM +0900, A_Man_Without_Clue wrote:
>> E:
>> /tmp/apt-dpkg-install-6Cr5xr/03-gstreamer1.0-plugins-good_1.14.0-4_amd64.deb:
>> trying to overwrite
>> '/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstlame.so', which is also
>> in package gstreamer1.0-plugins-ugly:amd64 1:1.12.3-dmo1
> 
> I suspect that the "dmo" suffix indicates that this package was
> installed from "debian multimedia" which is not part of Debian. If
> so, you're on your own there. Maybe remove such packages and try
> again.
> 
> Cheers,
> Andy
> 


Thanks, seemed like I'd added multimedia repository which I now have
disabled. I just simply removed gstreamer then now I have no problem.
I don't even know what that was for.

Thank you.

M.W.C.

Re: Debian glossary?

[Andy Smith]

Hello,

On Mon, Apr 30, 2018 at 06:46:01AM -0500, Richard Owlett wrote:
> Man pages by their nature/purpose assume a certain level of expertise.
> They can be daunting for the uninitiated.
> 
> Comments?

https://www.greenend.org.uk/rjk/misc/nipple.html :
The only "intuitive" interface is the nipple. After that it's
all learned.

If learning about this stuff wasn't difficult, quite a few of us
would be out of a job. Something that's even harder than attaining
the knowledge is writing good documentation about the knowledge.
Something that's nearly impossible is writing good documentation
that meets the needs of readers with every level of expertise,
including "none".

The learning also never ends. Even if you get to the point of having
all your computers doing exactly what you want with software that
hasn't changed in a decade, someone comes along and invents a new
init system, or finds out that all CPUs made in the last 20 years
are insecure, or something.

So, get used to it, I guess? ;)

Cheers,
Andy

Instalar geforce 9400gt

[Lucas Rodrigues de Sá]

Boa noite pessoal,

Estou seguindo os passos do Debian Wik para instalar a placa supracitada e
não estou tendo sucesso.

Estou usando o Debian Jessie .

Logo após a instalação dos drivers a tá fica toda preta e não sei como
restaurar sem ter q formatar. Alguém pode me auxiliar na investigação do
erro?

Verifiquei que após a instalação do driver da um erro no carregamento do
kernel, porém não sei qual especificamente. Estou reformando e vou tentar
instalar novamente.

Atenciosamente,

Lucas

how to keep geoip database uptodate

[kamaraju kusumanchi]

How do I keep geoip database up to date on Debian stable? Currently, I
am not able to get information on some IP addresses. For example,

 % geoiplookup 45.229.2.42
GeoIP Country Edition: IP Address not found

I tried geoipupdate, but it is looking for a license.

 % geoipupdate -v
geoipupdate 2.3.1
Can't open license file /etc/GeoIP.conf
 % ls -al /etc/GeoIP.conf
ls: cannot access '/etc/GeoIP.conf': No such file or directory

% dpkg -l \*geoip\* | grep ^ii
ii  geoip-bin   1.6.9-4  amd64IP lookup command line
tools that use the GeoIP library
ii  geoip-database  20170512-1   all  IP lookup command line
tools that use the GeoIP library (country database)
ii  geoipupdate 2.3.1-1  amd64MaxMind GeoIP/GeoIP2
database updates
ii  libgeoip1:amd64 1.6.9-4  amd64non-DNS IP-to-country
resolver library

% cat /etc/debian_version
9.4


thanks
raju

-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

Re: messed up release in apt

[Brian]

On Tue 01 May 2018 at 09:18:56 -0500, David Wright wrote:

> On Tue 01 May 2018 at 08:11:28 (-0500), Anil Duggirala wrote:
> > > If it were my machine (so that if I sank it I would be the only one
> > > to
> > > go down with the ship), I might run:
> > > 
> > >  'apt-key update'
> > > 
> > 
> > When running that command I am getting :
> > Warning: 'apt-key update' is deprecated and should not be used anymore!
> > Note: In your distribution this command is a no-op and can therefore be
> > removed safely.
> > 
> > > after removing 
> > > 
> > >  '/etc/apt/trusted.gpg' 
> > > 
> > When you say removing you mean :
> > rm /etc/apt/trusted.gpg ?
> > 
> > I appreciate any other alternative procedure to correct this,
> > thanks,
> 
> I don't know if this rather long thread would help. It does appear
> that /etc/apt/trusted.gpg is no longer used, in favour of
> /etc/apt/trusted.gpg.d/ but if the former exists, it can cause
> problems. There's a new user on stretch called _apt but I don't
> know its function.

A security enhancement. _apt is an unprivileged user, allowing
sandboxed downloading. The user exists to protect against bugs
in the http protocol handler, ssl libraries, compressors, etc.
It also protects against permission issues elsewhere.

-- 
Brian.

Re: Changement de disque problématique

[BERTRAND Joël]

BERTRAND Joël a écrit :
>   Bonjour à tous,
> 
>   Un disque d'un volume raid6 vient de lâchement retourner au paradis des
> disques durs et j'ai décidé de le remplacer. Plus exactement, j'ai
> envoyé quelqu'un le changer.
> 
>   Il est parfaitement bien détecté par la carte Adaptec. Linux le détecte
> aussi au travers de la même carte :
> 
> [1.276579] aacraid :02:00.0: 64 Bit DAC enabled
> [1.296334] scsi host0: aacraid
> [1.318756] scsi 0:1:0:0: Direct-Access HGST HTS721010A9E630
> JB0O PQ: 0 ANSI: 5
> [1.319430] scsi 0:1:1:0: Direct-Access HGST HTS721010A9E630
> JB0O PQ: 0 ANSI: 5
> [1.320096] scsi 0:1:2:0: Direct-Access HGST HTS721010A9E630
> JB0O PQ: 0 ANSI: 5
> [1.320701] scsi 0:1:3:0: Direct-Access HGST HTS721010A9E630
> JB0O PQ: 1 ANSI: 5
> 
>   J'ai changé le 4e (que signifie PQ ?).
> 
>   Plus loin, dans le dmesg, j'ai un magnifique :
> 
> [   27.157820] sd 0:1:0:0: Attached scsi generic sg0 type 0
> [   27.157854] sd 0:1:1:0: Attached scsi generic sg1 type 0
> [   27.157894] sd 0:1:2:0: Attached scsi generic sg2 type 0
> [   27.157922] scsi 0:1:3:0: Attached scsi generic sg3 type 0
> [   27.157951] sd 2:0:0:0: Attached scsi generic sg4 type 0
> [   27.157977] sd 3:0:0:0: Attached scsi generic sg5 type 0
> [   27.158005] sr 6:0:0:0: Attached scsi generic sg6 type 5
> 
>   Et forcément, le disque n'est pas formatable. Il est accessible par
> /dev/sg3 :
> Root rayleigh:[/dev] > smartctl -a /dev/sg3
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-3-amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
> 
> === START OF INFORMATION SECTION ===
> Vendor:   HGST
> Product:  HTS721010A9E630
> Revision: JB0O
> User Capacity:1 000 204 886 016 bytes [1,00 TB]
> Logical block size:   512 bytes
> Rotation Rate:7200 rpm
> Form Factor:  2.5 inches
> Logical Unit id:  0x5000cca836cbd379
> Serial number:JS1007620V0H2W
> Device type:  disk
> Local Time is:Tue May  1 18:08:41 2018 CEST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
> Temperature Warning:  Disabled or Not Supported
> ...
> 
>   Mais il n'est pas reconnu comme un disque !... Je suppose que j'ai raté
> quelque chose.
> 
>   Merci de vos lumières,
> 
>   JKB
> 

Bon, je me réponds à moi-même après un moment de panique. Les cartes
Adaptec écrivent un bout de la configuration _sur_ le disque. L'état de
la grappe n'est pas seulement dans la carte. Le nouveau disque était
ready et non online.

./arcconf CREATE 1 JBOD 0 3 a résolu la chose sans même redémarrer.

Désolé pour le bruit.

JKB

-- 
Dr. KACHELHOFFER-BERTRAND Joël
Systella SAS, 7, la Sudrie 19130 VIGNOLS FRANCE
Tel.: +33 (0)6 16 01 80 60
http://www.systella.fr

Re: k3b não grava cd com usuário

[riesdra]

Tranquilo, obrigado.
--
Ricardo Libanio



 On Ter, 01 mai 2018 13:17:34 -0300 athenago...@gmail.com wrote 

Desculpe-me, Ricardo.
Não investiguei mais, porque estava ocupado terminando um trabalho.
Mas eu também uso aplicativos do kde (embora meu gerenciador de janelas seja o 
fluxbox), por isto ainda vou dar uma solução e reportar aqui.

Atenciosamente,
Atenágoras Souza Silva.

Em 1 de maio de 2018 13:13, riesdra  escreveu:
Deixei o k3b pra lá, estou usando o xfburn do xfce mesmo.

--
Ricardo Libanio



 On Ter, 01 mai 2018 02:28:23 -0300 paulo.p.olive...@sapo.pt wrote 


Eu uso o Brasero.

Abraço,

Paulo.

Às 01:10 de 01-05-2018, riesdra escreveu:
Eu deixei ele com 777 e não funcionou também.
--
Ricardo Libanio



 On Seg, 30 abr 2018 22:08:50 -0300  athenago...@gmail.com 
wrote 

A outra solução que encontrei para isto está na alteração de permissões para o 
programa wodim:
chmod +s wodim

Veja a discussão abaixo:
https://ubuntuforums.org/archive/index.php/t-1291337.html

Atenciosamente,
Atenágoras Souza Silva.


Em 30 de abril de 2018 21:44, riesdra  escreveu:
meu usuário já esta no grupo cdrom.

--
Ricardo Libanio




 Em Seg, 30 abr 2018 21:33:31 -0300 Atenágoras Silva 
escreveu  
Acho que você precisa ter o usuário adicionado no grupo cdrom para usar k3b sem 
problemas. Só que se for esse o problema, você não deveria ter conseguido com o 
xfburn.

2018-04-30 21:21 GMT-03:00 riesdra :
não existe grupo dev.

--
Ricardo Libanio




 Em Seg, 30 abr 2018 21:18:46 -0300 riesdra escreveu  
ao cdrom já esta, vou adicionar ao dev.

--
Ricardo Libanio




 Em Seg, 30 abr 2018 21:11:04 -0300 China escreveu  
Adiciona o usuário ao grupo dev e cdrom.

Em Seg, 30 de abr de 2018 20:32, riesdra  escreveu:
Olá

estou tendo problema para gravar cds com k3b, esta dando erro no cdrecord, diz 
que o cdrecord não tem permissão para abrir dispositivo, o erro que na 
depuração é

Devices

---

HL-DT-ST DVDRAM GUE0N T.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, 
DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R sequencial, DVD-R de 
dupla camada sequencial, DVD-R de dupla camada com salto, DVD-RAM, DVD-RW em 
sobrescrita restrita, DVD-RW sequencial, DVD+RW, DVD+R, DVD+R de dupla camada, 
CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, 
RAW/R96R, Sobrescrita restrita, Salto de camada] [%7]


K3b::IsoImager

---

mkisofs print size result: 341524 (699441152 bytes)


System

---

K3b Version: 17.8.3

KDE Version: 5.37.0

Qt Version: 5.10.1

Kernel: 4.15.0-3-amd64


Used versions

---

mkisofs: 1.1.11

cdrecord: 1.1.11


cdrecord

---

/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK 
limits.

/usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 
Bytes on /dev/zero.

TOC Type: 1 = CD-ROM


cdrecord command:

---

/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=10 -sao driveropts=burnfree 
-force -data -tsize=341524s -


mkisofs

---

341524

I: -input-charset not specified, using utf-8 (detected in locale settings)


mkisofs calculate size command:

---

/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid mp3 -volset 
-appid K3B THE CD KREATOR (C) 1998-2017 SEBASTIAN TRUEG, MICHAL MALEK AND 
LESLIE ZHAI -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 
-sort /tmp/k3b.pKzwBG -rational-rock -hide-list /tmp/k3b.pVdrhm -joliet 
-joliet-long -hide-joliet-list /tmp/k3b.PzLFro -no-cache-inodes 
-full-iso9660-filenames -iso-level 3 -path-list /tmp/k3b.FqXJdE


mkisofs command:

---

/usr/bin/genisoimage -gui -graft-points -volid mp3 -volset -appid K3B THE CD 
KREATOR (C) 1998-2017 SEBASTIAN TRUEG, MICHAL MALEK AND LESLIE ZHAI -publisher 
-preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/k3b.tiGsmk 
-rational-rock -hide-list /tmp/k3b.oAesHn -joliet -joliet-long 
-hide-joliet-list /tmp/k3b.IDFRXl -no-cache-inodes -full-iso9660-filenames 
-iso-level 3 -path-list /tmp/k3b.PHhDbR


se alguém souber como posso resolver isto, desde já agradeço a atenção de todos.




--
Ricardo Libanio
















-- 
Paulo Oliveira
Contactos:
paulo.p.olive...@sapo.pt
Telm: +351 912887324/+351 964088335

Re: k3b não grava cd com usuário

[Atenágoras Silva]

Desculpe-me, Ricardo.
Não investiguei mais, porque estava ocupado terminando um trabalho.
Mas eu também uso aplicativos do kde (embora meu gerenciador de janelas
seja o fluxbox), por isto ainda vou dar uma solução e reportar aqui.

Atenciosamente,
Atenágoras Souza Silva.

Em 1 de maio de 2018 13:13, riesdra  escreveu:

> Deixei o k3b pra lá, estou usando o xfburn do xfce mesmo.
>
> --
>
>
>
> *Ricardo Libanio*
>
>  On Ter, 01 mai 2018 02:28:23 -0300 * paulo.p.olive...@sapo.pt
>  * wrote 
>
>
> Eu uso o Brasero.
>
> Abraço,
>
> Paulo.
>
> Às 01:10 de 01-05-2018, riesdra escreveu:
>
> Eu deixei ele com 777 e não funcionou também.
> --
>
>
>
> *Ricardo Libanio *
>
>  On Seg, 30 abr 2018 22:08:50 -0300 * athenago...@gmail.com
>  * wrote 
>
> A outra solução que encontrei para isto está na alteração de permissões
> para o programa wodim:
> chmod +s wodim
>
> Veja a discussão abaixo:
> https://ubuntuforums.org/archive/index.php/t-1291337.html
>
> Atenciosamente,
> Atenágoras Souza Silva.
>
>
> Em 30 de abril de 2018 21:44, riesdra  escreveu:
>
> meu usuário já esta no grupo cdrom.
>
> --
>
>
>
> *Ricardo Libanio *
>
>
>  Em Seg, 30 abr 2018 21:33:31 -0300 *Atenágoras
> Silva>* escreveu 
>
> Acho que você precisa ter o usuário adicionado no grupo cdrom para usar
> k3b sem problemas. Só que se for esse o problema, você não deveria ter
> conseguido com o xfburn.
>
> 2018-04-30 21:21 GMT-03:00 riesdra :
>
> não existe grupo dev.
>
> --
>
>
>
> *Ricardo Libanio *
>
>
>  Em Seg, 30 abr 2018 21:18:46 -0300 *riesdra >* escreveu 
>
> ao cdrom já esta, vou adicionar ao dev.
>
> --
>
>
>
> *Ricardo Libanio *
>
>
>  Em Seg, 30 abr 2018 21:11:04 -0300 *China >* escreveu 
>
> Adiciona o usuário ao grupo dev e cdrom.
>
> Em Seg, 30 de abr de 2018 20:32, riesdra  escreveu:
>
> Olá
>
> estou tendo problema para gravar cds com k3b, esta dando erro no cdrecord,
> diz que o cdrecord não tem permissão para abrir dispositivo, o erro que na
> depuração é
>
> Devices
>
> ---
>
> HL-DT-ST DVDRAM GUE0N T.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R,
> DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R sequencial,
> DVD-R de dupla camada sequencial, DVD-R de dupla camada com salto, DVD-RAM,
> DVD-RW em sobrescrita restrita, DVD-RW sequencial, DVD+RW, DVD+R, DVD+R de
> dupla camada, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R,
> RAW/R16, RAW/R96P, RAW/R96R, Sobrescrita restrita, Salto de camada] [%7]
>
>
> K3b::IsoImager
>
> ---
>
> mkisofs print size result: 341524 (699441152 bytes)
>
>
> System
>
> ---
>
> K3b Version: 17.8.3
>
> KDE Version: 5.37.0
>
> Qt Version: 5.10.1
>
> Kernel: 4.15.0-3-amd64
>
>
> Used versions
>
> ---
>
> mkisofs: 1.1.11
>
> cdrecord: 1.1.11
>
>
> cdrecord
>
> ---
>
> /usr/bin/wodim: Operation not permitted. Warning: Cannot raise
> RLIMIT_MEMLOCK limits.
>
> /usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for
> 12587008 Bytes on /dev/zero.
>
> TOC Type: 1 = CD-ROM
>
>
> cdrecord command:
>
> ---
>
> /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=10 -sao
> driveropts=burnfree -force -data -tsize=341524s -
>
>
> mkisofs
>
> ---
>
> 341524
>
> I: -input-charset not specified, using utf-8 (detected in locale settings)
>
>
> mkisofs calculate size command:
>
> ---
>
> /usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid mp3
> -volset -appid K3B THE CD KREATOR (C) 1998-2017 SEBASTIAN TRUEG, MICHAL
> MALEK AND LESLIE ZHAI -publisher -preparer -sysid LINUX -volset-size 1
> -volset-seqno 1 -sort /tmp/k3b.pKzwBG -rational-rock -hide-list
> /tmp/k3b.pVdrhm -joliet -joliet-long -hide-joliet-list /tmp/k3b.PzLFro
> -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list
> /tmp/k3b.FqXJdE
>
>
> mkisofs command:
>
> ---
>
> /usr/bin/genisoimage -gui -graft-points -volid mp3 -volset -appid K3B THE
> CD KREATOR (C) 1998-2017 SEBASTIAN TRUEG, MICHAL MALEK AND LESLIE ZHAI
> -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort
> /tmp/k3b.tiGsmk -rational-rock -hide-list /tmp/k3b.oAesHn -joliet
> -joliet-long -hide-joliet-list /tmp/k3b.IDFRXl -no-cache-inodes
> -full-iso9660-filenames -iso-level 3 -path-list /tmp/k3b.PHhDbR
>
>
> se alguém souber como posso resolver isto, desde já agradeço a atenção de
> todos.
>
>
>
> --
>
>
>
> *Ricardo Libanio *
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> Paulo Oliveira
> Contactos:
> paulo.p.olive...@sapo.pt
> Telm: +351 912887324/+351 964088335
>
>
>

Re: k3b não grava cd com usuário

[riesdra]

Deixei o k3b pra lá, estou usando o xfburn do xfce mesmo.
--
Ricardo Libanio



 On Ter, 01 mai 2018 02:28:23 -0300 paulo.p.olive...@sapo.pt wrote 

Eu uso o Brasero.

Abraço,

Paulo.

Às 01:10 de 01-05-2018, riesdra escreveu:
Eu deixei ele com 777 e não funcionou também.
--
Ricardo Libanio



 On Seg, 30 abr 2018 22:08:50 -0300 athenago...@gmail.com wrote 

A outra solução que encontrei para isto está na alteração de permissões para o 
programa wodim:
chmod +s wodim

Veja a discussão abaixo:
https://ubuntuforums.org/archive/index.php/t-1291337.html

Atenciosamente,
Atenágoras Souza Silva.


Em 30 de abril de 2018 21:44, riesdra  escreveu:
meu usuário já esta no grupo cdrom.

--
Ricardo Libanio




 Em Seg, 30 abr 2018 21:33:31 -0300 Atenágoras Silva 
escreveu  
Acho que você precisa ter o usuário adicionado no grupo cdrom para usar k3b sem 
problemas. Só que se for esse o problema, você não deveria ter conseguido com o 
xfburn.

2018-04-30 21:21 GMT-03:00 riesdra :
não existe grupo dev.

--
Ricardo Libanio




 Em Seg, 30 abr 2018 21:18:46 -0300 riesdra escreveu  
ao cdrom já esta, vou adicionar ao dev.

--
Ricardo Libanio




 Em Seg, 30 abr 2018 21:11:04 -0300 
  China 
  escreveu  
Adiciona o usuário ao grupo dev e cdrom.

Em Seg, 30 de abr de 2018 20:32, riesdra  escreveu:
Olá

estou tendo problema para gravar cds com k3b, esta dando erro no cdrecord, diz 
que o cdrecord não tem permissão para abrir dispositivo, o erro que na 
depuração é

Devices

---

HL-DT-ST DVDRAM GUE0N T.02 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, 
DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R sequencial, DVD-R de 
dupla camada sequencial, DVD-R de dupla camada com salto, DVD-RAM, DVD-RW em 
sobrescrita restrita, DVD-RW sequencial, DVD+RW, DVD+R, DVD+R de dupla camada, 
CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, 
RAW/R96R, Sobrescrita restrita, Salto de camada] [%7]


K3b::IsoImager

---

mkisofs print size result: 341524 (699441152 bytes)


System

---

K3b Version: 17.8.3

KDE Version: 5.37.0

Qt Version:   5.10.1

Kernel: 4.15.0-3-amd64


Used versions

---

mkisofs: 1.1.11

cdrecord: 1.1.11


cdrecord

---

/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK 
limits.

/usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 
Bytes on /dev/zero.

TOC Type: 1 = CD-ROM


cdrecord command:

---

/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=10 -sao driveropts=burnfree 
-force -data -tsize=341524s -


mkisofs

---

341524

I: -input-charset not specified, using utf-8
   (detected in locale settings)


mkisofs calculate size command:

---

/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid   
mp3 -volset -appid K3B THE CD 
KREATOR (C) 1998-2017 SEBASTIAN TRUEG, MICHAL MALEK AND LESLIE ZHAI -publisher 
-preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/k3b.pKzwBG 
-rational-rock -hide-list /tmp/k3b.pVdrhm -joliet -joliet-long 
-hide-joliet-list /tmp/k3b.PzLFro -no-cache-inodes -full-iso9660-filenames 
-iso-level 3 -path-list /tmp/k3b.FqXJdE


mkisofs command:

---

/usr/bin/genisoimage -gui -graft-points -volid mp3 -volset -appid K3B THE CD 
KREATOR (C) 1998-2017 SEBASTIAN TRUEG, MICHAL MALEK AND LESLIE ZHAI -publisher 
-preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/k3b.tiGsmk 
-rational-rock -hide-list /tmp/k3b.oAesHn -joliet -joliet-long 
-hide-joliet-list /tmp/k3b.IDFRXl -no-cache-inodes -full-iso9660-filenames 
-iso-level 3 -path-list /tmp/k3b.PHhDbR


se alguém souber como posso resolver isto, desde já agradeço a atenção de todos.




--
Ricardo Libanio
















-- 
Paulo Oliveira
Contactos:
paulo.p.olive...@sapo.pt
Telm: +351 912887324/+351 964088335

Changement de disque problématique

[BERTRAND Joël]

Bonjour à tous,

Un disque d'un volume raid6 vient de lâchement retourner au paradis des
disques durs et j'ai décidé de le remplacer. Plus exactement, j'ai
envoyé quelqu'un le changer.

Il est parfaitement bien détecté par la carte Adaptec. Linux le détecte
aussi au travers de la même carte :

[1.276579] aacraid :02:00.0: 64 Bit DAC enabled
[1.296334] scsi host0: aacraid
[1.318756] scsi 0:1:0:0: Direct-Access HGST HTS721010A9E630
JB0O PQ: 0 ANSI: 5
[1.319430] scsi 0:1:1:0: Direct-Access HGST HTS721010A9E630
JB0O PQ: 0 ANSI: 5
[1.320096] scsi 0:1:2:0: Direct-Access HGST HTS721010A9E630
JB0O PQ: 0 ANSI: 5
[1.320701] scsi 0:1:3:0: Direct-Access HGST HTS721010A9E630
JB0O PQ: 1 ANSI: 5

J'ai changé le 4e (que signifie PQ ?).

Plus loin, dans le dmesg, j'ai un magnifique :

[   27.157820] sd 0:1:0:0: Attached scsi generic sg0 type 0
[   27.157854] sd 0:1:1:0: Attached scsi generic sg1 type 0
[   27.157894] sd 0:1:2:0: Attached scsi generic sg2 type 0
[   27.157922] scsi 0:1:3:0: Attached scsi generic sg3 type 0
[   27.157951] sd 2:0:0:0: Attached scsi generic sg4 type 0
[   27.157977] sd 3:0:0:0: Attached scsi generic sg5 type 0
[   27.158005] sr 6:0:0:0: Attached scsi generic sg6 type 5

Et forcément, le disque n'est pas formatable. Il est accessible par
/dev/sg3 :
Root rayleigh:[/dev] > smartctl -a /dev/sg3
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-3-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:   HGST
Product:  HTS721010A9E630
Revision: JB0O
User Capacity:1 000 204 886 016 bytes [1,00 TB]
Logical block size:   512 bytes
Rotation Rate:7200 rpm
Form Factor:  2.5 inches
Logical Unit id:  0x5000cca836cbd379
Serial number:JS1007620V0H2W
Device type:  disk
Local Time is:Tue May  1 18:08:41 2018 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning:  Disabled or Not Supported
...

Mais il n'est pas reconnu comme un disque !... Je suppose que j'ai raté
quelque chose.

Merci de vos lumières,

JKB

Re: messed up release in apt

[Jimmy Johnson]

On 05/01/2018 06:11 AM, Anil Duggirala wrote:

If it were my machine (so that if I sank it I would be the only one
to
go down with the ship), I might run:

  'apt-key update'



When running that command I am getting :
Warning: 'apt-key update' is deprecated and should not be used anymore!
Note: In your distribution this command is a no-op and can therefore be
removed safely.


after removing

  '/etc/apt/trusted.gpg'


When you say removing you mean :
rm /etc/apt/trusted.gpg ?

I appreciate any other alternative procedure to correct this,
thanks,



If you have a desktop and Synaptic installed you can do all the things 
you want to do in Synaptic, like force a different version and 
reinstalling the keyring or installing distro-info.


Cheers,
--
Jimmy Johnson

Devuan ASCII - TDE Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

Re: messed up release in apt

[David Wright]

On Tue 01 May 2018 at 08:11:28 (-0500), Anil Duggirala wrote:
> > If it were my machine (so that if I sank it I would be the only one
> > to
> > go down with the ship), I might run:
> > 
> >  'apt-key update'
> > 
> 
> When running that command I am getting :
> Warning: 'apt-key update' is deprecated and should not be used anymore!
> Note: In your distribution this command is a no-op and can therefore be
> removed safely.
> 
> > after removing 
> > 
> >  '/etc/apt/trusted.gpg' 
> > 
> When you say removing you mean :
> rm /etc/apt/trusted.gpg ?
> 
> I appreciate any other alternative procedure to correct this,
> thanks,

I don't know if this rather long thread would help. It does appear
that /etc/apt/trusted.gpg is no longer used, in favour of
/etc/apt/trusted.gpg.d/ but if the former exists, it can cause
problems. There's a new user on stretch called _apt but I don't
know its function.

https://lists.debian.org/debian-user/2017/07/msg00289.html

BTW when someone writes "remove file foo", it's generally safer
to interpret this as "mv -i foo some-safe-hidden-place" rather
than destroying its contents altogether. The same goes for
directories, move them rather than deleting them.

A lot of configuration files have rather strict naming requirements
which makes them very easy to hide.

Cheers,
David.

Re: messed up release in apt

[Curt]

On 2018-05-01, Anil Duggirala  wrote:
>> If it were my machine (so that if I sank it I would be the only one
>> to
>> go down with the ship), I might run:
>> 
>>  'apt-key update'
>> 
>
> When running that command I am getting :
> Warning: 'apt-key update' is deprecated and should not be used anymore!
> Note: In your distribution this command is a no-op and can therefore be
> removed safely.

I guess I gave you some (obsolete) bad advice.

I don't know what the solution to your problem is because I don't know
what is provoking it.  

My idea was to regenerate the '/etc/apt/trusted.gpg' file; it appears
'apt-key update' is not (no longer?) a secure way of doing so, thus the
deprecation.

>> after removing 
>> 
>>  '/etc/apt/trusted.gpg' 
>> 
> When you say removing you mean :
> rm /etc/apt/trusted.gpg ?

I should have told you to back it up first.

> I appreciate any other alternative procedure to correct this,
> thanks,

I can only think of reinstalling the 'debian-archive-keyring'. Of course
if apt is inoperable you'll have to download the Stretch package and
'dpkg -i'... 

But as I've already put my foot in my mouth...

-- 

Re: messed up release in apt

[Anil Duggirala]

> If it were my machine (so that if I sank it I would be the only one
> to
> go down with the ship), I might run:
> 
>  'apt-key update'
> 

When running that command I am getting :
Warning: 'apt-key update' is deprecated and should not be used anymore!
Note: In your distribution this command is a no-op and can therefore be
removed safely.

> after removing 
> 
>  '/etc/apt/trusted.gpg' 
> 
When you say removing you mean :
rm /etc/apt/trusted.gpg ?

I appreciate any other alternative procedure to correct this,
thanks,

Re: messed up release in apt

[Anil Duggirala]

> By old, I was referring to sources.list with jessie backports. I wold
> do
> that to make sure that apt will clean up all dependencies for Wine in
> jessie backports. 

I thought that was what you meant, I did as you instructed. Just trying
to get rid of this "key" error now.
thanks a lot,

Re: Debian glossary?

[songbird]

Brian wrote:
...
> Is there an advantage in using noauto *and* nofail?

  i leave nofail there as a reminder that i don't 
consider that partition important enough to be a 
fatal error even if i temporarily remove or change 
the noauto.

  having been bitten once i tend to be more 
cautious on subsequent outings...


  songbird

Re: Debian glossary?

[Brian]

On Tue 01 May 2018 at 07:28:43 -0400, songbird wrote:

> Gene Heskett wrote:
> ...
> > Let me clarify that, to a right Pain In The Ass when trying to write an 
> > armhf or arm64 systen to its boot u-sd card. They grab the card the 
> > instant its plugged in and then dd has a hell of a time trying to write 
> > to a mounted device.
> 
>   noauto is a frequently used option here along with nofail
> (in fstab).  if armhf or arm64 have broken mount commands 
> is not something i can answer...

Is there an advantage in using noauto *and* nofail?

-- 
Brian.

pinfo a very useful command

[songbird]

  thanks for the mention of it.  bonus day here IMO
(anytime i find a more useful interface than something
else i rarely use).


  and for Richard,

  reading through the output of:

pinfo coreutils

  will give you a good boost of basic command line 
related knowlege.  :)


  songbird

Re: Debian glossary?

[songbird]

Gene Heskett wrote:
...
> Let me clarify that, to a right Pain In The Ass when trying to write an 
> armhf or arm64 systen to its boot u-sd card. They grab the card the 
> instant its plugged in and then dd has a hell of a time trying to write 
> to a mounted device.

  noauto is a frequently used option here along with nofail
(in fstab).  if armhf or arm64 have broken mount commands 
is not something i can answer...


  songbird

Re: Systemd no m'atura un servei

[Alex Muntada]

Hola Narcis,

> També hi ha el cas que ara m'ocupa d'un servei que no atura a
> temps tots els processos i accions (timeout), amb la qual cosa,
> puc necessitar fer «stop» per segona vegada, quan Systemd pensa
> que l'estat és de no iniciat.

Si el servei no atura a temps tots els processos i accions el
primer cop per timeout, per què creus que serà suficient fer-ho
una segona vegada? No podria donar-se el cas que també salti el
timeout i aleshores tampoc et serviria el ExecStopPost?

Sense conèixer els detalls de fons, la meva intuïció em diu que
caldria atacar el problema des d'algun angle diferent.

Salut,
Alex



signature.asc
Description: PGP signature

Re: duckduckgo en français ?

[F. Dubois]

Le 01/05/2018 à 10:33, Pierre Frenkiel a écrit :

bonjour,
Quelqu'un connait-il un moyen de configurer duckduckgo pour qu'il donne
des réponses en français?

Cordialement,


Bonjour, lors de l'installation dans firefox j'avais sélectionné

DDuckGo_ssl_fr

au lieu de

DuckDuckGo

dans les préférences de firefox

about:preferences#search

Les réponses sont en français par défaut et le canard me parle en français.

Voilà.

Bonne journée

Fabien

Re: duckduckgo en français ?

[bruno volpi]

salut,

quand tu fais une recherche  en haut à droite de ta page click sur les 
trois barres  et choisis autres paramètres.


configure duckduckgo comme tu veux

Slts


Le 01/05/2018 à 10:41, Raphaël POITEVIN a écrit :

Bonjour,

Pierre Frenkiel  writes:

Quelqu'un connait-il un moyen de configurer duckduckgo pour qu'il donne
des réponses en français?

https://duckduckgo.com/bang?q=!lang

Re: duckduckgo en français ?

[Raphaël POITEVIN]

Bonjour,

Pierre Frenkiel  writes:
> Quelqu'un connait-il un moyen de configurer duckduckgo pour qu'il donne
> des réponses en français?

https://duckduckgo.com/bang?q=!lang
-- 
Raphaël

Re: duckduckgo en français ?

[Yann Serre]

Je pense très fort à canardcanardva, mais je vais garder ça pour moi.
Bon 1er mai

Le 01/05/2018 à 10:33, Pierre Frenkiel a écrit :

bonjour,
Quelqu'un connait-il un moyen de configurer duckduckgo pour qu'il donne
des réponses en français?

Cordialement,
--
Pierre Frenkiel

duckduckgo en français ?

[Pierre Frenkiel]

bonjour,
Quelqu'un connait-il un moyen de configurer duckduckgo pour qu'il donne
des réponses en français?

Cordialement,
--
Pierre Frenkiel

Re: messed up release in apt

[Curt]

On 2018-04-30, Anil Duggirala  wrote:
>
> I  removed all backported packages. Then did apt-get autoremove. Then
> removed the jessie-backports line from sources.list. I appear to have
> come back to my original system. However I am now getting an error on
> apt update.
> W: http://security.debian.org/debian-security/dists/stretch/updates/InR
> elease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as
> the file is not readable by user '_apt' executing apt-key.
> W: http://ftp.us.debian.org/debian/dists/stretch-updates/InRelease: The
> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
> W: http://ftp.us.debian.org/debian/dists/stretch/Release.gpg: The
> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.
>
> Any help on that?
> thanks!
>

I'm uncertain.

If it were my machine (so that if I sank it I would be the only one to
go down with the ship), I might run:

 'apt-key update'

after removing 

 '/etc/apt/trusted.gpg' 

This gleaned from the innertubes.

Maybe someone more knowledgable will pipe up.

-- 
"Three prisoners were locked in a cell. When the largest of them finished his
food, he immediately ate the others. Too bad. An apostrophe in the right place
might have prevented a horrible crime." Joe Gunn

Re: messed up release in apt

[Dejan Jocic]

On 30-04-18, Anil Duggirala wrote:
> > I would first use old sources.list to purge wine and follow it up
> > with
> > autoremove. But after that new, this time intended and correct,
> > sources.list with apt-get should solve problem.
> > 
> 
> When you say "old" do you mean the sources.list without the jessie
> backports entry? Could you explain to me why exactly you would do that,
> thanks a lot for your help
> 

By old, I was referring to sources.list with jessie backports. I wold do
that to make sure that apt will clean up all dependencies for Wine in
jessie backports. It is probably not needed and it is more than likely
overkill, but I'm always bit of paranoid when it comes to mixing up
things in sources.list, specially when backports are involved. Simply
changing your sources.list to correct backports and then doing update
and upgrade with apt should get you version of Wine with dependencies
for stretch backports. 

Sorry for possible confusion and for not explaining it bit better in
first place.