3200G Ryzen 3 / Vega 8 for Buster?

[Felix Miata]

Is it enough to upgrade to buster-backports kernel and AMD firmware to run Xorg 
on
the 3200G CPU/APU? The R7 Kaveri motherboard/APU of a friend who is virtually
blind fried. When he has hardware trouble, it's me gets to figure out howto and
fix it. He bought the new goodies on assumption they are enough for support from
Stable, but apparently that's not the case. X is not able to run, as Xorg.0.log
reports there is no framebuffer device or /dev/dri/card0.

TIA
-- 
Evolution as taught in public schools is religion, not science.

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

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

Re: Why I don't like UUIDs (Re: can't mount sdf1 in stretch, gparted claims its fat32)

[Stefan Monnier]

>> PS: The only problem with LVM names is that Linux doesn't let you
>> rename a volume group while it's active (at least last time I tried),
>> which makes it painful to rename the volume group in which lives your
>> root partition.
> How painful is it to dd a live cd, boot from it and rename?

Very.  It's called "downtime".
Every time you have to reboot, it means your OS has somewhat failed you.


Stefan

Re: Why I don't like UUIDs (Re: can't mount sdf1 in stretch, gparted claims its fat32)

[0...@caiway.net]

> PS: The only problem with LVM names is that Linux doesn't let you
> rename a volume group while it's active (at least last time I tried),
> which makes it painful to rename the volume group in which lives your
> root partition.
> 

How painful is it to dd a live cd, boot from it and rename?
3 minutes of pain, if that is what you want to call it?

Why I don't like UUIDs (Re: can't mount sdf1 in stretch, gparted claims its fat32)

[Stefan Monnier]

>> Me too, so I usually label the permanent stuff at least. UUID's can and
>> will change for no detectable reason.
> For those reading along or finding this in search results: no, filesystem
> UUIDs don't change for no detectable reason. Don't implement anything based
> on this theory.

What he meant is that filesystem UUIDs are (re)created automatically
based on a heuristic of what it means for a filesystem to be "the same".

This heuristic can be wrong in both directions: sometimes you delete and
create a new filesystem which is supposed to "be" the same filesystem as
before (but gets a new UUID), and other times you copy a filesystem so
as to get "another one" (but it keeps its UUID).

While I'm sure this can be managed by explicitly setting UUIDs, I've
found it much more pleasant to manage explicit names (I personally
prefer LVM names over filesystem labels, but filesystem labels work well
for those filesystems I don't put under LVM).  Not only I can pronounce
them and they carry meaning, but they tend to be much more visible (and
hence easier to manipulate).


Stefan


PS: The only problem with LVM names is that Linux doesn't let you rename
a volume group while it's active (at least last time I tried), which
makes it painful to rename the volume group in which lives your root partition.

Re: can't mount sdf1 in stretch, gparted claims its fat32

[Gene Heskett]

On Tuesday 04 February 2020 15:03:54 David Wright wrote:

> On Tue 04 Feb 2020 at 11:48:10 (-0500), Gene Heskett wrote:
> > On Tuesday 04 February 2020 08:51:47 Stefan Monnier wrote:
> > > >> I bet some of his RT patches caused a mess
> > > >
> > > > Nope, I just needed to reboot.
> > >
> > > "Needed to reboot" in this context means "need to work around a
> > > bug". I have no idea whether that bug has anything to with the RT
> > > patches, but the fact that rebooting avoided the problem is at
> > > least no proof that the problem was not caused by the RT patches
> > > (nor the opposite).
> >
> > Uptime is as you point out, dependent on the kernel. One of my
> > machines at the farthest reaches of my local net, running wheezy and
> > a small metal lathe, copy paste from an ssh login:
> > gene@lathe:~$ uname -a
> > Linux lathe 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian
> > 3.4.55-4linuxcnc i686 GNU/Linux
> > gene@lathe:~$ uptime
> >  11:09:34 up 167 days, 14:06, 1 user, load average: 0.00, 0.01, 0.05
>
> [etc etc]
>
> No idea what uptime has to do with mounting a card.
>
> But I did wonder why you didn't just try mounting the card in one of
> your several machines.
>
All the others are outside of the house, meaning I'd have to dress for 
the weather.

> 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 

Systemd logging stopped (SOLVED)

[Frank McCormick]

I have since rebooted to a  shutdown and logging is back. I don't know 
why simple reboots didn't solve the problem but

it's solved now.

--
Frank McCormick

More info on systemd logging fail

[Frank McCormick]

Looking at dmesg I see a bunch of lines like this:

Stopping User Runtime Directory /run/user/118...
[   55.241395] systemd[897]: user-runtime-dir@118.service: Failed to 
connect stdout to the journal socket, ignoring: Connection refused

[   55.249255] systemd[1]: run-user-118.mount: Succeeded.

Started Run anacron jobs.
[ 2846.911055] systemd[2236]: anacron.service: Failed to connect stdout 
to the journal socket, ignoring: Connection refused

[ 2846.915533] systemd[1]: anacron.service: Succeeded.

Those are just two example of "failing to connect stdout to the journal 
socket"




--
Frank McCormick

Re: can't mount sdf1 in stretch, gparted claims its fat32

[David Wright]

On Tue 04 Feb 2020 at 11:48:10 (-0500), Gene Heskett wrote:
> On Tuesday 04 February 2020 08:51:47 Stefan Monnier wrote:
> 
> > >> I bet some of his RT patches caused a mess
> > >
> > > Nope, I just needed to reboot.
> >
> > "Needed to reboot" in this context means "need to work around a bug".
> > I have no idea whether that bug has anything to with the RT patches,
> > but the fact that rebooting avoided the problem is at least no proof
> > that the problem was not caused by the RT patches (nor the opposite).
> >
> Uptime is as you point out, dependent on the kernel. One of my machines 
> at the farthest reaches of my local net, running wheezy and a small 
> metal lathe, copy paste from an ssh login:
> gene@lathe:~$ uname -a
> Linux lathe 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc 
> i686 GNU/Linux
> gene@lathe:~$ uptime
>  11:09:34 up 167 days, 14:06, 1 user, load average: 0.00, 0.01, 0.05

[etc etc]

No idea what uptime has to do with mounting a card.

But I did wonder why you didn't just try mounting the card in one of
your several machines.

Cheers,
David.

Re: Re: About "deprecated" packages

[Vincas Dargis]

2020-02-04 09:59, Andrei POPESCU rašė:

On Lu, 03 feb 20, 19:30:24, Vincas Dargis wrote:

Hi,

I've discovered that we have `openbve-data` [0] package for o-o-stable up to
the unstable, but binary package `openbve` [1] is only available for
o-o-stable...

`openbve-data` looks useless without binaries, and probably should be removed..?

What's the way to notify about this kind of packages?


https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages

Kind regards,
Andrei



Thanks!

Re: systemd logging stopped

[Frank McCormick]

On 2/4/20 11:30 AM, john doe wrote:

On 2/4/2020 4:56 PM, Frank McCormick wrote:

Noticed this morning that systemd is no longer logging boots on my machine.
There is a  log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully updated.

Can anyone help?



https://lists.debian.org/debian-user/2020/02/msg2.html

HTH.

--
John Doe



Yes, that's the one. But the message implies everything should happen 
automatically. In my case all it did was to stop logging.



--
Frank McCormick

Re: systemd logging stopped

[Frank McCormick]

On 2/4/20 11:31 AM, Peter Ehlert wrote:


On 2/4/20 7:56 AM, Frank McCormick wrote:
Noticed this morning that systemd is no longer logging boots on my 
machine.

There is a  log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully updated.



I got updated systemd (244.1-2) to 244.1-3 this morning, don't know if 
it relates... I have not rebooted for a few days





  Yes so did I, but still lo logging. systemd logs end at midnight last 
night when I suspended the system.

I have rebooted twice since.


--
Frank McCormick

Re: debian format usb drive that a Mac likes

[Charlie Gibbs]

On Tue, 04 Feb 2020 08:48:54 -0600, "Martin McCormick"
marti...@suddenlink.net> wrote:

> If one is on a debian system and formatting a usb drive
> that will be recognized by a Mac, I know that xfs is usually
> a good choice for the file system but what type of partition
> are we supposed to use to enclose that xfs file system?

I know from personal experience that Macs recognize FAT32
(read/write) and NTFS (read only) - but not ext3.

> I know if you plug a linux thumb drive in to a Mac, the
> Mac says it can't read the disk and immediately offers to
> initialize it for you.

This behaviour goes all the way back to the original
classic Mac in the mid-'80s; back then they would even
eagerly offer to format FAT16 disks created on an MS-DOS box.
Death to impure file systems!

--
/~\  Charlie Gibbs  |  Microsoft is a dictatorship.
\ /|  Apple is a cult.
 X   I'm really at ac.dekanfrus |  Linux is anarchy.
/ \  if you read it the right way.  |  Pick your poison.

Re: [1/2HS] Mysql et le symbole Euro €

[G2PC]

> Page Web de mon site, code PHP :
> echo mb_internal_encoding();
> UTF-8 
>
> Merci pour tous ces commentaires + liens.
>
> Avant "" m'affichait bien €
> Pourquoi plus maintenant ?
>
> J'ai bien essayé :
> Si UTF-8 = "?"
> Si ISO 8859-1(5)= "¤".
>
> Et pourquoi si champ phpmyadmin = 30¤ (et pas )
> mon site affiche correctement 30 € ?
> Et mysql en mode console, champ = 30 €
>
> Lorsque je fais un update ou insert sql,
> cotisation='30 ' qui devient sous phpmyadmin : 30¤
>
> Serait-ce phpmyadmin ?
>
> Bonne soirée,

Tu as omis de vérifier la structure de ta base de données, tu peux faire
un export de la structure ?
De la table concernée au moins ?
Vérifie l'encodage de la table et de la colonne, ça donne quoi ?

Re: debian format usb drive that a Mac likes

[Felix Miata]

Martin McCormick composed on 2020-02-04 15:48 (UTC+0100):

>   If one is on a debian system and formatting a usb drive
> that will be recognized by a Mac, I know that xfs is usually a
> good choice for the file system but
> what type of partition are we supposed to use to enclose that xfs
> file system?
 >  I know if you plug a linux thumb drive in to a Mac, the
> Mac says it can't read the disk and immediately offers to
> initialize it for you.

I formatted this on MacOS El Capitan, mounted it just now in openSUSE 15.1:

# mount | grep 1000
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=1627828k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdh1 on /run/media/username/Lexar type hfsplus 
(ro,nosuid,nodev,relatime,umask=22,uid=1000,gid=1000,nls=utf8,uhelper=udisks2)
-- 
Evolution as taught in public schools is religion, not science.

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

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

Re: debian format usb drive that a Mac likes

[Felix Miata]

Martin McCormick composed on 2020-02-04 09:48 (UTC-0500):

>   If one is on a debian system and formatting a usb drive
> that will be recognized by a Mac, I know that xfs is usually a
> good choice for the file system but
> what type of partition are we supposed to use to enclose that xfs
> file system?
 
>   I know if you plug a linux thumb drive in to a Mac, the
> Mac says it can't read the disk and immediately offers to
> initialize it for you.

I formatted this on MacOS El Capitan, mounted it just now in openSUSE 15.1:

# mount | grep 1000
tmpfs on /run/user/1000 type tmpfs 
(rw,nosuid,nodev,relatime,size=1627828k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdh1 on /run/media/username/Lexar type hfsplus 
(ro,nosuid,nodev,relatime,umask=22,uid=1000,gid=1000,nls=utf8,uhelper=udisks2)
-- 
Evolution as taught in public schools is religion, not science.

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

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

Re: systemd logging stopped

[john doe]

On 2/4/2020 4:56 PM, Frank McCormick wrote:
> Noticed this morning that systemd is no longer logging boots on my machine.
> There is a  log in /var/log/journal, but it's from yesterday.
> I seem to recall a message here about a change in logging
> but I can't find it.
> I am running Debian Sid fully updated.
>
> Can anyone help?
>

https://lists.debian.org/debian-user/2020/02/msg2.html

HTH.

--
John Doe

Re: can't mount sdf1 in stretch, gparted claims its fat32

[Gene Heskett]

On Tuesday 04 February 2020 08:51:47 Stefan Monnier wrote:

> >> I bet some of his RT patches caused a mess
> >
> > Nope, I just needed to reboot.
>
> "Needed to reboot" in this context means "need to work around a bug".
> I have no idea whether that bug has anything to with the RT patches,
> but the fact that rebooting avoided the problem is at least no proof
> that the problem was not caused by the RT patches (nor the opposite).
>
>
> Stefan
Uptime is as you point out, dependent on the kernel. One of my machines 
at the farthest reaches of my local net, running wheezy and a small 
metal lathe, copy paste from an ssh login:
gene@lathe:~$ uname -a
Linux lathe 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc 
i686 GNU/Linux
gene@lathe:~$ uptime
 11:09:34 up 167 days, 14:06, 1 user, load average: 0.00, 0.01, 0.05

And that machine hasn't a ups.

various other machines running newer stuff have shorter uptimes with a 
ups, this one running stretch:

gene@coyote:/media/sde1$ uname -a
Linux coyote 4.9.0-11-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.189-3+deb9u2 
(2019-11-11) x86_64 GNU/Linux

has never run more than about 30 days, with a ups, without developing an 
excuse to reboot it, in this present case 34 days. Timer wrap, whatever, 
its only good for about 30 days. The glaring exception to the newer= 
shorter uptmes is the rpi4 running one of my lathes, It now has a ups, 
and if I don't reboot it, it will run till the rapture.

One thing I don't do if I can help it, is spin down spinning rust, worst 
thing you every do short of a 30-06 thru it to a hard drive. I've an 
original seacrate 1T drive spinning in this machine with over 80,000 
spinning hours on it, still has the 25 reallocated sectors it had when I 
updated the firmwear in it when it was about 30 days old. I've had 2 
drives fail out of 9 here in the time since I jumped from amigados to 
linux in 1999. Skipped windows although I had to buy a cheap one last 
summer to use as a display for a redpitaya's vector network analyzer.  
I've replaced several because I outgrew them, but only 2 outright 
failures in 2 decades. I think thats pretty good. 

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: systemd logging stopped

[Peter Ehlert]

On 2/4/20 7:56 AM, Frank McCormick wrote:
Noticed this morning that systemd is no longer logging boots on my 
machine.

There is a  log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully updated.
I got updated systemd (244.1-2) to 244.1-3 this morning, don't know if 
it relates... I have not rebooted for a few days




Can anyone help?

Re: [1/2HS] Mysql et le symbole Euro €

[ajh . valmer]

On Tuesday 04 February 2020 05:34:20 G2PC wrote:
> D'après ce que tu écris, PHPMyAdmin retournerait le symbole en tant que
> ISO 8859-1 ?  https://fr.wikipedia.org/wiki/ISO/CEI_8859-15

Page Web de mon site, code PHP :
echo mb_internal_encoding();
UTF-8 

Merci pour tous ces commentaires + liens.

Avant "" m'affichait bien €
Pourquoi plus maintenant ?

J'ai bien essayé :
Si UTF-8 = "?"
Si ISO 8859-1(5)= "¤".

Et pourquoi si champ phpmyadmin = 30¤ (et pas )
mon site affiche correctement 30 € ?
Et mysql en mode console, champ = 30 €

Lorsque je fais un update ou insert sql,
cotisation='30 ' qui devient sous phpmyadmin : 30¤

Serait-ce phpmyadmin ?

Bonne soirée,


> Lire :
>https://openclassrooms.com/forum/sujet/afficher-le-symbole-euro-present-dans-une-base-de-donnees-52071
>https://forum.phpfrance.com/php-debutant/stocker-sigle-symbole-euro-dans-table-sql-t269428.html
> En conclure qu'il faut vérifier l'encodage :
> 1- De ton fichier
> 2- De ta base/table
> 3- De ta connexion PHP car tu peux forcer l'encodage lors de la connexion
> Ta BDD utilise quel encodage ? Le meilleur moyen de le savoir ou de s'en
> assurer, c'est de faire un dump d'une ligne qui a un symbole euro dans
> un fichier et d'ouvrir ce fichier avec un editeur hexa pour voir si
> c'est bien de l'UTF-8 (sequence UTF-8: E2 82 AC ).
> Je dis UTF8 car il serait préférable d'être en UTF8, puisque c'est la
> norme à suivre d'après le W3C, et, qui permet justement de standardiser
> ce type de problématiques de caractères spéciaux.
> En gros, ça se rapproche avec ça :
> 
https://www.developpez.net/forums/d606691/php/php-base-donnees/encodage-caracteres-sigle/
> https://openclassrooms.com/forum/sujet/signe-euro-avec-utf8decode-79959
> Bref, assures toi déjà de connaître l'encodage de ta base de données,
> et, de ton fichier.
> Si tu as quelque chose qui n'est pas en UTF8, demande toi si il ne
> serait pas mieux de passer à l'UTF8.
> Une fois en UTF8, et, les problèmes d'accents réglés, le euro devrait
> passer sans aucun problème.
> Pense à bien sauvegarder les données, et BDD, avant de commencer à faire
> des conversions, au risque de tout casser.

Re: can't mount sdf1 in stretch, gparted claims its fat32

[Greg Wooledge]

On Tue, Feb 04, 2020 at 11:24:56AM -0500, Michael Stone wrote:
> On Tue, Feb 04, 2020 at 11:06:10AM -0500, Gene Heskett wrote:
> > Me too, so I usually label the permanent stuff at least. UUID's can and
> > will change for no detectable reason.
> 
> For those reading along or finding this in search results: no, filesystem
> UUIDs don't change for no detectable reason. Don't implement anything based
> on this theory.

I was just about to make a similar reply.  The only time a file system's
UUID changes is if you destroy and recreate the file system, or go out
of your way to change the UUID through some file-system-specific tool
like xfs_admin -U uuid.

But, labels are great.  If you like using labels, that's fantastic.  Keep
doing that.

Re: can't mount sdf1 in stretch, gparted claims its fat32

[Michael Stone]

On Tue, Feb 04, 2020 at 11:06:10AM -0500, Gene Heskett wrote:

Me too, so I usually label the permanent stuff at least. UUID's can and
will change for no detectable reason.


For those reading along or finding this in search results: no, 
filesystem UUIDs don't change for no detectable reason. Don't implement 
anything based on this theory.

Re: diagramme de gantt

[arniom]

Bonjour,

Openproject fait ça

https://www.openproject.org/fr/

On 03/02/2020 07:00, Bernard Schoenacker wrote:

bonjour,

je recherche une solution pour employer des diagrammes
de gantt en version web et je n'arrive pas à trouver
la solution sachant que je part d'une base sur younohost

qui pourrait simplement me donner un début de solution
pour éclairer ma lanterne


merci pour votre aimable attention

bien à vous
bernard

systemd logging stopped

[Frank McCormick]

Noticed this morning that systemd is no longer logging boots on my machine.
There is a  log in /var/log/journal, but it's from yesterday.
I seem to recall a message here about a change in logging
but I can't find it.
I am running Debian Sid fully updated.

Can anyone help?

--
Frank McCormick

Re: can't mount sdf1 in stretch, gparted claims its fat32

[Gene Heskett]

On Tuesday 04 February 2020 07:47:58 songbird wrote:

> Gene Heskett wrote:
> > On Monday 03 February 2020 23:56:47 David Wright wrote:
> >> Well, at least one of my guesses was correct.
> >>
> >:)
> >
> > FWIW, the reboot fixed the can't mount, both partitions on this sd
> > card now mount normally, but are on /dev/sde now since the were
> > found at bootup. I've had this happen before, back before the other
> > mobo caught fire.
>
>   that is why i always put a label on a file system and
> mount it using that in the fstab.
>
>   i hate how devices can change out from under you
> otherwise.  some people use the UUIDs but i don't like
> those or have enough devices where i want to use them.
> labels work very well for me.
>
Me too, so I usually label the permanent stuff at least. UUID's can and 
will change for no detectable reason. The only time a name changes is if 
the medium has become incontinent on its way to totally dying. But thats 
a SWAG, as I've never had it happen on my watch.

>   songbird


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: "Ethernet trouble" thread

[David Wright]

On Tue 04 Feb 2020 at 13:20:35 (+0100), Tom H wrote:
> On Mon, Feb 3, 2020 at 2:54 PM Greg Wooledge  wrote:
> > On Sat, Feb 01, 2020 at 05:45:26PM +0100, Tom H wrote:
> >>
> >> You state that it's no longer udev that renames NICs. The following's
> >> from a sid VM using svsinit+sysvrc.
> > [...]
> >> udev is renaming "eth0".
> >>
> >> You can still use "/etc/udev/rules.d/" to rename NICs. Just like with
> >> "/etc/systemd/network/*.link", you gain simple names linked to a NIC's
> >> MAC address, but lose the predictable names' advantage that swapiing
> >> out a NIC preserves its name.
> >
> > Yes, it MIGHT still work. Or it might not. Support for it has
> > been officially removed. Whatever the 70-persistent-net.rules file
> > does on your system is unique to your system.
> >
> > https://wiki.debian.org/NewInBuster#Network_interface_name_migration
> >
> >  "The buster release notes warn that the
> >  /etc/udev/rules.d/70-persistent-net.rules method for assigning
> >  persistent network interface names is no longer supported."
> >
> > https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-names
> >
> >  "If your system was upgraded from an earlier release, and still uses
> >  the old-style network interface names that were deprecated with stretch
> >  (such as eth0 or wlan0), you should be aware that the mechanism of
> >  defining their names via /etc/udev/rules.d/70-persistent-net.rules is
> >  officially not supported by udev in buster (while it may still work
> >  in some cases)."
> 
> Thanks. Even though this is the official policy/statement, I don't buy it.
> 
> The problem's that "70-persistent-net.rules" has been used to rename
> NICs within the kernel "ethX" namespace. Until udev upstream declares
> the "SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="mac_address",
> NAME="net0" syntax and mechanism deprecated/obsoleted, I'll assume
> that the Debian release notes and wiki are wrongly melding the fact
> that renaming a NIC to "ethX" is deprecated (and that it might not
> work in the future), with the fact that
> "/etc/udev/rules.d/.rule" can still be used to associate a
> NIC's MAC address with a name.

I assume that's why they wrote "while it may still work in some cases".
The trouble is that so many people seem overly attached to "eth0" as
the name of their interface, even though it's about the worst name
to choose under all the new regimes, and notwithstanding that there's
an almost infinite namespace now available.

But myunderstanding is that if you're going to use udev to change
the interface name, it's important to know that it has completed
before trying to bring up the interface. That can be tricky enough,
but is made doubly difficult when the name is the same at the end
as it was to start with. What do you wait on?

Cheers,
David.

Re: can't mount sdf1 in stretch, gparted claims its fat32

[David Wright]

On Tue 04 Feb 2020 at 07:47:58 (-0500), songbird wrote:
> Gene Heskett wrote:
> > On Monday 03 February 2020 23:56:47 David Wright wrote:
> >
> >> Well, at least one of my guesses was correct.
> >
> >:)
> >
> > FWIW, the reboot fixed the can't mount, both partitions on this sd card 
> > now mount normally, but are on /dev/sde now since the were found at 
> > bootup. I've had this happen before, back before the other mobo caught 
> > fire.
> 
>   that is why i always put a label on a file system and
> mount it using that in the fstab.
> 
>   i hate how devices can change out from under you 
> otherwise.  some people use the UUIDs but i don't like 
> those or have enough devices where i want to use them.
> labels work very well for me.

You can also use any of the links in /dev/disk. For example, I have at
least one system that will only boot from a few favoured USB sticks,
so I use the same ones over for netinst i386 and netinst amd64.
However, the soft labelling on the sticks varies from release to
release, but the ID of each stick doesn't, so in /etc/fstab I use,
for example:

/dev/disk/by-id/usb-Generic_Flash_Disk_58F99DC1-0:0 /media/alsglobal2g iso9660 
ro,user,noauto

(The mount point is created by udev which spots that ID_SERIAL_SHORT=58F99DC1)

Cheers,
David.

Re: debian format usb drive that a Mac likes

[Alex Mestiashvili]

On 2/4/20 3:48 PM, Martin McCormick wrote:

If one is on a debian system and formatting a usb drive
that will be recognized by a Mac, I know that xfs is usually a
good choice for the file system but
what type of partition are we supposed to use to enclose that xfs
file system?

I know if you plug a linux thumb drive in to a Mac, the
Mac says it can't read the disk and immediately offers to
initialize it for you.

Thanks.

Martin McCormick



I guess you have to go with extfat.
Linux can read and may be write hfs/hfs+, read apfs, but apple's 
filesystems support is kind of miserable.


Best,
Alex

debian format usb drive that a Mac likes

[Martin McCormick]

If one is on a debian system and formatting a usb drive
that will be recognized by a Mac, I know that xfs is usually a
good choice for the file system but
what type of partition are we supposed to use to enclose that xfs
file system?

I know if you plug a linux thumb drive in to a Mac, the
Mac says it can't read the disk and immediately offers to
initialize it for you.

Thanks.

Martin McCormick

Re: can't mount sdf1 in stretch, gparted claims its fat32

[songbird]

Gene Heskett wrote:
> On Monday 03 February 2020 23:56:47 David Wright wrote:
>
>> Well, at least one of my guesses was correct.
>
>:)
>
> FWIW, the reboot fixed the can't mount, both partitions on this sd card 
> now mount normally, but are on /dev/sde now since the were found at 
> bootup. I've had this happen before, back before the other mobo caught 
> fire.

  that is why i always put a label on a file system and
mount it using that in the fstab.

  i hate how devices can change out from under you 
otherwise.  some people use the UUIDs but i don't like 
those or have enough devices where i want to use them.
labels work very well for me.


  songbird

Re: can't mount sdf1 in stretch, gparted claims its fat32

[Stefan Monnier]

>> I bet some of his RT patches caused a mess
> Nope, I just needed to reboot.

"Needed to reboot" in this context means "need to work around a bug".
I have no idea whether that bug has anything to with the RT patches, but
the fact that rebooting avoided the problem is at least no proof that
the problem was not caused by the RT patches (nor the opposite).


Stefan

Re: "Ethernet trouble" thread

[Tom H]

On Mon, Feb 3, 2020 at 2:54 PM Greg Wooledge  wrote:
> On Sat, Feb 01, 2020 at 05:45:26PM +0100, Tom H wrote:
>>
>> You state that it's no longer udev that renames NICs. The following's
>> from a sid VM using svsinit+sysvrc.
> [...]
>> udev is renaming "eth0".
>>
>> You can still use "/etc/udev/rules.d/" to rename NICs. Just like with
>> "/etc/systemd/network/*.link", you gain simple names linked to a NIC's
>> MAC address, but lose the predictable names' advantage that swapiing
>> out a NIC preserves its name.
>
> Yes, it MIGHT still work. Or it might not. Support for it has
> been officially removed. Whatever the 70-persistent-net.rules file
> does on your system is unique to your system.
>
> https://wiki.debian.org/NewInBuster#Network_interface_name_migration
>
>  "The buster release notes warn that the
>  /etc/udev/rules.d/70-persistent-net.rules method for assigning
>  persistent network interface names is no longer supported."
>
> https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#migrate-interface-names
>
>  "If your system was upgraded from an earlier release, and still uses
>  the old-style network interface names that were deprecated with stretch
>  (such as eth0 or wlan0), you should be aware that the mechanism of
>  defining their names via /etc/udev/rules.d/70-persistent-net.rules is
>  officially not supported by udev in buster (while it may still work
>  in some cases)."

Thanks. Even though this is the official policy/statement, I don't buy it.

The problem's that "70-persistent-net.rules" has been used to rename
NICs within the kernel "ethX" namespace. Until udev upstream declares
the "SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="mac_address",
NAME="net0" syntax and mechanism deprecated/obsoleted, I'll assume
that the Debian release notes and wiki are wrongly melding the fact
that renaming a NIC to "ethX" is deprecated (and that it might not
work in the future), with the fact that
"/etc/udev/rules.d/.rule" can still be used to associate a
NIC's MAC address with a name.

Re: Wireless Connectivity - Hot Spot vs Corp

[jamesalex12]

hey this good information thank you 
Field Services Technician
  



-
I am working as a network technician .very passionate to learn new technologies.
every new updates are very interesting to learn.this is the tech place to know 
about new things
Field Services Technician 

--
Sent from: http://debian.2.n7.nabble.com/Debian-User-f2135253.html

Re: can't mount sdf1 in stretch, gparted claims its fat32

[Gene Heskett]

On Tuesday 04 February 2020 02:21:32 deloptes wrote:

> Dan Ritter wrote:
> > There's no FAT filesystem there. It might be corrupted, it might
> > actually be on /dev/sdf with a bogus partition table.
>
> I bet some of his RT patches caused a mess

Nope, I just needed to reboot.

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: OT red por cable con portal captivo sin trafico interno.

[Ramses]

El 4 de febrero de 2020 8:45:18 CET, Antonio Trujillo Carmona 
 escribió:
>El 3/2/20 a las 14:34, Paynalton escribió:
>>
>>
>> El lun., 3 de febrero de 2020 2:26 a. m., Antonio Trujillo Carmona
>> > > escribió:
>>
>> El 1/2/20 a las 14:14, Ramses escribió:
>> > El 31 de enero de 2020 12:04:37 CET, Antonio Trujillo Carmona
>> > > escribió:
>> >> El 29/1/20 a las 17:41, Paynalton escribió:
>> >>>
>> >>>
>> >>> El mié., 29 ene. 2020 a las 7:40, Antonio Trujillo Carmona
>> >>> (> 
>> >>> > >>) escribió:
>> >>>
>> >>>     El 28/1/20 a las 8:42, Antonio Trujillo Carmona escribió:
>> >>>     >     En nuestro hospital tenemos una VLan de gracia para
>los
>> >>>     equipos no
>> >>>     > identificados.
>> >>>     > Debido al abuso que se hace de esa vlan nos estamos
>> planteando
>> >>>     poner un
>> >>>     > portal de validación y anular el trafico interno.
>> >>>     > No se trata tanto de bloquear o filtrar usuarios como
>de
>> evitar
>> >>>     que se
>> >>>     > puedan conectar dispositivos electromédicos u OT a la
>> red, por
>> >>>     lo que no
>> >>>     > es importante el nivel de seguridad, cualquier elección
>> haría
>> >> que un
>> >>>     > dispositivo automático fallara en adquirir red, que es
>> lo que
>> >>>     buscamos.
>> >>>     > Los conmutadores (HP procurbe) solo admiten 2 de 3
>posibles
>> >>>     formas de
>> >>>     > acceso y tienen activado el filtrado 802.1x y por MAC,
>> por lo
>> >>>     que no se
>> >>>     > puede activar el acceso web.
>> >>>     > ¿Alguna idea?
>> >>>     >
>> >>>     Muchas gracias a todos por las respuestas.
>> >>>
>> >>>     Realmente mi pregunta no iba sobre que portal usar,
>aunque
>> >>>     agradezco los
>> >>>     apuntes y los probare, si no por como configurar una red
>> por dhcp
>> >> para
>> >>>     que los equipos que estén en la misma red y en el mismo
>> >> conmutador
>> >>>     (switch) no se vean entre ellos.
>> >>>
>> >>>
>> >>>
>> >>> Para mantener aislamiento debes usar vlans, manteniendo a la
>red
>> >>> médica en una vlan y la red pública en otra.
>> >>>
>> >>> El mismo DHCP puede decidir a qué vlan se va cada equipo y
>qué
>> >>> servicios puede tener.
>> >>>
>> >>> En el gateway de la red pública debes colocar un acceso por
>proxy
>> >>> controlado por temporizador como te había mencionado en un
>correo
>> >>> anterior.
>> >>>
>> >>> El DHCP debe entregar la ruta de un wpad para la
>configuración
>> >>> automática del proxy.
>> >>>
>> >>> Debes tener un servicio web que entregue el archivo wpad, el
>cual
>> >>> indicará que la salida a internet es a través del proxy.
>> >>>
>> >>> Así, en un caso de uso típico sucede:
>> >>>
>> >>> Caso A:
>> >>>
>> >>> -visitante llega con su teléfono.
>> >>> -visitante se conecta a la red pública abierta
>> >>> -teléfono solicita configuración al DHCP
>> >>> -DHCP entrega configuración de red y una ruta para wpad
>> >>> -visitante intenta entrar a internet
>> >>> -navegador del teléfono consulta el wpad
>> >>> -navegador redirige la petición al proxy
>> >>> -proxy redirige al visitante a una página de error donde le
>pide
>> >>> contraseña, o una encuesta o la foto de la enfermera Salo en
>> traje de
>> >> baño
>> >>> -visitante interactúa con la página y gana el acceso
>temporizado
>> >>> -proxy permite el acceso por 15 minutos antes de mostrar de
>> nuevo el
>> >>> pack de verano de la enfermera Salo.
>> >>>
>> >>> Caso B:
>> >>>
>> >>> -llega un interno con un novedoso aparato que no sirve para
>> nada pero
>> >>> que consiguió barato en amazon.
>> >>> -interno conecta el aparato a la red pública por flojera de
>ir a
>> >>> sistemas a pedir acceso
>> >>> -aparato no tiene navegador, por lo que no puede ver las
>candentes
>> >>> fotos de la enfermera Salo
>> >>> -aparato no logra conectarse y el interno no tiene más
>remedio
>> que ir
>> >>> a pedir acceso a la red controlada.
>> >>> -Helpdesk registra macaddress en el DHCP
>> >>> -aparato se vuelve a conectar a la red
>> >>> -DHCP encuentra al aparato en su waitlist y entrega IP de la
>vlan
>> >>> controlada.
>> >>>  
>> >> Muchas gracias por las aportaciones.
>> >>
>> >> Si esto ya lo se, se trata de evitar que llegue un laboratorio
>e
>> >> instale
>> >> unos equipos sin pasar por el servicio de informática, en la
>> >> actualidad,
>> >> como no 

Re: About "deprecated" packages

[Andrei POPESCU]

On Lu, 03 feb 20, 19:30:24, Vincas Dargis wrote:
> Hi,
> 
> I've discovered that we have `openbve-data` [0] package for o-o-stable up to
> the unstable, but binary package `openbve` [1] is only available for
> o-o-stable...
> 
> `openbve-data` looks useless without binaries, and probably should be 
> removed..?
> 
> What's the way to notify about this kind of packages?

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature