Re: Debian "Bookworm" Installation
On Wed 13 Apr 2022 at 17:13:39 (-0700), David Christensen wrote: > On 4/13/22 16:07, Peter Hillier-Brook wrote: > > I've just attempted to Install "Bookworm" to a USB stick and it > > went mostly to plan, apart from the fact that it won't boot. > > However that's not the issue at hand: I can't find a way to > > persuade the installer's partitioner to use GPT instead of the > > MS-DOS partitioning scheme. > > I use the d-i at the simplest level I can (e.g. text "Install" mode > from the main menu). From what I have observed, d-i detects if the > host is using BIOS or UEFI, and chooses MBR or GPT partitioning > accordingly. Assume the host firmware can operate as UEFI, I would use > the CMOS Setup program to set the host firmware to UEFI and then boot > d-i. I didn't know that, probably because I have never tried to run the debian-installer with what's effectively a blank disk.¹ So my answer would be to write a blank partition table onto the USB stick before you start the installer. You can do this with fdisk using its "g" command, or with gdisk using its "o" command. If you want to keep the contents of the stick, rather than starting afresh, you can usually convert it from MBR to GPT with gdisk. If the last partition has been created to completely fill the stick, this will probably fail, because a GPT disk needs room for a backup partition table at the very end. You would need to shrink the last partition's filesystem, and then the partition itself, before converting the stick. ¹ Back in the 1990s, I required dual-booting with DOS6.22, and so I let DOS's FDISK set the disk geometry and create the first partition. Since that era, I've always created my partitioning scheme before starting the installer. Cheers, David.
Re: backing up backups
On Wed, Apr 13, 2022 at 4:42 PM David Christensen wrote: > On 4/13/22 09:20, Default User wrote: > > >> Hey guys, sorry for just getting back with you now. > >> Unfortunately, I am just now recovering from a self-inflicted computer > >> disaster. > >> > >> While fighting with rsync, I did either: > >> > >> sudo rsync -aAXHSxvv --delete --info=progress2,stats2,name2 > >> /media/default/MSD1/ /media/default/MSD2 > >> or > >> sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 > >> /media/default/MSD1/ /media/default/MSD2/ > >> > >> Just one small problem: MSD2 was not connected to my computer! > >> (Don't say it . . . ) > >> > >> Instead of giving an error message, rsync just created a directory on my > >> computer called /media/defaultMSD2, and filled it up until my / > partition > >> was full, and THEN my desktop environment (Cinnamon) popped up a > >> notification saying so. How thoughtful. > >> > >> The computer then would not reboot into the operating system. > >> > >> No problem, I say. I will just use Timeshift to restore from its backup > of > >> a few hours earlier. > >> > >> But that did not work, even after deleting the extra directory, and > trying > >> restores from multiple Timeshift backups. > >> > >> Anyway, I never could fix the problem. But I did take it as an > opportunity > >> to "start over". I put in a new(er) SSD, and did a fresh install, > replacing > >> Cinnamon with Gnome. Mistake - now I remember why I dislike Gnome, ever > >> since Gnome 3. Wish I had re-installed Cinnamon, but too late now, out > of > >> time. For now I will just have to grit my teeth and live with it. > >> > >> [BTW, yes, I do have all of my data. Backfilling it into my new setup > will > >> no doubt be an ongoing adventure.] > >> > >> Anyway, just a few notes about the rsync situation: > >> > >> 1) Having or not having a trailing / on the destination directory did > not > >> seem to make any difference in the size of the copy made, or otherwise. > >> Nevertheless, I intend to heed the advice given to have a trailing / > after > >> both source and destination, or neither, as appropriate. > >> > >> 2) Using or not using an "S" option with rsync did not seem to make any > >> difference, at least concerning the size of the copy made. > >> > >> 3) Yes, I really should check into using checksums to avoid "bot rot". > >> Good advice. > >> > >> Finally, Gnome sucks. (Did I mention that?) > >> > >> Thanks for the replies. > > > Congratulations! You now have more experience: > > "Doing things right is a matter of experience. Experience is a matter > of doing things wrong." > > > As you find system administration commands that work, put them into > scripts: > > #!/bin/sh > sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 > /media/default/MSD1/ /media/default/MSD2/ > > > Use a version control system for system administration. Create a > project for every machine. Check in system configuration files, > scripts, partition table backups, encryption header backups, RAID header > backups, etc.. Maintain a plain text log file with notes of what you > did (e.g. console sessions), when, and why. > > > Put your OS on a small, fast device (e.g. SSD) and put your data on an > array of large devices (e.g. ZFS pool with one or more HDD mirrors). > Backup both as before. Additionally, take images of your OS device. > > > David > > Yikes! David, I really think I am too old to learn all of that. But maybe I can learn at least some of it, over time. Please understand that I am not training to be a real system administrator, except that I guess anyone is (or should be able to be) actually the "system administrator" of their own computer(s). Anyway, thanks for the advice.
Re: Debian "Bookworm" Installation
On 4/13/22 16:07, Peter Hillier-Brook wrote: Hello All, I've just attempted to Install "Bookworm" to a USB stick and it went mostly to plan, apart from the fact that it won't boot. However that's not the issue at hand: I can't find a way to persuade the installer's partitioner to use GPT instead of the MS-DOS partitioning scheme. Anyone with thoughts (Brian?) about this? Best wishes. Peter HB I use the d-i at the simplest level I can (e.g. text "Install" mode from the main menu). From what I have observed, d-i detects if the host is using BIOS or UEFI, and chooses MBR or GPT partitioning accordingly. Assume the host firmware can operate as UEFI, I would use the CMOS Setup program to set the host firmware to UEFI and then boot d-i. David
Debian "Bookworm" Installation
Hello All, I've just attempted to Install "Bookworm" to a USB stick and it went mostly to plan, apart from the fact that it won't boot. However that's not the issue at hand: I can't find a way to persuade the installer's partitioner to use GPT instead of the MS-DOS partitioning scheme. Anyone with thoughts (Brian?) about this? Best wishes. Peter HB
Re: Comment réserver à un seul fichier des logs en provenance d'une application donnée
Salut, Je n'ai jamais utilisé natlog mais sa page man me suggère de s'intéresser à son fichier de configuration et aux options de lancement: --log=argument (pour désactiver le log système en activant le log dans un fichier particulier) et --log-rotate=spec (pour la rotation et la rétention) par exemple pour spécifier où atterrit le logging: --log=/chemin/de/ton/fichier.log et pour une rotation d'un jour et une rétention de 365 jours, peut-être (je ne suis pas sûr d'avoir compris la spécification du format): --log-rotate=time[1]365
Re: Impossible de joindre un ancien serveur
Vu que je suis une bille en réseaux, j'espère que quelqu'un corrigera si je dis des bêtises: Si c'est du iptables ou du nftables syntaxe iptables et pas du pur nftables, regarder là comment réinitialiser les règles. Et vraisembleblement faire la même chose pour IPV6 (ip6tables)? https://qastack.fr/server/497438/how-to-reset-ubuntu-12-04-iptables-to-default-without-locking-oneself-out
Re: backing up backups
On 4/13/22 09:20, Default User wrote: Hey guys, sorry for just getting back with you now. Unfortunately, I am just now recovering from a self-inflicted computer disaster. While fighting with rsync, I did either: sudo rsync -aAXHSxvv --delete --info=progress2,stats2,name2 /media/default/MSD1/ /media/default/MSD2 or sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 /media/default/MSD1/ /media/default/MSD2/ Just one small problem: MSD2 was not connected to my computer! (Don't say it . . . ) Instead of giving an error message, rsync just created a directory on my computer called /media/defaultMSD2, and filled it up until my / partition was full, and THEN my desktop environment (Cinnamon) popped up a notification saying so. How thoughtful. The computer then would not reboot into the operating system. No problem, I say. I will just use Timeshift to restore from its backup of a few hours earlier. But that did not work, even after deleting the extra directory, and trying restores from multiple Timeshift backups. Anyway, I never could fix the problem. But I did take it as an opportunity to "start over". I put in a new(er) SSD, and did a fresh install, replacing Cinnamon with Gnome. Mistake - now I remember why I dislike Gnome, ever since Gnome 3. Wish I had re-installed Cinnamon, but too late now, out of time. For now I will just have to grit my teeth and live with it. [BTW, yes, I do have all of my data. Backfilling it into my new setup will no doubt be an ongoing adventure.] Anyway, just a few notes about the rsync situation: 1) Having or not having a trailing / on the destination directory did not seem to make any difference in the size of the copy made, or otherwise. Nevertheless, I intend to heed the advice given to have a trailing / after both source and destination, or neither, as appropriate. 2) Using or not using an "S" option with rsync did not seem to make any difference, at least concerning the size of the copy made. 3) Yes, I really should check into using checksums to avoid "bot rot". Good advice. Finally, Gnome sucks. (Did I mention that?) Thanks for the replies. Congratulations! You now have more experience: "Doing things right is a matter of experience. Experience is a matter of doing things wrong." As you find system administration commands that work, put them into scripts: #!/bin/sh sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 /media/default/MSD1/ /media/default/MSD2/ Use a version control system for system administration. Create a project for every machine. Check in system configuration files, scripts, partition table backups, encryption header backups, RAID header backups, etc.. Maintain a plain text log file with notes of what you did (e.g. console sessions), when, and why. Put your OS on a small, fast device (e.g. SSD) and put your data on an array of large devices (e.g. ZFS pool with one or more HDD mirrors). Backup both as before. Additionally, take images of your OS device. David
Comment réserver à un seul fichier des logs en provenance d'une application donnée
Bonjour, Je teste l'application natlog sur Bullseye. Comme son nom l'indique, elle loggue le détail de connexions NATées avec des lignes comme: NATLOG: from 1338990672:55588 thru 1338990747:807100 (UTC): tcp 192.168.19.72:4467 (via: 129.125.90.132:4467) to to 200.49.219.180:443; sent: 802, received: 7669 Ces lignes se distinguent des autres par le préfixe NATLOG: en début de ligne. Mon soucis premier, pour des raisons de: 1. maîtrise de l'espace disque 2. de confidentialité 3. d'appliquer une politique de rétention spécifique (1 an pour les données de natlog, 7 jours pour le reste) est dans dans un premier d'éviter que ces lignes soient répétées dans les différents journaux de log, qu'ils soient binaires ou textuels. En particulier, par défaut, la commande journalctl m'affiche ces lignes NATLOG. J'imagine qu'elles sont donc présentes dans les fichiers du répertoire /var/log/journal. D'autre part, j'observe la présence de ces lignes dans les fichiers daemon.log et syslog. J'imagine deux voies: A. Paramétrer rsyslog pour dupliquer une fois de plus ces données en les consignant dans un fichier à part, et appliquer une rétention spécifique sur ce fichier (avec logrotate) B. Paramétrer les outils de log (journal ? rsyslogd ?) pour qu'ils ignorent ces lignes dans leurs propres journaux (est-ce simplement possible ?) tout en les mettant à disposition des autres daemons de log en aval. Que conseillez-vous ? Slts
Re: backing up backups
On Wed, Apr 13, 2022 at 12:09 PM Default User wrote: > > > On Mon, Apr 11, 2022 at 12:03 PM David Christensen < > dpchr...@holgerdanske.com> wrote: > >> On 4/10/22 22:15, to...@tuxteam.de wrote: >> > On Sun, Apr 10, 2022 at 09:44:59PM -0700, David Christensen wrote: >> >> On 4/10/22 19:58, Default User wrote: >> >>> Hello! >> >>> >> >>> My setup: >> >>> - single home x86-64 computer running Debian 11 Stable, up to date. >> >>> - one 4-Tb external usb hard drive to use as a backup device, labeled >> MSD1. >> >>> - another identical usb hard drive, labeled MSD2, to use as a copy of >> the >> >>> backups on MSD1. >> >>> - the computer and all storage devices are formatted ext4, not >> encrypted. >> >>> - two old Clonezilla disk images from when I installed Debian 11 last >> year >> >>> (probably irrelevant). >> >>> - Timeshift to daily back up system EXCEPT for data directories. >> >>> - Back in Time to daily back up data directories. >> >>> - Borgbackup to also daily back up data directories. >> >>> - Rsync to frequently backup any changed data between the daily Back >> in >> >>> Time and Borgbackup backups of data directories, using this command: >> >>> >> >>> sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 >> --exclude-from >> >>> "/home/default/rsync_exclude_list.txt" /home >> >>> /media/default/MSD1/rsync_backups_of_host_home_directory_only >> >>> >> >>> Each type of backup is in a separate subdirectory on MSD1 (Timeshift, >> Back >> >>> in TIme, Rsync, etc.). >> >>> >> >>> It "seems" to work okay, BUT . . . >> >>> >> >>> Then I try to use rsync to make an identical copy of backup device >> MSD1 on >> >>> an absolutely identical 4-Tb external usb hard drive, >> >>> labeled MSD2, using this command: >> >>> >> >>> sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 >> >>> /media/default/MSD1/ /media/default/MSD2 >> >> >> >> >> >> See 'man 1 rsync'. You have a slash at the end of SRC, but not at the >> end >> >> of DEST. I would add a slash after "MSD2": >> > >> > The only thing I find in rsync's man page about trailing slashes >> > in the `dest' argument would be relevant if MSD2 didn't exist (in >> > the OP's case it seems it does, no?) >> >> >> There are four combinations for rsync(1) SRC and DEST vs. trailing >> slashes. I use two -- trailing slashes on SRC and DEST for directories, >> and no trailing slashes on SRC and DEST for single files. The other two >> combinations may "work" under certain circumstances, but they have >> caused me grief in the past and I avoid them as a matter of habit. >> >> >> David >> >> > > Hey guys, sorry for just getting back with you now. > Unfortunately, I am just now recovering from a self-inflicted computer > disaster. > > While fighting with rsync, I did either: > > sudo rsync -aAXHSxvv --delete --info=progress2,stats2,name2 > /media/default/MSD1/ /media/default/MSD2 > or > sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2 > /media/default/MSD1/ /media/default/MSD2/ > > Just one small problem: MSD2 was not connected to my computer! > (Don't say it . . . ) > > Instead of giving an error message, rsync just created a directory on my > computer called /media/defaultMSD2, and filled it up until my / partition > was full, and THEN my desktop environment (Cinnamon) popped up a > notification saying so. How thoughtful. > > The computer then would not reboot into the operating system. > > No problem, I say. I will just use Timeshift to restore from its backup of > a few hours earlier. > > But that did not work, even after deleting the extra directory, and trying > restores from multiple Timeshift backups. > > Anyway, I never could fix the problem. But I did take it as an opportunity > to "start over". I put in a new(er) SSD, and did a fresh install, replacing > Cinnamon with Gnome. Mistake - now I remember why I dislike Gnome, ever > since Gnome 3. Wish I had re-installed Cinnamon, but too late now, out of > time. For now I will just have to grit my teeth and live with it. > > [BTW, yes, I do have all of my data. Backfilling it into my new setup will > no doubt be an ongoing adventure.] > > Anyway, just a few notes about the rsync situation: > > 1) Having or not having a trailing / on the destination directory did not > seem to make any difference in the size of the copy made, or otherwise. > Nevertheless, I intend to heed the advice given to have a trailing / after > both source and destination, or neither, as appropriate. > > 2) Using or not using an "S" option with rsync did not seem to make any > difference, at least concerning the size of the copy made. > > 3) Yes, I really should check into using checksums to avoid "bot rot". > Good advice. > > Finally, Gnome sucks. (Did I mention that?) > > Thanks for the replies. > > Uh oh . . . I just realized, this was supposed to have been sent to debian-user@lists.debian,org - NOT directly to Daivd Christensen. Sorry for the mistake. (Gmail also sucks. At least as far as composing and
Re: Impossible de joindre un ancien serveur
On Wednesday 13 April 2022 11:41:18 Migrec wrote: > "... impossible de contacter le serveur depuis les clients ..." Le serveur a dû prendre sa retraite :-) Tu contactes le serveur comment ? Peux tu te logguer à ton serveur en mode SSH ? Merci. A. Valmer
Re: Impossible de joindre un ancien serveur
On Wednesday 13 April 2022 11:41:18 Migrec wrote: > Jusqu'à présent, tout mon réseau domestique passait par un petit serveur > sous Debian > (NFS, DNS, DHCP, surveillance, CUPS, etc.). Malheureusement, je n'ai plus le > temps > de m'en occuper. Les box ayant considérablement évoluées et prenant un bonne > partie des fonctions, je souhaite me passer du serveur. > Tout mon réseau est fonctionnel et accède directement au net via la box > (freebox) qui fait DHCP. > Par contre, je voulais juste faire de mon serveur un client comme les autres > et depuis impossible > de contacter le serveur depuis les clients. Le serveur peut contacter les > clients sans pb. > Je soupçonne des règles iptables qui sont restées mais impossible de > retrouver comment les > enlever. > Des idée pour faire passer mon serveur à un simple client ? > "impossible de contacter le serveur depuis les clients..." Tu contactes le serveur comment ? Peux tu te logguer à ton serveur en mode SSH ? Merci. A. Valmer
[RESOLU] Re: Wireshark ne décode pas certains AVP Radius, pourtant présents dans ses dictionnaires
Le lun. 11 avr. 2022 à 15:13, Roberto C. Sánchez a écrit : > > On Mon, Apr 11, 2022 at 08:29:45AM +0200, Olivier wrote: > > @Roberto: > > Je souhaiterai que Wireshark décode les attributs 186, 187 ou 188 au > > lieu d'afficher Unknown-Attribute. > > > > J'avais imaginé qu'une erreur de config ou un choix d'option de > > compilation empêchait wireshark d'utiliser le dictionnaire > > /usr/share/wireshark/radius/dictionnaru.rfc7268 contenant la > > définition de ces attributs. > > > > Sur mon PC (Buster, avec wireshark 2.6.20-0+deb10u3), il y a le suivant > aux premières lignes du fichier /usr/share/wireshark/radius/dictionary: > > # 2014-11-03 Comment out > # dictionary.rfc7155 > # dictionary.rfc7268 > > Ensuite plus bas (ligne 125): > > #$INCLUDE dictionary.rfc7268 > > Peut-être que décommenter cette ligne pourrait donner le résultat > souhaité. > > Salut, > > -Roberto > > -- > Roberto C. Sánchez > En effet, dé-commenter la ligne "#$INCLUDE dictionary.rfc7268": - provoque une erreur sur les lignes 26 et 37 du fichier dictionnary.rfc7268 - mais permet en échange une lecture correcte des paramètres AVP 186, 187 etc. Une première solution serait sans doute de corriger ce fichier dictionary.rfc7268 (et le rfc7155 qui doit lui aussi avoir une erreur). Merci à tous ! Merci infiniment à tous pour vos réponses
Re: Impossible de joindre un ancien serveur
On Wednesday 13 April 2022 11:41:18 Migrec wrote: > Jusqu'à présent, tout mon réseau domestique passait par un petit serveur > sous Debian > (NFS, DNS, DHCP, surveillance, CUPS, etc.). Malheureusement, je n'ai plus le > temps > de m'en occuper. Les box ayant considérablement évoluées et prenant un bonne > partie des fonctions, je souhaite me passer du serveur. > Tout mon réseau est fonctionnel et accède directement au net via la box > (freebox) qui fait DHCP. > Par contre, je voulais juste faire de mon serveur un client comme les autres > et depuis impossible > de contacter le serveur depuis les clients. Le serveur peut contacter les > clients sans pb. > Je soupçonne des règles iptables qui sont restées mais impossible de > retrouver comment les > enlever. > Des idée pour faire passer mon serveur à un simple client ? > impossible de contacter le serveur depuis les clients... Tu contactes le serveur comment ? Peux tu te logguer à ton serveur en mode SSH ? Merci. A. Valmer
Re: SOS... Modo gráfico deshabilitado.
... A quién me enseñó este comando update-rc.d gdm3 disable, hace ya muchos años :D He encontrado algo, bueno, trato de recordar lo que hice :) Bruno Tendler me había sugerido, update-rc.d gdm3 -f enable entonces lo que hice fue, invoke-rc.d gdm3 force-reload enable el sistema me dio esto, invoke-rc.d gdm3 enable force-reload gdm.service is not active, cannot reload invoke-rc.d: initscript gdm3, action reload failed. pero me dejó ver esto, startx|reload|force-reload|status así que experiente un poco, invoke-rc.d gdm3 status me dijo que gdm3 no estaba activo, entonces hice esto, invoke-rc.d gdm3 start y con esto logro que levante X pero... ya lo deja fijo como si hiciera, sudo systemctl set-default graphic.target y si hago, startx: orden no encontrada. o gdm3 start se pasma, ja ja ja, pero valga que todavía que aún no he descativado ctrl+alt+del :) estamos más cerca, pero aún falta pues para volver a multi-user.target sin que haya que reiniciar. sudo systemctl set-default graphic.target sudo reboot 8-) -- Saludos, Luis
Re: Impossible de joindre un ancien serveur
On Wednesday 13 April 2022 11:41:18 Migrec wrote: > Jusqu'à présent, tout mon réseau domestique passait par un petit serveur > sous Debian > (NFS, DNS, DHCP, surveillance, CUPS, etc.). Malheureusement, je n'ai plus le > temps > de m'en occuper. Les box ayant considérablement évoluées et prenant un bonne > partie des fonctions, je souhaite me passer du serveur. > Tout mon réseau est fonctionnel et accède directement au net via la box > (freebox) qui fait DHCP. > Par contre, je voulais juste faire de mon serveur un client comme les autres > et depuis impossible > de contacter le serveur depuis les clients. Le serveur peut contacter les > clients sans pb. > Je soupçonne des règles iptables qui sont restées mais impossible de > retrouver comment les > enlever. > Des idée pour faire passer mon serveur à un simple client ? > impossible de contacter le serveur depuis les clients... Tu contactes le serveur comment ? Peux tu te logguer à ton serveur en mode SSH ?
Re: SOS... Modo gráfico deshabilitado.
... Dios permita :) > ¿Tampoco puedes cargar el entorno gráfico con «startx»? (si no te > funciona el comando con el usuario prueba a ejecutarlo desde root) startx: órden no encontrada :) Con root tampoco. ... Hacen los cambios bien pero no levanta gnome al iniciar. Obviamente, update-rc.d gdm3 disable, este es quien tiene la culpa, y no yo :D Si estás en lo cierto, reconfigurando el paquete se solventará... en caso contrario, ya sabes a quién culpar :-P A quién me enseñó este comando update-rc.d gdm3 disable, hace ya muchos años :D -- Saludos, Luis
Impossible de joindre un ancien serveur
Bonjour, Jusqu'à présent, tout mon réseau domestique passait par un petit serveur sous Debian (NFS, DNS, DHCP, surveillance, CUPS, etc.). Malheureusement, je n'ai plus le temps de m'en occuper. Les box ayant considérablement évoluées et prenant un bonne partie des fonctions, je souhaite me passer du serveur. Tout mon réseau est fonctionnel et accède directement au net via la box (freebox) qui fait DHCP. Par contre, je voulais juste faire de mon serveur un client comme les autres et depuis impossible de contacter le serveur depuis les clients. Le serveur peut contacter les clients sans pb. Je soupçonne des règles iptables qui sont restées mais impossible de retrouver comment les enlever. Des idée pour faire passer mon serveur à un simple client ? Merci pour toute aide !
Re: SOS... Modo gráfico deshabilitado.
El 2009-12-21 a las 23:11 -0500, luis escribió: Mando a la lista... > > > update-rc.d gdm3 disable > > > > ¿Qué te devuelve la orden «systemctl get-default»? > > Me devuelve que tengo el modo gráfico, pero no lo levanta automáticamente. ¿Has probado a reconfigurar el gestor de sesiones? sudo dpkg-reconfigure gdm3 > > ¿Tampoco puedes cargar el entorno gráfico con «startx»? (si no te > > funciona el comando con el usuario prueba a ejecutarlo desde root) > > startx: órden no encontrada :) > > Con root tampoco. Será que no tienes instalado xinit :-? > Al ejecutar estos, > > sudo systemctl set-default multi-user.target > sudo systemctl set-default > multi-user.target > sudo systemctl reboot > > sudo systemctl set-default graphical.target > sudo systemctl set-default > graphical.target > sudo systemctl reboot > > Hacen los cambios bien pero no levanta gnome al iniciar. Obviamente, > update-rc.d gdm3 disable, este es quien tiene la culpa, y no yo :D Si estás en lo cierto, reconfigurando el paquete se solventará... en caso contrario, ya sabes a quién culpar :-P Saludos, -- Camaleón
Re: SOS... Modo gráfico deshabilitado.
On Tue, 12 Apr 2022 23:26:28 -0400, Bruno Tendler wrote: Hola Luis. Estos son algunos comandos que se me ocurren que pueden llegar a activar el servicio gdm3 de nuevo. # update-rc.d gdm3 -f enable Por emplear update-rc.d gdm3 disable es que me ha pasado lo que me pasó :) No obstante probé este, update-rc.d gdm3 enable, pero nada. -- Saludos, Luis
Re: Help settings up sound card on Debian stable
Le 12/04/2022 à 03:48, manp...@gmail.com a écrit : Hi, I have been trying to set up a Minisforum HX90[1] with Debian stable with backports. Most of the stuff works out of the box except sound, bluetooth, and Wi-Fi. Hi, I have no idea of what you could do to make it work on stable, sorry. But did you try running testing? It would be probably simpler, and testing generally runs great. Regards, Yvan OpenPGP_signature Description: OpenPGP digital signature
Re: SOS... Modo gráfico deshabilitado.
El 2022-04-12 a las 22:52 -0400, luis escribió: > Estaba tratando de resolver el cambio de la interfaz gráfica a texto y use > un comando para versiones anteriores de debian, > > update-rc.d gdm3 disable > > Y ahora no logro levantar la interfaz gráfica. Hice lo siguiente, pero > nada... > > update-rc.d gdm3 enable > > No funciona '< Pues menos mal que te copié/pegué las instrucciones con las órdenes en otro correo >>>:-) > La forma correcta es: > > To change boot target to the text mode: > > sudo systemctl set-default multi-user.target > > Reboot the system using the reboot command: > > sudo systemctl reboot > > How to switch boot target to GUI (graphical UI). > > Find which target unit is used by default: > > systemctl get-default > > To change boot target to the GUI mode: > > sudo systemctl set-default graphical.target > > Make sure you reboot the Linux box using the reboot command: > > sudo rebootPero ya metí la pata, y necesito revertir esto, > > update-rc.d gdm3 disable ¿Qué te devuelve la orden «systemctl get-default»? ¿Tampoco puedes cargar el entorno gráfico con «startx»? (si no te funciona el comando con el usuario prueba a ejecutarlo desde root) Saludos, -- Camaleón
