Re: Wayland vs X
On Fri, Mar 11, 2022 at 03:09:08PM -0600, Nicholas Geovanis wrote: [...] > > Isn't it all about X by design to not be able to safely protect a > > running X applications to snoop on other running X applications, > > something like the content of a window cannot safely kept private? I > > remember to have read that Wayland was invented for this reason, to > > overcome these security flaws of X which in the beginning of X have not > > been a concern to anyone, but nowadays security issues are of much > > importance to almost everyone. > > (I have no reference for this statement, just remember to have something > > like this read in the past) > > > > That was exactly what I asked here a few days ago. And I was told that I > was incorrect, that Wayland was simply a better implementation of X. That > the old implementation X.org was still under active development. Showing > that I was mistaken. They only removed the stuff me and you don't need. Promised ;-) Cheers -- t signature.asc Description: PGP signature
Re: Comment éteindre un serveur proprement pour permettre le redémarrage automatique ?
Le vendredi 4 mars 2022 à 17:30:03 UTC+1, Olivier a écrit : > Bonjour, > > J'envisage de protéger des serveurs distants (de type NUC) avec un > "onduleur administrable". Mon objectif est d'éviter d'endommager un > disque (toujours de type SSD ou NVMe) à cause d'une coupure brutale de > courant. > > J'accepte que les services soient interrompus tant que dure la panne > de courant mais j'aimerai qu'idéalement, les services redémarrent sans > intervention humaine quand le courant revient (si par chance, celui-ci > devait revenir sans action humaine). > > > Imaginons qu'un serveur distant protégé par cet onduleur > administrable, reçoive de ce dernier ou d'ailleurs, la notification > d'une panne de courant prolongée. > > Quelle commande d'extinction-hibernation doit-il émettre afin : > 1- qu'il consomme le minimum d'énergie tant que dure la panne de courant > 2- qu'il re-démarre dès que le courant revient. > > J'ai vu dans le BIOS une option "After Power Failure: Stay Off/Power > On Normal Boot/Power On PXE". Je l'ai essayé mais elle ne fonctionne > après une commande poweroff, ce qui me semble logique. > > Une idée ? > > Slts Les développeurs pour les vrai datacenter on fait un script si le groupe électrogène fait défaut les serveurs sauvegarde, puis sont en extinction et le bios de la carte mère se réveil, y avait quelque chose sous 2.4 en kernel sous rh6, j’ai pas suivi sous debian ! Voir un walk on wan, réveil par interface réseau ? Le français des ups aps avait fait quelque chose je crois ? Mais bon les disques qui crachent faut modifier le firmware du disque ? Mais ça ne crache pas … — Ptilou
Re: Wayland vs X
On Fri, Mar 11, 2022 at 03:41:09PM -0500, The Wanderer wrote: [...] > The most important one for my purposes, and therefore the one that I > remember, is the ability to have multiple desktop-like things which are > actually all just viewports on one much-larger single area [...] There seems to be some basis to it. And some solution. But then, you're perhaps bound to a specific toolkit [1] [2] or perhaps compositor. > Another limitation of XWayland as I've heard it described (by the same > person on whose statements the previous paragraph is based, as well as > in online discussions related to XWeston, below), as compared to a full > X server: where you can (and, in fact, usually need to) run a window > manager on top of an X server [...] This is absolutely my main beef: I do chose my window manager judiciously; after long use I know it well and perceive it as my ally in front of applications which sometimes have (to me) strange ideas of GUI [0]. With X, the window manager is the one implementing window decorations (this isn't in the protocol, but it is a strong convention applications had to follow in practice). With Wayland, you can see the appetite of applications and toolkits to unleash their "creativity" on the unsuspecting user. I don't look forward to the day where the browser gives some random javascript advertisment control over its absolute position on my screen or over its window decorations. But this day is coming: don't forget that our main browser provider is an ad company, and this industry (as the closely related DRM industry, too) tends to view your computer as /their/ "content" delivery device. You can get a feel of that taste now with all those "GUIs" badly implemented by the never-ending horde of javascript frameworks. Jamie Zawinski's CADT [2] was hell, we now discovered an even worse place. I'll stick to X. My computer feels a bit more... mine this way. Cheers [0] Heck, I've even a key shortcut for xkill, afer some incarnation of... yes, Firefox, decided to ignore the window close button. They've fixed it in the meantime, it seems, but I do keep that shortcut around. [1] https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/wayland-display-server/1074550-kde-now-has-virtual-desktop-support-on-wayland and the links therein. [2] https://www.jwz.org/doc/cadt.html -- tomás signature.asc Description: PGP signature
Re: evince has died a horrible death. Sob...
Emanuel Berg writes: > Pankaj Jangid wrote: >> >> For reading PDFs, I still use evince (the default). > > I use xpdf(1) but I'm not a PDF reader power user ... > > Here are some settings: > I am also not a power user. I use what came with a default desktop install of Debian. But I am overwhelmed by the customizability of xpdf now. Thanks for reminding.
Re: evince has died a horrible death. Sob...
On Friday, 11 March 2022 22:45:28 EST Pankaj Jangid wrote: > gene heskett writes: > > What its its feature complete replacement in a buster install? This > > machine is bullseye, the logged into machine is buster. > > For reading PDFs, I still use evince (the default). For > annotating/marking in the PDFs, I use xournalpp. It is actively > maintained upstream. > And having built ghostscript at about version 5 for the amiga's back in the day when ghostscript did both ps and pdf up to 1.2, I can appreciate just how difficult that trick is. My now ancient hat is off to the coder who gets that and actually makes it work. 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, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: evince has died a horrible death. Sob...
gene heskett writes: > What its its feature complete replacement in a buster install? This > machine is bullseye, the logged into machine is buster. > For reading PDFs, I still use evince (the default). For annotating/marking in the PDFs, I use xournalpp. It is actively maintained upstream.
Disques ssd sensibles aux coupures brutales ?
Bonjour, Je reviens sur ce thread parce que : Le 04/03/22 à 17:21, Olivier a écrit : > Mon objectif est d'éviter d'endommager un disque (toujours de type SSD ou > NVMe) à cause d'une > coupure brutale de courant. m'étonne un peu. Un disque ssd est vraiment sensible à une coupure brutale ? Je me souviens™ du devoir de parquer les disques avant d'éteindre un PC, mais c’était au siècle dernier ! Assez rapidement les constructeurs ont ajoutés du park auto à l’extinction (j’imagine le nb de plaintes qu’ils ont eu de gens ayant dépensé des fortunes pour un hd, parti en fumée parce que qqun avait déplacé un PC éteint), puis du park auto à la coupure de courant (ils ont réinventé le ressort). Depuis les ssd y’a plus de tête risquant de se retrouver au mauvais endroit au mauvais moment, donc en cas de coupure de courant je veux bien qu’il y ait un risque sur les datas (et encore, avec les fs journalisés ça devrait plus trop être le cas), mais un risque sur le matériel ? C’est toujours d’actualité ? Si oui faut vraiment que je m’inquiète car sur mon PC actuel j’ai du reboot hard ~3×/semaine depuis 1an 1/2, du "recovered inode" à chaque reboot après un plantage, mais heureusement les disques sont toujours là (un nvme et un disque HD classique à plateaux, moins sollicité). Rien d’ironique, je suis une buse en hardware et peux très bien avoir de fausses idées reçues, si qqun qui sait peut confirmer / infirmer ça m’intéresse. PS: ça ne remet pas en cause l’intérêt d’un onduleur, mais pour du NAS perso, ça me paraît un peu overkill (je ne parle pas du coût environnemental, changer les batteries tous les 2ans, toussa, juste du coût humain pour s’occuper de l’onduleur et sa communication avec la machine, plutôt que de laisser la machine redémarrer toute seule quand le courant revient). -- Daniel Lorsque j'ai été kidnappé, ma mère a réagi tout de suite: elle a sous-loué ma chambre. Woody Allen
Re: Comment recharger un module noyau planté ?
Le 11/03/22 à 10:56, David Martin a écrit : > Salut, > C'est juste le redémarrage qui ne se fait pas ? (boucle) Ça j'en sais rien, je parlais de boucle parce que la succession de messages du kern.log revient en boucle, d'abord du ath10k_pci :02:00.0: failed to wake target for read32 at en rafale, puis du ieee80211 phy0: Hardware restart was requested [ cut here ] ieee80211_restart_work called with hardware scan in progress WARNING: CPU: 1 PID: 57789 at net/mac80211/main.c:261 ieee80211_restart_work+0xf3/0x100 [mac80211] Modules linked in: puis une call trace et ça recommence -- Daniel Je n'ai fait celle-ci plus longue que parce que je n'ai pas eu le loisir de la faire plus courte. Blaise Pascal (Les Provinciales, celle-ci désigne une lettre)
Re: Comment recharger un module noyau planté ?
Le 10/03/22 à 20:09, Daniel Caillibaud a écrit : > Merci, j'essaierai la prochaine fois avec -f et -v, pour voir s'il parvient à > le décharger. avec rmmod -v -f ath10k_pci le -f aura été efficace, il m'a rendu la main aussitôt, mais le -v change pas grand chose, aucun retour. Ensuite, un `modprobe -v ath10k_pci` ne dit rien, mais ne fait rien non plus, sinon écrire dans kern.log Mar 11 23:31:01 dell kernel: [33602.770218] ath10k_pci :02:00.0: failed to read device register, device is gone Mar 11 23:31:01 dell kernel: [33602.770222] ath10k_pci :02:00.0: failed to reset chip: -5 Mar 11 23:31:03 dell kernel: [33605.371019] ath10k_pci: probe of :02:00.0 failed with error -5 Mais au moins, la dépose du module planté m'a permis d'éteindre la machine proprement. Juste une frayeur au reboot, grub m'a répondu que je devais charger un noyau d'abord, un ctrl+alt+suppr pour relancer un nouveau reboot a réglé le pb, ma debian se prend pour windows :-/ (j'avais déjà vu ça après d'autres plantages, le 1er reboot hard échoue, il en faut un 2e pour repartir d'un pied peu dansant ni vaillant mais qui veut bien poser par terre). -- Daniel Si les imbéciles volaient, il ferait nuit. Frédéric Dard
Re: Simple and secure blogging software for nginx
Christian Britz wrote: ... > Running and writing the blog. At the moment I tend to a static > generator, which would probably also make archival easier?! that is what hugo is. many themes to choose from or do your own. songbird
Re: Wayland vs X
* On 2022 11 Mar 15:10 -0600, Nicholas Geovanis wrote: > That was exactly what I asked here a few days ago. And I was told that I > was incorrect, that Wayland was simply a better implementation of X. That > the old implementation X.org was still under active development. Showing > that I was mistaken. > > But if you read stuff online on this subject, you read exactly what I > wrote: that the X protocol is old and outdated, the X source is largely > unused at runtime, no real mindshare for X.org among X developers. > > Here's an example of these views from 2021, at linuxiac.org: > "Most of the features that the X Server protocol provided were not used > anymore. Pretty much all of the work that X11 did was redelegated to the > individual applications and the window manager. And yet all of those old > features are still there, weighing down on all of these applications, > hurting performance and security". > https://linuxiac.com/xorg-x11-wayland-linux-display-servers-and-protocols-explained/ > > I'm just trying to find out what the real story is. Keith Packard, a long time X developer, gave a talk at Linux Conf.au[1] in early 2020 about X history and politics[2]. As I recall (it's been two years since I watched it), much of what you wrote above echos Keith's comments. - Nate [1] https://www.keithp.com/blogs/tags/lca/ [2] https://youtu.be/cj02_UeUnGQ -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: Wayland vs X
* On 2022 11 Mar 14:06 -0600, Emanuel Berg wrote: > Nate Bargmann wrote: > > > Interesting as no one uses Wayland or X11 directly but > > through a window manager or quite likely one of the desktop > > environments. > > I don't know, I think it is fair to say I use X "directly", > I start it manually (but automatically, the command is in > a file) in a tty and then in ~/xinitrc launch a compositor and > WM, then xterm with tmux: > > picom & > openbsd-cwm & > > xterm \ > -T 'xterm' \ > -fullscreen \ > -e 'tmux new-session\; split-window -v\; select-pane -U' I suspect you're not the target audience for Wayland as it seems to me to be oriented toward the main desktop projects. I don't see that your use case would gain anything moving to Gnome or KDE. That's the great thing about Free systems, we don't all have to do things the same way. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: Wayland vs X
* On 2022 11 Mar 14:10 -0600, Emanuel Berg wrote: > Nate Bargmann wrote: > > >> No, I understood, but that sounds like too much emulator ... > > > > My understanding is that xwayland is an X server that runs > > under Wayland and the idea is that it handles X protocols > > but Wayland handles the video drivers and screen drawing. > > > > I have used Gnome on Wayland since late 2018. It improved > > a lot with the release of Bullseye. > > Okay, I'm on Bullseye as well. > > You have commands so I can try? I had just installed the system with the preselected Gnome desktop task and everything was put in place. I simply log into the Gnome desktop from GDM. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: Wayland vs X
On 2022-03-11 at 16:52, Emanuel Berg wrote: > The Wanderer wrote: > >> There may be multiple reasons, but one of them is that the feature >> set supported by Wayland (and/or the associated protocol, if any) >> is not a superset of the feature set supported by the X protocol. > > They should have covered everything used anyway ... this must be a > blunder on their part. My understanding (which is at best secondhand, and may well not be fully accurate, if accurate at all) is that they thought they *were* doing that, since obviously that one feature is a historical curiosity which can't possibly be useful to anybody, and is only present in the spec because the people who wrote the spec mistakenly thought it might turn out to be useful. Only to discover later that people actually *did* use that feature, but by that point it was too late to implement that feature in Wayland without breaking a lot of other things and/or requiring a deeper redesign than would be deemed practical. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Wayland vs X
Greg Wooledge writes: > On Fri, Mar 11, 2022 at 10:07:39PM +0100, Emanuel Berg wrote: > > OK, that stinks, I'm super-happy with my WM and it's > > configured and all. See? How do they expect anyone to switch > > to a supposedly superior solution when there are all these > > obstacles and limitations? > > I don't think anyone is switching. What I think is happening is that > old users (like us) are staying with what we know, and some new users > are using Wayland/GNOME because it's the default that Debian selected > for them. Some of the new users who grow up on Wayland may eventually > move on to other desktop environments, or other windowing systems, and > will become the next generation of old cranky gurus. Words of wisdom, Greg. I'm 79 and still use FVWM(1), c. '90s. Concerned about things like memory footprint, speed, configuration capability, reliability, 24/7/365 stability, intuitive operation, etc. My ~/.emacs is set up like the 'e' editor from PL1, c. '60s with line block moves and indent, 8^). John -- John Conover, cono...@panix.com, http://www.johncon.com/
Re: Wayland vs X
On 2022-03-11 at 16:07, Emanuel Berg wrote: > The Wanderer wrote: > >> Another limitation of XWayland as I've heard it described (by the >> same person on whose statements the previous paragraph is based, as >> well as in online discussions related to XWeston, below), as >> compared to a full X server: where you can (and, in fact, usually >> need to) run a window manager on top of an X server, I'm given to >> understand that you cannot run a window manager on top of XWayland. >> Instead, the window manager needs to be implemented as a Wayland >> compositor, and you then run XWayland inside of that. (I have not >> actually tried to do this myself, for reasons which I'm about to >> get into, so I may have some of the details wrong.) > > OK, that stinks, I'm super-happy with my WM and it's configured and > all. See? How do they expect anyone to switch to a supposedly > superior solution when there are all these obstacles and limitations? > If it is just about replacing one protocol by another why can't that > be done for WMs as well? There may be multiple reasons, but one of them is that the feature set supported by Wayland (and/or the associated protocol, if any) is not a superset of the feature set supported by the X protocol. That said, you may still find value in XWeston, and I'd be interested to hear reports from anyone who tries it - the more obscure and niche the window manager they try it with, the better. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Wayland vs X
On Fri, Mar 11, 2022 at 10:27:18PM +0100, Emanuel Berg wrote: > I switched from mplayer to mpv ... And I switched from Latin-1 to UTF-8. But until I see fvwm (or something close enough) ported to Wayland, I have *no* incentive to give up X.
Re: Wayland vs X
On Fri, Mar 11, 2022 at 10:07:39PM +0100, Emanuel Berg wrote: > OK, that stinks, I'm super-happy with my WM and it's > configured and all. See? How do they expect anyone to switch > to a supposedly superior solution when there are all these > obstacles and limitations? I don't think anyone is switching. What I think is happening is that old users (like us) are staying with what we know, and some new users are using Wayland/GNOME because it's the default that Debian selected for them. Some of the new users who grow up on Wayland may eventually move on to other desktop environments, or other windowing systems, and will become the next generation of old cranky gurus.
Re: Wayland vs X
On Fri, Mar 11, 2022, 12:25 PM Marco Möller < ta...@debianlists.mobilxpress.net> wrote: > On 11.03.22 14:14, Christian Britz wrote: > > > > > > On 2022-03-11 12:47 UTC+0100, Nate Bargmann wrote: > > > >> I have used Gnome on Wayland since late 2018. It improved a lot with > >> the release of Bullseye. I use this setup on two machines, a laptop and > >> a desktop that has two monitors. So far I have not had any issues with > > > > And what is the practical _advantage_ over a X11 setup? > > > > The question is serious. Everytime I tried Wayland, something was not > > working as expected, uncomfortable to use and so on. Yes, Wayland > > support has improved a lot, but I still do not really see what I miss > > because I stick to X11. I know that Wayland has a cleaner design, but > > that bothers me not too much as a user. > > > > Regards, > > Christian > > > > Isn't it all about X by design to not be able to safely protect a > running X applications to snoop on other running X applications, > something like the content of a window cannot safely kept private? I > remember to have read that Wayland was invented for this reason, to > overcome these security flaws of X which in the beginning of X have not > been a concern to anyone, but nowadays security issues are of much > importance to almost everyone. > (I have no reference for this statement, just remember to have something > like this read in the past) > That was exactly what I asked here a few days ago. And I was told that I was incorrect, that Wayland was simply a better implementation of X. That the old implementation X.org was still under active development. Showing that I was mistaken. But if you read stuff online on this subject, you read exactly what I wrote: that the X protocol is old and outdated, the X source is largely unused at runtime, no real mindshare for X.org among X developers. Here's an example of these views from 2021, at linuxiac.org: "Most of the features that the X Server protocol provided were not used anymore. Pretty much all of the work that X11 did was redelegated to the individual applications and the window manager. And yet all of those old features are still there, weighing down on all of these applications, hurting performance and security". https://linuxiac.com/xorg-x11-wayland-linux-display-servers-and-protocols-explained/ I'm just trying to find out what the real story is. And isn't it because of Wayland protecting windows by design against > other windows, that operations like Copy between GUI applications > are (still) not always running smoothly and need extra efforts to become > well implemented? > (Again, I have no reference for this statement, just remember to have > something like this read in the past) > > Regards, > Marco > >
Re: Wayland vs X
On 2022-03-11 at 06:47, Nate Bargmann wrote: > * On 2022 10 Mar 17:04 -0600, Emanuel Berg wrote: > >> didier gaumet wrote: >> OK, thanks, I won't switch then I think ... I like feh and use it a lot. >>> >>> Just to be clear in case there would be a misunderstanding >>> because my sentence was not accurate enough: what I meant is feh >>> (for example) is not directly compatible with Wayland, but can be >>> run in the X11 compatibility layer of Wayland (Xwayland, the >>> nested X server that can be run inside Wayland) >> >> No, I understood, but that sounds like too much emulator ... > > My understanding is that xwayland is an X server that runs under > Wayland and the idea is that it handles X protocols but Wayland > handles the video drivers and screen drawing. That's a rough match for my own understanding, with the added qualification that apparently there are some features of the X protocol which Wayland doesn't support, and which XWayland therefore may well also not (be able to) support. (Although, while writing this mail, I've seen assertions that the XWayland codebase *is* the X.org codebase, just with the hardware-related parts stripped out and replaced with calls to Wayland - in which case maybe those features would be working after all.) The most important one for my purposes, and therefore the one that I remember, is the ability to have multiple desktop-like things which are actually all just viewports on one much-larger single area. The big advantage of this is that it lets you have a window that's larger than any one single desktop, and switch around between desktops to look at different parts of that window. One of my brothers and I have both made productive use of this feature (for values of "productive" that relate to games and entertainment, anyway), and would not be happy to lose access to it. (Possible FUD alert; I don't have any citations for the next paragraph, although I trust the person from whom I learned of it.) I remember having been informed that people had brought this up with the Wayland developers, and that the upshot of the ensuing conversation was that those developers considered this feature to be an odd historical wart on the X specification, clearly of no value, and not worth supporting or implementing - and because they considered it so, Wayland had been designed in a way that made it difficult or impossible to implement that feature, even with people now requesting it. Another limitation of XWayland as I've heard it described (by the same person on whose statements the previous paragraph is based, as well as in online discussions related to XWeston, below), as compared to a full X server: where you can (and, in fact, usually need to) run a window manager on top of an X server, I'm given to understand that you cannot run a window manager on top of XWayland. Instead, the window manager needs to be implemented as a Wayland compositor, and you then run XWayland inside of that. (I have not actually tried to do this myself, for reasons which I'm about to get into, so I may have some of the details wrong.) That's a showstopper from my perspective, since the window manager I use A: is in long-tail maintenance mode, with very little work done over the past decade (relatively speaking), and will certainly not be rewritten as a Wayland compositor, and B: includes features which are built on top of that multiple-desktops windows-larger-than-the-desktop X feature, and which therefore probably cannot be implemented on top of Wayland. For reference in case anyone is interested, that window manager is Enlightenment DR16, also known as e16. It hasn't been in Debian for quite several releases now, I compile it from the upstream source tree. The solution to this is apparently XWeston[1], but I remember that being reported as having performance problems (though I'm not finding those reports again now) and I don't know how well supported it is even by its developer; it doesn't seem to have been touched since its initial development work in 2015. I keep meaning to try out running e16 inside of XWeston, but to date have not acquired a sufficiently circular tuit. [1] https://github.com/ackalker/Xweston https://bbs.archlinux.org/viewtopic.php?id=185297 https://www.reddit.com/r/linux/comments/2dna8v/xweston_xwayland_with_weston_the_other_way_round/ https://www.linuxquestions.org/questions/slackware-14/how-can-i-install-wayland-on-slackware-4175694086/page2.html -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Outil en CLI pour convertir une IPv4 en entier et réciproquement
salut Stéphane,
> % python3 -c "import sys, ipaddress; addr =
> ipaddress.ip_address(sys.argv[1]); print(int(addr))" 192.0.2.1
> 3221225985
ne faudrait-il pas tenir compte de l'endianisme? pour ma part j'ai:
/tmp/ipv4int 192.0.2.1
16908480 192.0.2.1
en executant ce code:
// vi: noet
#include
#include
int
main (int argc, char ** argv ) {
struct in_addr addr;
for (uint8_t i=1; i
Re: Outil en CLI pour convertir une IPv4 en entier et réciproquement
salut,
> Qui connait le nom d'un paquet Debian comprenant un outil de
> conversion d'IPv4 en entier et réciproquement ?
les réponses suivantes sont à coté de la plaque vu que tu
souhaites un outils dédié mais pourrais tu satisfaire ma curiosité
en m'expliquant à quoi ça peut servir?
ipv4int() <<. bc
ibase=16
$( for i; do
echo $i | tr . '\n' | tac | xargs printf '%02hX'
echo
done)
.
// vi: noet
#include
#include
int
main (int argc, char ** argv ) {
struct in_addr addr;
for (uint8_t i=1; i
Re: Wayland vs X
On Fri, 11 Mar 2022, Marco M?ller wrote: Isn't it all about X by design to not be able to safely protect a running X applications to snoop on other running X applications, something like the content of a window cannot safely kept private? I remember to have read that Wayland was invented for this reason, to overcome these security flaws of X which in the beginning of X have not been a concern to anyone, but nowadays security issues are of much importance to almost everyone. (I have no reference for this statement, just remember to have something like this read in the past) This is definitely true. Not sure if xev lets you pass in a window on the commandline but if not it's trivial to hack it to snoop on say keystrokes to any window. My ipmi-on-rpi uses exactly this trick to hook keystrokes typed to the video player without having to patch the code.
Re: got a mdadm puzzler
On Friday, 11 March 2022 13:11:14 EST Andy Smith wrote: > Hello, > > On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > > 2. I've had since the last of about 20 installs of bullseye, a very > > early boot message about ata6 at the 10 and 20 second marks of the > > reboot IF it was not a full powerdown reboot. > > Did you not at any point think that letting us know what the exact > error message was would be useful here? > IF that error message ever made it to the logs, I don't know which one. Its output to the screen, but I'll grep syslog for ata6. Found some, first instance was reboot, 2nd instance was bootup from a full powerdown of about 5 seconds: Mar 8 15:55:01 coyote kernel: [0.699889] ata6: SATA max UDMA/133 abar m2048@0xdf34b000 port 0xdf34b380 irq 126 Mar 8 15:55:01 coyote kernel: [6.071345] ata6: link is slow to respond, please be patient (ready=0) Mar 8 15:55:01 coyote kernel: [ 10.759342] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 16.111352] ata6: link is slow to respond, please be patient (ready=0) Mar 8 15:55:01 coyote kernel: [ 20.791354] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 26.143351] ata6: link is slow to respond, please be patient (ready=0) Mar 8 15:55:01 coyote kernel: [ 55.843357] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 55.843417] ata6: limiting SATA link speed to 3.0 Gbps Mar 8 15:55:01 coyote kernel: [ 60.895357] ata6: COMRESET failed (errno=-16) Mar 8 15:55:01 coyote kernel: [ 60.895417] ata6: reset failed, giving up 2nd instance, after power down Mar 8 15:56:06 coyote kernel: [0.684458] ata6: SATA max UDMA/133 abar m2048@0xdf34b000 port 0xdf34b380 irq 127 Mar 8 15:56:06 coyote kernel: [0.998471] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Mar 8 15:56:06 coyote kernel: [0.999415] ata6.00: ACPI cmd ef/ 10:06:00:00:00:00 (SET FEATURES) succeeded Mar 8 15:56:06 coyote kernel: [0.999416] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Mar 8 15:56:06 coyote kernel: [0.999417] ata6.00: ACPI cmd b1/ c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Mar 8 15:56:06 coyote kernel: [1.000270] ata6.00: ATA-9: ST2000DM001-1ER164, CC25, max UDMA/133 Mar 8 15:56:06 coyote kernel: [1.000272] ata6.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA Mar 8 15:56:06 coyote kernel: [1.001605] ata6.00: ACPI cmd ef/ 10:06:00:00:00:00 (SET FEATURES) succeeded Mar 8 15:56:06 coyote kernel: [1.001606] ata6.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Mar 8 15:56:06 coyote kernel: [1.001607] ata6.00: ACPI cmd b1/ c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Mar 8 15:56:06 coyote kernel: [1.002460] ata6.00: configured for UDMA/133 And this is the bootup I'm runniing on. > > So how do I go about querying mdadm to determine whats going south > > here? > As is so often the case with the problems you bring up, we risk > going down completely the wrong route because you do not supply > actual error messages or complete problem descriptions and just tell > us that you've decided it's a problem with XYZ subsystem. Much time > is spent looking into XYZ only to later find it was irrelevant or > the process could at least have been seriously improved by knowing > the symptoms to begin with (infamous "enabling IPv6 causes my > compile to fail" memories here). > > > The man pages are quite verbose, but I can't seem to find how to > > query > > what it has, without supplying the device names of all drives that > > s/b > > part of the array. > > > > And why do I see the ata6 error on a reboot, but not on a full > > powerdown reboot? > > So, WHAT IS "THE ATA6 ERROR"? > > Without knowing that it's very hard to speculate but I would point > out that things like "ATA" are way below the level of md which just > knows about block devices. So if you are seeing an "ata6 error" it > most likely has nothing whatsoever to do with your md setup, except > in the sense that if you are having problems with your storage > devices it's obviously going to percolate upwards and cause you RAID > grief too. > > > This is my first experience at software raid, so I am a new bee. My > > fingers are at your command. > > Then I command them to tell us useful information BEFORE you decide > where the problem lies. > > However, if you do want to know more about investigating your mdadm > setup, you already got the hint about cat /proc/mdstat. Here's some > other stuff: > > https://raid.wiki.kernel.org/index.php/Asking_for_help > > Thanks, > Andy > > -- > https://bitfolk.com/ -- No-nonsense VPS hosting > > . 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, 1940) If we desire respect for the law, we must first make the law
Re: Simple and secure blogging software for nginx
On Fri, Mar 11, 2022 at 12:48:28PM -0400, Chris Mitchell wrote:
> I believe Apache and nginx both have fairly robust support for popular
> server-side languages like PHP, so many toolkits will work happily on
> top of either one.
nginx can be told to contact php-fpm in order to run PHP scripts.
Here's a basic outline of what you want:
1) Install nginx. Set up your virtual hosts ("sites"), so that each
one is working, at least to the point of delivering an index.html
page out of the correct site's directory.
2) Install php-fpm.
3) In the virtual host that wants to allow PHP scripts, add a stanza like
this one:
location ~ \.php$ {
fastcgi_split_path_info ^(.+\.php)(/.+)$;
fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root/$fastcgi_script_name;
include fastcgi_params;
}
The exact path of the unix domain socket will depend on which version
of Debian (and therefore php-fpm) you're using.
4) Reload nginx, and test it.
This is quite different from the Apache philosophy of "oh, we will
provide a special apache-php module, and you need to configure Apache
to use this module". nginx uses a more strict separation. The web
server runs as one user, and the php-fpm daemon runs as a different
user, and they communicate over a unix domain socket.
That will matter if your PHP scripts need to write to files. You'll
need to make sure the files have appropriate ownership/permissions for
php-fpm to write to them, and *possibly* for nginx to read them, if
they're intended to be served directly. (If they're not intended to
be served, then don't store them under the document_root, and nginx
won't be able to find them.)
Re: evince has died a horrible death. Sob...
On Friday, 11 March 2022 13:11:36 EST Brian wrote: > On Fri 11 Mar 2022 at 11:28:05 -0500, gene heskett wrote: > > Thats been the most complete pdf viewer I've ever used. But I just > > tried to look at a doc I have looked at hundreds of times over he > > last years, and it got all upset all over itself, while I was logged > > into that machine with an ssh -Y login. > > > > What its its feature complete replacement in a buster install? This > > machine is bullseye, the logged into machine is buster. > > I would advise an inexperienced, lazy or incompetent user to extcute > 'apt search pdf' and search for "viewer" and "reader". Testing the > offerings striles me as fun. > > "feature complete"? Judge for yourself. > okular appears to fit the specs now. So while it sucked in 154 other dependencies, its now installed on all 6 machines. Working well on all. Thanks Brian > -- > Brian. > > . 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, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Simple and secure blogging software for nginx
Thank you for your thoughts, Russel, On 2022-03-11 18:40 UTC+0100, Russell L. Harris wrote: > Christian is talking about three different projects, each of which is > demanding of time. > > Securing and maintaining a web server is a difficult matter. But when > you can purchase hosting for US$4 per month, is it worth your while? Absolutely true. I do it on my own for fun and learning. If I only wanted the diary, I would contract a hoster. > Maintaining a blogging engine is a wholly different matter. And most people > are > looking for an engine which is requires little or no maintenance > (Blosxom, for example) and is simple and natural to use. WordPress I will look into this. > began as a blogging engine, but quickly morphed into an all-consuming > religion. :-) > Writing a public diary about moving to a new town is yet another > matter, and should not be constrained by either the blogging engine > or the web server. That task can easily consume all of your time. I don't hope so! I want to enjoy the new town! :-) (Actually I will live there for only half a year, at least that is the plan). The diary is for me, my friends and my family. > You need to decide on your primary goal and focus upon that. Running and writing the blog. At the moment I tend to a static generator, which would probably also make archival easier?! Regards, Christian -- http://www.cb-fraggle.de
Re: Wayland vs X
On 11.03.22 14:14, Christian Britz wrote: On 2022-03-11 12:47 UTC+0100, Nate Bargmann wrote: I have used Gnome on Wayland since late 2018. It improved a lot with the release of Bullseye. I use this setup on two machines, a laptop and a desktop that has two monitors. So far I have not had any issues with And what is the practical _advantage_ over a X11 setup? The question is serious. Everytime I tried Wayland, something was not working as expected, uncomfortable to use and so on. Yes, Wayland support has improved a lot, but I still do not really see what I miss because I stick to X11. I know that Wayland has a cleaner design, but that bothers me not too much as a user. Regards, Christian Isn't it all about X by design to not be able to safely protect a running X applications to snoop on other running X applications, something like the content of a window cannot safely kept private? I remember to have read that Wayland was invented for this reason, to overcome these security flaws of X which in the beginning of X have not been a concern to anyone, but nowadays security issues are of much importance to almost everyone. (I have no reference for this statement, just remember to have something like this read in the past) And isn't it because of Wayland protecting windows by design against other windows, that operations like Copy between GUI applications are (still) not always running smoothly and need extra efforts to become well implemented? (Again, I have no reference for this statement, just remember to have something like this read in the past) Regards, Marco
Re: evince has died a horrible death. Sob...
On Fri 11 Mar 2022 at 11:28:05 -0500, gene heskett wrote: > Thats been the most complete pdf viewer I've ever used. But I just tried > to look at a doc I have looked at hundreds of times over he last years, > and it got all upset all over itself, while I was logged into that > machine with an ssh -Y login. > > What its its feature complete replacement in a buster install? This > machine is bullseye, the logged into machine is buster. I would advise an inexperienced, lazy or incompetent user to extcute 'apt search pdf' and search for "viewer" and "reader". Testing the offerings striles me as fun. "feature complete"? Judge for yourself. -- Brian.
Re: got a mdadm puzzler
Hello, On Thu, Mar 10, 2022 at 07:18:56AM -0500, gene heskett wrote: > 2. I've had since the last of about 20 installs of bullseye, a very early > boot message about ata6 at the 10 and 20 second marks of the reboot IF > it was not a full powerdown reboot. Did you not at any point think that letting us know what the exact error message was would be useful here? > So how do I go about querying mdadm to determine whats going south here? As is so often the case with the problems you bring up, we risk going down completely the wrong route because you do not supply actual error messages or complete problem descriptions and just tell us that you've decided it's a problem with XYZ subsystem. Much time is spent looking into XYZ only to later find it was irrelevant or the process could at least have been seriously improved by knowing the symptoms to begin with (infamous "enabling IPv6 causes my compile to fail" memories here). > The man pages are quite verbose, but I can't seem to find how to query > what it has, without supplying the device names of all drives that s/b > part of the array. > > And why do I see the ata6 error on a reboot, but not on a full powerdown > reboot? So, WHAT IS "THE ATA6 ERROR"? Without knowing that it's very hard to speculate but I would point out that things like "ATA" are way below the level of md which just knows about block devices. So if you are seeing an "ata6 error" it most likely has nothing whatsoever to do with your md setup, except in the sense that if you are having problems with your storage devices it's obviously going to percolate upwards and cause you RAID grief too. > This is my first experience at software raid, so I am a new bee. My > fingers are at your command. Then I command them to tell us useful information BEFORE you decide where the problem lies. However, if you do want to know more about investigating your mdadm setup, you already got the hint about cat /proc/mdstat. Here's some other stuff: https://raid.wiki.kernel.org/index.php/Asking_for_help Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Simple and secure blogging software for nginx
On Fri, Mar 11, 2022 at 08:19:02AM -0500, songbird wrote: Christian Britz wrote: ... Thank you, I allow my self to reply on the list. I heard that WordPress is very common, but I fear it might be oversized for my public diary about moving to a new town, which I plan to write. And it is very often in the news with security holes... Don't want some bad person to manipulate my cute tiny Raspi, now that it has finally moved to pure Debian. ;-) I want the solution to be in the repository to benefit from unattended-upgrades. i use hugo for my website. but hugo is not nginx. Christian is talking about three different projects, each of which is demanding of time. Securing and maintaining a web server is a difficult matter. But when you can purchase hosting for US$4 per month, is it worth your while? Maintaining a blogging engine is a wholly different matter. And most people are looking for an engine which is requires little or no maintenance (Blosxom, for example) and is simple and natural to use. WordPress began as a blogging engine, but quickly morphed into an all-consuming religion. Writing a public diary about moving to a new town is yet another matter, and should not be constrained by either the blogging engine or the web server. That task can easily consume all of your time. You need to decide on your primary goal and focus upon that. RLH
Re: evince has died a horrible death. Sob...
On Fri, Mar 11, 2022 at 11:28:05AM -0500, gene heskett wrote: > Thats been the most complete pdf viewer I've ever used. But I just tried > to look at a doc I have looked at hundreds of times over he last years, > and it got all upset all over itself, while I was logged into that > machine with an ssh -Y login. Your post is so full of tacit assumptions and implicit conclusions that I have no idea where to start helping you :-) What got upset: the doc, evince, ssh or -Y? If yes: what are the symptoms? Is evince really dead? If yes: how do you know? > What its its feature complete replacement in a buster install? This > machine is bullseye, the logged into machine is buster. This assumes that you want to replace evince. For whatever reason. Explain it to us, and we might have ideas. Cheers -- t signature.asc Description: PGP signature
Re: Simple and secure blogging software for nginx
On Thu, 10 Mar 2022 22:39:34 +0100 Christian Britz wrote: > Sure, I think I was not precise in my posting. I am willing to add > something dynamic, and I was not sure if Apache and nginx support the > same toolkits. > > You and others brought in several static content generators, I will > consider that option too. I believe Apache and nginx both have fairly robust support for popular server-side languages like PHP, so many toolkits will work happily on top of either one. That said, you did mention "as secure as possible" in your initial request, and obviously no other option comes anywhere near static html pages in terms of security. Count me as another voice in favour of a static site generator. In particular, I've been playing around with Hugo, which won me over largely by virtue of using Markdown as its input format. With all respect to LaTeX (sorry Russell!), it's a staggeringly complex language with a steep learning curve. If you want a markup language that supports every typographical feature ever invented, you can't beat LaTeX. For basic web content with links, emphasis, and the occasional bulleted list, Markdown is enough tool for the job, and has the advantages of simplicity and vastly greater human-readability. I don't know about you, but I don't need a 747 to get to the corner store. Site generators like Hugo automatically generate nav menus, TOCs, and similar, so you get a lot of the convenience features of a blogging platform... just without the platform. If you use git, you can make a relatively uncomplicated, entirely self-hosted deploy pipeline that updates the site automatically whenever you make a commit to the website's git repo, as shown here: https://www.digitalocean.com/community/tutorials/how-to-deploy-a-hugo-site-to-production-with-git-hooks-on-ubuntu-14-04 And since the content is all plain Markdown files stored in a sensible directory structure on disk, it's very portable in case you want to move to some other platform later. There is definitely a bit of a learning curve with Hugo, though if you start with a pre-built "theme", it's not overly hard to get a site up and running now and delve into all the customizable details later. Cheers! -Chris
Re: evince has died a horrible death. Sob...
On 2022-03-11 17:28 UTC+0100, gene heskett wrote: > Thats been the most complete pdf viewer I've ever used. But I just tried > to look at a doc I have looked at hundreds of times over he last years, > and it got all upset all over itself, while I was logged into that > machine with an ssh -Y login. > > What its its feature complete replacement in a buster install? This > machine is bullseye, the logged into machine is buster. What is the actual problem? How does an "upset" PDF viewer behave? -- http://www.cb-fraggle.de
Re : Outil en CLI pour convertir une IPv4 en entier et réciproquement
Le 11/03/2022 17:40:52, Stephane Bortzmeyer a écrit :
> % python3 -c "import sys, ipaddress; addr =
> ipaddress.ip_address(sys.argv[1]); print(int(addr))" 192.0.2.1
> 3221225985
Ha, c’est juste ça ?
>>> sum(256**(3-i)*a for i,a in enumerate(map(int,"192.0.2.1".split("."
3221225985
nicolas patrois : pts noir asocial
--
RÉALISME
M : Qu'est-ce qu'il nous faudrait pour qu'on nous considère comme des humains ?
Un cerveau plus gros ?
P : Non... Une carte bleue suffirait...
Re: Outil en CLI pour convertir une IPv4 en entier et réciproquement
On Fri, Mar 11, 2022 at 05:29:01PM +0100, Olivier wrote a message of 11 lines which said: > conversion d'IPv4 en entier et réciproquement ? % python3 -c "import sys, ipaddress; addr = ipaddress.ip_address(sys.argv[1]); print(int(addr))" 192.0.2.1 3221225985
Re: evince has died a horrible death. Sob...
On 3/11/22, gene heskett wrote: > Thats been the most complete pdf viewer I've ever used. But I just tried > to look at a doc I have looked at hundreds of times over he last years, > and it got all upset all over itself, while I was logged into that > machine with an ssh -Y login. > > What its its feature complete replacement in a buster install? This > machine is bullseye, the logged into machine is buster. Thinking out loud.. Did you try a different PDF file to make sure it's not just one suddenly corrupt file instead of being evince? Personally, I use Atril on XFCE4, but all I've ever done is read files. I follow Atril's Github that was active in the last few weeks: https://github.com/mate-desktop/atril/ Important to note for some users is that I occasionally see requests for useful features that apparently Atril might not do while other packages do. Cindy :) -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: Wayland vs X
Le vendredi 11 mars 2022 à 08:07 -0600, Nate Bargmann a écrit : > > Gnome is now native with Wayland and its visual effects only work > with > Wayland as I understand it. I did try Gnome Flashback as it runs on > X11 > and the visual effects were disabled. In some cases that's not an > issue and is likely appropriate for some hardware. [...] If I am not wrong: - Gnome (aka Gnome shell) can run in X or Wayland (Debian defaults to Wayland), its window manager is Mutter and it needs an hardware accelerated graphic card - Gnome Classic is a pre-configured Gnome2-like DE based on Gnome shell, it cans also run in X or Wayland (but Debian still defaults to X in Bullseye), its window manager is Mutter and it needs an hardware accelerated graphic card - Gnome Flashback is an evolution of the old Gnome Fallback, it can run in X but not in Wayland as its window manager is Metacity (like Gnome2). It's a Gnome2-like DE that does not require an hardware accelerated graphic card So Gnome Classic would probably suits you better than Gnome Flashback
Re: evince has died a horrible death. Sob...
Am 11. Mar, 2022 schwätzte gene heskett so: moin moin, I dropped evince for okular a few years ago and have been happy with the change. I run KDE, so that might make a difference. I do ssh -Y into containers without KDE installed to use it shooting the display back to a debian box with KDE. I use this on a box that had buster installed and has now been upgraded to bullseye. ciao, der.hans Thats been the most complete pdf viewer I've ever used. But I just tried to look at a doc I have looked at hundreds of times over he last years, and it got all upset all over itself, while I was logged into that machine with an ssh -Y login. What its its feature complete replacement in a buster install? This machine is bullseye, the logged into machine is buster. Thank you. Cheers, Gene Heskett. -- # https://www.LuftHans.com https://www.PhxLinux.org # The key to making programs fast is to make them do practically # nothing. ;-) -- Mike Haertel, 2011Aug21
Outil en CLI pour convertir une IPv4 en entier et réciproquement
Bonjour, Qui connait le nom d'un paquet Debian comprenant un outil de conversion d'IPv4 en entier et réciproquement ? Sauf erreur ipcalc et ipcalc-ng ne font pas cette conversion. J'ai trouvé des exemples en bash, ici ou là mais regarderai volontiers un outil dédié. Slts
evince has died a horrible death. Sob...
Thats been the most complete pdf viewer I've ever used. But I just tried to look at a doc I have looked at hundreds of times over he last years, and it got all upset all over itself, while I was logged into that machine with an ssh -Y login. What its its feature complete replacement in a buster install? This machine is bullseye, the logged into machine is buster. Thank you. 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, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Quel(s) serveur(s) DHCP pour 250 LAN de petite taille (/28) ?
Très intéressant ! Je n'y a avais pas pensé du tout ! Dans mon labo, le serveur DHCP fait office de routeur mais sur l'implémentation cible, il est possible que ce rôle soit confié à une machine tierce. Dans les 2 cas, il faudra savoir configurer en masse les réseaux et les relais DHCP. Le ven. 11 mars 2022 à 14:43, Erwan David a écrit : > > Le 11/03/2022 à 12:48, Olivier a écrit : > > Bonjour, > > > > Je souhaite mettre en place sur une machine Bullseye, un service DHCP > > traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses) > > mais chacun avec 1 ou 2 machines connectées, au maximum. > > > > 1. Qui a déjà mis en oeuvre ce type de chose ? Avec quels composants ? > > Quel retour d'expérience ? > > > > 2. Je connais le serveur DHCP d'ISC. J'ai l'habitude de lister les > > interfaces sur lesquelles il écoute > > en complétant la ligne INTERFACESv4 du fichier /etc/default/interfaces. > > Existe-t-il une autre façon de fournir la liste des interfaces ? > > Plutôt que d'avoir ton serveur avec une interface dans chacun de tes 250 > réseaux, tu peux utiliser un relais dhcp (par exemple sur le ou les > touteurs qui relient tes réseaux) C'est plus simple puisque ton serveur > DHCP n'a qu'une uinterface. Le relais lui envoie l'adresse de > l'interface qui a reçu la reqêute et ton serveur trouve le pool > correspondant. > > C'est très simple à mettre en place >
Re: Consulta xrdp
El 2022-03-11 a las 12:29 -0300, Fernando Romero escribió: > Estoy usando xrdp como conexión de escritorio remoto a mi debian desde > windows u otro linux. > El problema que tengo es que si tengo al usuario logueado en linux (debian) > no me permite conectarme por remoto, estuve tocando la configuración de > xrdp para que me permita múltiples conexiones pero no le encontre la vuelta. > ¿Alguien conoce como hacerlo? Por aquí te dan algunas ideas: xRDP – Allow multiple sessions (local and remote) for the same user – HowTo https://c-nergy.be/blog/?p=16698 Saludos, -- Camaleón
Re: Quel(s) serveur(s) DHCP pour 250 LAN de petite taille (/28) ?
On Friday 11 March 2022 12:48:54 Olivier wrote: > Je souhaite mettre en place sur une machine Bullseye, un service DHCP > traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses) > mais chacun avec 1 ou 2 machines connectées, au maximum. > 1. Qui a déjà mis en oeuvre ce type de chose ? Avec quels composants ? > Quel retour d'expérience ? > 2. Je connais le serveur DHCP d'ISC. J'ai l'habitude de lister les > interfaces sur lesquelles il écoute > en complétant la ligne INTERFACESv4 du fichier /etc/default/interfaces. > Existe-t-il une autre façon de fournir la liste des interfaces ? > 3. Suggestions ? Conseils ? Hello, Entre autres, il faut bien calculer les numéros de netmask, (segmentation des réseaux et sous réseaux) qui ne sera plus 255.255.255.0, selon ce que l'on veut, souvent l'imperméabilisation des réseaux entre eux (sécurité, interdire l'accès à des sous-réseaux). Bonne soirée. A. Valmer
Consulta xrdp
Hola como estan. Estoy usando xrdp como conexión de escritorio remoto a mi debian desde windows u otro linux. El problema que tengo es que si tengo al usuario logueado en linux (debian) no me permite conectarme por remoto, estuve tocando la configuración de xrdp para que me permita múltiples conexiones pero no le encontre la vuelta. ¿Alguien conoce como hacerlo? Saludos
Re: Simple and secure blogging software for nginx
Christian Britz wrote: ... > Thank you, I allow my self to reply on the list. > I heard that WordPress is very common, but I fear it might be oversized > for my public diary about moving to a new town, which I plan to write. > And it is very often in the news with security holes... Don't want some > bad person to manipulate my cute tiny Raspi, now that it has finally > moved to pure Debian. ;-) > > I want the solution to be in the repository to benefit from > unattended-upgrades. i use hugo for my website. but hugo is not nginx. songbird
Re: Wayland vs X
* On 2022 11 Mar 07:16 -0600, Christian Britz wrote: > > > On 2022-03-11 12:47 UTC+0100, Nate Bargmann wrote: > > > I have used Gnome on Wayland since late 2018. It improved a lot with > > the release of Bullseye. I use this setup on two machines, a laptop and > > a desktop that has two monitors. So far I have not had any issues with > > And what is the practical _advantage_ over a X11 setup? Gnome is now native with Wayland and its visual effects only work with Wayland as I understand it. I did try Gnome Flashback as it runs on X11 and the visual effects were disabled. In some cases that's not an issue and is likely appropriate for some hardware. > The question is serious. Everytime I tried Wayland, something was not > working as expected, uncomfortable to use and so on. Yes, Wayland > support has improved a lot, but I still do not really see what I miss > because I stick to X11. I know that Wayland has a cleaner design, but > that bothers me not too much as a user. Interesting as no one uses Wayland or X11 directly but through a window manager or quite likely one of the desktop environments. Debian packaging seems to sort this out where a DE like Xfce only installs Xorg packages and Gnome installs Wayland and Xwayland. That said, if hardware support is not present, then I suspect that any advanced features will have problems. Use what works for you. I am just providing my experience as I'm not a cheerleader for Wayland or against Xorg, just a satisfied user of both. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Re: Quel(s) serveur(s) DHCP pour 250 LAN de petite taille (/28) ?
Le 11/03/2022 à 12:48, Olivier a écrit : Bonjour, Je souhaite mettre en place sur une machine Bullseye, un service DHCP traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses) mais chacun avec 1 ou 2 machines connectées, au maximum. 1. Qui a déjà mis en oeuvre ce type de chose ? Avec quels composants ? Quel retour d'expérience ? 2. Je connais le serveur DHCP d'ISC. J'ai l'habitude de lister les interfaces sur lesquelles il écoute en complétant la ligne INTERFACESv4 du fichier /etc/default/interfaces. Existe-t-il une autre façon de fournir la liste des interfaces ? Plutôt que d'avoir ton serveur avec une interface dans chacun de tes 250 réseaux, tu peux utiliser un relais dhcp (par exemple sur le ou les touteurs qui relient tes réseaux) C'est plus simple puisque ton serveur DHCP n'a qu'une uinterface. Le relais lui envoie l'adresse de l'interface qui a reçu la reqêute et ton serveur trouve le pool correspondant. C'est très simple à mettre en place
Re: Wayland vs X
On 2022-03-11 12:47 UTC+0100, Nate Bargmann wrote: > I have used Gnome on Wayland since late 2018. It improved a lot with > the release of Bullseye. I use this setup on two machines, a laptop and > a desktop that has two monitors. So far I have not had any issues with And what is the practical _advantage_ over a X11 setup? The question is serious. Everytime I tried Wayland, something was not working as expected, uncomfortable to use and so on. Yes, Wayland support has improved a lot, but I still do not really see what I miss because I stick to X11. I know that Wayland has a cleaner design, but that bothers me not too much as a user. Regards, Christian -- http://www.cb-fraggle.de
Re: Wayland vs X
* On 2022 10 Mar 17:04 -0600, Emanuel Berg wrote: > didier gaumet wrote: > > >> OK, thanks, I won't switch then I think ... I like feh and > >> use it a lot. > > > > Just to be clear in case there would be a misunderstanding > > because my sentence was not accurate enough: what I meant is > > feh (for example) is not directly compatible with Wayland, but > > can be run in the X11 compatibility layer of Wayland > > (Xwayland, the nested X server that can be run inside > > Wayland) > > No, I understood, but that sounds like too much emulator ... My understanding is that xwayland is an X server that runs under Wayland and the idea is that it handles X protocols but Wayland handles the video drivers and screen drawing. I have used Gnome on Wayland since late 2018. It improved a lot with the release of Bullseye. I use this setup on two machines, a laptop and a desktop that has two monitors. So far I have not had any issues with any Debian provided packages. They just work, including feh which I call from neomutt to display images. No fuss, no configuration, it just works. I've even built and locally installed GTK2 apps without issue. I did have a display issue with a proprietary third party program that was built with some older version of Qt, as I recall. That has been replaced by a version that is FOSS and it works fine. On the desktop with dual monitors I have xscreensaver running and it has the most issues with detecting events as when I do strictly keyboard work it will time out and start running a saver. Moving the mouse wakes it up. It also glitches at other times even when using the mouse, but this is not a show stopper for me. It also doesn't handle DPMS on Wayland either which I can live with (I'm sure the built in Gnome blanker works just fine). My GPUs are stock Intel on board graphics as I don't game nor do I need fancy 3D capability. This hardware is sufficient for displaying the GL screen savers and for whatever compositing requirements Gnome has. HTH - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 signature.asc Description: PGP signature
Quel(s) serveur(s) DHCP pour 250 LAN de petite taille (/28) ?
Bonjour, Je souhaite mettre en place sur une machine Bullseye, un service DHCP traitant 250 réseaux locaux de petite taille (/28 soit 16 adresses) mais chacun avec 1 ou 2 machines connectées, au maximum. 1. Qui a déjà mis en oeuvre ce type de chose ? Avec quels composants ? Quel retour d'expérience ? 2. Je connais le serveur DHCP d'ISC. J'ai l'habitude de lister les interfaces sur lesquelles il écoute en complétant la ligne INTERFACESv4 du fichier /etc/default/interfaces. Existe-t-il une autre façon de fournir la liste des interfaces ? 3. Suggestions ? Conseils ? Slts
Re: Simple and secure blogging software for nginx
Take a look at https://dotclear.org/ which is PHP based. Some time ago Debian also had it packaged. Regards, Jörg.
Re: Comment recharger un module noyau planté ?
Salut, C'est juste le redémarrage qui ne se fait pas ? (boucle) Le jeu. 10 mars 2022 à 13:41, Daniel Caillibaud a écrit : > Bonjour, > > J'ai toujours mes pbs de plantage kernel à cause du module wifi > (ath10k_pci), même si ça c'est > arrangé (ça plante 1 à 2 fois par semaine, mais seulement le réseau, avant > tout était figé, > donc je peux sauvegarder ce que je fais, c'est juste pénible avec des > consoles ouvertes ou un > truc en cours dans un navigateur). > > Est-ce que dans un tel cas on peut recharger le module noyau sans reboot > hard ? > (le reboot soft fonctionne pas, le PC veut pas s'arrêter) > > J'ai essayé > rmmod ath10k_pci > (en pensant passer ensuite à insmod ou modprob) > > mais ça ne fait rien, ça ne rend pas la main et ne dit rien (pas pensé à > ajouter -v, je le > ferai la prochaine fois) > > J'étais sur un noyau 5.12.9 compilé maison (avec intel-microcode > 3.20210608.2 de bullseye), je > vais essayer linux-image-5.16.0-0.bpo.3-amd64-unsigned et > intel-microcode=3.20220207.1~bpo11+1 > pour voir si ça s'arrange, mais la réponse m'intéresse quand même. > > > > Le détail : > > 1) modinfo ath10k_pci > > filename: > /lib/modules/5.12.9/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko > … > description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB > devices > author: Qualcomm Atheros > … > depends:ath10k_core > retpoline: Y > intree: Y > name: ath10k_pci > vermagic: 5.12.9 SMP mod_unload modversions > parm: irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint) > parm: reset_mode:0: auto, 1: warm only (default: 0) (uint) > > > 2) Les messages de kern.log au plantage du module : > > Mar 10 09:36:13 dell kernel: [144708.337905] IPv6: > ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready > Mar 10 09:36:13 dell kernel: [144708.337965] wlp2s0: Limiting TX power to > 23 (26 - 3) dBm as advertised by 68:a3:78:b8:7e:94 > Mar 10 10:14:13 dell kernel: [146989.982839] ath10k_pci :02:00.0: > failed to wake target for write32 of 0x0579 at 0x0003543c: -110 > [plein de failed to wake target] > Mar 10 10:17:23 dell kernel: [147179.685280] ath10k_pci :02:00.0: > failed to wake target for read32 at 0x0003a028: -110 > Mar 10 10:17:26 dell kernel: [147182.767232] ath10k_pci :02:00.0: > failed to read device register, device is gone > Mar 10 10:17:26 dell kernel: [147182.768293] ieee80211 phy0: Hardware > restart was requested > Mar 10 10:17:26 dell kernel: [147182.768303] [ cut here > ] > Mar 10 10:17:26 dell kernel: [147182.768304] ieee80211_restart_work called > with hardware scan in progress > Mar 10 10:17:26 dell kernel: [147182.768350] WARNING: CPU: 1 PID: 186880 > at net/mac80211/main.c:261 ieee80211_restart_work+0xf3/0x100 [mac80211] > Mar 10 10:17:26 dell kernel: [147182.768375] Modules linked in: loop(E) > rfcomm(E) ctr(E) ccm(E) cmac(E) algif_hash(E) algif_skcipher(E) af_alg(E) > bnep(E) binfmt_misc(E) intel_rapl_msr(E) dell_smm_hwmon(E) > snd_hda_codec_hdmi(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) > coretemp(E) snd_sof_pci_intel_icl(E) snd_sof_intel_hda_common(E) > soundwire_intel(E) kvm_intel(E) soundwire_generic_allocation(E) > soundwire_cadence(E) snd_sof_intel_hda(E) snd_sof_pci(E) snd_sof(E) kvm(E) > snd_sof_xtensa_dsp(E) snd_soc_hdac_hda(E) snd_hda_ext_core(E) > snd_soc_acpi_intel_match(E) snd_soc_acpi(E) irqbypass(E) rapl(E) > snd_soc_core(E) intel_cstate(E) snd_hda_codec_realtek(E) snd_compress(E) > nls_ascii(E) soundwire_bus(E) snd_hda_codec_generic(E) intel_uncore(E) > ledtrig_audio(E) nls_cp437(E) btusb(E) btrtl(E) snd_hda_intel(E) > ath10k_pci(E) btbcm(E) btintel(E) snd_intel_dspcfg(E) snd_intel_sdw_acpi(E) > ath10k_core(E) vfat(E) pcspkr(E) fat(E) ath(E) bluetooth(E) serio_raw(E) > snd_hda_codec(E) efi_pstore(E) wmi_bmof(E) intel_wmi_thunderbolt(E) > Mar 10 10:17:26 dell kernel: [147182.768403] snd_hda_core(E) snd_hwdep(E) > mac80211(E) snd_pcm(E) iTCO_wdt(E) uvcvideo(E) intel_pmc_bxt(E) > snd_timer(E) iTCO_vendor_support(E) watchdog(E) snd(E) ee1004(E) > videobuf2_vmalloc(E) jitterentropy_rng(E) soundcore(E) videobuf2_memops(E) > videobuf2_v4l2(E) cfg80211(E) drbg(E) videobuf2_common(E) ansi_cprng(E) > processor_thermal_device(E) videodev(E) processor_thermal_rfim(E) > libarc4(E) processor_thermal_mbox(E) mc(E) joydev(E) mei_me(E) > ecdh_generic(E) processor_thermal_rapl(E) rfkill(E) intel_rapl_common(E) > ecc(E) sg(E) mei(E) intel_soc_dts_iosf(E) int3403_thermal(E) > int340x_thermal_zone(E) tpm_crb(E) tpm_tis(E) tpm_tis_core(E) tpm(E) > evdev(E) int3400_thermal(E) rng_core(E) acpi_thermal_rel(E) acpi_tad(E) > intel_pmc_core(E) ac(E) intel_hid(E) sparse_keymap(E) acpi_pad(E) msr(E) > parport_pc(E) ppdev(E) lp(E) parport(E) fuse(E) configfs(E) sunrpc(E) > efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc32c_generic(E) > crc16(E) mbcache(E) jbd2(E) dm_crypt(E) dm_mod(E) sr_mod(E) > Mar 10 10:17:26 dell kernel: [147182.768439] sd_mod(E)
Re: Launch a minimal MATE DE
On 9/03/22 04:06, David Wright wrote: On Tue 08 Mar 2022 at 07:00:08 (+0100), to...@tuxteam.de wrote: On Tue, Mar 08, 2022 at 01:54:11PM +1300, Richard Hector wrote: [...] > Just to solve the infinite recursion problem: > > richard@zircon:~$ apt-file search bin/apt-file > apt-file: /usr/bin/apt-file > > so install the apt-file package :-) Oh, a recursive fishing rod :-) Sorry to disappoint, but I think we're dealing with repetition here, rather than recursion: Perhaps both. Cheers, Richard
Re: Simple and secure blogging software for nginx
On 2022-03-11 06:06 UTC+0100, Russell L. Harris wrote: > Life is too short to mess around with a markup language other than > LaTeX. Work always in LaTeX. Next topic on my learning agenda. :-) -- http://www.cb-fraggle.de
