(deb-cat) Desfragmentacio de l'arrencada

[Narcis Garcia]

Quan un ordinador arrenca, executa programes i aquests carreguen
llibreries i fitxers d'arreu del volum de disc.
Això produeix lectures aleatòries de centenars de fitxers amb els blocs
dispersos per tota la unitat ja que, quan es desfragmenta un disc dur,
la única cosa que s'ordena és que cada fitxer tingui els seus blocs de
dades contínus en el disc.

És a dir, podem tenir fitxers emmagatzemats com a lletres:
A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z

Però l'arrencada carrega per exemple el gestor d'arrencada (A) el qual
carrega el sistema del nucli (B), i el qual aleshores demana fitxers
d'arreu com R, J, Y, D, K per la qual cosa el capçal d'un disc dur no fa
més que canviar de posició tota l'estona i fent que la càrrega sigui
molt més lenta del què el disc seria capaç de transmetre seqüencialment.
Això es nota molt amb el soroll d'un disc dur quan arrenca el sistema.

L'ideal en aquest exemple seria poder reorganitzar els blocs del disc així:
A,B,R,J,Y,D,K, C,E,F,G,H,I,L,M,N,O,P,Q,S,T,U,V,W,X,Z
De manera que de la A a la K es llegís tot sense interrupció.

Hi ha alguna eina que faciliti això per accelerar l'arrencada?

Gràcies.

-- 

Narcis Garcia

__
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

Re: Got a machine name problem

[Gene Heskett]

On Tuesday 23 February 2021 23:54:03 Stefan Monnier wrote:

> >> Then reboot and cross your fingers.
> >
> > Arthritis at 86 is beginning to make that painful. :(
>
> I don't believe in crossing fingers either  FWIW, I pick my nose
> instead, and I think it works just as well (but be careful not to do
> that right after chopping some habanero),
>
>
> Stefan

And that rather sounds like the voice of experience :(

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Got a machine name problem

[David Wright]

On Tue 23 Feb 2021 at 20:21:41 (-0600), Tom Browder wrote:
> On Tue, Feb 23, 2021 at 19:36 David Wright wrote:
> > On Tue 23 Feb 2021 at 20:05:11 (-0500), Gene Heskett wrote:
> > > On Tuesday 23 February 2021 14:29:01 Tom Browder wrote:
> 
> ...
> 
> > > > I also edit /etc/hosts and make the first couple of lines look like
> > > > this:
> > > >
> > > > 127.0.0.1 localhost.localdomain.com   localhost
> > > > 127.0.1.1 TLM.geneslinuxbox.netTLM
> 
> 
> David, you got me. I put those lines in years ago (on some person's
> recommendation), while I was still running pre-Debian 4 (probably Redhat in
> the box days).
> 
> It works and that's all I can say.

Sorry, I didn't spot it was part of your quote because of gene in
the second line. Using RedHat might explain the localhost.localdomain,
but not the addition of .com. AIUI RedHat's addition of
localhost.localdomain was the main reason that Debian inserted
it, only to remove it again. I think localhost, on its own,
has been recommended for years. RFC 1912 dates from 1996.

Following the addition, there was a discussion on devel,
which I understood to conclude with the sentiments in
https://lists.debian.org/debian-devel/2005/10/msg00572.html
and its removal.

On Tue 23 Feb 2021 at 17:55:40 (-0800), David Christensen wrote:
> 
> Changing the hostname on a Debian system is a good way to gain an
> appreciation for DRY:
> 
> https://en.wikipedia.org/wiki/Don't_repeat_yourself
> 
> I see that several readers have already respond with pieces of the
> following.  You might want to check the whole shopping list:
> 
> https://wiki.debian.org/Hostname
> 
> If and when you get tired of looking for needles in the haystack,
> and/or you find them inside binary files that you dare not edit, you
> may realize that your best bet is to backup, wipe, reinstall with the
> new hostname, and restore.  Or, you could just do that first and
> forget about searching the haystack.

A little OTT, but if that's the case, then all the more reason to read
RFC 1178 *before* you name the machine at all, and never change it.
Of course, you can always rotate that to 8117 if you're intensely private.

Cheers,
David.

Re: Got a machine name problem

[Stefan Monnier]

>> Then reboot and cross your fingers.
> Arthritis at 86 is beginning to make that painful. :(

I don't believe in crossing fingers either  FWIW, I pick my nose
instead, and I think it works just as well (but be careful not to do
that right after chopping some habanero),


Stefan

Re: Got a machine name problem

[Gene Heskett]

On Tuesday 23 February 2021 20:35:54 David Wright wrote:

> On Tue 23 Feb 2021 at 20:05:11 (-0500), Gene Heskett wrote:
> > On Tuesday 23 February 2021 14:29:01 Tom Browder wrote:
> > > On Tue, Feb 23, 2021 at 11:59 AM Gene Heskett wrote: ...
> > >
> > > > Nothing I do survives a reboot, so what do I do to actually
> > > > rename the machine and make it stick? Hopefully without losiing
> > > > the networking
> > >
> > > Hey, Gene.  I usually have to fiddle around a little, but I've
> > > always had success on Debian this way (as root):
> > >
> > > # hostname TLM
> > >
> > >edit /etc/hostname and set the desired name to TLM if it's not
> > > already changed
> > >
> > > I also edit /etc/hosts and make the first couple of lines look
> > > like this:
> > >
> > > 127.0.0.1 localhost.localdomain.com   localhost
> > > 127.0.1.1 TLM.geneslinuxbox.netTLM
> >
> > The first line is std here.
> >
> > Why should it have the 2nd one?
>
> If some software wants to know the IP address of TLM before the
> network is up, there's no point in handing it 192.168.M.N,
> so you use a loopback address to itself.
>
> However, putting TLM on the first line can apparently make
> localhost.localdomain into the canonical name of the system,
> which is probably not what you want.
>
> BTW I don't know where your .com came from in the first line.
>
Not my first line, thats from someone elses reply.
Actually, the domain name here is sick bird out on the net, but to linux 
its just a unique text string. I have known some of the smarter animals 
we share this planet with, and have witnessed horses that had been to 
school, and watching one of them work one Sunday morning certainly was 
an education. He knew what his job was with or without a saddle warmer 
on board, and he understood his job was easier as a 900 lb quarterhorse 
without 235 lbs of Bobby in the saddle, so the rest of the morning all 
Bobby had to do was look at a calf that needed branded and vaccinated 
(my job was running the black leg sringe) and that horse would go get 
that calf and run it into Bobby's waiting loop for the takedown. And 
I've met a sorta tame coyote that was easily the smartest looks like a 
dog, critter ever. Lady was picky who she was friends with, but she  
could also do simple math by barking the number of the answer times.

So my local domainname is coyote.den. Sometimes its unreal how you 
remember such details 40+ years later. Lets just say its been quite a 
ride the last 80 some years.

> Cheers,
> David.


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

[BUG REPORT] luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot convert 'nil' to 'unsigned short'

[Tiezhu Yang]

(1) Background
Source: luajit
Version: luajit_2.1.0~beta3+dfsg-5.3_mips64el.deb
Severity: important
Link: https://packages.debian.org/sid/luajit

(2) Description of problem
When I build bcc, there exists the following build error:
[ 34%] Generating bcc.o
/usr/bin/luajit: /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua:240: cannot 
convert 'nil' to 'unsigned short'
[ 35%] Linking C executable bcc-lua
cc: error: bcc.o: No such file or directory

(3) Steps to Reproduce
# According to https://packages.debian.org/source/sid/bpfcc,
# BCC build dependencies:
sudo apt-get install arping bison clang-format cmake dh-python \
  dpkg-dev pkg-kde-tools ethtool flex inetutils-ping iperf \
  libbpf-dev libclang-dev libclang-cpp-dev libedit-dev libelf-dev \
  libfl-dev libzip-dev linux-libc-dev llvm-dev libluajit-5.1-dev \
  luajit python3-netaddr python3-pyroute2 python3-distutils python3
# In oreder to avoid "/bin/sh: 1: python: not found"
sudo apt-get install python

git clone https://github.com/iovisor/bcc.git
mkdir bcc/build; cd bcc/build
cmake ..
make

(4) Additional info
I just replace the following old file [1] with the latest new file [2],
then the error disappeared.
[1] /usr/share/luajit-2.1.0-beta3/jit/bcsave.lua
[2] https://github.com/LuaJIT/LuaJIT/blob/v2.1/src/jit/bcsave.lua

It seems that this commit fixed it:
https://github.com/LuaJIT/LuaJIT/commit/94d0b53004a5

(5) Question and Suggestion
Could you please update the luajit package used with the latest source code?

Thanks,
Tiezhu

Re: Got a machine name problem

[Tom Browder]

On Tue, Feb 23, 2021 at 19:36 David Wright  wrote:

> On Tue 23 Feb 2021 at 20:05:11 (-0500), Gene Heskett wrote:
> > On Tuesday 23 February 2021 14:29:01 Tom Browder wrote:

...

> > > I also edit /etc/hosts and make the first couple of lines look like
> > > this:
> > >
> > > 127.0.0.1 localhost.localdomain.com   localhost
> > > 127.0.1.1 TLM.geneslinuxbox.netTLM


David, you got me. I put those lines in years ago (on some person's
recommendation), while I was still running pre-Debian 4 (probably Redhat in
the box days).

It works and that's all I can say.

Best,

-Tom

Re: Got a machine name problem

[David Christensen]

On 2021-02-23 09:58, Gene Heskett wrote:

Greetings all;

I have been working on a lower priority project, replacing some atom
powered machines with i5 powered Dells. Installing buster but something
is overriding my efforts to rename the machine after the install because
I'd like to replace "lathe" with "TLM" for The Little Monster.

Nothing I do survives a reboot, so what do I do to actually rename the
machine and make it stick? Hopefully without losiing the networking
which I don't have after the last reboot, probably because of the
current volatility of interface names.



Changing the hostname on a Debian system is a good way to gain an 
appreciation for DRY:


https://en.wikipedia.org/wiki/Don't_repeat_yourself


I see that several readers have already respond with pieces of the 
following.  You might want to check the whole shopping list:


https://wiki.debian.org/Hostname


If and when you get tired of looking for needles in the haystack, and/or 
you find them inside binary files that you dare not edit, you may 
realize that your best bet is to backup, wipe, reinstall with the new 
hostname, and restore.  Or, you could just do that first and forget 
about searching the haystack.



David

Re: Got a machine name problem

[David Wright]

On Tue 23 Feb 2021 at 20:05:11 (-0500), Gene Heskett wrote:
> On Tuesday 23 February 2021 14:29:01 Tom Browder wrote:
> > On Tue, Feb 23, 2021 at 11:59 AM Gene Heskett wrote: ...
> >
> > > Nothing I do survives a reboot, so what do I do to actually rename
> > > the machine and make it stick? Hopefully without losiing the
> > > networking
> >
> > Hey, Gene.  I usually have to fiddle around a little, but I've always
> > had success on Debian this way (as root):
> >
> > # hostname TLM
> >
> >edit /etc/hostname and set the desired name to TLM if it's not
> > already changed
> >
> > I also edit /etc/hosts and make the first couple of lines look like
> > this:
> >
> > 127.0.0.1 localhost.localdomain.com   localhost
> > 127.0.1.1 TLM.geneslinuxbox.netTLM
> 
> The first line is std here.
> 
> Why should it have the 2nd one?

If some software wants to know the IP address of TLM before the
network is up, there's no point in handing it 192.168.M.N,
so you use a loopback address to itself.

However, putting TLM on the first line can apparently make
localhost.localdomain into the canonical name of the system,
which is probably not what you want.

BTW I don't know where your .com came from in the first line.

Cheers,
David.

Re: Got a machine name problem

[Gene Heskett]

On Tuesday 23 February 2021 19:22:19 James B wrote:

> With systemd-based Debian, the probably now best way to set a hostname
> is with:
>
> hostnamectl set-hostname NAME
>
> What Tom suggested is completely valid, but hostnamectl should I
> understand be the preferred route as I believe it will update
> everything necessary automatically.Doing it this way will also be a
> persistent change.
>
> James

Does this also have a set-domainname option? This also is disappearing on 
a reboot. Not ack the man page so I assume there is a different method 
to handle that?

Thanks James.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Unable to boot on Xen HVM + OVMF

[John Mok]

Hi,

Tried to install Buster on Xen HVM + OVMF. Installation completed
successfully, but unable to boot (Windows HVM guest has no boot
problem).

Re-install Buster with BIOS and boot succeeded.

OVMF boot NOT supported on Debian ? I hope someone could point me in
the right direction.

Best regards,

John Mok

Re: Got a machine name problem

[Gene Heskett]

On Tuesday 23 February 2021 14:29:01 Tom Browder wrote:

> On Tue, Feb 23, 2021 at 11:59 AM Gene Heskett 
> wrote: ...
>
> > Nothing I do survives a reboot, so what do I do to actually rename
> > the machine and make it stick? Hopefully without losiing the
> > networking
>
> Hey, Gene.  I usually have to fiddle around a little, but I've always
> had success on Debian this way (as root):
>
> # hostname TLM
>
>edit /etc/hostname and set the desired name to TLM if it's not
> already changed
>
> I also edit /etc/hosts and make the first couple of lines look like
> this:
>
> 127.0.0.1 localhost.localdomain.com   localhost
> 127.0.1.1 TLM.geneslinuxbox.netTLM

The first line is std here.

Why should it have the 2nd one?

> Then reboot and cross your fingers.

Arthritis at 86 is beginning to make that painful. :(
>
> Blessings,
>
> -Tom
>
> P.S. Keep your powder dry!

Absolutely. I may yet live to see the last box opened.


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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Got a machine name problem

[James B]

To my mind, getting familiar with the newer 'ctl' commands that come with 
systemd is no bad idea.I like the consistency, personally.The 'systemctl' 
command is one to be used all the time particularly.

-- 
  James B
  portoteache...@fastmail.com

Em Qua, 24 Fev ʼ21, às 00:22, James B escreveu:
> With systemd-based Debian, the probably now best way to set a hostname is 
> with:
> 
> hostnamectl set-hostname NAME
> 
> What Tom suggested is completely valid, but hostnamectl should I 
> understand be the preferred route as I believe it will update 
> everything necessary automatically.Doing it this way will also be a 
> persistent change.
> 
> James
> -- 
>   James B
>   portoteache...@fastmail.com
> 
> Em Ter, 23 Fev ʼ21, às 19:29, Tom Browder escreveu:
> > On Tue, Feb 23, 2021 at 11:59 AM Gene Heskett  wrote:
> > ...
> > > Nothing I do survives a reboot, so what do I do to actually rename the
> > > machine and make it stick? Hopefully without losiing the networking
> > 
> > Hey, Gene.  I usually have to fiddle around a little, but I've always
> > had success on Debian this way (as root):
> > 
> > # hostname TLM
> > 
> >edit /etc/hostname and set the desired name to TLM if it's not
> > already changed
> > 
> > I also edit /etc/hosts and make the first couple of lines look like this:
> > 
> > 127.0.0.1 localhost.localdomain.com   localhost
> > 127.0.1.1 TLM.geneslinuxbox.netTLM
> > 
> > Then reboot and cross your fingers.
> > 
> > Blessings,
> > 
> > -Tom
> > 
> > P.S. Keep your powder dry!
> > 
> >
> 
>

Re: Got a machine name problem

[James B]

With systemd-based Debian, the probably now best way to set a hostname is with:

hostnamectl set-hostname NAME

What Tom suggested is completely valid, but hostnamectl should I understand be 
the preferred route as I believe it will update everything necessary 
automatically.Doing it this way will also be a persistent change.

James
-- 
  James B
  portoteache...@fastmail.com

Em Ter, 23 Fev ʼ21, às 19:29, Tom Browder escreveu:
> On Tue, Feb 23, 2021 at 11:59 AM Gene Heskett  wrote:
> ...
> > Nothing I do survives a reboot, so what do I do to actually rename the
> > machine and make it stick? Hopefully without losiing the networking
> 
> Hey, Gene.  I usually have to fiddle around a little, but I've always
> had success on Debian this way (as root):
> 
> # hostname TLM
> 
>edit /etc/hostname and set the desired name to TLM if it's not
> already changed
> 
> I also edit /etc/hosts and make the first couple of lines look like this:
> 
> 127.0.0.1 localhost.localdomain.com   localhost
> 127.0.1.1 TLM.geneslinuxbox.netTLM
> 
> Then reboot and cross your fingers.
> 
> Blessings,
> 
> -Tom
> 
> P.S. Keep your powder dry!
> 
>

Re: authentication bug (or feature?) with multiple encrypted lvm2 volume groups

[Charles Curley]

On Tue, 23 Feb 2021 22:19:03 +0100
Marco Möller  wrote:

> Obviously, the in Step 2 entered (wrong) password (for "A") is stored 
> and without further interactive consultation automatically used as
> the input for the password authentication of "B".
> Is this a bug or a feature? If it is a bug, where to report it?

I think it is a feature. Had A and B had the same passphrase, the
system would have asked for a passphrase for A, and then applied it to
B as well; a nice convenience.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Help Understanding Samba/ssh/LDAP/sssd/Kerberos/File Sharing?

[Kent West]

On Thu, Feb 18, 2021 at 8:10 PM Kent West  wrote:

> Ultimate goal:
>  1. Allow Windows/Mac users to map drives to Debian fileshares.
>  2. Allow Windows/Mac users to ssh into same Debian box.
>
> Near as I've been able to figure out (the web documentation seems to be
> all over the map), there are basically three ways of authenticating users
> for logging into a Debian box (at the console, or possibly via ssh, or
> possibly to access Samba fileshares):
>
> 1) the oldest and least-preferred method - LDAP and
> manual configuration of various files
> 2) the winbindd method - still supported, but perhaps on the road to
> deprecation in favor of sssd
> 3) the "modern" sssd method
> (Kerberos also seems to be a method, but that may be wrapped up in one or
> the other above methods.)
>
> It is my (possibly incorrect) understanding that the sssd method does not
> yet provide Samba filesharing capabilities, making winbindd the preferred
> choice.
>
> I have found the realmd tool, which makes the setup of either winbindd or
> sssd for console-based logins pretty easy. I can get console-based logins
> to work with either of theses two methods:
>
> winbindd:
>
> realm join --membership-software=samba --client-software=winbind -U
> [domain-add-capable user] [domain-name]
>
> sssd:
>
> realm join -U [domain-add-capable user] [domain-name]
>
> With either of these two methods, I can log into the console with a login
> like:
>  user@domain
>
> But with the sssd method, I could never get samba shares to work. With the
> winbind method, I can't get ssh to work. And a huge roadblock is that I've
> simply beeb unable to wrap my brain around what is needed; as mentioned,
> the web documentation is all over the map.
>
> So with all that said, my basic question here: Is my understanding of the
> three methods, for joining an Active Directory domain, validating users
> from it for console logins, ssh logins, and mapping drives shared from the
> Debian box, close to correct?
>
> Thanks!
>
>
> --
> Kent West<")))><
> Westing Peacefully - http://kentwest.blogspot.com
>


Yes, after tinkering and fighting these past couple of days with virtual
machines and test machines, etc, I believe my understanding is correct.

My notes on the process, should anyone be interested, are here:
http://goshen.acu.edu/westk/DEBIAN/Debian2ADSetup.html

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

authentication bug (or feature?) with multiple encrypted lvm2 volume groups

[Marco Möller]

Two volume groups (lvm2) exists, Each of them is encrypted and thus 
protected by its own password. Lets call the volume groups and their 
corresponding passwords like this:


VGpassword
"A"   "pwA"
"B"   "pwB"

"pwA" and "pwB" differ from each other.

Step 1: during boot I am asked for the password of "A"
Step 2: by accident I enter "pwB"
Step 3: consequently an error message is shown and "A" is not opened
Step 4: I am asked again for the password of "A"
Step 5: I now enter correctly "pwA"
Step 6: "A" is opened
Step 7: "B" is immediately opened without asking for its password

I confirmed, that the opening of "B" does only take place, when having 
entered in Step 2 the "pwB". If I enter in Step 2 something else, then 
in Step 7 it is asked for the password of "B", I would enter it in a 
Step 8 correctly and consequently in a Step 9 the "B" would be opened.


Obviously, the in Step 2 entered (wrong) password (for "A") is stored 
and without further interactive consultation automatically used as the 
input for the password authentication of "B".

Is this a bug or a feature? If it is a bug, where to report it?

Thanks in advance for your kind advice, Marco.


PS:  This is how in the past, more than a year ago, I created this two 
encrypted volume groups according to my installation notes:
When installing a new Debian/testing (bullseye) OS, then I "Create new 
empty partition table”, then created also these two volume groups by 
"use as: physical volume for encryption" followed by "Create encrypted 
volumes".

Re: need to reinstall pulseaudio every day

[Nicholas Geovanis]

On Tue, Feb 23, 2021, 3:13 PM Dan Ritter  wrote:

> Pierre Frenkiel wrote:
> > On Tue, 23 Feb 2021, Nicholas Geovanis wrote:
> >
> > > Patient: Doctor when I move my arm this way, it hurts.
> > > Doctor: Don't do that with your arm. Next!
> >
> >  very funny, but I don't see how it is related to my pulseaudio problem,
> >  unless you suggest to don't use it !
>
> Could be an option. What do you need pulseaudio for that
> isn't handled by alsa, jack and/or apulse?
>

And one reason I interjected that is dealing with software sound synthesis
and learning that whole sectors recommend ALSA and jack to the exclusion of
others. Often not just a recommendation but a requirement. I dont have an
axe to grind on that, just that's what "they tell me".

-dsr-
>
>

Re: need to reinstall pulseaudio every day

[Dan Ritter]

Pierre Frenkiel wrote: 
> On Tue, 23 Feb 2021, Nicholas Geovanis wrote:
> 
> > Patient: Doctor when I move my arm this way, it hurts.
> > Doctor: Don't do that with your arm. Next!
> 
>  very funny, but I don't see how it is related to my pulseaudio problem,
>  unless you suggest to don't use it !

Could be an option. What do you need pulseaudio for that 
isn't handled by alsa, jack and/or apulse?

-dsr-

Re: Yahoo, Kmail : pas de réception

[ajh-valmer]

On Tuesday 23 February 2021 22:03:36 NoSpam wrote:
> Comme déjà évoqué par d'autres, cette liste s'appelle debian-user-french 
> donc entraide sur des problèmes spécifiques Debian. Perso je ne vois 
> aucun lien avec yahoo (!?!) et kmail ou thunderbird ne sont en aucun cas 
> spécifiques à Debian. J'ajouterai que notifié un HS dans le sujet aurait 
> été un plus.

Désolé, j'avais omis le [HS].

A. Valmer

Re: Yahoo, Kmail et Thunderbird : pas de réception

[NoSpam]

Le 23/02/2021 à 19:39, ajh-valmer a écrit :

[...]
Merci d'avoir essayé, sympa, enfin une aide efficace :-)


[...]

Comme déjà évoqué par d'autres, cette liste s'appelle debian-user-french 
donc entraide sur des problèmes spécifiques Debian. Perso je ne vois 
aucun lien avec yahoo (!?!) et kmail ou thunderbird ne sont en aucun cas 
spécifiques à Debian. J'ajouterai que notifié un HS dans le sujet aurait 
été un plus.


--

Daniel

Re: mounten SD-kaartje dat in foto camera zit

[Geert Stappers]

On Tue, Feb 23, 2021 at 09:17:12PM +0100, René Luijckx wrote:
> Hoi,
> 
> Ik gebruik een versie van Debian 9.13 ( stretch ).
> Het ( automatisch ) mounten van SD-kaartjes is normaal gesproken geen
> probleem.
> Ontkoppelen ditto.
> Echter .
> het mounten van micro-SD-kaartjes die in mijn camera hebben gezeten gaat
> slechts eenmalig. Ik sluit mijn laptop zelden af, klap hem dicht en hij
> gaat in slaapstand.
> In mijn camera zitten 2 SD kaartjes, per kaartje 1 soort foto's of
> video-bestanden. Beiden exfat geformateerd. exfat-utils is geïnstalleerd.
> Na een reboot kan ik beide kaartjes *eenmalig* benaderen.
> Een heel enkele keer lukt het door te wisselen met een kaartje uit een
> andere machine ( fat16 ) toch een kaartje uit de camera te benaderen.
> Meestal echter niet.
> Ook in Gparted zijn de kaartjes dan niet te zien.
> 
> Suggesties ?

Vertel a.u.b. meer over de "hardware" tussen laptop en SD-kaartjes.




Wat ik **zelf bedacht** heb, is deze ketting:

 * Laptop
 * USB poort   (Type ...,  werkt goed met ... )
 * USB kabel,  de originele die bij de camera hoort
 * USB connector, geen beschadigingen te zien
 * Camera, lastig te omschrijven, toch een poging
   * Stroom van uit het stopcontact  (niet op batterijen)
   * Wakker  (niet in een slaapstand over andere power save mode
   * Display c.q. Menu van de camera toont beide SD-kaartjes
   * De sleufen voor de SD-kaartje verschillen alleen van nummer
  ( geen aanwijzigingen als "Configuration"  of "Mass storage"
of andere verschillen, gewoon SD1 en SD2)
 * Beide SD-kaartjes zijn van dezelfde Klasse
   ( https://en.wikipedia.org/wiki/SD_card#Class )




> Na een reboot kan ik beide kaartjes *eenmalig* benaderen.

Wat is er **voor** en **na**  met  `lsusb` te zien?

Kernel diagnostic messages, commando `dmesg` wat laat die zien?



En als de Linux onderzocht is, onderzoek dan ook de camera kant.


Groeten
Geert Stappers
Leerde later pas dat Andriod devices verschillende USB-modes hebben.
-- 
Silence is hard to parse

Re: need to reinstall pulseaudio every day

[Pierre Frenkiel]

On Tue, 23 Feb 2021, Nicholas Geovanis wrote:


Patient: Doctor when I move my arm this way, it hurts.
Doctor: Don't do that with your arm. Next!


 very funny, but I don't see how it is related to my pulseaudio problem,
 unless you suggest to don't use it !

best regards,
--
Pierre Frenkiel

mounten SD-kaartje

[René Luijckx]

Hoi,

Ik gebruik een versie van Debian 9.13 ( stretch ).
Het ( automatisch ) mounten van SD-kaartjes is normaal gesproken geen
probleem.
Ontkoppelen ditto.
Echter .
het mounten van micro-SD-kaartjes die in mijn camera hebben gezeten gaat
slechts eenmalig. Ik sluit mijn laptop zelden af, klap hem dicht en hij
gaat in slaapstand.
In mijn camera zitten 2 SD kaartjes, per kaartje 1 soort foto's of
video-bestanden. Beiden exfat geformateerd. exfat-utils is geïnstalleerd.
Na een reboot kan ik beide kaartjes *eenmalig* benaderen.
Een heel enkele keer lukt het door te wisselen met een kaartje uit een
andere machine ( fat16 ) toch een kaartje uit de camera te benaderen.
Meestal echter niet.
Ook in Gparted zijn de kaartjes dan niet te zien.

Suggesties ?

Bij voorbaat dank,

René.

Re: Yahoo, Kmail et Thunderbird : pas de réception

[didier gaumet]

Le 23/02/2021 à 19:39, ajh-valmer a écrit :


Merci d'avoir essayé, sympa, enfin une aide efficace :-)

Kmail (TDE), je sais pas pourquoi ça va pas :
Voici mes configs :
-Mail : @yahoo.com
-Serveur : pop.mail.yahoo.com > -Port : 995
-Système : Debian Buster
J'utilise systemd
Méthode d'identification : Que faut-il mettre ?
- Texte en clair
- LOGIN
- PLAIN


je dirais LOGIN


Sous Kmail, on peut obtenir automatiquement ces configs par :
"Vérifier ce que le serveur peut gérer",
Si je clique, pas de dialogue possible avec le serveur Yahoo (blocage),
alors qu'avec les autres comptes, ça répond instantanément.

Du nouveau : j'ai créé un nouveau compte @yahoo.com
et là, ça marche... mais qu'avec Thunderbird.


Essaie de reproduire le même paramétrage dans Kmail que dans thunderbird 
(Edition->Paramètres des comptes->le compte yahoo->paramètres serveur: 
chez moi c'est de l'IMAP, sécurité SSL/TLS, authentification OAuth2). Si 
tu n'arrives à rien avec ton Kmail ça peut vouloir dire (j'en sais rien, 
j'ai pas vérifié) que le Kmail de Trinity n'incorpore pas certaines 
fonctions car trop vieux ou pas assez développé, ou que tu n'as pas 
installé/paramétré certaines fonctions/bibliothèques de Trinity dans 
Debian ou qu'il faut bidouiller pour parfaire l'intégration de Trinity 
qui n'est pas suffisante dans Debian, ou...


Si rien ne marche, tu peux vérifier que le Kmail de KDE/plasma 
fonctionne avec Yahoo en testant un liveCD/DVD debian KDE (pour éviter 
de risquer de polluer ton install Trinity sur ton PC avec des morceaux 
de vrai KDE/Plasma)

Re: Got a machine name problem

[Tom Browder]

On Tue, Feb 23, 2021 at 11:59 AM Gene Heskett  wrote:
...
> Nothing I do survives a reboot, so what do I do to actually rename the
> machine and make it stick? Hopefully without losiing the networking

Hey, Gene.  I usually have to fiddle around a little, but I've always
had success on Debian this way (as root):

# hostname TLM

   edit /etc/hostname and set the desired name to TLM if it's not
already changed

I also edit /etc/hosts and make the first couple of lines look like this:

127.0.0.1 localhost.localdomain.com   localhost
127.0.1.1 TLM.geneslinuxbox.netTLM

Then reboot and cross your fingers.

Blessings,

-Tom

P.S. Keep your powder dry!

Re: Yahoo, Kmail et Thunderbird : pas de réception

[ajh-valmer]

On Tuesday 23 February 2021 18:13:18 didier gaumet wrote:
> Test: je viens de me créer un compte mail yahoo.com et je n'ai eu 
> aucun problème pour accéder par Thunderbird au mail de Yahoo m'informant 
> d'une activité Thunderbird liée à mon compte
> Contexte: Buster (avec systemd, Gnome, Thunderbird mais pas de Kmail)
> Hypothèse: Si tu n'utilises pas systemd tu as peut-être une config un 
> peu bancale bancale (ex: Thunderbird dépend de udev qui dépend de 
> libsystemd). Si tu utilises un bureau (Trinity?) non présent dans 
> Debian, il est possible que Trinity ne soit pas à jour au niveau de 
> certaines bibliothèques (ex: authentification...), que son Kmail soit 
> trop vieux comparé au Kmail de Plasma/KDE ou que l'intégration dans 
> Debian ne soit pas complète ce qui amène à des fonctionnalités manquantes
> Suggestion: si ce n'est pas déjà le cas et si possible, rester dans un 
> environnement Debian Stable standard avec les paquets des dépôts Debian

Merci d'avoir essayé, sympa, enfin une aide efficace :-)

Kmail (TDE), je sais pas pourquoi ça va pas :
Voici mes configs :
-Mail : @yahoo.com
-Serveur : pop.mail.yahoo.com
-Port : 995
-Système : Debian Buster
J'utilise systemd
Méthode d'identification : Que faut-il mettre ? 
- Texte en clair
- LOGIN
- PLAIN

Sous Kmail, on peut obtenir automatiquement ces configs par :
"Vérifier ce que le serveur peut gérer",
Si je clique, pas de dialogue possible avec le serveur Yahoo (blocage),
alors qu'avec les autres comptes, ça répond instantanément.

Du nouveau : j'ai créé un nouveau compte @yahoo.com
et là, ça marche... mais qu'avec Thunderbird.

Bonne soirée.

Re: blocage au démarrage /var/ plein

[roger . tarani]

J'ai trouvé un coupable !

Contexte : mise en veille (icône "pause" : "suspend to RAM", je crois, qui 
nécessite une alimentation de la machine; bref, seule la RAM reste alimentée ; 
ce n'est pas  l'hibernation profonde "suspend to disk")

Dès la première sortie de veille, les fichiers kernel.log, messages et syslog 
(dans /var/log/) sont emplis d'un message répétitif :
   comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected
(voir détails ci-dessous)

En cherchant un peu avec ce message d'erreur, il s'agirait d'une carte NI PCI 
installée et qui ne supporte pas la mise en veille prolongée.

$ lspci 
(...)
10:00.0 Unassigned class [ff00]: National Instruments PCI-MIO-16E-4

Le truc bizarre est que cette carte est installée depuis très longtemps, qu 
ej'utilise la veillet que le message d'erreur répétif est nouveau.

La question devient : comment faire taire cette carte, sans devoir la 
débrancher électriquement ?
Merci.





=== DETAILS : kern.log en sortie de suspend to RAM ===

PM: suspend entry (deep)
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.001 seconds) done.
OOM killer disabled.
Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
sd 4:0:0:0: [sdb] Synchronizing SCSI cache
sd 1:0:0:0: [sda] Synchronizing SCSI cache
sd 1:0:0:0: [sda] Stopping disk
serial 00:03: disabled
e1000e: EEE TX LPI TIMER: 
br0: port 1(enp0s25) entered disabled state
sd 4:0:0:0: [sdb] Stopping disk
ACPI: Preparing to enter system sleep state S3
PM: Saving platform NVS memory
Disabling non-boot CPUs ...
IRQ 25: no longer affine to CPU1
smpboot: CPU 1 is now offline
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x1
 cache: parent cpu1 should not be sleeping
hpet: hpet3 irq 25 for MSI
CPU1 is up
ACPI: Waking up from system sleep state S3
usb usb1: root hub lost power or was reset
usb usb3: root hub lost power or was reset
usb usb5: root hub lost power or was reset
usb usb6: root hub lost power or was reset
usb usb7: root hub lost power or was reset
usb usb8: root hub lost power or was reset
serial 00:03: activated
sd 1:0:0:0: [sda] Starting disk
sd 4:0:0:0: [sdb] Starting disk
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
usb 4-4: reset high-speed USB device number 3 using ehci-pci
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
ata6: SATA link down (SStatus 4 SControl 300)
ata7: SATA link down (SStatus 4 SControl 300)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
ata4.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
ata4.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata4.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
ata4.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
ata4.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
ata4.00: configured for UDMA/100
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
tpm tpm0: TPM is disabled/deactivated (0x7)
comedi comedi0: Card removed?
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: ni_tio_handle_interrupt: Gi_Gate_Error detected.
comedi comedi0: Card removed?
comedi comedi0: 

Re: Got a machine name problem

[Dan Ritter]

Gene Heskett wrote: 
> Greetings all;
> 
> I have been working on a lower priority project, replacing some atom 
> powered machines with i5 powered Dells. Installing buster but something 
> is overriding my efforts to rename the machine after the install because 
> I'd like to replace "lathe" with "TLM" for The Little Monster.
> 
> Nothing I do survives a reboot, so what do I do to actually rename the 
> machine and make it stick? Hopefully without losiing the networking 
> which I don't have after the last reboot, probably because of the 
> current volatility of interface names.

Typically, edit /etc/hostname and reboot, or run 
hostname -F /etc/hostname
for immediate effect.

Check to see if you have assigned a name via dhcp or in
/etc/hosts.

-dsr-

Got a machine name problem

[Gene Heskett]

Greetings all;

I have been working on a lower priority project, replacing some atom 
powered machines with i5 powered Dells. Installing buster but something 
is overriding my efforts to rename the machine after the install because 
I'd like to replace "lathe" with "TLM" for The Little Monster.

Nothing I do survives a reboot, so what do I do to actually rename the 
machine and make it stick? Hopefully without losiing the networking 
which I don't have after the last reboot, probably because of the 
current volatility of interface names.

Thanks.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: [HS] Recherche Développeur pour interview

[Pierre Couderc]

On 2/23/21 12:17 PM, Sylvain Caselli wrote:

Le 23/02/2021 à 07:13, Pierre Couderc a écrit :
Quand un développe avec un langage efficace (C ou C++), il n'y a 
aucune raison a priori d'utiliser l'assembleur.
je ne sais pas si c'est encore vrai, mais lors de l’échantillonnage 
d'une valeur (du son par exemple) l'utilisation du convertisseur (ou 
tout device du microcontrôleur) ce faisait en assembleur (dans le pgm 
C à) car en C c'est beaucoup trop lent. Logique car il reconfigure 
tout à chaque fois. Je n'ai plus le choix maintenant mais pour lire un 
bouton ou un capteur et allumer une led ou faire tourner un moteur les 
langages évolués m'ont finalement semblé bien compliqués pour faire de 
la robotique. Maintenant qu'il faut les connecter et des interfaces 
tactiles c'est effectivement plus simple (mais est-ce bien utile ?).


Je ne sais pas non plus, mais je sais que les  parties critiques en 
temps sont - par nature - des boucles extrêmement courtes, et ce sont 
les seules où on peut être amené à utiliser de l'assembleur...

Re: is it possible to add a secondary disk to an existing debian systems and install programs to the secondary disk

[Joe]

On Tue, 23 Feb 2021 11:37:12 -0500
rhkra...@gmail.com wrote:

> On Tuesday, February 23, 2021 11:13:12 AM Nicholas Geovanis wrote:
> > You can always add more filesystem space later. It's easier if
> > you're using LVM but that isn't required. You just build another
> > filesystem on the new drive after it's installed and mount it into
> > your filesystems, at the appropriate mount point.  
> 
> Don't you have to do things like copy the old filesystem content to
> the new filesystem (possibly using a temporary mount point for one of
> those), then move the new filesystem to the old mount point?  (Maybe
> that is only if they are "system" filesystems (e.g., /var, /etc,
> /home ...?)
> 

Yes, and you also need to delete the content in the original directory
tree, or else you don't recover the space. Most of this is most easily
done from a live/rescue OS with the host OS offline, though it can be
done online with a bit more work.

If you're moving /usr it is wise to rebuild grub from chroot, making a
new initramfs. Systemd requires /usr during boot and gets quite upset
if it can't find it. I'm aware there is controversy about putting
essential system software in a tree named '/usr' and I'm not going to
add to it.

There are many web articles on how to add and mount a new drive, but
hardly any (mostly one for Ubuntu repeated widely) for actually moving
an existing directory tree, especially a system one like /usr. I
hesitate to offer details as it is a long time, pre-systemd, since I
last did it.


-- 
Joe

Re: Yahoo et Kmail : pas de réception

[didier gaumet]

Test: je viens de me créer un compte e-ùmail yahoo.com et je n'ai eu 
aucun problème pour accéder par Thunderbird au mail de Yahoo m'informant 
d'une activité Thunderbird liée à mon compte


Contexte: Buster (avec systemd, Gnome, Thunderbird mais pas de Kmail)

Hypothèse: Si tu n'utilises pas systemd tu as peut-être une config un 
peu bancale bancale (ex: Thunderbird dépend de udev qui dépend de 
libsystemd). Si tu utilises un bureau (Trinity?) non présent dans 
Debian, il est possible que Trinity ne soit pas à jour au niveau de 
certaines bibliothèques (ex: authentification...), que son Kmail soit 
trop vieux comparé au Kmail de Plasma/KDE ou que l'intégration dans 
Debian ne soit pas complète ce qui amène à des fonctionnalités manquantes


Suggestion: si ce n'est pas déjà le cas et si possible, rester dans un 
environnement Debian Stable standard avec les paquets des dépôts Debian

Re: is it possible to add a secondary disk to an existing debian systems and install programs to the secondary disk

[Nicholas Geovanis]

On Tue, Feb 23, 2021, 10:37 AM  wrote:

> On Tuesday, February 23, 2021 11:13:12 AM Nicholas Geovanis wrote:
> > You can always add more filesystem space later. It's easier if you're
> using
> > LVM but that isn't required. You just build another filesystem on the new
> > drive after it's installed and mount it into your filesystems, at the
> > appropriate mount point.
>
> Don't you have to do things like copy the old filesystem content to the
> new
> filesystem (possibly using a temporary mount point for one of those), then
> move
> the new filesystem to the old mount point?  (Maybe that is only if they
> are
> "system" filesystems (e.g., /var, /etc, /home ...?)
>

I answered that in my 2nd paragraph, which you see right below this text.
One step at a time for a newer sysadmin.

> Where is that? Depends on your needs. What if it's a critical filesystem
> > that you can't unmount while the OS is up? Or what if you need to copy a
> > critical fs to the new drive and reboot using the new, bigger copy? If
> > either is the case, write back and we'll pick it up from there.
>
>

Re: is it possible to add a secondary disk to an existing debian systems and install programs to the secondary disk

[rhkramer]

On Tuesday, February 23, 2021 11:13:12 AM Nicholas Geovanis wrote:
> You can always add more filesystem space later. It's easier if you're using
> LVM but that isn't required. You just build another filesystem on the new
> drive after it's installed and mount it into your filesystems, at the
> appropriate mount point.

Don't you have to do things like copy the old filesystem content to the new 
filesystem (possibly using a temporary mount point for one of those), then move 
the new filesystem to the old mount point?  (Maybe that is only if they are 
"system" filesystems (e.g., /var, /etc, /home ...?)

> Where is that? Depends on your needs. What if it's a critical filesystem
> that you can't unmount while the OS is up? Or what if you need to copy a
> critical fs to the new drive and reboot using the new, bigger copy? If
> either is the case, write back and we'll pick it up from there.

Re: is it possible to add a secondary disk to an existing debian systems and install programs to the secondary disk

[James H. H. Lampert]

On 2/23/21 8:13 AM, Nicholas Geovanis wrote:

You can always add more filesystem space later. It's easier if you're using
LVM but that isn't required. You just build another filesystem on the new
drive after it's installed and mount it into your filesystems, at the
appropriate mount point.


Indeed, and on my DOS/Linux dual-boot at home, I have the Linux side set 
up to mount all five DOS volumes.


--
JHHL

Re: is it possible to add a secondary disk to an existing debian systems and install programs to the secondary disk

[Nicholas Geovanis]

You can always add more filesystem space later. It's easier if you're using
LVM but that isn't required. You just build another filesystem on the new
drive after it's installed and mount it into your filesystems, at the
appropriate mount point.

Where is that? Depends on your needs. What if it's a critical filesystem
that you can't unmount while the OS is up? Or what if you need to copy a
critical fs to the new drive and reboot using the new, bigger copy? If
either is the case, write back and we'll pick it up from there.

On Mon, Feb 22, 2021, 5:03 PM Semih Ozlem 
wrote:

> processor i3-7100 ram 4 gb other details will have to restart the machine
> to tell.
> storage device there is an internal hard disk (500gb) that has windows
> installed on it, which I can not install another operating system to for
> now for reasons that I would have to back up files before and I don't have
> time right now to do that, and I am not sure about what would be the safest
> way of copying files (or should I clone the disk instead)
> I will send lshw output shortly for interfaces and everything else.
>
> Software goal is (i) be able to test different systems, and planning to
> use virtualization for this purpose (ii) possibly create virtual machines
> with programs installed (iii) a sort of a potential goal is to build a web
> site and host it , but mainly just rather for learning how to do it, since
> probably I can not afford for now actually investing in necessary equipment
> and probably it is easier to do that by paying some service rather than
> doing it all on one's own (iv) be able to run some programming projects in
> python
>
> I sort of like exploring and testing out new things, and most of it is not
> planned. But basically I would like to have the system be able to hold (i)
> security tools/antivirus (ii) server (apache and samba), probably LAMP or
> nginx (iii) math packages / programs (R,gnuplot, lapack, and possibly
> others) (iv) programming packages (gcc,python,java,rhino) at the very least
> (v) virtualization (virtualbox) (vi) calibre (document viewing and creating
> instruments) (v) latex (vi) programs to record and view videos or audios,
> if possible running on the same machine. Of these, I may forego idea of
> running a server if this slows things too much.
>
> If possible also programming tools for machine-learning.
>
> David , 23 Şub 2021 Sal, 01:10 tarihinde şunu
> yazdı:
>
>> On Tue, 23 Feb 2021 at 08:38, Semih Ozlem 
>> wrote:
>>
>> > I have a usb device that I can attach for testing now.
>>
>> Sorry if I overlooked that you provided this information already
>> elsewhere, but I think it would help us to help you if you would
>> properly describe for us the hardware that you are currently using.
>>
>> 1) What processor and motherboard hardware are you currently using?
>>Make and model?
>> 2) How much RAM is available?
>> 3) What storage devices (eg hard disk drives) are connected to this?
>>Make and model?   Using what busses/interfaces (eg SATA, USB)?
>> 4) What is the software goal? What is the intended use?
>>What services or applications do you wish to run on this hardware?
>>
>>

Re: [HS] Recherche Développeur pour interview

[F. Dubois]

Le 23/02/2021 à 12:28, ajh-valmer a écrit :

D'après ce que je comprends,
les interviewers ont besoin d'un développeur professionnel,
dont c'est le métier, pas d'un simple utilisateur.

Ada, langage très utilisé dans la haute technologie pourrait faire l'affaire :

https://www.adalog.fr/fr/acces.html

"L'utilisateur est placé devant un dilemme : doit-il se mettre entre les mains
de Sun/Java ou de Microsoft/C# ?  Restez libre avec Ada !"


Bonjour,

Sans compter que cela remet, un peu, Ada Lovelace à sa place dans 
l'histoire de l'informatique ! Un hommage à une femme dans un milieu qui 
reste encore bien masculin, c'est une très bonne chose.


Fabien

Re: need to reinstall pulseaudio every day

[Pierre Frenkiel]

On Tue, 23 Feb 2021, David Wright wrote:



When did this start to happen?
   . for years?
   . since installation?

Is this buster?

Are you running any applications, particularly those involving sound,
as root, particularly in response to some previous problem?

Is it just that binary that goes missing, or does apt/dpkg actually
show that the entire package is uninstalled?

The pulseaudio package contains about 216 files. Have they all gone,
or just the one binary? (Run   $ dpkg -L pulseaudio   to list them.)


 hi David,
 I'll answer to-morrow.
 Meantime, may-be my every minute check will have given some usefull information

best regards,
--
Pierre Frenkiel

Re: need to reinstall pulseaudio every day

[David Wright]

On Tue 23 Feb 2021 at 09:38:08 (+0100), Pierre Frenkiel wrote:
> every morning, ls /usr/bin/pulseaudio gives:
> ls: cannot access '/usr/bin/pulseaudio': No such file or directory
> and I must issue "aptitude reinstall pulseaudio" I plan to put the ls
> command every minute to find when it disappears,
> unless somebody can give me an axplanation (and a fix...)

When did this start to happen?
. for years?
. since installation?

Is this buster?

Are you running any applications, particularly those involving sound,
as root, particularly in response to some previous problem?

Is it just that binary that goes missing, or does apt/dpkg actually
show that the entire package is uninstalled?

The pulseaudio package contains about 216 files. Have they all gone,
or just the one binary? (Run   $ dpkg -L pulseaudio   to list them.)

Cheers,
David.

Re: need to reinstall pulseaudio every day

[Nicholas Geovanis]

Patient: Doctor when I move my arm this way, it hurts.
Doctor: Don't do that with your arm. Next!

☺

On Tue, Feb 23, 2021, 7:09 AM  wrote:

> On Tue, Feb 23, 2021 at 01:40:22PM +0100, Nicolas George wrote:
> > Greg Wooledge (12021-02-23):
> > > This *is* part of the diagnostics.  Preventing the deletion and then
> > > watching the logs to see who complains may help you pinpoint the
> > > culprit.  Or it may not.  But it's worth a try.
> >
> > Watching the logs was not in the advice. With that addition, the advice
> > is reasonable. Without, it was terrible, as was "changing the disk".
>
> [META] we are in violent agreement. Instead of saying "DON'T DO THIS",
> I'd humbly propose to enhance that advice, then :)
>
> Cheers
>  - t
>

Re: AD user can't ssh in

[Nicholas Geovanis]

And OK, remembered this too ☺
The clocks of all servers in a Kerberos domain must be tightly sync'd and
under control of a local master clock. That's because of the timestamps in
the Kerberos tickets. Authentication fails without it. And again as with
name resolution, that config must be complete before you obtain the
Kerberos TGT.

On Tue, Feb 23, 2021, 8:30 AM Nicholas Geovanis 
wrote:

> Let me add this if I may Kent, esp for others who might go there. When you
> first configure the linux server into an LDAP/AD or LDAP domain, you MUST
> complete the "final production" name resolution/resolver/DNS config BEFORE
> joining the domain. If you don't but later move it into that domain, it
> still won't authenticate right. And that really has to do with Kerberos
> setup, esp the TGT and ticketing. Doing the setup in docker or a Xen VM
> doesn't change that fact.
>
> On Mon, Feb 22, 2021, 3:12 PM Nicholas Geovanis 
> wrote:
>
>> On Mon, Feb 22, 2021, 1:47 PM Kent West  wrote:
>>
>>>
>>>
>>> On Mon, Feb 22, 2021 at 1:37 PM Kent West  wrote:
>>>


 On Mon, Feb 22, 2021 at 7:52 AM Nicholas Geovanis <
 nickgeova...@gmail.com> wrote:

> On Sun, Feb 21, 2021, 5:09 PM Kent West  wrote:
>
> Brand new Debian box (tried Buster, then when that didn;' work,
> upgraded tp unstable - meh, it's a test box to get things sorted out 
> before
> production use).
> 
> su'd to root
>
> apt install'd aptitude, realmd, packagekit
>
> (packagekit grabbed the needed dependencies, such as sssd and samba
> (at least parts of them, and maybe part of KRB5 (the keytab thing-y), and
> [mostly] configured them)
>
> Ran "realm join MY.DOMAIN -U my_add-to-domain_user"
>
> getent passwd domain_user successfully returns data on the domain user:
>
> acutech@21260-debianvm:~$ getent passwd glerp@my.domain
> glerp@my.domain:*:495633057:495600513:glerp:/home/glerp@my.domain
> :/bin/bash
> 
> 
>
> Here are a few relevant lines from /var/log/auth.log:
>
> Feb 21 17:04:54 21260-debianvm sshd[5284]: pam_unix(sshd:auth):
> authentication failure; logname= uid=0 euid=0 tty=ssh ruser=
> rhost=127.0.0.1  user=glerp@my.domain
> Feb 21 17:04:54 21260-debianvm sshd[5284]: pam_sss(sshd:auth):
> authentication success; logname= uid=0 euid=0 tty=ssh ruser=
> rhost=127.0.0.1 user=glerp@my.domain
> Feb 21 17:04:54 21260-debianvm sshd[5284]: pam_sss(sshd:account):
> Access denied for user glerp@my.domain: 6 (Permission denied)
> Feb 21 17:04:54 21260-debianvm sshd[5284]: Failed password for
> glerp@my.domain from 127.0.0.1 port 59998 ssh2
> Feb 21 17:04:54 21260-debianvm sshd[5284]: fatal: Access denied for
> user glerp@my.domain by PAM account configuration [preauth]
>
>
> So I think what this is telling you is that authentication succeeded
> for the "auth" clause in the "sshd" section of the PAM config file
> (pam_sss). But then authentication failed in the "account" clause of the
> sshd section.
>
> So the question is why there?
>
>
 .
>>
>>>
 I built another virtual machine on another Debian box, following the
>>> same steps. That one worked.
>>>
>>> I compared all the files I could think of (/etc/pam.d/ files,
>>> /etc/nsswitch.conf, /etc/ssd/ssd_config, etc), and made them identical.
>>> Didn't help.
>>>
>>> I then rebuilt the offending machine, removed it from the domain,
>>> followed the same steps again, and now ... it works.
>>>
>>> Go figure.
>>>
>>
>> And having been on that merry-go-round myself more than once, Mr West☺
>> that usually means something bad happened in the initial Kerberos
>> ticket granting process that happens at LDAP/AD initial config. First you
>> need a ticket-granting-ticket from the LDAP or AD domain (the TGT). And
>> then you need a session ticket for each kerberos session. Those sessions
>> are usually much shorter than the lifetime of a single boot. So sometimes
>> they need to be re-acquired outside of the boot process. And yes,
>> nsswitch.conf is vital.
>>
>> There are folks on debian-user who understand it better than me. The
>> first time I did that was on Solaris 8 however. Built LDAP, nss and AD
>> interface code from source. No base config files except for PAM. Took a few
>> tries but it worked. It's hard to shake out and you did it.
>> West in pieces... ☺
>>
>> I would have loved to have found the problem, but more importantly for
>>> me, I now know the process works. For now, that's sufficient.
>>>
>>>
>>>
>>> --
>>> Kent West<")))><
>>> Westing Peacefully - http://kentwest.blogspot.com
>>>
>>

Re: AD user can't ssh in

[Nicholas Geovanis]

Let me add this if I may Kent, esp for others who might go there. When you
first configure the linux server into an LDAP/AD or LDAP domain, you MUST
complete the "final production" name resolution/resolver/DNS config BEFORE
joining the domain. If you don't but later move it into that domain, it
still won't authenticate right. And that really has to do with Kerberos
setup, esp the TGT and ticketing. Doing the setup in docker or a Xen VM
doesn't change that fact.

On Mon, Feb 22, 2021, 3:12 PM Nicholas Geovanis 
wrote:

> On Mon, Feb 22, 2021, 1:47 PM Kent West  wrote:
>
>>
>>
>> On Mon, Feb 22, 2021 at 1:37 PM Kent West  wrote:
>>
>>>
>>>
>>> On Mon, Feb 22, 2021 at 7:52 AM Nicholas Geovanis <
>>> nickgeova...@gmail.com> wrote:
>>>
 On Sun, Feb 21, 2021, 5:09 PM Kent West  wrote:

 Brand new Debian box (tried Buster, then when that didn;' work,
 upgraded tp unstable - meh, it's a test box to get things sorted out before
 production use).
 
 su'd to root

 apt install'd aptitude, realmd, packagekit

 (packagekit grabbed the needed dependencies, such as sssd and samba (at
 least parts of them, and maybe part of KRB5 (the keytab thing-y), and
 [mostly] configured them)

 Ran "realm join MY.DOMAIN -U my_add-to-domain_user"

 getent passwd domain_user successfully returns data on the domain user:

 acutech@21260-debianvm:~$ getent passwd glerp@my.domain
 glerp@my.domain:*:495633057:495600513:glerp:/home/glerp@my.domain
 :/bin/bash
 
 

 Here are a few relevant lines from /var/log/auth.log:

 Feb 21 17:04:54 21260-debianvm sshd[5284]: pam_unix(sshd:auth):
 authentication failure; logname= uid=0 euid=0 tty=ssh ruser=
 rhost=127.0.0.1  user=glerp@my.domain
 Feb 21 17:04:54 21260-debianvm sshd[5284]: pam_sss(sshd:auth):
 authentication success; logname= uid=0 euid=0 tty=ssh ruser=
 rhost=127.0.0.1 user=glerp@my.domain
 Feb 21 17:04:54 21260-debianvm sshd[5284]: pam_sss(sshd:account):
 Access denied for user glerp@my.domain: 6 (Permission denied)
 Feb 21 17:04:54 21260-debianvm sshd[5284]: Failed password for
 glerp@my.domain from 127.0.0.1 port 59998 ssh2
 Feb 21 17:04:54 21260-debianvm sshd[5284]: fatal: Access denied for
 user glerp@my.domain by PAM account configuration [preauth]


 So I think what this is telling you is that authentication succeeded
 for the "auth" clause in the "sshd" section of the PAM config file
 (pam_sss). But then authentication failed in the "account" clause of the
 sshd section.

 So the question is why there?


>>> .
>
>>
>>> I built another virtual machine on another Debian box, following the
>> same steps. That one worked.
>>
>> I compared all the files I could think of (/etc/pam.d/ files,
>> /etc/nsswitch.conf, /etc/ssd/ssd_config, etc), and made them identical.
>> Didn't help.
>>
>> I then rebuilt the offending machine, removed it from the domain,
>> followed the same steps again, and now ... it works.
>>
>> Go figure.
>>
>
> And having been on that merry-go-round myself more than once, Mr West☺
> that usually means something bad happened in the initial Kerberos
> ticket granting process that happens at LDAP/AD initial config. First you
> need a ticket-granting-ticket from the LDAP or AD domain (the TGT). And
> then you need a session ticket for each kerberos session. Those sessions
> are usually much shorter than the lifetime of a single boot. So sometimes
> they need to be re-acquired outside of the boot process. And yes,
> nsswitch.conf is vital.
>
> There are folks on debian-user who understand it better than me. The first
> time I did that was on Solaris 8 however. Built LDAP, nss and AD interface
> code from source. No base config files except for PAM. Took a few tries but
> it worked. It's hard to shake out and you did it.
> West in pieces... ☺
>
> I would have loved to have found the problem, but more importantly for me,
>> I now know the process works. For now, that's sufficient.
>>
>>
>>
>> --
>> Kent West<")))><
>> Westing Peacefully - http://kentwest.blogspot.com
>>
>

Off topic - Ecuador

[Romero, Fernando]

Consulta hay alguien de Ecuador en esta lista?
Necesito consultar algo.

Saludos
"El contenido del presente mensaje (y sus anexos) es privado, confidencial y de 
exclusivo uso para el destinatario referenciado; es de p?blico conocimiento que 
las comunicaciones por medio de Internet no permiten asegurar ni garantizar la 
confidencialidad de los mensajes transmitidos, as? como tampoco su integridad o 
su correcta recepci?n; es por ello que SOFSE no se responsabiliza de posibles 
perjuicios derivados de la captura, incorporaciones de virus o cualquier otra 
manipulaci?n efectuada por terceros. Las opiniones expresadas en este mensaje y 
en los archivos adjuntos son propias del remitente y no representan la opini?n 
o pol?ticas de SOFSE, salvo que se diga expresamente y el remitente se 
encuentre autorizado para ello"

Re: need to reinstall pulseaudio every day

[tomas]

On Tue, Feb 23, 2021 at 01:40:22PM +0100, Nicolas George wrote:
> Greg Wooledge (12021-02-23):
> > This *is* part of the diagnostics.  Preventing the deletion and then
> > watching the logs to see who complains may help you pinpoint the
> > culprit.  Or it may not.  But it's worth a try.
> 
> Watching the logs was not in the advice. With that addition, the advice
> is reasonable. Without, it was terrible, as was "changing the disk".

[META] we are in violent agreement. Instead of saying "DON'T DO THIS",
I'd humbly propose to enhance that advice, then :)

Cheers
 - t


signature.asc
Description: Digital signature

Re: need to reinstall pulseaudio every day

[tomas]

On Tue, Feb 23, 2021 at 01:07:10PM +0100, Nicolas George wrote:
> fm+deb+u...@phosphorusnetworks.com (12021-02-23):
> > maybe change your disk, but for now, try:
> > 
> > # chattr +i /usr/bin/pulseaudio
> > 
> > and see if it continues disappearing.
> 
> And if somebody has an ache somewhere, they should just take
> painkillers?
> 
> Fixing the symptom without understanding the issue is rarely a good
> idea, especially with an unsubtle heavy handed measure.

That's why I proposed looking into the logs. I've used it like this
as a diagnostic device.

Cheers
 - t


signature.asc
Description: Digital signature

Re: need to reinstall pulseaudio every day

[Nicolas George]

Greg Wooledge (12021-02-23):
> This *is* part of the diagnostics.  Preventing the deletion and then
> watching the logs to see who complains may help you pinpoint the
> culprit.  Or it may not.  But it's worth a try.

Watching the logs was not in the advice. With that addition, the advice
is reasonable. Without, it was terrible, as was "changing the disk".

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: need to reinstall pulseaudio every day

[Greg Wooledge]

Nicolas George (geo...@nsup.org) wrote:
> fm+deb+u...@phosphorusnetworks.com (12021-02-23):
> > maybe change your disk, but for now, try:
> > 
> > # chattr +i /usr/bin/pulseaudio
> > 
> > and see if it continues disappearing.
> 
> And if somebody has an ache somewhere, they should just take
> painkillers?
> 
> Fixing the symptom without understanding the issue is rarely a good
> idea, especially with an unsubtle heavy handed measure.

This *is* part of the diagnostics.  Preventing the deletion and then
watching the logs to see who complains may help you pinpoint the
culprit.  Or it may not.  But it's worth a try.

What's your better idea?  Don't just bad-mouth other people's suggestions
if you have none of your own.

Other suggestions I might make would include:

ls -ld /usr/bin /usr/bin/pulseaudio  # (before the deletion)

If it turns out the permissions on /usr/bin are incorrect, that's a
thing you'll want to fix immediately.

Re: need to reinstall pulseaudio every day

[Nicolas George]

fm+deb+u...@phosphorusnetworks.com (12021-02-23):
> maybe change your disk, but for now, try:
> 
> # chattr +i /usr/bin/pulseaudio
> 
> and see if it continues disappearing.

And if somebody has an ache somewhere, they should just take
painkillers?

Fixing the symptom without understanding the issue is rarely a good
idea, especially with an unsubtle heavy handed measure.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: need to reinstall pulseaudio every day

[tomas]

On Tue, Feb 23, 2021 at 08:37:34AM -0300, fm+deb+u...@phosphorusnetworks.com 
wrote:

[...]

> maybe change your disk, but for now, try:
> 
> # chattr +i /usr/bin/pulseaudio
> 
> and see if it continues disappearing.

And watch your log files. Perhaps you catch the perpetrator
whining loudly that it can't delete that file.

Cheers
 - t


signature.asc
Description: Digital signature

Re: need to reinstall pulseaudio every day

[fm+deb+user]

>
>hi,
>the problem is exactly what says my subject.
>every morning, ls /usr/bin/pulseaudio gives:
> ls: cannot access '/usr/bin/pulseaudio': No such file or directory
>and I must issue "aptitude reinstall pulseaudio" 
>I plan to put the ls command every minute to find when it disappears,
>unless somebody can give me an axplanation (and a fix...)
>
>best regards,
>-- 
>Pierre Frenkiel
>
>

maybe change your disk, but for now, try:

# chattr +i /usr/bin/pulseaudio

and see if it continues disappearing.

Regards, 

Fabio Martins
GPG: 0xCC59C123
Fingerprint: D06E 24DE 2A72 1BB3 A1A0  C790 E51E 33C4 CC59 C123
PHOSPHORUS NETWORKS
https://phosphorusnetworks.com/

Re: Ferramenta de Automação de instalação

[P. J.]

O equivalente ao kickstart para instalação unattended é o pressed[1]

[1]
https://wiki.debian.org/DebianInstaller/Preseed

Em 19/02/2021, Leandro Moreira escreveu:
> Prezados, boa tarde!
>
> Existe para o debian alguma ferramenta  que automatize a configuração do
> sistema operaciona, como o kickstart faz no redhat.
>
> Att.
>
> --
> Leandro Moreira
> DevOPS | Kubernetes | Cloud | Especialista em Infraestrutura
> LPIC1 - Linux Professional Institute Certified | Docker Certified Associate
> E-mail: lean...@leandromoreira.eti.br
> Mobile.: + 55(32) 99906-5713
>


-- 
|  .''`.   A fé não dá respostas. Só impede perguntas.
| : :'  :
| `. `'`
|   `-   Je vois tout

Re: [HS] Recherche Développeur pour interview

[ajh-valmer]

D'après ce que je comprends,
les interviewers ont besoin d'un développeur professionnel,
dont c'est le métier, pas d'un simple utilisateur.

Ada, langage très utilisé dans la haute technologie pourrait faire l'affaire :

https://www.adalog.fr/fr/acces.html

"L'utilisateur est placé devant un dilemme : doit-il se mettre entre les mains 
de Sun/Java ou de Microsoft/C# ?  Restez libre avec Ada !"

Re: Yahoo et Kmail : pas de réception

[Gaëtan PERRIER]

Le mardi 23 février 2021 à 12:16 +0100, ajh-valmer a écrit :
> On Sunday 21 February 2021 20:20:37 didier gaumet wrote:
> > Le 21/02/2021 à 19:27, ajh-valmer a écrit :
> > > Avec Kmail, impossible de recevoir les mails de @yahoo.com.
>  
> > https://fr.aide.yahoo.com/kb/R%C3%A9soudre-les-probl%C3%A8mes-denvoi-et-de-r%C3%A9ception-des-mails-en-mode-POP-ou-IMAP-sln3792.html
> 
> Merci, j'ai lu mais rien à faire, je reçois cette info sans cesse :
> "il est probable le mot de passe que vous avez saisi soit incorrect".
> 
> J'ai testé avec Thunderbird = pareil.
> 
> Il faudrait connaître si un membre de la ML qui a un compte mail Yahoo,
> a pu résoudre le problème...
> 

Je l'ai résolu d'une façon radicale: je n'utilise plus l'adresse yahoo que
j'avais ...

Gaëtan


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

Re: [HS] Recherche Développeur pour interview

[Sylvain Caselli]

Le 23/02/2021 à 07:13, Pierre Couderc a écrit :
Quand un développe avec un langage efficace (C ou C++), il n'y a 
aucune raison a priori d'utiliser l'assembleur.



Bonjour,

je ne sais pas si c'est encore vrai, mais lors de l’échantillonnage 
d'une valeur (du son par exemple) l'utilisation du convertisseur (ou 
tout device du microcontrôleur) ce faisait en assembleur (dans le pgm C 
à) car en C c'est beaucoup trop lent. Logique car il reconfigure tout à 
chaque fois. Je n'ai plus le choix maintenant mais pour lire un bouton 
ou un capteur et allumer une led ou faire tourner un moteur les langages 
évolués m'ont finalement semblé bien compliqués pour faire de la 
robotique. Maintenant qu'il faut les connecter et des interfaces 
tactiles c'est effectivement plus simple (mais est-ce bien utile ?).


Sylvain

Re: Yahoo et Kmail : pas de réception

[ajh-valmer]

On Sunday 21 February 2021 20:20:37 didier gaumet wrote:
> Le 21/02/2021 à 19:27, ajh-valmer a écrit :
> > Avec Kmail, impossible de recevoir les mails de @yahoo.com.
 
>https://fr.aide.yahoo.com/kb/R%C3%A9soudre-les-probl%C3%A8mes-denvoi-et-de-r%C3%A9ception-des-mails-en-mode-POP-ou-IMAP-sln3792.html

Merci, j'ai lu mais rien à faire, je reçois cette info sans cesse :
"il est probable le mot de passe que vous avez saisi soit incorrect".

J'ai testé avec Thunderbird = pareil.

Il faudrait connaître si un membre de la ML qui a un compte mail Yahoo,
a pu résoudre le problème...

Bonne journée.

Re: Una de discs durs

[Josep Lladonosa]

A la feina hem posat uns quants ssd i algun disc dur agafsts amb una brida
on es pot.

Això sí, discs durs sempre ben posats en horitzontal o vertical, que els
plats de dins giren i cap inclinació no és bona...

Un altre aspecte a tenir en compte és que el xassís metàl·lic del disc
hauria d'estar en contacte amb el de la caixa del PC però funcionaria igual
ja que el connector sata té el negatiu (tot i que no és ben bé el
mateix...).

El dt., 23 de febr. 2021, 9:20, Joan  va escriure:

> El Fri, 12 Feb 2021 09:49:35 +0100
> Joan  va escriure:
>
> > El Sun, 3 Jan 2021 09:29:35 +0100
> > Josep Lladonosa  va escriure:
> >
> > > Hola, Joan,
> > >
> > >
> > > Que no sigui cosa del cable SATA.
> > > A la feina hem tingut experiències similars i canviant-lo s'ha
> > > resolt.
> >
> >
> > Per cert, després de canviar el cable SATA ja no ha tornat a succeir
> > la "corrupció"... O sigui, dono per bona l'explicació que era el cable
> > SATA.
> >
> > I t'agraeixo molt, Josep, que apuntessis en aquesta direcció...
> >
> > Pd.: sembla mentida que el que pugui fallar sigui un element estàtic
> > com un cbale... O que aquest comenci a fallar "un bon dia"...
> >
>
>
> Doncs no era el cable. Ahir em va tornar a fallar el disc dur...
>
> Ara em repassaré els missatges que em vau enviar, donant-me línies
> d'investigació (quin pal, perquè aquest tema de hardware no el controlo
> gens!).
>
> De moment, com que l'ordinador, un slimbox, no te dos anys, els he
> enviat un missatge per veure si la garantia cobreix aquest tema (entenc
> que si, però ja vorem).
>
> Estava pensant, però, si comprar-me'n un altre, mentre resolc aquest
> tema, i uso el vell com a dipòsit per clonar/sincronitzar periòdicament
> el primer, en plan backup o, fins i tot, si és possible fer un RAID
> (tampoc sé si és bona idea usar un disc que es va corrompent com a
> segon element del raid). Ara, una cosa que veig és que l'slimbox permet
> collar un disc SATA, però no dos, malgrat tenir el connector de la
> placa base, el que no te és lloc per "cargolar-lo": es pot posar "sense
> collar"??
>
>
>
> >
> > >
> > > La fiabilitat dels discs durs és poca, sempre és recomanable tenir
> > > còpies de seguretat i fer-los treballar per parelles, en raid 1, per
> > > exemple.
> > >
> > > Cada fabricant indica la seva garantia.
> > > Per a mi, els pitjors, Seagate. Els millors, Hitachi (HGST que crec
> > > que és de Western Digital, ara, i que també està bé).
> > >
> > > Bon any,
> > > Josep
> > >
> > > El dg., 3 de gen. 2021, 9:01, Joan  va
> > > escriure:
> > > > El problema que tinc m'ha passat dugues vegades en dugues
> > > > setmanes, i tinc dubtes de si és un tema físic del disc (un disc
> > > > SATA de 4Tb) no massa vell, de potser un parell d'anys, o un
> > > > problema del soft que "desgabella" el disc
> > > >
> > > > És un disc secundari (el sistema el tinc en un SSD) a on guardo
> > > > videos, fotos, etc. Un dels meus sospitosos com a causa de tot
> > > > plegat podria ser l'amule.
> > > >
> > > > Bé, la qüestió és que quan arrenco el sistema la cosa va
> > > > malament, i queda en mode d'emergència, perquè detecta un error:
> > > >
> > > > de gen. 02 16:21:12 pc2019 systemd-fsck[502]: magatzem: Inode
> > > > 38666373 has an invalid extent node (blk 154697780, lblk 0) de
> > > > gen. 02 16:21:12 pc2019 systemd-fsck[502]: magatzem: UNEXPECTED
> > > > INCONSISTENCY; RUN fsck MANUALLY. de gen. 02 16:21:12 pc2019
> > > > systemd-fsck[502]: (i.e., without -a or -p options) de
> > > > gen. 02 16:21:12 pc2019 systemd-fsck[430]: fsck failed with exit
> > > > status 4. de gen. 02 16:21:12 pc2019 systemd-fsck[430]: Running
> > > > request emergency.target/start/replace de gen. 02 16:21:12 pc2019
> > > > systemd[1]: systemd-fsck@dev-disk-by
> > > > \x2duuid-eabfd9a3\x2d1b1f\x2d4144\x2da9d3\x2dd514566fa3fb.service:
> > > > Main process exited, code=exited, status=1/FAILURE de gen. 02
> > > > 16:21:12 pc2019 systemd[1]:
> > > > systemd-fsck@dev-disk-by
> > > > \x2duuid-eabfd9a3\x2d1b1f\x2d4144\x2da9d3\x2dd514566fa3fb.service:
> > > > Failed with result 'exit-code'. de gen. 02 16:21:12 pc2019
> > > > systemd[1]: Failed to start File System Check on
> > > > /dev/disk/by-uuid/eabfd9a3-1b1f-4144-a9d3-d514566fa3fb. de gen. 02
> > > > 16:21:12 pc2019 systemd[1]: Dependency failed for /media/magatzem.
> > > > de gen. 02 16:21:12 pc2019 systemd[1]: Dependency failed for Local
> > > > File Systems. de gen. 02 16:21:12 pc2019 systemd[1]:
> > > > local-fs.target: Job local-fs.target/start failed with result
> > > > 'dependency'. de gen. 02 16:21:12 pc2019 systemd[1]:
> > > > local-fs.target: Triggering OnFailure= dependencies. de gen. 02
> > > > 16:21:12 pc2019 systemd[1]: media-magatzem.mount: Job
> > > > media-magatzem.mount/start failed with result 'dependency'.
> > > >
> > > > I a mi em mostra aquesta pantalla:
> > > >
> > > >
> > > >
> https://upload.disroot.org/r/APnYtXLB#NArCJjbVYVzxd9Hui4K9xb9xhkHzk9i1vE++Qf8BQQA=
> > > >
> > > > Llavors jo per sol·lucionar-ho 

Re: is it possible to add a secondary disk to an existing debian systems and install programs to the secondary disk

[martin f krafft]

Semih,

Maybe I can provide a quick and easy solution, depending on what 
happens when you type


```
$ sudo lvs
```

into a terminal. Could you let us know what that spits out?

Thanks,

--
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
the security, stability and reliability of a computer system

is reciprocally proportional to
the amount of vacuity between the ears of the admin.


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

need to reinstall pulseaudio every day

[Pierre Frenkiel]

hi,
the problem is exactly what says my subject.
every morning, ls /usr/bin/pulseaudio gives:
ls: cannot access '/usr/bin/pulseaudio': No such file or directory
and I must issue "aptitude reinstall pulseaudio" 
I plan to put the ls command every minute to find when it disappears,

unless somebody can give me an axplanation (and a fix...)

best regards,
--
Pierre Frenkiel

Re: is it possible to add a secondary disk to an existing debian systems and install programs to the secondary disk

[Andrei POPESCU]

On Ma, 23 feb 21, 00:37:52, Semih Ozlem wrote:
> I am currently pre-planning. If it could be done, then I am going to go
> about searching and purchasing necessary devices in order to do the task.
> That's why I am asking in the first place. I have a usb device that I can
> attach for testing now.
> 
> Currently I am just running from a live usb. Here is the output of df -h

It seems to me like you are making some assumptions about Debian (and 
possibly Linux distributions in general) that lead to wrong conclusions.

While it is technically possible to install Debian packages to different 
locations this is most likely the wrong solution to your problem.

For a start it may help to understand the Filesystem Hierarchy 
Standard[1][2].

Additionally, a major difference between Debian (as well as most other 
Linux systems) and Windows is that library packages are installed to be 
available for all other packages on the system. This means that a 
library package forcibly installed to a different location is suddenly 
unavailable for packages that might need it. And this is just the 
beginning of potential problems if you go this route.

As you seem to want to experiment the best solution for you is to do 
just that: experiment ;)

I would recommend to start with a blank drive[3] and keep your 
partitioning as simple as possible (e.g. all in one partition).

As you start filling the drive you can look into what data (preferable, 
if your application supports it) or parts of the system you need to move 
to different drives. Common candidates are /home (user data) and /var 
(variable application data) and even /usr (system packages, rather 
unlikely though).

As has already been suggested, LVM can be used to make your storage more 
flexible, while adding significant complexity.

[1] https://manpages.debian.org/hier
[2] Live systems in particular might deviate significantly from it.

Have fun,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Una de discs durs

[Joan]

El Fri, 12 Feb 2021 09:49:35 +0100
Joan  va escriure:

> El Sun, 3 Jan 2021 09:29:35 +0100
> Josep Lladonosa  va escriure:
> 
> > Hola, Joan,
> > 
> > 
> > Que no sigui cosa del cable SATA.
> > A la feina hem tingut experiències similars i canviant-lo s'ha
> > resolt.  
> 
> 
> Per cert, després de canviar el cable SATA ja no ha tornat a succeir
> la "corrupció"... O sigui, dono per bona l'explicació que era el cable
> SATA.
> 
> I t'agraeixo molt, Josep, que apuntessis en aquesta direcció...
> 
> Pd.: sembla mentida que el que pugui fallar sigui un element estàtic
> com un cbale... O que aquest comenci a fallar "un bon dia"...
> 


Doncs no era el cable. Ahir em va tornar a fallar el disc dur... 

Ara em repassaré els missatges que em vau enviar, donant-me línies
d'investigació (quin pal, perquè aquest tema de hardware no el controlo
gens!).

De moment, com que l'ordinador, un slimbox, no te dos anys, els he
enviat un missatge per veure si la garantia cobreix aquest tema (entenc
que si, però ja vorem).

Estava pensant, però, si comprar-me'n un altre, mentre resolc aquest
tema, i uso el vell com a dipòsit per clonar/sincronitzar periòdicament
el primer, en plan backup o, fins i tot, si és possible fer un RAID
(tampoc sé si és bona idea usar un disc que es va corrompent com a
segon element del raid). Ara, una cosa que veig és que l'slimbox permet
collar un disc SATA, però no dos, malgrat tenir el connector de la
placa base, el que no te és lloc per "cargolar-lo": es pot posar "sense
collar"??



> 
> > 
> > La fiabilitat dels discs durs és poca, sempre és recomanable tenir
> > còpies de seguretat i fer-los treballar per parelles, en raid 1, per
> > exemple.
> > 
> > Cada fabricant indica la seva garantia.
> > Per a mi, els pitjors, Seagate. Els millors, Hitachi (HGST que crec
> > que és de Western Digital, ara, i que també està bé).
> > 
> > Bon any,
> > Josep
> > 
> > El dg., 3 de gen. 2021, 9:01, Joan  va
> > escriure: 
> > > El problema que tinc m'ha passat dugues vegades en dugues
> > > setmanes, i tinc dubtes de si és un tema físic del disc (un disc
> > > SATA de 4Tb) no massa vell, de potser un parell d'anys, o un
> > > problema del soft que "desgabella" el disc
> > >
> > > És un disc secundari (el sistema el tinc en un SSD) a on guardo
> > > videos, fotos, etc. Un dels meus sospitosos com a causa de tot
> > > plegat podria ser l'amule.
> > >
> > > Bé, la qüestió és que quan arrenco el sistema la cosa va
> > > malament, i queda en mode d'emergència, perquè detecta un error:
> > >
> > > de gen. 02 16:21:12 pc2019 systemd-fsck[502]: magatzem: Inode
> > > 38666373 has an invalid extent node (blk 154697780, lblk 0) de
> > > gen. 02 16:21:12 pc2019 systemd-fsck[502]: magatzem: UNEXPECTED
> > > INCONSISTENCY; RUN fsck MANUALLY. de gen. 02 16:21:12 pc2019
> > > systemd-fsck[502]: (i.e., without -a or -p options) de
> > > gen. 02 16:21:12 pc2019 systemd-fsck[430]: fsck failed with exit
> > > status 4. de gen. 02 16:21:12 pc2019 systemd-fsck[430]: Running
> > > request emergency.target/start/replace de gen. 02 16:21:12 pc2019
> > > systemd[1]: systemd-fsck@dev-disk-by
> > > \x2duuid-eabfd9a3\x2d1b1f\x2d4144\x2da9d3\x2dd514566fa3fb.service:
> > > Main process exited, code=exited, status=1/FAILURE de gen. 02
> > > 16:21:12 pc2019 systemd[1]:
> > > systemd-fsck@dev-disk-by
> > > \x2duuid-eabfd9a3\x2d1b1f\x2d4144\x2da9d3\x2dd514566fa3fb.service:
> > > Failed with result 'exit-code'. de gen. 02 16:21:12 pc2019
> > > systemd[1]: Failed to start File System Check on
> > > /dev/disk/by-uuid/eabfd9a3-1b1f-4144-a9d3-d514566fa3fb. de gen. 02
> > > 16:21:12 pc2019 systemd[1]: Dependency failed for /media/magatzem.
> > > de gen. 02 16:21:12 pc2019 systemd[1]: Dependency failed for Local
> > > File Systems. de gen. 02 16:21:12 pc2019 systemd[1]:
> > > local-fs.target: Job local-fs.target/start failed with result
> > > 'dependency'. de gen. 02 16:21:12 pc2019 systemd[1]:
> > > local-fs.target: Triggering OnFailure= dependencies. de gen. 02
> > > 16:21:12 pc2019 systemd[1]: media-magatzem.mount: Job
> > > media-magatzem.mount/start failed with result 'dependency'.
> > >
> > > I a mi em mostra aquesta pantalla:
> > >
> > >
> > > https://upload.disroot.org/r/APnYtXLB#NArCJjbVYVzxd9Hui4K9xb9xhkHzk9i1vE++Qf8BQQA=
> > >
> > > Llavors jo per sol·lucionar-ho gaig un e2fsck -c /dev/sdb1
> > >
> > > Que em dona aquestes pantalles (les resumeixo, perquè bàsicament
> > > son 20 minuts de anar dient "yes" a tot el que em proposa, després
> > > de la revisió que dura unes 8 hores o més:
> > >
> > >
> > > https://upload.disroot.org/r/kRLsL2RX#bF9doWYguCMHAvj3APaJNb+GbUBq9zCX2mdrkLJhMAQ=
> > >
> > > https://upload.disroot.org/r/sYqhJfcy#Wv3pVBo0OuvfosT/i1LfCRx+6sTWwSkpWGDJIl4uTkI=
> > >
> > > https://upload.disroot.org/r/UTbxj19F#u5TA97h7ykB7KFj58OSPhgFLqwqFBSv00nHAQ8FoPpU=
> > >
> > > Llavors, les meves preguntes:
> > >
> > > 1) Us sembla que és un fallo de hard (el disc comença a fer el
> > > tonto, amb només 15 mesos), i ja em 

Re: 'ddgr' cli for duckduckgo snafu?

[Michael Howard]

On 23/02/2021 08:13, Darac Marjal wrote:

On 22/02/2021 22:56, Bob Bernstein wrote:

On Mon, 22 Feb 2021, Nicholas Geovanis wrote:


I had the same experience. Gave up on duckduckgo but one time it came
thru
in a pinch.

Why give up on the search engine merely because a rogue util has gone
goofy?

I went looking for duckduckgo search syntax and found what I need,
which is not all that much.

https://help.duckduckgo.com/duckduckgo-help-pages/results/syntax/

WHAT I REALLY WANT TO KNOW is why every doctor's office in the country
wants me to show up fifteen minutes early. Why not just push all the
appts back fifteen minutes? Gets me there at the same time No good?
Hmm...those bastards are up to something.

How do you know that's not already the case? What's the difference
between "Your appointment is at 1430, please arrive 15 minutes early"
and "Your appointment is at 1415, there will be a fifteen minute waiting
period before the doctor sees you"? Nothing measurable.

You need to be there 15 minutes early so you get a good dose of whatever 
is hanging about!


WHAT I REALLY WANT TO KNOW is why anybody is making appointments at 
every doctor's office in the country?


--
Michael Howard.

Re: 'ddgr' cli for duckduckgo snafu?

[Darac Marjal]

On 22/02/2021 22:56, Bob Bernstein wrote:
> On Mon, 22 Feb 2021, Nicholas Geovanis wrote:
>
>> I had the same experience. Gave up on duckduckgo but one time it came
>> thru
>> in a pinch.
>
> Why give up on the search engine merely because a rogue util has gone
> goofy?
>
> I went looking for duckduckgo search syntax and found what I need,
> which is not all that much.
>
> https://help.duckduckgo.com/duckduckgo-help-pages/results/syntax/
>
> WHAT I REALLY WANT TO KNOW is why every doctor's office in the country
> wants me to show up fifteen minutes early. Why not just push all the
> appts back fifteen minutes? Gets me there at the same time No good?
> Hmm...those bastards are up to something.
How do you know that's not already the case? What's the difference
between "Your appointment is at 1430, please arrive 15 minutes early"
and "Your appointment is at 1415, there will be a fifteen minute waiting
period before the doctor sees you"? Nothing measurable.



OpenPGP_signature
Description: OpenPGP digital signature