Re: NVME disk drive

[Jeremy Ardley]

Almost certainly no.

Recent versions of debian can run SATA and PCIe variants without 
anything special.


The only thing you may want is specialised software tools to monitor the 
device, but they aren't essential.



On 8/12/21 3:29 pm, Piper H wrote:

dear community

I bought a new NVME disk and plan to replace the old SSD disk on my 
home box.

Does this NVME require a special drive for the Debian system?

Thank you
Piper

--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

NVME disk drive

[Piper H]

dear community

I bought a new NVME disk and plan to replace the old SSD disk on my home
box.
Does this NVME require a special drive for the Debian system?

Thank you
Piper

Re: Install older versions of Debian with WSL

[john doe]

On 12/7/2021 5:15 PM, Andrew M.A. Cater wrote:

On Tue, Dec 07, 2021 at 03:54:37PM +0100, Max Nadig wrote:

Hi,

I was trying to install Debian 10 via WSL on windows. The problem is, I 
automatically get v11 Bullseye.
Is there some way to specify the version or load a custom Debian version with 
WSL?

I already posted this question into the WSL Git repo. So far I couldn't find a 
solution for this.
https://github.com/microsoft/WSL/issues/7805

Are there maybe legacy builds of the Debian microsoft store app available? This 
would probably solve my problem.

Thank you for the help, best,
Max


Why do you want Debian 10 specifically? You could try the IRC channel

#debian-wsl

on OFTC / see if you can find the maintainer.

In general terms, as soon as a release is put out, it's uploaded by
rhaist to Microsoft - you want the latest stable to be the one used,



If you realy need Buster, using VirtualBox or Qemu on Windows might fit
the bill.

--
John Doe

Re: mariadb qui ne démarre plus

[Sébastien Dinot]

Bonjour Joël,

BERTRAND Joël a écrit :

> les seuls cas à peu près similaires indiquent que la base de données
> était déjà corrompu (mais bizarrement, cela s'est aussi passé juste
> avec une mise à jour entre les mêmes versions). Or dans mon cas, ce
> n'est pas possible. J'ai réinstallé une version récente de la réplique
> pas plus tard que ce matin et elle fonctionnait avant que je ne
> redémarre la machine à la suite de sa mise à jour...

« ce n'est pas possible », en informatique « ce n'est pas possible » ;)


> déc. 07 23:08:26 hilbert mysqld[3627]: 2021-12-07 23:08:26 0 [ERROR]
> Fatal error: Can't open and lock privilege tables: 'mysql.user' is not
> of type 'TABLE'

Ce message d'erreur laisse pourtant bien supposer une corruption des
données, à moins que ce message ne soit induit par l'impossibilité
d'accéder au fichier et donc par un problème de permission sur le
répertoire ou le fichier. As-tu vérifié ces permissions ? Utilises-tu
SELinux ou AppArmor ? Utilises-tu les répertoires standard du système ou
as-tu déporté les fichiers ailleurs ?

Sinon, le disque dur est-il récent ? L'as-tu contrôlé via un fsck ?

Sur la page ci-dessous, on trouve une base de connaissance listant les
différentes raisons pouvant conduire à l'échec du démarrage de MariaDB
et ce qu'il faut faire pour y remédier :

https://mariadb.com/kb/en/what-to-do-if-mariadb-doesnt-start/



-- 
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: SD card, exfat, file mtime wrong

[David Wright]

On Wed 08 Dec 2021 at 16:37:25 (+1100), David wrote:
> On Wed, 8 Dec 2021 at 16:16, David Christensen wrote:
> > On 12/7/21 7:28 PM, David wrote:
> > > On Wed, 8 Dec 2021 at 14:07, David Christensen wrote:
> > >> On 12/6/21 6:37 PM, David Christensen wrote:
> 
> > > I might also check this info
> > >https://unix.stackexchange.com/a/640906
> > > that I mentioned before, just to see if it was relevant. I didn't
> > > look closely.
> 
> > It looks like vfat only.
> 
> I wonder did you note this part? ...
> """
> Seems like the problem resides in the Linux kernel itself, as the
> timezone may (and usually do) differ between the kernel and the
> userspace. time.c file in the kernel/time in the Linux kernel source
> tree holds (and exports) the struct timezone sys_tz, which is then
> used in fs/fat/misc.c in the FAT time <-> UNIX time conventions. The
> tz_minuteswest field of this struct is used to show the difference
> between the current timezone and the UTC, and it is taken into
> consideration if the tz=UTC option is not passed to the mount.vfat
> command.
> """
> Which I do not read as necessarily being "vfat only".
> 
> Because perhaps you are likewise not passing that option when
> mounting exfat, maybe because it does not even have that
> option, per my other links.
> 
> In your situation, I would run the test code given there to
> see if it is relevant, and if there is any difference with the
> older Debian versions that do work.

It's probably worth reading the Release Notes for bullseye, §2.2.8,
and making sure that you're using the appropriate utilities. That
section indicates the main change that has occurred.

If the camera is just a camera, my advice would still be to use UTC.
It's astonishing how complicated using anything else can become, as
/everything/ that touches the filesystem and the image and its
thumbnails etc etc has to get it absolutely right.

Cheers,
David.

Re: SD card, exfat, file mtime wrong

[David]

On Wed, 8 Dec 2021 at 16:16, David Christensen
 wrote:
> On 12/7/21 7:28 PM, David wrote:
> > On Wed, 8 Dec 2021 at 14:07, David Christensen  
> > wrote:
> >> On 12/6/21 6:37 PM, David Christensen wrote:

> > I might also check this info
> >https://unix.stackexchange.com/a/640906
> > that I mentioned before, just to see if it was relevant. I didn't
> > look closely.

> It looks like vfat only.

I wonder did you note this part? ...
"""
Seems like the problem resides in the Linux kernel itself, as the
timezone may (and usually do) differ between the kernel and the
userspace. time.c file in the kernel/time in the Linux kernel source
tree holds (and exports) the struct timezone sys_tz, which is then
used in fs/fat/misc.c in the FAT time <-> UNIX time conventions. The
tz_minuteswest field of this struct is used to show the difference
between the current timezone and the UTC, and it is taken into
consideration if the tz=UTC option is not passed to the mount.vfat
command.
"""
Which I do not read as necessarily being "vfat only".

Because perhaps you are likewise not passing that option when
mounting exfat, maybe because it does not even have that
option, per my other links.

In your situation, I would run the test code given there to
see if it is relevant, and if there is any difference with the
older Debian versions that do work.

Re: SD card, exfat, file mtime wrong

[David Christensen]

On 12/7/21 7:28 PM, David wrote:

On Wed, 8 Dec 2021 at 14:07, David Christensen
 wrote:

On 12/6/21 6:37 PM, David Christensen wrote:



I verified the clock in the camera before taking the picture.  It was
set to local time.
Debian 9 displays the correct mtime when I mount the SDXC card.
Debian 10 displays the correct mtime when I mount the SDXC card.
Debian 11 displays the wrong mtime when I mount the SDXC card.
How do I fix or work around this feature, bug, or whatever in Debian 11?
What package do I file a bug report against?


Based on the above regression I would suggest to file a bug with
the above information in Debian against the mount package.



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001306



I might also check this info
   https://unix.stackexchange.com/a/640906
that I mentioned before, just to see if it was relevant. I didn't
look closely.



It looks like vfat only.



2021-12-07 19:03:13 dpchrist@laalaa ~
$ dpkg-query -S /usr/bin/mount
dpkg-query: no path found matching pattern /usr/bin/mount


You've unfortunately hit a bug/breakage that is currently the
subject of some controversy in Debian.
See here, or search for "merge(d) user usr":
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000715#10



Yuck.


David

Re: SD card, exfat, file mtime wrong

[David]

On Wed, 8 Dec 2021 at 14:07, David Christensen
 wrote:
> On 12/6/21 6:37 PM, David Christensen wrote:

> I verified the clock in the camera before taking the picture.  It was
> set to local time.
> Debian 9 displays the correct mtime when I mount the SDXC card.
> Debian 10 displays the correct mtime when I mount the SDXC card.
> Debian 11 displays the wrong mtime when I mount the SDXC card.
> How do I fix or work around this feature, bug, or whatever in Debian 11?
> What package do I file a bug report against?

Based on the above regression I would suggest to file a bug with
the above information in Debian against the mount package.

I might also check this info
  https://unix.stackexchange.com/a/640906
that I mentioned before, just to see if it was relevant. I didn't
look closely.

> 2021-12-07 19:03:13 dpchrist@laalaa ~
> $ dpkg-query -S /usr/bin/mount
> dpkg-query: no path found matching pattern /usr/bin/mount

You've unfortunately hit a bug/breakage that is currently the
subject of some controversy in Debian.
See here, or search for "merge(d) user usr":
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000715#10

Re: SD card, exfat, file mtime wrong

[David Christensen]

On 12/6/21 6:37 PM, David Christensen wrote:

debian-user:

I recently installed debian-live-11.1.0-amd64-xfce+nonfree.iso on a Dell 
Latitude E6520:


2021-12-06 17:52:45 dpchrist@laalaa ~
$ cat /etc/debian_version ; uname -a
11.1
Linux laalaa 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 
GNU/Linux



I am in California, USA.  My timezone is Pacific Standard Time (PST). 
UTC is 8 hours ahead.  tzselect(1) calls my timezone "America/Los_Angeles".



When I insert a SDXC card formatted with exfat into a USB adapter, plug 
the adapter into the laptop, and double-click on the icon that appears 
on the desktop, the SD card filesystem is mounted:


2021-12-06 17:52:53 dpchrist@laalaa ~
$ mount | grep media
/dev/sdc1 on /media/dpchrist/**redacted** type exfat 
(rw,nosuid,nodev,relatime,uid=**redacted**,gid=**redacted**,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro,uhelper=udisks2) 




When I list the files on the SD card, the mtime is wrong.  For example, 
here is a photograph that I took about ten minutes ago:


2021-12-06 18:13:02 dpchrist@laalaa 
/media/dpchrist/**redacted**/DCIM/**redacted**

$ ll IMG_6947.JPG
-rwxr-xr-x 1 dpchrist dpchrist 3988022 2021-12-06 10:02:57 IMG_6947.JPG


It appears that mount(8) and/or the exfat driver consider the mtime to 
be in UTC, and are applying my timezone adjustment of -08:00 hours (?).



I would like Debian 11 to display the mtime without any modification 
(e.g. correct local time).



Suggestions?


David




On 12/6/21 7:39 PM, David wrote:

> In idle curiosity I spent a few seconds searching and will share what
> I found in case it might be useful.
>
> Apparently vfat has mount options to work around this, maybe
> exfat does?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998189
> https://www.kernel.org/doc/html/latest/filesystems/vfat.html
>
> And some details about exfat, and kernel timezone awareness.
>
> https://www.sans.org/blog/exfat-file-system-time-zone-concerns/
> 
https://unix.stackexchange.com/questions/640555/vfat-linux-invalid-file-timestamps-shown-after-a-reboot

>
> Hope this helps, I have nothing further to add.


On 12/6/21 9:07 PM, David Wright wrote:
> I would first start with the camera. What do the internal timestamps
> say about when you took the photograph. (I find it useful to take a
> photograph of a clock, and archive it.) Then look at the filesystem
> timestamp (which you've done). And of course, there's the filename,
> sometimes a sequence number, sometimes a timedate (mangled, so it
> usually sorts in a bizarre order). They're all different.
>
> The camera in my mobile telephone writes precise UTC timestamps in
> the file. I never see the filesystem as I can only bluetooth them out.
> However, the filenames are local minute-accurate timestamps.
>
> A SIM-less mobile (same manufacturer, different brand) behaves
> entirely differently, using local time for both. That mobile/must/
> display local time as it's my bedside/alarm clock. (It's odd: the
> time is not precise, yet it knows when to switch from standard
> to DST. I haven't worked out how it does that.)
>
> I keep the clock in my real camera set to UTC at all times, avoiding
> any problems (when mounted with options below). But you'd never
> want to routinely tell the time by working through its menus.
>
> Next comes the filesystem, exFAT, which I've not yet had to use.
> The wiki page says it uses local time, but has a time zone marker
> in offset relative to UTC (starting with Vista SP2). So that means
> there are probably newer devices out there that write it, and older
> ones which don't. So you'd need to check the behaviour writing onto
> both FAT and exFAT filesystems. And really you need to repeat your
> check in winter/summer. Does your device know the real local time
> or is it just counting time since you last set it. (Trust microsoft
> to screw things up yet again.)
>
> Finally, what does linux do, and are there mount options for exFAT.
> My SD cards are always mounted with:
> vfat 
rw,errors=remount-ro,utf8,tz=UTC,shortname=mixed,user,noauto,fmask=137,dmask=027

> regardless of which camera it was used in. When I copy the files
> off the card to a "proper" filesystem, I run a program that
> observes the camera's fingerprint, and makes appropriate adjustments
> to the filenames, and both internal and filesystem timestamps.
> (Eg, two of our phones add a/b/… suffixes to pictures taken within
> the same minute, yet the seconds can be read from the internal
> timestamps even if the timezone is wrong.)
>
> Whether there's another adjustment for people running RTC=local,
> I have no idea. Ditto for anyone who lets Windows loose on the task.
>
> Cheers,
> David.


On 12/6/21 11:50 PM, Dirk Neumann wrote:
> Most cameras write a timestamp also into the exif data. If you look at
> such an image, you will find something like this "2021:01:18 08:46:28"


I verified the clock in the camera before taking the picture.  It was 
set to local time.

Re: Webbserver

[Anders Jackson]

Hej.

Den tis 7 dec. 2021 kl 22:33 skrev Ttl <7ttl72...@gmail.com>:
>
> Kan jag ha webbserver på min  debian dator Guds frid ttl

Ja, det kan du.  Du kan läsa mer om det i boken "The Debian
Administrator's Handbook": https://debian-handbook.info/

Du kan läsa den på webbsidan, eller du kan köpa den om du vill hjälpa
de som skrivit boken. Du kan tom installera den som ett paket i
Debian, dvs

Utför följande två rader i kommando fönster så skall du kunna läsa den
lokalt på din dator.

sudo apt install debian-handbook
sensible-browser file:/usr/share/doc/debian-handbook/html

Lycka till.
/Jackson

mariadb qui ne démarre plus

[BERTRAND Joël]

Bonsoir à tous,

Je viens de mettre à jour une machine de test et mariadb ne démarre
plus (ni automatiquement, ni à la main). J'ai comme erreur, la chose
suivante :

déc. 07 23:07:47 hilbert systemd[1]: Starting MariaDB 10.3.29 database
server...
déc. 07 23:07:47 hilbert mysqld[2974]: 2021-12-07 23:07:47 0 [Note]
/usr/sbin/mysqld (mysqld 10.3.29-MariaDB-0+deb10u1-log) starting as
process 2974 ...
déc. 07 23:07:49 hilbert systemd[1]: mariadb.service: Main process
exited, code=exited, status=1/FAILURE
déc. 07 23:07:49 hilbert systemd[1]: mariadb.service: Failed with result
'exit-code'.
déc. 07 23:07:49 hilbert systemd[1]: Failed to start MariaDB 10.3.29
database server.

Root hilbert:[~] > systemctl start mysql
Job for mysql.service failed because the control process exited with
error code.
See "systemctl status mysql.service" and "journalctl -xeu mysql.service"
for details.
Root hilbert:[~] > systemctl status mysql.service
× mysql.service - LSB: Start and stop the mysql database server daemon
 Loaded: loaded (/etc/init.d/mysql; generated)
 Active: failed (Result: exit-code) since Tue 2021-12-07 23:08:54
CET; 9s ago
   Docs: man:systemd-sysv-generator(8)
Process: 3430 ExecStart=/etc/init.d/mysql start (code=exited,
status=1/FAILURE)
CPU: 705ms

déc. 07 23:08:25 hilbert mysqld[3627]: 2021-12-07 23:08:25 0 [Note]
Recovering after a crash using /var/log/mysql/mysql-bin
déc. 07 23:08:25 hilbert mysqld[3627]: 2021-12-07 23:08:25 0 [Note]
Starting crash recovery...
déc. 07 23:08:25 hilbert mysqld[3627]: 2021-12-07 23:08:25 0 [Note]
Crash recovery finished.
déc. 07 23:08:26 hilbert mysqld[3627]: 2021-12-07 23:08:26 0 [Note]
Server socket created on IP: '0.0.0.0'.
déc. 07 23:08:26 hilbert mysqld[3627]: 2021-12-07 23:08:26 0 [ERROR]
Fatal error: Can't open and lock privilege tables: 'mysql.user' is not
of type 'TABLE'
déc. 07 23:08:54 hilbert mysql[3430]: Starting MariaDB database server:
mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
déc. 07 23:08:54 hilbert mysql[4017]:  failed!
déc. 07 23:08:54 hilbert systemd[1]: mysql.service: Control process
exited, code=exited, status=1/FAILURE
déc. 07 23:08:54 hilbert systemd[1]: mysql.service: Failed with result
'exit-code'.
déc. 07 23:08:54 hilbert systemd[1]: Failed to start LSB: Start and stop
the mysql database server daemon.
Root hilbert:[~] >

Cette version de mariadb est une réplique donc pas critique pour
l'instant. Je n'ai rien trouvé sur internet qui corresponde à ce
problème. Plus exactement, les seuls cas à peu près similaires indiquent
que la base de données était déjà corrompu (mais bizarrement, cela s'est
aussi passé juste avec une mise à jour entre les mêmes versions). Or
dans mon cas, ce n'est pas possible. J'ai réinstallé une version récente
de la réplique pas plus tard que ce matin et elle fonctionnait avant que
je ne redémarre la machine à la suite de sa mise à jour...

Toute idée sera la bienvenue.

Bien cordialement,

JKB

Webbserver

[Ttl]

Kan jag ha webbserver på min  debian dator Guds frid ttl 

Skickat från min iPhone


Skickat från min iPhone

Re: packagekitd annonce une mise à jour qu'apt ne voit pas

[Daniel Caillibaud]

Le 06/12/21 à 14:31, didier gaumet  a écrit :

> Le lundi 06 décembre 2021 à 13:11 +0100, Daniel Caillibaud a
> écrit :[...]
> > Il y a des logs de ce qu’il a fait ? Car je suppose que ce "command
> > failed" est lié à qqchose
> > qu’il devait faire au reboot et qui a échoué, comment savoir de quoi
> > il s’agissait ?  
> 
> en épluchant les logs par la commande journalctl tu devrais pouvoir
> trouver ton bonheur? 

J'ai regardé a tout hasard, mais l'erreur a été affichée au boot avant le menu 
grub, c'est donc
assez logique que journalctl n'en ai pas de trace.

> Mais as-tu besoin d'une autre confirmation que ce qui suit?

C'était pour savoir d'où ce command failed pouvait bien venir, et pour 
comprendre un peu mieux
ce qui se passe au boot dans ce genre de cas et si y'a moyen d'en avoir des 
traces, plus par
curiosité qu'autre chose.

Bonne soirée,

-- 
Daniel

Les vrais philosophes passent leur vie à ne point croire ce qu'ils 
voient, et à tâcher de deviner ce qu'ils ne voient point.
Bernard Fontenelle

Re: Install older versions of Debian with WSL

[Andrew M.A. Cater]

On Tue, Dec 07, 2021 at 03:54:37PM +0100, Max Nadig wrote:
> Hi,
> 
> I was trying to install Debian 10 via WSL on windows. The problem is, I 
> automatically get v11 Bullseye.
> Is there some way to specify the version or load a custom Debian version with 
> WSL?
> 
> I already posted this question into the WSL Git repo. So far I couldn't find 
> a solution for this.
> https://github.com/microsoft/WSL/issues/7805
> 
> Are there maybe legacy builds of the Debian microsoft store app available? 
> This would probably solve my problem.
> 
> Thank you for the help, best,
> Max

Why do you want Debian 10 specifically? You could try the IRC channel 

#debian-wsl 

on OFTC / see if you can find the maintainer.

In general terms, as soon as a release is put out, it's uploaded by 
rhaist to Microsoft - you want the latest stable to be the one used,

Hope this helps,

Andy C

Re: filesystem I'd?

[Andrew M.A. Cater]

On Mon, Dec 06, 2021 at 08:45:24PM -0800, Gene Heskett wrote:
> On Mon, 6 Dec, 2021 at 10:44 PM, David Wright  
> wrote:
>  
> 
> To: debian-user@lists.debian.org
> On Mon 06 Dec 2021 at 18:34:14 (-0800), Gene Heskett wrote:
> > Whats the name of the filesystem used on 64G micro-sd's labeled SDXC ?
> 
> When you buy it? — exFAT. No guarantees after that.
> 
> 
> 
> Then I recalled that writing an img or iso to it, replaces the file system. 
> So dd wrote
> the .img to the raw card, and it looks all normal now. I haven't boot tested 
> it yet, 
> 
> cuz I have a method worked out to install an older realtime kernel, but I'll 
> do that 
> 
> in the morning to one of the two, then boot test it. 
> 
> 
> 
> If it doesn't work, I'll test the second card. If that one works, I'll have 
> to mount my 
> 
> development system and sweat some blood building a newer kernel for it. It 
> took a week 
> 
> or more to get 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT running well on raspian 
> buster. But 
> 
> it has an easier job here than there, here its running linuxcnc to run an 80 
> yo metal lathe,
> 

Note - the version of Raspbian out there now is Bullseye - you might be
almost as well using Gunnar's Raspberry Pi builds for vanilla Debian.

> 
> Where these card's are going back to they will be running a few tons of 
> Cincinnati 4 
> 
> axis milling machine. Using linuxcnc of coarse. A machine big enough to start 
> with 
> 
> a 600 lb block of good alu, and  give you a toyota V8 engine block ready for 
> parts 
> 
> about 8 hours later. 
> 
> 
> 
> Cheers, David.
> 
> .

All best, as ever,

Andy C.

Re: Wireguard on Bullseye

[Charles Curley]

On Tue, 7 Dec 2021 08:11:10 +0100
john doe  wrote:

> Looking at the logs should help you understand if it is a FW issue.

Yup. Already done that.


> 
> If you can not disable your firewall, allowing ping is a good idea!!!
> :)

I prefer not to disable a firewall, even on my own network (except when
trying to debug something).

> 
> CIDR notation is generaly used when defining a subnet or an IP range.
> but rarely when you need to access a specific IP.

I was wondering about that when I copied the command from the Debian
wiki page. It didn't make sense in this instance, and didn't work.

-- 
Does anybody read signatures any more?

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

Install older versions of Debian with WSL

[Max Nadig]

Hi,

I was trying to install Debian 10 via WSL on windows. The problem is, I 
automatically get v11 Bullseye.
Is there some way to specify the version or load a custom Debian version with 
WSL?

I already posted this question into the WSL Git repo. So far I couldn't find a 
solution for this.
https://github.com/microsoft/WSL/issues/7805

Are there maybe legacy builds of the Debian microsoft store app available? This 
would probably solve my problem.

Thank you for the help, best,
Max

Re: filesystem I'd?

[Curt]

On 2021-12-07, piorunz  wrote:
> On 07/12/2021 03:43, David Wright wrote:
>> On Mon 06 Dec 2021 at 18:34:14 (-0800), Gene Heskett wrote:
>>> Whats the name of the filesystem used on 64G micro-sd's labeled SDXC ?
>>
>> When you buy it? — exFAT. No guarantees after that.
>>
>> Cheers,
>> David.
>>
> I love that range of responses, each one about something totally
> different, all due to Gene not remembering that he needs to let readers
> know what he know, if he expects any help whatsoever with what he asks for.
> 

According to Wikipedia, the SDXC format "adopts Microsoft's exFAT file system as
a mandatory feature." I'm uncertain what's to know beyond that in the
context of this thread.

Of course, the OP probably could've discovered this detail by himself.
Then again, he's 85 or something and maybe wants to use us like Santa's
little helpers. I'm no spring chicken myself, but I'm afraid the mood of
the season overtook me.

Re: grijze desktop, geen items

[Floris Renaud]

On Monday 06 December 2021 22:24:14 (+01:00), Geert Stappers wrote:

> On Mon, Dec 06, 2021 at 10:03:28PM +0100, Ernst van der Storm wrote:
> > Beste collega's,
> >
> > Tijdens een manoeuvre waarbij een externe drive is verwijderd -- in 
mijn
> > afwezigheid -- is mijn desktopachtergrondafbeelding verdwenen, en 
erger, alle

> > items van de desktop worden niet meer weergegeven.
> > Al die items zijn wel te bereiken met de bestandsbeheer.
> >
> > Heeft iemand ervaring met het oplossen hiervan? Ik heb een dubbel 
scherm,

> > dat werkt weer goed, maar ja, die lege achtergrond?
>
> Ik zou het ook niet weten.
> Hun die het misschien wel weten,
> willen weten welke "desktop" (XFCE, TWM, GNOME, KDE, ... ) gebruikt
> wordt.
>
 
Met

set | grep DESKTOP
kan je gemakkelijk uitvinden welke desktop je gebruikt.

Re: filesystem I'd?

[piorunz]

On 07/12/2021 03:43, David Wright wrote:

On Mon 06 Dec 2021 at 18:34:14 (-0800), Gene Heskett wrote:

Whats the name of the filesystem used on 64G micro-sd's labeled SDXC ?


When you buy it? — exFAT. No guarantees after that.

Cheers,
David.


I love that range of responses, each one about something totally
different, all due to Gene not remembering that he needs to let readers
know what he know, if he expects any help whatsoever with what he asks for.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Re: filesystem I'd?

[Michael Lange]

Hi,

On Mon, 6 Dec 2021 21:56:04 -0500
Greg Wooledge  wrote:

> On Mon, Dec 06, 2021 at 06:34:14PM -0800, Gene Heskett wrote:
> > Whats the name of the filesystem used on 64G micro-sd's labeled SDXC ?
> 
> Are you asking us how you could find out?  'Cause you can't seriously
> expect us to know what file system is on your device.
> 
> One way to find out would be to mount it, by any means necessary, and
> then run "mount" and see what file system type it reports.
> 
> Another way would be to use "file -s" on whatever block device your
> system assigns to it.  Plug the device in, wait a bit, run dmesg, and
> see what device name(s) you've got.  Then run file -s on whatever
> partition seems appropriate, if the device is partitioned, or else on
> the full device (/dev/sdx) if it's not partitioned.
> 

alternatively, when the device is plugged in, running

lsblk -o NAME,FSTYPE,LABEL,SIZE

will probably provide enough information to identify the card in question
without having to look through the dmesg output.

Best regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

We have found all life forms in the galaxy are capable of superior
development.
-- Kirk, "The Gamesters of Triskelion", stardate 3211.7

Re: Administration CUPS impossible

[Michel Memeteau - EKIMIA]

Super,

C'est certainement lié a ce bug qui est prochainement corrigé dans debian

https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1950484
[image: photo]
*Michel Memeteau*
Directeur, Ekimia SAS
+33 (0)9 72 30 83 34 <+33+9+72+30+83+34> | m...@ekimia.fr | Notre WebBoutique
: https://shop.ekimia.fr  | 620 avenue de la roche
fourcade 13400 Aubagne
 FRANCE




Contactez nous directement par Tchat sur http://bit.ly/ekitchat





Le lun. 6 déc. 2021 à 19:53,  a écrit :

> Le 06/12/2021 à 09:35, Michel Memeteau - EKIMIA a écrit :
> > cat /etc/group |grep $USER
>
> Effectivement, je n'étais pas dans le groupe lpadmin.
>
> J'ai donc fait un sudo usermod -aG lpadmin moi
>
> J'ai retenté de modifier les réglages de CUPS en localhost:631, et ça a
> marché. J'ai relancé mon navigateur web pour m'assurer que les réglages
> sont confirmés, et c'est tout bon.
>
> Merci de m'avoir aiguillé sur cette piste.
>
>