Re: Mysql et php5.6 => 7.4

2021-04-17 Thread Jean-Michel OLTRA 


Bonjour,


Le samedi 17 avril 2021, ajh-valmer a écrit...


> $mysqli = new mysqli($servername, $username, $password, "association");
> if ($mysqli->connect_errno) {
> echo "Echec lors connexion MySQL : (" . $mysqli->connect_errno . ") " . 
> $mysqli->connect_error;
> }

> $query_string="UPDATE cotisation SET email='$MAIL' 
> WHERE id_cotisation='$ID'";
> if (!$query_string = mysqli_query($query_string)) {
> print ("Erreur de la requete $query_string");  
> exit(); 
> }

Tu dois utiliser l'identifiant de connexion, $mysqli obtenu plus haut.

Donc :
- soit c'est mysqli_query($mysqli, $queryString)
- soit c'est $mysqli->query($queryString)
Tout dépend de ta manière de coder : plutôt procédural (mysqli_query) ou
objet ($mysqli->query).

-- 
jm

Re: new user MacBook

2021-04-17 Thread riveravaldez 
On 4/17/21, David Christensen  wrote:
> On 4/17/21 8:39 AM, Thanos Katsiolis wrote:
>> Hello,
>>
>> I am a new user who would like to try Debian.
>>
>> I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to
>> also
>> install Debian. Will I have any issues installing Debian regarding
>> hardware?
>> I would also appreciate it if you have any tips before the installation
>> as
>> well as if there is any source that helps for the installation.
>>
>> Forgive me if this is not the right place to ask this question, and feel
>> free directing me to the right place.
>
>
> That is called "dual-boot'.  Setting it up correctly is non-trivial; the
> details vary by computer make and model.  Even when I have succeeded at
> dual-boot, I found that, no matter which OS I was running, I always
> needed to do something on the other OS.
>
>
> The obvious answer today is virtualization.  I suggest installing
> VirtualBox, creating a virtual machine, and installing Debian into the
> virtual machine.  That will allow you to "try Debian" (or any other x86
> operating system) with far less risk of making your MacBook unbootable,
> corrupting the native OS, or destroying data.  And, you can use both
> macOS and Debian at the same time.

Hi,

another option (not sure why not mentioned, sorry if this is not convenient)
could be to try with a LiveCD/DVD/USB, you can check:

https://wiki.debian.org/LiveCD
https://wiki.debian.org/DebianLive
https://www.debian.org/CD/live/
https://wiki.debian.org/USBBoot
https://wiki.debian.org/DebianLive/MultibootISO

(Maybe in that order.)

Hope this helps. :)

Best regards!

Re: Need help finding the right package under which to report a bug

2021-04-17 Thread Robbi Nespu 

On 4/18/21 12:31 PM, Robbi Nespu wrote:



I hope my guess is right. It on recently added on kernel up stream, I 
can see the log here


https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu


--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: Need help finding the right package under which to report a bug

2021-04-17 Thread Robbi Nespu 

Hello

On 4/18/21 10:08 AM, Joshua Brickel wrote:
I am using bullseye and when I perform an update (apt-get dist-upgrade)  
to the system I get get the following messages.  I'm not sure if this is 
an intramfs-tools issue or a firmware-amd-graphics issue.  I have the 
latest version firmware/lib/firmware/-amd-graphics installed.


Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-6-amd64
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_ta.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_sos.bin 
for module amdgpu
W: Possible missing firmware /lib/fJoshua Brickelirmware/amdgpu/arcturus_ta.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for 
module amdgpuJoshua Brickel
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_rlc.bin 
for module amdgpuJoshua Brickel
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_mec2.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_mec.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_me.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_pfp.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_ce.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for 
module amdgpu
W: Possible missing firmware /lib/firmwaJoshua Brickelre/amdgpu/navy_flounder_sdma.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_vcn.bin 
for module amdgpuJoshua Brickel
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_floundtheer_smc.bin 
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for 
module amdgpu
W: Possible missing firmware 
/lib/firmware/amdgpu/navy_flounder_dmcub.bin for module amdgpu




I hope my guess is right. It on recently added on kernel up stream, I 
can see the log here


A quick or temporary solution are to git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git 
and copy thus selection (warning line) of missing modules to 
/lib/firmware/amdgpu/


(Don't try my solution if you are novice).

Look like the bug are the 5.10.0-6-amd64 kernel.

--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: command to start sshfs at bootup?

2021-04-17 Thread Gene Heskett 
On Saturday 17 April 2021 21:47:20 Greg Wooledge wrote:

> getent hosts 3dprint
nothing is returned.

I think I might be on the trail though, I just recalled I had to rename 
another machine several months back, from 6040 to sixty40, someplace it 
doesn't like a hostname starting with a number. So I'll investigate that 
tomorrow. I just shut that one down for the night since I've not yet 
added it to amanda's nightly backups.

Thanks Greg.

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

Need help finding the right package under which to report a bug

2021-04-17 Thread Joshua Brickel 
I am using bullseye and when I perform an update (apt-get dist-upgrade)  to
the system I get get the following messages.  I'm not sure if this is an
intramfs-tools issue or a firmware-amd-graphics issue.  I have the latest
version firmware-amd-graphics installed.

Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-6-amd64
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_gpu_info.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_ta.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_sos.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_ta.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_asd.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sos.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_rlc.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec2.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_mec.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_rlc.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_mec2.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_mec.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_me.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_pfp.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_ce.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_sdma.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_sdma.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin
for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_vcn.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_smc.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navy_flounder_dmcub.bin
for module amdgpu

Re: command to start sshfs at bootup?

2021-04-17 Thread Greg Wooledge 
> > The first probable cause that comes to mind for me is that the sshd or
> > the SFTP subsystem of sshd on this "3dprint" host is not working
> > properly. Check the logs on that host and look for anything that might
> > tell you more.
> 
> no mention of sshfs in the logs of the other machines that are Just 
> Working.

Don't "look for sshfs".  The messages may not contain that string.
What you want to do (in general) is see what messages appeared at the
exact time of your failure.  Regardless of whether they contain a
certain string.

> > 1) Does "getent hosts 3dprint" give me the correct IP address?
> no, despite this line in my /etc/hosts
> 192.168.71.45   3dprint.coyote.den3dp

... what *does* it give?

Also, if you want to refer to the machine as "3dprint" then the alias
"3dprint" should appear in your hosts file.  Not "3dp" (or in addition
to "3dp").

> > 2) Can I ping it?
> yes as 3dprint, also as the alias 3dp
> 
> > 3) Can I ssh into it?  As gene?
> yes
> > 4) Can I sftp into it?  As gene?
> 
> haven't tried that, normally use mc, as me to shift things around.

...

Do I even need to say anything more at this point?

You aren't ACTUALLY RUNNING any of the commands that I said to run, are
you.  You're just giving the answers you *think* they would give.

Re: command to start sshfs at bootup?

2021-04-17 Thread Gene Heskett 
On Saturday 17 April 2021 20:26:19 Greg Wooledge wrote:

> On Sat, Apr 17, 2021 at 08:11:37PM -0400, Gene Heskett wrote:
> > I just checked this machine and 4 others, all of whom are mounted to
> > their own named directory as subdirs of /sshnet, which work
> > perfectly without a mention of it in any machines /etc/fstab. Adding
> > the new machine as the last line in this $HOME/bin/mount-machines
> > bash script: 
> > #!/bin/bash
> > sshfs g...@sixty40.coyote.den:/ /sshnet/sixty40
> > sshfs gene@lathe:/  /sshnet/lathe
> > sshfs gene@GO704:/  /sshnet/GO704
> > sshfs pi@rpi4:/ /sshnet/rpi4
> > sshfs gene@TLM://sshnet/TLM
> > sshfs gene@3dprint://sshnet/3dprint
> > --
> > Thats 5 machines that Just Work, and the last says:
> >
> > read: Connection reset by peer
> >
> > sshfs has been installed, but its not running.  How do I start it?
>
> I read this about 5 times trying to figure out what you're actually
> saying.  I find it very confusing.
>
> Near as I can tell after all those attempts to read it, you have ONE
> client machine and SIX server machines.

the other way around generally  although I have inverted the operation in 
order to get something from his machine to anotheer machine on my farm.

> You are trying to set up 6 
> separate sshfs mounts, all from the same client machine, one to each
> of your servers.
>
> Based on the pathname of the script that you give, you appear to be
> trying to do this from an interactive shell.
yes, bash, as me. Root is disallowed. So it only works aas me, although I 
cann ssh into the other machine and then become root with a sudo.

> Not at boot time, not at 
> login time, not using cron, not using a systemd unit, not using
> /etc/rc.local, not using a sysv-rc init.d script, not using any kind
> of automounting.

correct

>
> Now, as near as I can tell from your message, your problem comes down
> to this:
>
>   From an interactive shell, I run the command
> sshfs gene@3dprint:/ /sshnet/3dprint
>
>   and I get the error
> read: Connection reset by peer
>
> The first probable cause that comes to mind for me is that the sshd or
> the SFTP subsystem of sshd on this "3dprint" host is not working
> properly. Check the logs on that host and look for anything that might
> tell you more.

no mention of sshfs in the logs of the other machines that are Just 
Working.

> Also try the typical steps that one would try when debugging an sshfs
> connection:
>
> 1) Does "getent hosts 3dprint" give me the correct IP address?
no, despite this line in my /etc/hosts
192.168.71.45   3dprint.coyote.den3dp

> 2) Can I ping it?
yes as 3dprint, also as the alias 3dp

> 3) Can I ssh into it?  As gene?
yes
> 4) Can I sftp into it?  As gene?

haven't tried that, normally use mc, as me to shift things around.


> 5) If any of the above fail, is there an error message that appears in
> the logs on either system at the same time?
no.

> Any additional debugging step recommendations would need to be based
> on yet-to-be-revealed details.  E.g. there's no point trying something
> like "ssh -vvv" if you can't even ping the machine.
Humm, I just recalled that I had to rename another machine to sixty40 as 
6040 was apparently not a valid hostname. I now wonder if I should 
rename that machine to threedeeprint.domain.name.

That has to be it, I'll change that and try it tomorrow


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: command to start sshfs at bootup?

2021-04-17 Thread Greg Wooledge 
On Sat, Apr 17, 2021 at 08:11:37PM -0400, Gene Heskett wrote:
> I just checked this machine and 4 others, all of whom are mounted to 
> their own named directory as subdirs of /sshnet, which work perfectly 
> without a mention of it in any machines /etc/fstab. Adding the new 
> machine as the last line in this $HOME/bin/mount-machines bash script:
> 
> #!/bin/bash
> sshfs g...@sixty40.coyote.den:/ /sshnet/sixty40
> sshfs gene@lathe:/  /sshnet/lathe
> sshfs gene@GO704:/  /sshnet/GO704
> sshfs pi@rpi4:/   /sshnet/rpi4
> sshfs gene@TLM:/  /sshnet/TLM
> sshfs gene@3dprint:/  /sshnet/3dprint
> --
> Thats 5 machines that Just Work, and the last says:
> 
> read: Connection reset by peer
> 
> sshfs has been installed, but its not running.  How do I start it?

I read this about 5 times trying to figure out what you're actually
saying.  I find it very confusing.

Near as I can tell after all those attempts to read it, you have ONE
client machine and SIX server machines.  You are trying to set up 6
separate sshfs mounts, all from the same client machine, one to each of
your servers.

Based on the pathname of the script that you give, you appear to be trying
to do this from an interactive shell.  Not at boot time, not at login
time, not using cron, not using a systemd unit, not using /etc/rc.local,
not using a sysv-rc init.d script, not using any kind of automounting.

Now, as near as I can tell from your message, your problem comes down to
this:

  From an interactive shell, I run the command
sshfs gene@3dprint:/ /sshnet/3dprint

  and I get the error
read: Connection reset by peer

The first probable cause that comes to mind for me is that the sshd or
the SFTP subsystem of sshd on this "3dprint" host is not working properly.
Check the logs on that host and look for anything that might tell you
more.

Also try the typical steps that one would try when debugging an sshfs
connection:

1) Does "getent hosts 3dprint" give me the correct IP address?
2) Can I ping it?
3) Can I ssh into it?  As gene?
4) Can I sftp into it?  As gene?
5) If any of the above fail, is there an error message that appears in the
   logs on either system at the same time?

Any additional debugging step recommendations would need to be based on
yet-to-be-revealed details.  E.g. there's no point trying something like
"ssh -vvv" if you can't even ping the machine.

Re: command to start sshfs at bootup?

2021-04-17 Thread Gene Heskett 
On Saturday 17 April 2021 19:01:10 Dan Ritter wrote:

> Gene Heskett wrote:
> > Greetings all;
> >
> > Bringing up a new machine on my local network and I've forgotten
> > how, in buster, to start sshfs at bootup?
>
> /etc/fstab:
>
> user@host:/remote/folder /mount/point  fuse.sshfs
> noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home
>/user/.ssh/id_rsa,allow_other,reconnect 0 0
>
> You don't need all of those options -- in particular, you don't
> want noauto and you do want an IdentityFile option.
>
> -dsr-

I just checked this machine and 4 others, all of whom are mounted to 
their own named directory as subdirs of /sshnet, which work perfectly 
without a mention of it in any machines /etc/fstab. Adding the new 
machine as the last line in this $HOME/bin/mount-machines bash script:

#!/bin/bash
sshfs g...@sixty40.coyote.den:/ /sshnet/sixty40
sshfs gene@lathe:/  /sshnet/lathe
sshfs gene@GO704:/  /sshnet/GO704
sshfs pi@rpi4:/ /sshnet/rpi4
sshfs gene@TLM://sshnet/TLM
sshfs gene@3dprint://sshnet/3dprint
--
Thats 5 machines that Just Work, and the last says:

read: Connection reset by peer

sshfs has been installed, but its not running.  How do I start it?


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

Debian chromium package enable_hangout_services_extension=false by default. How to turn it on during run time?

2021-04-17 Thread Robbi Nespu 
Hello! I not able to use "screen share" on google meet using chromium 
browser.


Each time I clicked on it, I get "your browser can't share your screen" 
and dev tool > console don't complaint anything about it.


I did a google-fu and found out it related with a feature that been 
disabled by debian (rule) during built.


$ apt-cache policy chromium
chromium:
  Installed: 89.0.4389.114-1
  Candidate: 89.0.4389.114-1
  Version table:
 *** 89.0.4389.114-1 500
500 http://ftp.jp.debian.org/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status

So I checked here 
https://sources.debian.org/src/chromium/89.0.4389.114-1/debian/rules/

# disabled features
defines+=is_debug=false \
 use_goma=false \
 use_ozone=false \
 use_sysroot=false \
 use_allocator=\"none\" \
 use_libjpeg_turbo=true \
 use_custom_libcxx=false \
 use_gnome_keyring=false \
 use_unofficial_version_number=false \
 enable_vr=false \
 enable_nacl=false \
 enable_nacl_nonsfi=false \
 enable_swiftshader=false \
 enable_reading_list=false \
 enable_one_click_signin=false \
 enable_iterator_debugging=false \
 enable_hangout_services_extension=false \ # <--- HERE
 optimize_webui=false \
 angle_has_histograms=false \
 enable_js_type_check=false \
 treat_warnings_as_errors=false \

How I can turn it on during runtime? without need to patch manually and 
built the package locally?


--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: command to start sshfs at bootup?

2021-04-17 Thread Dan Ritter 
Gene Heskett wrote: 
> Greetings all;
> 
> Bringing up a new machine on my local network and I've forgotten how, in 
> buster, to start sshfs at bootup?
> 

/etc/fstab:

user@host:/remote/folder /mount/point  fuse.sshfs 
noauto,x-systemd.automount,_netdev,users,idmap=user,IdentityFile=/home/user/.ssh/id_rsa,allow_other,reconnect
 0 0

You don't need all of those options -- in particular, you don't
want noauto and you do want an IdentityFile option.

-dsr-

Re: new user MacBook

2021-04-17 Thread David Christensen 

On 4/17/21 8:39 AM, Thanos Katsiolis wrote:

Hello,

I am a new user who would like to try Debian.

I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to also
install Debian. Will I have any issues installing Debian regarding hardware?
I would also appreciate it if you have any tips before the installation as
well as if there is any source that helps for the installation.

Forgive me if this is not the right place to ask this question, and feel
free directing me to the right place.



That is called "dual-boot'.  Setting it up correctly is non-trivial; the 
details vary by computer make and model.  Even when I have succeeded at 
dual-boot, I found that, no matter which OS I was running, I always 
needed to do something on the other OS.



The obvious answer today is virtualization.  I suggest installing 
VirtualBox, creating a virtual machine, and installing Debian into the 
virtual machine.  That will allow you to "try Debian" (or any other x86 
operating system) with far less risk of making your MacBook unbootable, 
corrupting the native OS, or destroying data.  And, you can use both 
macOS and Debian at the same time.



David

Re: Dispositivo de Rede Wi-fi Não reconhecido e com problemas na configuração do arquivo interfaces

2021-04-17 Thread Rodolfo 
Esse cara tem uma placa wifi parecida com a sua, ele resolveu da seguinte
forma:

https://www.reddit.com/r/debian/comments/ehcpab/debian_10_wifi_is_not_showing_up_anywhere_even/


Att.

Em sáb., 17 de abr. de 2021 às 18:24, Antonio Caetano <
antoniocaet...@protonmail.com> escreveu:

> Boa noite Rodolfo, tudo bem?
>
> Já tentei desabilitar o secure boot, mas não resolveu, de qualquer forma
> obrigado pela ajuda.
>
> Att,
>
>
> Antonio Caetano
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> Em sábado, 17 de abril de 2021 às 19:10, Rodolfo 
> escreveu:
>
> Olha, não sei se vai te ajudar, mas logo que comprei meu notebook instalei
> o Debian Buster, logo de primeira o wifi pegou mas ficava caindo do
> nada depois de tanto fuçar, resolvi desabilitar o secure boot, e parou
> de cair e de quebra a placa gráfica também começou a funcionar. Faça esse
> teste.
>
>
> Att.
>
> Em sáb., 17 de abr. de 2021 às 18:06, Antonio Caetano <
> antoniocaet...@protonmail.com> escreveu:
>
>> Boa tarde amigos, tudo bem?
>>
>> Estou com um problema, tenho uma placa de rede wireless da intel e quando
>> instalei o debian 10 buster, por padrão não foi instalado o firmware e
>> muito menos carregou os módulos no kernel, daí pesquisei um pouco e
>> consegui instalar um firmware da intel, entretanto ele funciona
>> parcialmente, eu consigo acessar a rede wifi, navegar na internet,
>> entretanto se eu tentar configurar um dhcp na própria placa ou configurar
>> ip estático no ficheiro /etc/network/interfaces o sistema me desconecta da
>> rede wifi e não reconhece mais o firmware que instalei muito menos carrega
>> os módulos necessários, basicamente eu nem consigo mais enxergar a rede
>> wi-fi. Em resumo só funciona a configuração de "interface network lo" e
>> "inet loopback", daí é muito complicado,pois não consigo fazer testes com
>> virtualização, servidores de arquivo que necessitam de ip estático etc, e
>> outros computadores não me enxergam na rede, gostaria por gentileza que uma
>> ajuda se possível, desde já agradeço abraço a todos. Segue abaixo
>> informações que talvez ajudem vocês a entenderem meu problema.
>>
>> # FIRMWARE INSTALADO NO DIRETORIO /USR/LIB/FIRMWARE:
>>
>> root@debian:/usr/lib/firmware# ls
>> av7110iwlwifi-135-6.ucodeiwlwifi-5150-2.ucode
>> iwlwifi-7265D-22.ucode iwlwifi-9260-th-b0-jf-b0-38.ucode
>> carl9170-1.fw iwlwifi-2000-6.ucode   iwlwifi-6000-4.ucode
>> iwlwifi-7265D-29.ucode iwlwifi-9260-th-b0-jf-b0-41.ucode
>> cis   iwlwifi-2030-6.ucode   iwlwifi-6000g2a-5.ucode
>> iwlwifi-8000C-22.ucode keyspan_pda
>> dsp56kiwlwifi-3160-17.ucode  iwlwifi-6000g2a-6.ucode
>> iwlwifi-8000C-36.ucode usbduxfast_firmware.bin
>> hpiwlwifi-3160-9.ucode   iwlwifi-6000g2b-6.ucode
>> iwlwifi-8265-22.ucode  usbdux_firmware.bin
>> intel iwlwifi-3168-22.ucode  iwlwifi-6050-5.ucode
>> iwlwifi-8265-36.ucode  usbduxsigma_firmware.bin
>> isci  iwlwifi-3168-29.ucode  iwlwifi-7260-17.ucode
>> iwlwifi-9000-pu-b0-jf-b0-34.ucode
>> iwlwifi-1000-5.ucode  iwlwifi-3945-2.ucode   iwlwifi-7260-9.ucode
>> iwlwifi-9000-pu-b0-jf-b0-38.ucode
>> iwlwifi-100-5.ucode   iwlwifi-4965-2.ucode   iwlwifi-7265-17.ucode
>> iwlwifi-9000-pu-b0-jf-b0-41.ucode
>> iwlwifi-105-6.ucode   iwlwifi-5000-5.ucode   iwlwifi-7265-9.ucode
>> iwlwifi-9260-th-b0-jf-b0-34.ucode
>> root@debian:/usr/lib/firmware# cd /etc/network/
>>
>>
>>
>> SAIDA COMANDO LSPCI:
>>
>> root@debian:/etc/network# lspci
>> 00:00.0 Host bridge: Intel Corporation Device 3e35 (rev 0c)
>> 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
>> (Whiskey Lake) (rev 02)
>> 00:04.0 Signal processing controller: Intel Corporation Skylake Processor
>> Thermal Subsystem (rev 0c)
>> 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture
>> Model
>> 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP
>> Thermal Controller (rev 30)
>> 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI
>> Controller (rev 30)
>> 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
>> 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi
>> [Wireless-AC] (rev 30)
>> 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 9de8 (rev
>> 30)
>>
>>
>> CONFIGURAÇÃO ARQUIVO /ETC/NETWORK/INTERFACES(ÚNICO QUE CONECTA AO WIFI E
>> NAVEGA NA INTERNET):
>>
>> root@debian:/etc/network# cat /etc/network/interfaces
>> # This file describes the network interfaces available on your system
>> # and how to activate them. For more information, see interfaces(5).
>>
>> source /etc/network/interfaces.d/*
>>
>> # The loopback network interface
>> auto lo
>> iface lo inet loopback
>>
>>
>>
>>
>>
>> Att,
>>
>>
>> Antonio Caetano
>>
>>
>>
>>
>

command to start sshfs at bootup?

2021-04-17 Thread Gene Heskett 
Greetings all;

Bringing up a new machine on my local network and I've forgotten how, in 
buster, to start sshfs at bootup?

Thanks for a clue or 2.

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: Dispositivo de Rede Wi-fi Não reconhecido e com problemas na configuração do arquivo interfaces

2021-04-17 Thread Rodolfo 
Olha, não sei se vai te ajudar, mas logo que comprei meu notebook instalei
o Debian Buster, logo de primeira o wifi pegou mas ficava caindo do
nada depois de tanto fuçar, resolvi desabilitar o secure boot, e parou
de cair e de quebra a placa gráfica também começou a funcionar. Faça esse
teste.


Att.

Em sáb., 17 de abr. de 2021 às 18:06, Antonio Caetano <
antoniocaet...@protonmail.com> escreveu:

> Boa tarde amigos, tudo bem?
>
> Estou com um problema, tenho uma placa de rede wireless da intel e quando
> instalei o debian 10 buster, por padrão não foi instalado o firmware e
> muito menos carregou os módulos no kernel, daí pesquisei um pouco e
> consegui instalar um firmware da intel, entretanto ele funciona
> parcialmente, eu consigo acessar a rede wifi, navegar na internet,
> entretanto se eu tentar configurar um dhcp na própria placa ou configurar
> ip estático no ficheiro /etc/network/interfaces o sistema me desconecta da
> rede wifi e não reconhece mais o firmware que instalei muito menos carrega
> os módulos necessários, basicamente eu nem consigo mais enxergar a rede
> wi-fi. Em resumo só funciona a configuração de "interface network lo" e
> "inet loopback", daí é muito complicado,pois não consigo fazer testes com
> virtualização, servidores de arquivo que necessitam de ip estático etc, e
> outros computadores não me enxergam na rede, gostaria por gentileza que uma
> ajuda se possível, desde já agradeço abraço a todos. Segue abaixo
> informações que talvez ajudem vocês a entenderem meu problema.
>
> # FIRMWARE INSTALADO NO DIRETORIO /USR/LIB/FIRMWARE:
>
> root@debian:/usr/lib/firmware# ls
> av7110iwlwifi-135-6.ucodeiwlwifi-5150-2.ucode
> iwlwifi-7265D-22.ucode iwlwifi-9260-th-b0-jf-b0-38.ucode
> carl9170-1.fw iwlwifi-2000-6.ucode   iwlwifi-6000-4.ucode
> iwlwifi-7265D-29.ucode iwlwifi-9260-th-b0-jf-b0-41.ucode
> cis   iwlwifi-2030-6.ucode   iwlwifi-6000g2a-5.ucode
> iwlwifi-8000C-22.ucode keyspan_pda
> dsp56kiwlwifi-3160-17.ucode  iwlwifi-6000g2a-6.ucode
> iwlwifi-8000C-36.ucode usbduxfast_firmware.bin
> hpiwlwifi-3160-9.ucode   iwlwifi-6000g2b-6.ucode
> iwlwifi-8265-22.ucode  usbdux_firmware.bin
> intel iwlwifi-3168-22.ucode  iwlwifi-6050-5.ucode
> iwlwifi-8265-36.ucode  usbduxsigma_firmware.bin
> isci  iwlwifi-3168-29.ucode  iwlwifi-7260-17.ucode
> iwlwifi-9000-pu-b0-jf-b0-34.ucode
> iwlwifi-1000-5.ucode  iwlwifi-3945-2.ucode   iwlwifi-7260-9.ucode
> iwlwifi-9000-pu-b0-jf-b0-38.ucode
> iwlwifi-100-5.ucode   iwlwifi-4965-2.ucode   iwlwifi-7265-17.ucode
> iwlwifi-9000-pu-b0-jf-b0-41.ucode
> iwlwifi-105-6.ucode   iwlwifi-5000-5.ucode   iwlwifi-7265-9.ucode
> iwlwifi-9260-th-b0-jf-b0-34.ucode
> root@debian:/usr/lib/firmware# cd /etc/network/
>
>
>
> SAIDA COMANDO LSPCI:
>
> root@debian:/etc/network# lspci
> 00:00.0 Host bridge: Intel Corporation Device 3e35 (rev 0c)
> 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
> (Whiskey Lake) (rev 02)
> 00:04.0 Signal processing controller: Intel Corporation Skylake Processor
> Thermal Subsystem (rev 0c)
> 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
> 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP
> Thermal Controller (rev 30)
> 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI
> Controller (rev 30)
> 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
> 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi
> [Wireless-AC] (rev 30)
> 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 9de8 (rev
> 30)
>
>
> CONFIGURAÇÃO ARQUIVO /ETC/NETWORK/INTERFACES(ÚNICO QUE CONECTA AO WIFI E
> NAVEGA NA INTERNET):
>
> root@debian:/etc/network# cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
>
>
>
>
> Att,
>
>
> Antonio Caetano
>
>
>
>

Dispositivo de Rede Wi-fi Não reconhecido e com problemas na configuração do arquivo interfaces

2021-04-17 Thread Antonio Caetano 
Boa tarde amigos, tudo bem?

Estou com um problema, tenho uma placa de rede wireless da intel e quando 
instalei o debian 10 buster, por padrão não foi instalado o firmware e muito 
menos carregou os módulos no kernel, daí pesquisei um pouco e consegui instalar 
um firmware da intel, entretanto ele funciona parcialmente, eu consigo acessar 
a rede wifi, navegar na internet, entretanto se eu tentar configurar um dhcp na 
própria placa ou configurar ip estático no ficheiro /etc/network/interfaces o 
sistema me desconecta da rede wifi e não reconhece mais o firmware que instalei 
muito menos carrega os módulos necessários, basicamente eu nem consigo mais 
enxergar a rede wi-fi. Em resumo só funciona a configuração de "interface 
network lo" e "inet loopback", daí é muito complicado,pois não consigo fazer 
testes com virtualização, servidores de arquivo que necessitam de ip estático 
etc, e outros computadores não me enxergam na rede, gostaria por gentileza que 
uma ajuda se possível, desde já agradeço abraço a todos. Segue abaixo 
informações que talvez ajudem vocês a entenderem meu problema.

# FIRMWARE INSTALADO NO DIRETORIO /USR/LIB/FIRMWARE:

root@debian:/usr/lib/firmware# ls
av7110 iwlwifi-135-6.ucode iwlwifi-5150-2.ucode iwlwifi-7265D-22.ucode 
iwlwifi-9260-th-b0-jf-b0-38.ucode
carl9170-1.fw iwlwifi-2000-6.ucode iwlwifi-6000-4.ucode iwlwifi-7265D-29.ucode 
iwlwifi-9260-th-b0-jf-b0-41.ucode
cis iwlwifi-2030-6.ucode iwlwifi-6000g2a-5.ucode iwlwifi-8000C-22.ucode 
keyspan_pda
dsp56k iwlwifi-3160-17.ucode iwlwifi-6000g2a-6.ucode iwlwifi-8000C-36.ucode 
usbduxfast_firmware.bin
hp iwlwifi-3160-9.ucode iwlwifi-6000g2b-6.ucode iwlwifi-8265-22.ucode 
usbdux_firmware.bin
intel iwlwifi-3168-22.ucode iwlwifi-6050-5.ucode iwlwifi-8265-36.ucode 
usbduxsigma_firmware.bin
isci iwlwifi-3168-29.ucode iwlwifi-7260-17.ucode 
iwlwifi-9000-pu-b0-jf-b0-34.ucode
iwlwifi-1000-5.ucode iwlwifi-3945-2.ucode iwlwifi-7260-9.ucode 
iwlwifi-9000-pu-b0-jf-b0-38.ucode
iwlwifi-100-5.ucode iwlwifi-4965-2.ucode iwlwifi-7265-17.ucode 
iwlwifi-9000-pu-b0-jf-b0-41.ucode
iwlwifi-105-6.ucode iwlwifi-5000-5.ucode iwlwifi-7265-9.ucode 
iwlwifi-9260-th-b0-jf-b0-34.ucode
root@debian:/usr/lib/firmware# cd /etc/network/

SAIDA COMANDO LSPCI:

root@debian:/etc/network# lspci
00:00.0 Host bridge: Intel Corporation Device 3e35 (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (Whiskey 
Lake) (rev 02)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 0c)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal 
Controller (rev 30)
00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI 
Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi 
[Wireless-AC] (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 9de8 (rev 30)

CONFIGURAÇÃO ARQUIVO /ETC/NETWORK/INTERFACES(ÚNICO QUE CONECTA AO WIFI E NAVEGA 
NA INTERNET):

root@debian:/etc/network# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

Att,

Antonio Caetano

Re: Wi-fi imbutido não encontra nenhuma rede

2021-04-17 Thread riesdra 
Se tiver acesso a internet pelo cabo instale o pacote firmware-realtek * 
Precisa do non-free no sources.Talvez isto resolva.--Ricardo Libanio  On 
Sáb, 17 abr 2021 16:33:46 -0300  leonardodearaujoaugu...@gmail.com  wrote 
Estou com dificuldades para fazer com que a minha placa Realtek 8188CE 
(imbutida, notebook Positivo C14CR21 (não tenho informação sobre o modelo 
específico de notebook, mas segue a ficha pelo hw-probe. 
https://linux-hardware.org/?probe=2829ea9d87))Resultado de inxi 
-n:cynthia@cy:~$ inxi -nNetwork:  Device-1: Realtek RTL8188CE 802.11b/g/n WiFi 
Adapter driver: rtl8192ce   IF: wlp1s0 state: down mac: 9a:53:9b:7a:84:35   
Device-2: JMicron JMC250 PCI Express Gigabit Ethernet driver: jme   IF: 
enp2s0f5 state: down mac: 80:ee:73:79:ec:99   IF-ID-1: usb0 state: unknown 
speed: N/A duplex: N/A mac: ae:27:3e:fe:26:72 Ao erro: em tese a placa é 
reconhecida e aparentemente funciona, mas não localiza nenhum SSID. Tentei 
conectar diretamente à rede existente, sem sucesso.O driver que o sistema 
utiliza é o rtl8192ce. Encontrei também um driver alternativo no github, pra 
nenhum efeito. Tentei utilizar o ndiswrapper para tentar carregar um driver 
windows (sei que a placa funciona, ela é funcional no windows 10) e igualmente 
não obtive sucesso.Alguém com experiência nesse dispositivo poderia auxiliar? 
Posso prover logs se necessário.Obrigado!

Re: Mysql et php5.6 => 7.4

2021-04-17 Thread ajh-valmer 
On Wednesday 14 April 2021 22:09:38 Jean-Michel OLTRA wrote:
> Tiens, une doc en français :
> https://www.php.net/manual/fr/mysqli.quickstart.connections.php
> MariaDB [mysql]> select user, plugin, host from user;
> (chez moi, c'est MariaDB, pas mysql).
> +-+---+---+
> | User| plugin| Host  |
> +-+---+---+
> | root| unix_socket   | localhost |
> | jm  | mysql_native_password | localhost |
> | mariadb.sys | mysql_native_password | localhost |
> +-+---+---+
> Et lire ce qui concerne l'authentification sous mysql 8.
> Ton souci vient peut-être (probablement) de là.

Merci !

J'ai réussi à me connecter à la base mysql8 par ce script :
$mysqli = new mysqli($servername, $username, $password, "association");
if ($mysqli->connect_errno) {
echo "Echec lors connexion MySQL : (" . $mysqli->connect_errno . ") " . 
$mysqli->connect_error;
}

Par contre, c'est ce script php5.6 que je dois adapter en php7.4 :
=
$query_string="UPDATE cotisation SET email='$MAIL' 
WHERE id_cotisation='$ID'";
if (!$query_string = mysqli_query($query_string)) {
print ("Erreur de la requete $query_string");  
exit(); 
}
print ("$MAIL | ID");
}
mysqli_close();
print ("OK !");
exit();
=

Bonne nuit,

Ajh. Valmer

Wi-fi imbutido não encontra nenhuma rede

2021-04-17 Thread Leonardo de Araújo Augusto 
Estou com dificuldades para fazer com que a minha placa Realtek
8188CE (imbutida, notebook Positivo C14CR21 (não tenho informação sobre o
modelo específico de notebook, mas segue a ficha pelo hw-probe.
https://linux-hardware.org/?probe=2829ea9d87))

Resultado de inxi -n:

cynthia@cy:~$ inxi -n

Network:

  Device-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce

  IF: wlp1s0 state: down mac: 9a:53:9b:7a:84:35

  Device-2: JMicron JMC250 PCI Express Gigabit Ethernet driver: jme

  IF: enp2s0f5 state: down mac: 80:ee:73:79:ec:99

  IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac:
ae:27:3e:fe:26:72


Ao erro: em tese a placa é reconhecida e aparentemente funciona, mas não
localiza nenhum SSID. Tentei conectar diretamente à rede existente, sem
sucesso.

O driver que o sistema utiliza é o rtl8192ce. Encontrei também um driver
alternativo no github, pra nenhum efeito. Tentei utilizar o ndiswrapper
para tentar carregar um driver windows (sei que a placa funciona, ela é
funcional no windows 10) e igualmente não obtive sucesso.

Alguém com experiência nesse dispositivo poderia auxiliar? Posso prover
logs se necessário.

Obrigado!

Re: new user MacBook

2021-04-17 Thread Andrew M.A. Cater 
On Sat, Apr 17, 2021 at 06:39:50PM +0300, Thanos Katsiolis wrote:
> Hello,
> 
> I am a new user who would like to try Debian.
> 
> I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to also
> install Debian. Will I have any issues installing Debian regarding hardware?
> I would also appreciate it if you have any tips before the installation as
> well as if there is any source that helps for the installation.
> 
> Forgive me if this is not the right place to ask this question, and feel
> free directing me to the right place.

If this is an Intel model, the topic came up earlier today: there are
InstallingDebianOn pages in the Debian wiki. You may also find the 
image at https://cdimage.debian.org/debian-cd/current/multi-arch/
iso-cd/debian-10.9.0-amd64-i386-netinst.iso useful

[Line deliberately wrapped - it's one long line]

Hope this helps,

Andy Cater

new user MacBook

2021-04-17 Thread Thanos Katsiolis 
Hello,

I am a new user who would like to try Debian.

I have a MacBook Pro (Early 11) which runs Mac OS, to which I want to also
install Debian. Will I have any issues installing Debian regarding hardware?
I would also appreciate it if you have any tips before the installation as
well as if there is any source that helps for the installation.

Forgive me if this is not the right place to ask this question, and feel
free directing me to the right place.

Re: Problem with Macbook 2,1 Installation Instructions

2021-04-17 Thread Steve McIntyre 
Sorry, just realised that i forgot to CC Carl on my response. In case
he's not reading the list:

Andy Cater wrote:
>On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote:
>> Can anyone please help me with this installation?
>> 
>> https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1
>> 
>> the line:
>> grub-install --target=i386-efi --efi-directory=/mnt/usb
>> --boot-directory=/mnt/usb/boot --bootloader-id=boot --removable
>> 
>> I try this and it says 'doesn't look like an EFI file system"
>> 
>> I'm really stuck here.
>> 
>> This macbook supports 64 bit operating system but the UEFI requires 32 bit
>> 
>> that line I entered in the terminal (From the install guide) doesn't work.
>> any help is appreciated
>
>Ignore most of the above:
>
>There is a CD image that will work here: 
>
>https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.9.0-amd64-netinst.iso

Sorry, no. That's a good answer for solving awkward problems for *even
older* Mac machines, but not this one. The machine that Carl has is
similar to the Bay Trail netbooks - it's 64-bit but with crappy
firmware that's limited to 32-bit only.

Carl: please try the multi-arch netinst from

https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.9.0-amd64-i386-netinst.iso

instead. That will start in 32-bit UEFI, then install a 64-bit system
with a 32-bit version of Grub etc. You should not need to do anything
special for this to work.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back

Re: Problem with Macbook 2,1 Installation Instructions

2021-04-17 Thread Steve McIntyre 
Andy Cater wrote:
>On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote:
>> Can anyone please help me with this installation?
>> 
>> https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1
>> 
>> the line:
>> grub-install --target=i386-efi --efi-directory=/mnt/usb
>> --boot-directory=/mnt/usb/boot --bootloader-id=boot --removable
>> 
>> I try this and it says 'doesn't look like an EFI file system"
>> 
>> I'm really stuck here.
>> 
>> This macbook supports 64 bit operating system but the UEFI requires 32 bit
>> 
>> that line I entered in the terminal (From the install guide) doesn't work.
>> any help is appreciated
>
>Ignore most of the above:
>
>There is a CD image that will work here: 
>
>https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.9.0-amd64-netinst.iso

Sorry, no. That's a good answer for solving awkward problems for *even
older* Mac machines, but not this one. The machine that Carl has is
similar to the Bay Trail netbooks - it's 64-bit but with crappy
firmware that's limited to 32-bit only.

Carl: please try the multi-arch netinst from

https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.9.0-amd64-i386-netinst.iso

instead. That will start in 32-bit UEFI, then install a 64-bit system
with a 32-bit version of Grub etc. You should not need to do anything
special for this to work.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts.  We were hired so that management could
 ignore our recommendations and tell us how to do our jobs."  -- Mike Andrews

Re: Problem with Macbook 2,1 Installation Instructions

2021-04-17 Thread Andrew M.A. Cater 
On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote:
> Can anyone please help me with this installation?
> 
> https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1
> 
> the line:
> grub-install --target=i386-efi --efi-directory=/mnt/usb
> --boot-directory=/mnt/usb/boot --bootloader-id=boot --removable
> 
> I try this and it says 'doesn't look like an EFI file system"
> 
> I'm really stuck here.
> 
> This macbook supports 64 bit operating system but the UEFI requires 32 bit
> 
> that line I entered in the terminal (From the install guide) doesn't work.
> any help is appreciated

Ignore most of the above:

There is a CD image that will work here: 

https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.9.0-amd64-netinst.iso

Note: none of the images team has your hardware. Somebody somewhere may
have similarly old Mac hardware and had reported successful installs a while
ago. There were discussions either here / debian-cd as to whether it was 
appropriate to continue making this Mac media.

All the very best, as ever,

Andy C

Problem with Macbook 2,1 Installation Instructions

2021-04-17 Thread Carl N 
Can anyone please help me with this installation?

https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1

the line:
grub-install --target=i386-efi --efi-directory=/mnt/usb
--boot-directory=/mnt/usb/boot --bootloader-id=boot --removable

I try this and it says 'doesn't look like an EFI file system"

I'm really stuck here.

This macbook supports 64 bit operating system but the UEFI requires 32 bit

that line I entered in the terminal (From the install guide) doesn't work.
any help is appreciated

Re: hello. Please help this big report go in the correct direction....

2021-04-17 Thread didier gaumet 

Le 17/04/2021 à 08:44, Timothy Danielson a écrit :
[...]
I am operating PureOS. I haven't honestly 

[...]
https://www.maketecheasier.com/backup-files-to-google-drive-linux/ 

[...]

Hello,

 From what I gather, PureOS is a Debian derivative with the Gnome Desktop.

 Nautilus, the Gnome file manager can access Google Drive 
out-of-the-box when a Google account is set up :


https://www.howtogeek.com/196635/an-official-google-drive-for-linux-is-here-sort-of-maybe-this-is-all-well-ever-get/
(go directly to the "on gnome desktops" chapter)

If you want to backup/restore to/from Google Sync, you just can use a 
simple Gnome backup tool like Deja-dup (I have verified, it is present 
in PureOS repositories)

 https://wiki.gnome.org/Apps/DejaDup

Non need to add a PPA, install google-drive-ocamlfuse or whatever...

Further,
- PureOs is not Debian even if it is based opon it: you would have 
better support inquiring the PureOS community thant the Debian one
- PureOS is not Ubuntu: I do not know exactly the situation but chances 
are that PPA repositories are no better supported in PureOS than in Debian


Cheers

Pulseaudio-dlna ne trouve pas Chromecast

2021-04-17 Thread Tulum 
Bonjour,

J'utilise Pulseaudio-dlna pour envoyer le son sur ma Box (Freebox Pop). 
Seulement pulseaudio-
dlna ne trouve pas le service chromecast de la box. Par contre spotify lui le 
trouve bien.
J'ai aussi un service DLNA sur la box qui lui est bien trouvé.
Je précise que le firewall est arrêté (firewalld). C'est autre problème que je 
soulèverai dans un 
autre post une fois celui-ci résolu.
Voilà la sortie en console :

*@PC1*:*~*$ pulseaudio-dlna --create-device-config 
04-17 09:39:17 pulseaudio_dlna.applicationINFO Using 
version: 0.6.0 
04-17 09:39:17 pulseaudio_dlna.applicationINFO Binding 
to *:8080 
04-17 09:39:17 pulseaudio_dlna.applicationINFO Starting 
discovery ... 
04-17 09:39:17 pulseaudio_dlna.plugins.chromecast INFO 
ChromecastPlugin.discover() 
04-17 09:39:17 pychromecast   INFO Querying 
device status 
Exception in thread zeroconf-ServiceBrowser__googlecast._tcp.local.: 
Traceback (most recent call last): 
 File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner 
   self.run() 
 File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1557, in run 
   self._service_state_changed.fire( 
 File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1333, in fire 
   h(**kwargs) 
 File "/usr/lib/python3/dist-packages/zeroconf/__init__.py", line 1427, in 
on_change 
   listener.add_service(*args) 
 File "/usr/lib/python3/dist-packages/pychromecast/discovery.py", line 65, in 
add_service 
   self._add_update_service(zconf, typ, name, self.add_callback) 
 File "/usr/lib/python3/dist-packages/pychromecast/discovery.py", line 123, in 
_add_update_service 
   callback(uuid, name) 
 File "/usr/lib/python3/dist-packages/pychromecast/__init__.py", line 246, in 
internal_callback 
   callback( 
 File "/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/__init__.py", 
line 36, in wrapper 
   device = f(*args, **kwargs) 
 File 
"/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/chromecast/__init__.py",
 line 47, in 
_on_device_added 
   return ChromecastRendererFactory.from_pychromecast(device) 
 File 
"/usr/lib/python3/dist-packages/pulseaudio_dlna/plugins/chromecast/renderer.py",
 line 183, 
in from_pychromecast 
   ip=pychromecast.host, 
AttributeError: 'Chromecast' object has no attribute 'host' 
Exception in thread Thread-10: 
Traceback (most recent call last): 
 File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner 
   self.run() 
 File "/usr/lib/python3.9/threading.py", line 1266, in run 
   self.function(*self.args, **self.kwargs) 
TypeError: 'ServiceBrowser' object is not callable 
04-17 09:39:22 pulseaudio_dlna.plugins.dlna.ssdp  INFO 
SSDPListener.shutdown() 
04-17 09:39:22 pulseaudio_dlna.plugins.dlna.ssdp  INFO 
SSDPListener.serve_forever() 
04-17 09:39:22 pulseaudio_dlna.plugins.dlna.ssdp  INFO 
SSDPListener.run() 
04-17 09:39:25 pulseaudio_dlna.discover   INFO 
SSDPDiscover.search() 
04-17 09:39:25 pulseaudio_dlna.plugins.dlna   INFO 
DLNAPlugin.discover() 
04-17 09:39:25 pulseaudio_dlna.holder INFO 
Holder.search() 
04-17 09:39:25 pulseaudio_dlna.applicationINFO 
Discovery complete. 
04-17 09:39:25 pulseaudio_dlna.applicationINFO Found 
the following devices: 
04-17 09:39:25 pulseaudio_dlna.applicationINFO ATV_2 
(DLNA) 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
Mp3Codec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
WavCodec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
AacCodec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
FlacCodec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
OggCodec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
L16Codec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
L16Codec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
L16Codec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO   - 
L16Codec 
04-17 09:39:25 pulseaudio_dlna.applicationINFO Your 
config was successfully 
written to
Si je comprends bien, il y a un problème avec zeroconf. Qwant ne m'a pas aidé.

Merci pour l'aide
BEGIN:VCARD
VERSION:3.0
EMAIL;TYPE:tu...@free.fr
N:
NICKNAME:Tulum
UID:4d162a53-38e0-42c1-8855-2a85da07fa7d
X-KADDRESSBOOK-MailAllowToRemoteContent:TRUE
END:VCARD



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

Re: Truc louche avec ssh

2021-04-17 Thread BERTRAND Joël 
Sébastien Dinot a écrit :
> Basile Starynkevitch a écrit :
>> je crois qu'il faut le compiler depuis son code source
> 
> Inutile, l'outil est disponible en version 1.3.2 (dernière version
> publiée par le projet, en juillet 2017) dans les versions stable,
> testing et unstable de Debian :
> 
> https://tracker.debian.org/pkg/mosh

Je viens de l'installer, je vous tiens au courant.

JKB

Re: Truc louche avec ssh

2021-04-17 Thread Sébastien Dinot 
Basile Starynkevitch a écrit :
> je crois qu'il faut le compiler depuis son code source

Inutile, l'outil est disponible en version 1.3.2 (dernière version
publiée par le projet, en juillet 2017) dans les versions stable,
testing et unstable de Debian :

https://tracker.debian.org/pkg/mosh

Sébastien

-- 
Sébastien Dinot, sebastien.di...@free.fr
http://www.palabritudes.net/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Re: Truc louche avec ssh

2021-04-17 Thread BERTRAND Joël 
Basile Starynkevitch a écrit :
> 
> On 4/16/21 10:01 PM, Sébastien Dinot wrote:
>> BERTRAND Joël a écrit :
>>> Rien à signaler dans tcpdump. C'est la première chose que j'ai
>>> regardé... Ça s'arrête sur un broken pipe. J'ai l'impression que c'est
>>> un routeur quelque part qui coupe, mais je ne vois pas comment il
>>> ferait la différence entre un terminal inactif et un tail -F.
>> Ne serait-ce tout simplement pas révélateur d'une connexion instable,
>> intermittente ? Tu ne t'en rends pas compte dans le terminal inactif,
>> car la coupure passe justement inaperçue (les sockets restent valides).
>> Mais lorsque le flux est continu, là, l'intermittence de la connexion se
>> révèle rapidement.
>>
>> Sébastien
> 
> 
> On pourrait dans ce cas utiliser mosh.
> 
> https://mosh.org/

Tiens, je n'avais pas pensé à ça. Effectivement, avec ma connexion de
type Internet pour les plouc (le réseau téléphonique d'Orange est plus
que foireux dans mon coin et j'attends la fibre avec une certaine
impatiente !), j'ai assez souvent des bagots. Après plus d'un an de
combat avec Orange (je suis en dégroupage partiel Nerim), la SEULE chose
que j'ai obtenu, c'est qu'ils limitent le débit de la ligne de 7,5 Mbps
à moins de 4 ! Pour envoyer des fichiers de fabrication à l'autre bout
du monde, j'en suis à envoyer des cartes SD par UPS !

Merci, je teste,

JKB

hello. Please help this big report go in the correct direction....

2021-04-17 Thread Timothy Danielson 
Hello,

I apologize for my  mental deficits. (I will leave that story for the end,
don't read it if you feel hurried,) I Respect what you do and I REALLY,
REALLY hate to ask for this level of assistance. I'm using PureOS, which I
guess is a derivative of Debian. I had started with 7.0 (Wheezy) and went
to 8.0. I never had the gonads to use Sid TBH. I ran the stables. Although
I was a TINY variant by running a KDE desktop. I also had XFCE and LXDE?
installed, for really no other reason than I had read about them and
certain authors SWORE by them so I gave them a whirl.

O.K. as I'm sure you will see, I am operating PureOS. I haven't honestly
kept up as well as I would wish as my internet is EXCLUSIVELY through my
cell phone now. (What can I say, it's one of the "wonders" of being poor in
the USA, which is better than poor in any 3rd world country. I'm now
complaining, simply sharing that I'm trying to do my best with what I
have.) Again I digress (OK, I'm 90% digressed! I want to be brief with my
story and after that will be a cut and paste of EVERYTHING I could put on
the screen so you could see what U saw and hope it will give you some
insight into what is going wrong and how t fix the problem. At this point,
I am simply going to hope that this is not 100% the result of my failed
updating.

*PERSONAL STORY*: OK, do NOT read this if pressed for time, however, you
may possibly, in some way  benefit from reading "some other blokes" rough
story. I received my TBI (Traumatic Brain Injury) On February 23rd, 2006.
How do I know this? well, when I was in coma; (from what I experienced was
on the average for those that were able to resume life afterwards;) I had
lost orientation to where and WHEN I was! I had some misunderstandings. I
THOUGHT I was a dew YEARS earlier than when I was and did not know I was
HOME... NOT in the ARMY! So, when I was awoken at 9:00 a.m. and saw the sun
FULLY RISEN, shining in it's blazing glory, not like it i at o'dark thirty
in the morning, i was freaked out! I started getting frustrated at some
poor nurse, (which I later felt SO BAD about my mis-reaction that I made a
trip JUST to apologize to her!) I yelled something to the effect of, "Why
did you wake me for PT so LATE!!! The 1SG (First Sargent) is going to
f*ck!n* kill me! I'll be article 15'ed! I don't want that $hi! (it was
understood in the military article 15 is 1/2 pay + extra duty for 2 weeks +
deferred promotion (which is MORE lost pay,))  (suffice to say, was REALLY,
REALLY, bad! This, was avoided TREMENDOUSLY!)   poor, poor nurse I
wasn't 100% swearing 2 of every 3 words forming a constructive and coherent
sentence... yet. BUT she was able to glimpse down that hall and see the
room on the end.


Long story short again, that was after my INITIAL brain injury which
honestly was HUGE for me! It was like taking a 52 card deck + 2 jokers and
then taking the jokers out and 5 random cards which NOBODY knew WHICH
specific ones were taken out. After that I had a couple shunt "revisions",
which involve me being put to sleep and have them open my head to repair
the "shunt", a device that basically helps my body do what most do
naturally. I woke up 90-95% of who I was before, much like the initial TBI.
but 95% of 95%f 95% is GREAT! when looking at the alternative OF COURSE!
but 95% of 95%f 95% is 85.7%... not terrible but that is on the upper end
too, and a 4the time will be 85.4%

/ if it were even slightly less like 92.5% it would be 79.2% ans 73.2%
respectively. My mistake was being god at math and NOT taking it as a
major! DOH!


as promised, here us *EVERYTHING* from my *terminal window*:


I messed up! there was a process that dely I umped more info and it
overwrote! ARRRGHH! I will try to reproduce it

https://www.maketecheasier.com/backup-files-to-google-drive-linux/

sudo add-apt-repository ppa:alessandro-strada/ppa

sudo apt update && sudo apt install google-drive-ocamlfuse

mkdir -p ~/mount/google-drive

I believe I created this dir and this is where the headaches started:

google-drive-ocamlfuse ~/mount/google-drive

strangely I had a similar readout after I attempted to run
reportbug but i am honestly a bit foggy on what I did:

timdanielson@td546:~$ google-drive-ocamlfuse ~/mount/google-drive
Could not find the database of available applications, run
update-command-not-found as root to fix this
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:

command-not-found version: 0.3
Python version: 3.7.3 final 0
Distributor ID: PureOS
Description:PureOS
Release:9.0
Codename:   amber
Exception information:

local variable 'cnf' referenced before assignment
Traceback (most recent call last):
  File "/usr/share/command-not-found/CommandNotFound/util.py", line
23, in crash_guard
callback()
  File "/usr/lib/command-not-found", line 93, in main
if not cnf.advise(args[0],