Re: Cheap NAS
>> > It's also worth noting: on my setup with a spinning rust laptop drive >> > hooked via USB 3 to my RPi, the drive doesn't spin continuously >> > (apparently). So on occasional use, I wait a couple of seconds for the >> > drive to spin up before it can transfer at full speed. It's possible an >> > SSD would solve this, but I had the laptop drive around already. [...] > Or try the hdparm command to change spindown time or other power saving > parameters. I use this to deliberately spin down my NAS drive after 10 [...] >if NAS1=`findmnt -n -o SOURCE /nas1/main`; then /sbin/hdparm -S120 $NAS1; > fi Side note: - In my experience, whether `hdparm -S..` works on a USB drive depends on the USB<->SATA adapter in use. If it doesn't, `hdparm` will tell you, tho. - On my WD drives, the `-S` seems to be completely ignored and instead the spin down time is chosen by the drive based on the APM setting (i.e. `hdparm -B...`). I heard there's a `idle3-tools` thingy that may be able to provide finer control, but I never tried it. Stefan
Re: debian freezing
Pierre Frenkiel wrote: > Since I installed Debian11, it happens from time to time (generally when > I leave the system unattended), that everything freezes: > > keyboard and mouse. > > I found on several blogs some silly recommendations, involving typing > something. I say "silly" because in that case in I can't do anything: > > neither with the keyboard nor the mouse > > when I say "frozen" it means "frozen" (may-be "dead" would be a better > word, as the computer doesn't answer to ping) ... have you tested your memory? songbird
Re: Apt upgrade problem
On Sun, 16 Oct 2022 23:44:00 +0100 Mark Fletcher wrote: > "apt list --upgradable" shows a new version of the Amazon Workspaces > client, version 4.3.0.1766. It also shows that there is one more > version available. This may be a silly question, but have you checked with Amazon customer support? Assuming such beast exists. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
On 17 October 2022 18:46 Diederik de Haas, wrote: > On maandag 17 oktober 2022 16:19:44 CEST Paul van der Vlis wrote: >> > Het BIOS is van 2012/2014, en al heeft het UEFI in de naam (16Mb AMI >> > UEFI Legal BIOS with GUI support) zal dat wel de reden zijn dat mijn >> > huis-nas voorlopig niet wil booten. >> >> Ja, je hebt volgens mij UEFI en GPT nodig om te kunnen booten vanaf een >> grote disk. Het gaat niet om de partitie, maar om de disk. > > Ik weet het niet 100% zeker, maar volgens mij heb je alleen GPT nodig, maar > niet (per se) UEFI. > https://superuser.com/questions/1393198/what-is-the-maximum-size-of-hard-drive-used-mbr-partitioning Installatie helemaal opnieuw gedaan. Grub geinstalleerd op /dev/sda en /dev/sdb vol goede hoop: maar bij het opstarten error: disk lvmid/A2weNY-Or4m-o6O2-sBnb-XFf2-syPz-1E4yml/poWL7U-Ry2d-a67B-C6xJ-0MGN-MP kc-gwk3IV not found grub-rescue > Ik vermoed dat ik dit moederbordje te oud is. Hieronder nog veel te veel info over de partitie. Disk sda: 3.65 TiB, 4000787030016 bytes, 7814037168 sectors Disk identifier: 447BC77F-6A03-464E-BB27-335E9731189C StartEndSectors Size Type sda1 2048 4095 20481M BIOS boot sda2 4096 980991 976896 477M Linux filesystem sda3 98099248865273905536 1.9G Linux RAID sda4 4886528 7814035455 7809148928 3.7T Linux RAID Disk sdb: 3.65 TiB, 4000787030016 bytes, 7814037168 sectors Disk identifier: CA7F1DA3-B3D7-4369-AD94-599D9DC78130 StartEndSectors Size Type sdb1 2048 4095 20481M BIOS boot sdb2 4096 980991 976896 477M Linux filesystem sdb3 98099248865273905536 1.9G Linux RAID sdb4 4886528 7814035455 7809148928 3.7T Linux RAID == Boot Info Summary === => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 2048 of the same hard drive for core.img. core.img is at this location and looks for (lvmid/A2weNY-Or4m-o6O2-sBnb-XFf2-syPz-1E4yml/poWL7U-Ry2d-a67B-C6xJ-0MGN-MP kc-gwk3IV)/boot/grub. It also embeds following components: modules --- fshelp ext2 diskfilter lvm biosdisk --- => Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector 2048 of the same hard drive for core.img. core.img is at this location and looks for (lvmid/A2weNY-Or4m-o6O2-sBnb-XFf2-syPz-1E4yml/poWL7U-Ry2d-a67B-C6xJ-0MGN-MP kc-gwk3IV)/boot/grub. It also embeds following components: signature.asc Description: PGP signature
Re: debian freezing
hi, I wrote some days ago that runing e screensaver doesn't give any improvment, but now I see that I was wrong: since I lauch xscreensaver, I never got any freezing. thanks everybody for your cooperation. Best regards, Pierre Frenkiel On Mon, 17 Oct 2022, The Wanderer wrote: On 2022-10-17 at 07:05, Pierre Frenkiel wrote: Since I installed Debian11, it happens from time to time (generally when I leave the system unattended), that everything freezes: keyboard and mouse. Do the lights stay on (frozen), or do they go out? Meaning the NumLock / CapsLock / ScrollLock lights on the keyboard, and the laser underneath your mouse (assuming you don't have an old-style ball mouse, or a trackball, or similar). I found on several blogs some silly recommendations, involving typing something. I say "silly" because in that case in I can't do anything: neither with the keyboard nor the mouse At a guess, this "something" might involve the so-called magic SysRq key? when I say "frozen" it means "frozen" (may-be "dead" would be a better word, as the computer doesn't answer to ping) and the only thing I can do is reboot, being after that obliged to re-install. Wait, reinstall? This was sounding a bit like a state I've managed to get the system into at various times in the past, where everything's wedged hard (the lights remain but won't toggle, for example), and a hard power-cycle was necessary to get out of it - but I was always able to boot back up and run the system normally afterwards; no reinstall was required. What is it you observe which leads you to conclude that a reinstall is needed at this point? I tried running the screensaver,but the problem remained. Has anybody a solution? Not with that little information. The only things I can suggest would be to find ways of getting more information. Depending on how the system is configured, there might be copies of the logs from before the freeze left even after new logs are begun when you boot up again. Some of them (from X-related logs to the ones holding dmesg or similar) may be relevant, if you can find them. If the boot process does wind up blowing away those logs, you may still be able to get access to them by booting to a live-media environment and looking at the hard drive from there. Failing that, you may be able to get some information out by setting up a process to dump the contents of those logs to another location every so often in a loop, waiting for the problem to reproduce, and then checking that location after the next boot. However, if the problem happens abruptly enough and is a hard-enough freeze that there's no time for anything to get logged (never mind for anything to be copied from the logs to another location) before all processing effectively halts, none of those are likely to help you. -- 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
Re: Creating a Debian derivative (WAS Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image).
It seems complicated to understand what I can do and what I can't. So,my idea is to prepare everything and then I will give my github repo (maybe configured as a private repo) to a debian legal representative hoping that he/she will tell me precisely where the project needs to be changed. But I also think that before talking with them,I need that some experienced user tries to pass his nvidia gpu installing "my" distro,to be sure that it works. What do you think ? Il giorno lun 17 ott 2022 alle ore 19:55 Andrew M.A. Cater < amaca...@einval.com> ha scritto: > [Title of the mail changed to reflect a new subject and topic following > the suggestions in the FAQ and mailing list code of conduct.] > Forwarded to the list as I sent this only to Mario by mistake. > > On Mon, Oct 17, 2022 at 06:29:45PM +0200, Mario Marietto wrote: > > Hello to everyone. > > > > Hi Mario, > > > I'm building my debian derivative distro not for business purposes,but to > > be useful to someone. Maybe I will ask for some money as a donation,but > I'm > > not even sure. When I will have created the first stable version,I will > put > > it in my github with all the scripts that I have added inside the ISO > > image. > > Money isn't really the issue here. > > Don't forget about the need to comply with licences on distribution of > source and so on. Do track _exactly_ the changes you make from Debian - > it will help you enormously. > > > I've read the guidelines and I've asked for clarifications to the > > legal debian department. They seemed to be very open in relation with the > > Debian logo usage,because it is open source,contrary to that of Ubuntu / > > Canonical and so I've chosen Debian. > > See also the Debian trademark guidelines: https://www.debian.org/trademark > > > Since my goal is not to earn money,I > > put the emphasis on the name of "my" distro,but at the same time I kept > the > > word Debian inside. It does not seem that this behavior is against some > > rules. What do you think ? > > You do need to chat to the trademark folks - Debian is usually fairly open > but it is important to get it right. Debian holds trademarks in the US, EU > China and Japan as a minimum. https://www.debian.org/trademark#trademarks > > > I'm not using a complicated preseed file. I'm > > using more configuration files ad hoc for the goal that I want to achieve > > (to create a debian distro ready for passing thru every nvidia gpu which > > work out of the box + various tools for achieving that goal and some > > premade configurations to use different kind of virtualization tools). > > You need to be very careful indeed that you can distribute all the code you > need to do this: you may also need to talk to Nvidia to work out how to get > them to distribute firmware updates and so on to you. > > Likewise for the visualisation tools - many of these are proprietary and > you'll > need to be able to distribute these to your users and also be absolutely > clear > that distributing them together on the same media doesn't upset any of the > individual vendors. > > > I > > want to share the project with you,also. When I am satisfied,I will put > the > > first ISO on my github + all the config files added and I would like to > > know what you think about it. To be honest,the Debian representative that > > I'm talking with does not reply fast and he / she does not seem to ask a > > decent amount of details. > > I think you need to check really clearly what the references on the Debian > wiki give: I think you need to think carefully about how much you want to > commit to this. If it didn't involve debian-live AND non-free code, I'd > suggest that you talked closely to others about making this a Debian Pure > Blend. As it is, I don't think that's an option. > > There's a lot to do as well as you possibly can before you can pass the > results of your work to a single user, I'm afraid. Debian-legal folk will > respond but you may need to be absolutely clear in your own mind exactly > what you're doing and the extent to which your learning curve will > get steeper to produce the solution. You may also want to talk to folk who > > Ot you're doing and the extent to which your learning curve will > get steeper to produce the solution. You may also want to talk to folk who > are already building and distributing distributions based on Debian-live. > > Distrowatch.com may help - LWN's distribtion's page is now almost a year > out > of date - but both of these may provide pointers to others who've done this > before you. > > With every good wish, as ever, > > Andy Cater > > > > > > Il giorno lun 17 ott 2022 alle ore 13:47 Thomas Schmitt < > scdbac...@gmx.net> > > ha scritto: > > > > > Hi, > > > > > > David Wright wrote: > > > > they are no longer Debian logos. You > > > > should give names to your edited files that indicate what they are: > > > > /your/ images for /your/ derivative. Add them to the archive and > > > > change the symlinks there. > > > > > > I
Creating a Debian derivative (WAS Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image).
[Title of the mail changed to reflect a new subject and topic following the suggestions in the FAQ and mailing list code of conduct.] Forwarded to the list as I sent this only to Mario by mistake. On Mon, Oct 17, 2022 at 06:29:45PM +0200, Mario Marietto wrote: > Hello to everyone. > Hi Mario, > I'm building my debian derivative distro not for business purposes,but to > be useful to someone. Maybe I will ask for some money as a donation,but I'm > not even sure. When I will have created the first stable version,I will put > it in my github with all the scripts that I have added inside the ISO > image. Money isn't really the issue here. Don't forget about the need to comply with licences on distribution of source and so on. Do track _exactly_ the changes you make from Debian - it will help you enormously. > I've read the guidelines and I've asked for clarifications to the > legal debian department. They seemed to be very open in relation with the > Debian logo usage,because it is open source,contrary to that of Ubuntu / > Canonical and so I've chosen Debian. See also the Debian trademark guidelines: https://www.debian.org/trademark > Since my goal is not to earn money,I > put the emphasis on the name of "my" distro,but at the same time I kept the > word Debian inside. It does not seem that this behavior is against some > rules. What do you think ? You do need to chat to the trademark folks - Debian is usually fairly open but it is important to get it right. Debian holds trademarks in the US, EU China and Japan as a minimum. https://www.debian.org/trademark#trademarks > I'm not using a complicated preseed file. I'm > using more configuration files ad hoc for the goal that I want to achieve > (to create a debian distro ready for passing thru every nvidia gpu which > work out of the box + various tools for achieving that goal and some > premade configurations to use different kind of virtualization tools). You need to be very careful indeed that you can distribute all the code you need to do this: you may also need to talk to Nvidia to work out how to get them to distribute firmware updates and so on to you. Likewise for the visualisation tools - many of these are proprietary and you'll need to be able to distribute these to your users and also be absolutely clear that distributing them together on the same media doesn't upset any of the individual vendors. > I > want to share the project with you,also. When I am satisfied,I will put the > first ISO on my github + all the config files added and I would like to > know what you think about it. To be honest,the Debian representative that > I'm talking with does not reply fast and he / she does not seem to ask a > decent amount of details. I think you need to check really clearly what the references on the Debian wiki give: I think you need to think carefully about how much you want to commit to this. If it didn't involve debian-live AND non-free code, I'd suggest that you talked closely to others about making this a Debian Pure Blend. As it is, I don't think that's an option. There's a lot to do as well as you possibly can before you can pass the results of your work to a single user, I'm afraid. Debian-legal folk will respond but you may need to be absolutely clear in your own mind exactly what you're doing and the extent to which your learning curve will get steeper to produce the solution. You may also want to talk to folk who Ot you're doing and the extent to which your learning curve will get steeper to produce the solution. You may also want to talk to folk who are already building and distributing distributions based on Debian-live. Distrowatch.com may help - LWN's distribtion's page is now almost a year out of date - but both of these may provide pointers to others who've done this before you. With every good wish, as ever, Andy Cater > > Il giorno lun 17 ott 2022 alle ore 13:47 Thomas Schmitt > ha scritto: > > > Hi, > > > > David Wright wrote: > > > they are no longer Debian logos. You > > > should give names to your edited files that indicate what they are: > > > /your/ images for /your/ derivative. Add them to the archive and > > > change the symlinks there. > > > > I found > > https://wiki.debian.org/Derivatives/Guidelines > > which Mario Marietto should check. > > > > Naming of files is not mentioned, afaics. > > But there is much emphasis on not using "Debian" in the name of the > > "business". This demand applies to various software packages and artwork, > > too: > > https://wiki.debian.org/Derivatives/Guidelines#De-.2FRe-branding > > > > I wonder whether a preseeded Debian Live ISO constitutes a derived distro > > and Mario Marietto's preseeding project qualifies as "business". > > The changes of which i know use an official Debian mechanism to shorten > > or hardcode the installation process. The Live personality is completely > > unchanged, afaik. > > > > So for now the only non-Debian thing is the title > >
Re: vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
On maandag 17 oktober 2022 16:19:44 CEST Paul van der Vlis wrote: > > Het BIOS is van 2012/2014, en al heeft het UEFI in de naam (16Mb AMI > > UEFI Legal BIOS with GUI support) zal dat wel de reden zijn dat mijn > > huis-nas voorlopig niet wil booten. > > Ja, je hebt volgens mij UEFI en GPT nodig om te kunnen booten vanaf een > grote disk. Het gaat niet om de partitie, maar om de disk. Ik weet het niet 100% zeker, maar volgens mij heb je alleen GPT nodig, maar niet (per se) UEFI. https://superuser.com/questions/1393198/what-is-the-maximum-size-of-hard-drive-used-mbr-partitioning signature.asc Description: This is a digitally signed message part.
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Hello to everyone. I'm building my debian derivative distro not for business purposes,but to be useful to someone. Maybe I will ask for some money as a donation,but I'm not even sure. When I will have created the first stable version,I will put it in my github with all the scripts that I have added inside the ISO image. I've read the guidelines and I've asked for clarifications to the legal debian department. They seemed to be very open in relation with the Debian logo usage,because it is open source,contrary to that of Ubuntu / Canonical and so I've chosen Debian. Since my goal is not to earn money,I put the emphasis on the name of "my" distro,but at the same time I kept the word Debian inside. It does not seem that this behavior is against some rules. What do you think ? I'm not using a complicated preseed file. I'm using more configuration files ad hoc for the goal that I want to achieve (to create a debian distro ready for passing thru every nvidia gpu which work out of the box + various tools for achieving that goal and some premade configurations to use different kind of virtualization tools). I want to share the project with you,also. When I am satisfied,I will put the first ISO on my github + all the config files added and I would like to know what you think about it. To be honest,the Debian representative that I'm talking with does not reply fast and he / she does not seem to ask a decent amount of details. Il giorno lun 17 ott 2022 alle ore 13:47 Thomas Schmitt ha scritto: > Hi, > > David Wright wrote: > > they are no longer Debian logos. You > > should give names to your edited files that indicate what they are: > > /your/ images for /your/ derivative. Add them to the archive and > > change the symlinks there. > > I found > https://wiki.debian.org/Derivatives/Guidelines > which Mario Marietto should check. > > Naming of files is not mentioned, afaics. > But there is much emphasis on not using "Debian" in the name of the > "business". This demand applies to various software packages and artwork, > too: > https://wiki.debian.org/Derivatives/Guidelines#De-.2FRe-branding > > I wonder whether a preseeded Debian Live ISO constitutes a derived distro > and Mario Marietto's preseeding project qualifies as "business". > The changes of which i know use an official Debian mechanism to shorten > or hardcode the installation process. The Live personality is completely > unchanged, afaik. > > So for now the only non-Debian thing is the title > "BridgeVmOS Debian Custom" > in > https://ibb.co/GHHDQ3H > It looks like a project name and thus could be regarded as "business". > > I wonder whether a title like > "Debian , preseeded by BridgeVmOS" > would be ok. > > > Well, before following the Guideline advise > "Consult the DebianProjectLeader meanwhile on a case-by-case basis" > Mario Marietto should probably list the changes in his ISO towards the > original ISO. I know of: > - Introducing a preseed file. > - Changing logo files in the initrd. > - (Packing up the ISO with xorrisofs options which are equivalent to > those currently used by Debian Live, as far as boot capabilities are > concerned. But Debian could move to other layouts for booting.) > > Such a list could then be the base of decisions. > > > Have a nice day :) > > Thomas > > -- Mario.
Re: Apt upgrade problem
On Sun, 16 Oct 2022 23:44:00 +0100 Mark Fletcher wrote: > After "sudo apt update", the system informs me there is 1 package that can > be upgraded. > > "sudo apt upgrade" reports nothing to do, 0 packages upgraded, 0 newly > installed, 0 to remove and 0 not upgraded... One possible reason could be the new package conflict with some other installed package. "apt upgrade" doesn't remove packages. Maybe "apt full-upgrade" is at hand? Maybe also "apt policy workspacesclient" gives some help. Or maybe "apt install workspacesclient=4.3.0.1766" installs the current version? (sorry, just some ideas and no safe solution from me, as I'm not using amazons workspaceclient) regards hede
Re: Cheap NAS
On Mon, 2022-10-17 at 11:28 -0400, Wayne Sallee wrote: > > Original Message > *Subject: * Re: Cheap NAS > *From: * Paulf > *To: * Debian-user > *CC: * > *Date: * 2022-10-16 02:31 PM > > It's also worth noting: on my setup with a spinning rust laptop drive > > hooked via USB 3 to my RPi, the drive doesn't spin continuously > > (apparently). So on occasional use, I wait a couple of seconds for the > > drive to spin up before it can transfer at full speed. It's possible an > > SSD would solve this, but I had the laptop drive around already. > > > > A simple timed read/write script could take care of that. Or try the hdparm command to change spindown time or other power saving parameters. I use this to deliberately spin down my NAS drive after 10 minutes so it uses a lot less power and to get rid of the noise. I do this at boot in /etc/rc.local # cat /etc/rc.local #!/bin/sh # Set spindown time for disk if NAS1=`findmnt -n -o SOURCE /nas1/main`; then /sbin/hdparm -S120 $NAS1; fi Rather than hard code the disk as /dev/sdc I use 'findmnt' to get the disk name from the point it's mounted at (/nas1/main in this case). I also do this in my daily backup scripts in case the drive setting gets lost, as it seems to do some times. -- Tixy
Re: Strange syslog behaviour [Solved]
Original Message *Subject: * Re: Strange syslog behaviour [Solved] *From: * Tixy *To: * Debian-user *CC: * *Date: * 2022-10-16 12:40 PM On Sun, 2022-10-16 at 09:09 -0400, Wayne Sallee wrote: It would be nice if updates presented "old file", "new file", "combined file"; choice: (1), (2), (3). It does offer several choices, one of them is to show a 'diff' of the old and new files. Only you can know what changes you made and want to keep, and just automatically merging files is very likely just to produce a broken config. Personally, I do a diff first, which usually acts of a reminder of what I've changed, then I accept the new file and in another terminal edit that to reapply my changes. Yes, I did do the diff, but I was in the middle of the update. I like Charles Curley's idea of having another terminal to make the needed changes as they come up. Wayne Sallee wa...@waynesallee.com http://www.WayneSallee.com
Re: Strange syslog behaviour [Solved]
Original Message *Subject: * Re: Strange syslog behaviour [Solved] *From: * Charles Curley *To: * Debian Users *CC: * *Date: * 2022-10-16 11:09 AM When I do an upgrade I run the upgrade in one terminal, and have Emacs running in another. As these differences pop up, I accept one of the options, then edit away as necessary. It takes a while to do an upgrade, but I usually get what I want and don't have to go back and make more edits. That's a good idea to use 2 terminals like that. Wayne Sallee wa...@waynesallee.com http://www.WayneSallee.com
Re: Cheap NAS
Original Message *Subject: * Re: Cheap NAS *From: * Paulf *To: * Debian-user *CC: * *Date: * 2022-10-16 02:31 PM It's also worth noting: on my setup with a spinning rust laptop drive hooked via USB 3 to my RPi, the drive doesn't spin continuously (apparently). So on occasional use, I wait a couple of seconds for the drive to spin up before it can transfer at full speed. It's possible an SSD would solve this, but I had the laptop drive around already. A simple timed read/write script could take care of that. Wayne Sallee wa...@waynesallee.com http://www.WayneSallee.com
Re: debian freezing
On Mon 17 Oct 2022 at 13:05:14 (+0200), Pierre Frenkiel wrote: > Since I installed Debian11, it happens from time to time (generally > when I leave the system unattended), that everything freezes: > > keyboard and mouse. > > I found on several blogs some silly recommendations, involving typing > something. I say "silly" because in that case in I can't do anything: > > neither with the keyboard nor the mouse > > when I say "frozen" it means "frozen" (may-be "dead" would be a better > word, as the computer doesn't answer to ping) > > and the only thing I can do is reboot, being after that obliged to > re-install. > > I tried running the screensaver,but the problem remained. > > Has anybody a solution? Is this the same machine where the file /usr/bin/pulseaudio kept disappearing from the filesystem, and you had to keep reinstalling it (just pulseaudio, IIRC)? That doesn't give much confidence in the hardware. You wrote sometime ago, "on my laptop". Assuming that means you have more than one machine, which is this? You could generate and copy a file of diagnostic information to the other machine each minute (incorporating a timestamp in the filename). It might not help if everything falls over together. My only other advice would be to check out the sleep states in the CMOS, and errors in dmesg concerning the ACPI. There might be something that bullseye is capable of using, that buster didn't, and it just doesn't work correctly on this machine, and so it falls into an unwakeable slumber. Cheers, David.
Custom configuration Re: Mouse / Tablet
On Mon 17 Oct 2022 at 13:12:50 (+), Maude Summerside wrote:
>
> Does someone has some knowledge how to do some custom configuration for
> a specific mouse / tablet ?
>
> I have a tablet that gets recognized properly like a pointing device but
> I'd like to modify some parameter. Mostly rotate the X and Y axis.
My method is probably more simple-minded that Nicolas's.
It doesn't handle VCs (non-graphical logins) for which I have
manual scripts.
My ~/.xsession calls ~/bin/xinput-xsession which contains the
following fragments:
Printing="printf" Xinput="xinput" Unique="$(mktemp --suffix=.list "$(printf
'%s%(%s)T%s' "${Uniquetrash:-/tmp}/xinput-" -1 "-")")"
xinput > "$Unique"
[ "$1" != quiet ] && cat "$Unique" || Printing=":" Xinput=":"
… which lists all the devices and their parameters when run
without arguments.
Matrix="X 0 0 0 X 0 0 0 1"
Devicetype="pointer"
Device="Logitech M325" # purple wireless
Id="$(grep "$Device[[:space:]]*id.*$Devicetype" "$Unique" | sed
's/^[^=]\+=//;s/\t.*//;')"
[ -n "$Id" ] && "$Printing" '\nXID %2s %s ' "$Id" "$Devicetype" && "$Xinput"
--list-props "$Id" && xinput --set-prop "$Id" "Coordinate Transformation
Matrix" ${Matrix//X/.3} && xinput --set-prop "$Id" "libinput Middle Emulation
Enabled" 1
… this last paragraph is repeated for each different pointer device.
Note that some devices appear as both a pointer and a keyboard.
I would imagine that the Matrix can transform the axes in any way
required. I just use it to tame the wild sensitivities of most mice.
Devicetype="keyboard"
Device="AT Translated Set 2 keyboard" # IBM model M, PS/2 plug, GB layout
Id="$(grep "$Device[[:space:]]*id.*$Devicetype" "$Unique" | sed
's/^[^=]\+=//;s/\t.*//;')"
[ -n "$Id" ] && "$Printing" '\nXID %2s %s ' "$Id" "$Devicetype" && "$Xinput"
--list-props "$Id" && setxkbmap gb -device "$Id"
… again, repeated.
The reason it's in ~/bin/ is so that you can call it anytime to
examine the properties. More importantly, devices like mice can
lose the sensitivity settings when X blanks the screen, or
require setting when you plug in a new one. I have fvwm set up to
execute the script (quietly) with a Ctrl-Alt-Shift-/ keystroke.
Cheers,
David.
Re: Mouse / Tablet
On 2022-10-17 09:19, Andrew M.A. Cater wrote: > On Mon, Oct 17, 2022 at 01:12:50PM +, Maude Summerside wrote: >> Hi, >> >> Does someone has some knowledge how to do some custom configuration for >> a specific mouse / tablet ? >> >> I have a tablet that gets recognized properly like a pointing device but >> I'd like to modify some parameter. Mostly rotate the X and Y axis. >> >> Thanks >> -- >> Polyna-Maude R.-Summerside >> -Be smart, Be wise, Support opensource development >> > > Hi :) > > Which pointing device is it recognised as - which driver is loaded? You may find there's a way to pass > arguments to, say, a synaptics driver or whatever. > > More information would be helpful if you have it. > Here's a dump from xinput *** ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB OPTICAL MOUSE id=9[slave pointer (2)] ⎜ ↳ HID 6901:2701 Mouse id=11 [slave pointer (2)] ⎜ ↳ HID 6901:2701 Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ SZ PING-IT INC. [T503] Driver Inside Tablet Mouseid=17 [slave pointer (2)] ⎜ ↳ SZ PING-IT INC. [T503] Driver Inside Tablet Consumer Control id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ Dell Dell USB Keyboard id=8[slave keyboard (3)] ↳ HID 6901:2701id=10 [slave keyboard (3)] ↳ HID 6901:2701 System Control id=13 [slave keyboard (3)] ↳ HS HyperFIDO id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HID 6901:2701 Consumer Control id=16 [slave keyboard (3)] ↳ SZ PING-IT INC. [T503] Driver Inside Tablet Consumer Control id=19 [slave keyboard (3)] ↳ SZ PING-IT INC. [T503] Driver Inside Tablet Keyboardid=20 [slave keyboard (3)] ↳ SZ PING-IT INC. [T503] Driver Inside Tablet id=21 [slave keyboard (3)] *** The device we are talking about should be #17 (T503 Tablet) Here's the list of props *** Device 'SZ PING-IT INC. [T503] Driver Inside Tablet Mouse': Device Enabled (154): 1 Coordinate Transformation Matrix (156): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Natural Scrolling Enabled (288): 0 libinput Natural Scrolling Enabled Default (289): 0 libinput Scroll Methods Available (290):0, 0, 1 libinput Scroll Method Enabled (291): 0, 0, 0 libinput Scroll Method Enabled Default (292): 0, 0, 0 libinput Button Scrolling Button (293): 2 libinput Button Scrolling Button Default (294): 2 libinput Middle Emulation Enabled (295):0 libinput Middle Emulation Enabled Default (296):0 libinput Accel Speed (297): 0.00 libinput Accel Speed Default (298): 0.00 libinput Accel Profiles Available (299):1, 1 libinput Accel Profile Enabled (300): 1, 0 libinput Accel Profile Enabled Default (301): 1, 0 libinput Left Handed Enabled (302): 0 libinput Left Handed Enabled Default (303): 0 libinput Send Events Modes Available (273): 1, 0 libinput Send Events Mode Enabled (274):0, 0 libinput Send Events Mode Enabled Default (275):0, 0 Device Node (276): "/dev/input/event22" Device Product ID (277):2290, 26641 libinput Drag Lock Buttons (304): libinput Horizontal Scroll Enabled (305): 1 *** I don't really mind to loose some tablet specific features, if I can get the axis properly working. So the "pressure" level and such is not of importance. Thanks > With every good wish, as ever, > > Andy C. > -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development
Re: Mouse / Tablet
Maude Summerside (12022-10-17): > Does someone has some knowledge how to do some custom configuration for > a specific mouse / tablet ? > > I have a tablet that gets recognized properly like a pointing device but > I'd like to modify some parameter. Mostly rotate the X and Y axis. I think some of the answers you seek can be found there: https://lists.debian.org/debian-user/2020/02/msg00755.html Regards, -- Nicolas George
Re: vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
Hoi Gijs en anderen, Op 17-10-2022 om 09:17 schreef Gijs Hillenius: [...] knip En nu moet ik die herbouwen, met twee nieuwe en grotere schijven. Ik weet niet (meer) in welke stap ik de / /boot en swap partities definieer. Maak ik 1 raid partitie op beide schijven, en verdeel ik daarna met lvm+encryptie de schijf in 3 partities? Of moet ik elke harde schijf in 3 verdelen, en van elke 2 gelijke partities dan één raid1 partitie maken? Als je grotere schijven wilt kunnen gebruiken dan 2TB dan moet je UEFI gebruiken en dan heb je GPT en een "BIOS boot" partitie nodig. Vaak is die maar 1 MB groot. Ik zou hem maken op zowel sda1 als sdb1. Alleen die op sda1 zal worden gebruikt, maar ik zou later als de boel klaar is met dd de inhoud van sda1 kopieren naar sdb1, en op sdb ook grub installeren. Ah, Paul, dank voor die uitleg! Het BIOS is van 2012/2014, en al heeft het UEFI in de naam (16Mb AMI UEFI Legal BIOS with GUI support) zal dat wel de reden zijn dat mijn huis-nas voorlopig niet wil booten. Ja, je hebt volgens mij UEFI en GPT nodig om te kunnen booten vanaf een grote disk. Het gaat niet om de partitie, maar om de disk. Wellicht kan ik booten vanaf een USB-dingetje. Ja, dat kan wel. Of van SSD bijvoorbeeld. Maar je zult wel GPT nodig hebben op de grote disk. Gisteren prikte ik twee 4TB schijven in de kast. Met de Debian 11 installer heb ik daar 1 4TB raid1 device van gemaakt. Vervolgens liep ik helemaal vast in het instellen van de LVM/encrypted ; ergste was nog dat ik de indeling niet ongedaan kreeg. Ik zou de partitietabel verwijderen. Dat kan volgens mij ook met de Debian installer door op de partitietabel een return te geven en een nieuwe partitietabel te maken. Dan is alles in 1x weg. Mocht het niet lukken, dan zou ik parted gebruiken met de optie "mktable", en "destroy data: yes". Maar ... De automatische optie in het menu blijkbaar wel: Raid device #0 #1 1.0 MB K biosgrub #2 512.0 MB ext #3 4.0 TB Ah, het is al gelukt blijkbaar. (hey, waar is de swap?) Die zou ik in LVM zetten. Maar bij het installeren van grub ging dat alsnog mis, het wilde niet in /dev/sdax noch /dev/sdbx. Wat raar, misschien toch geen GPT? -- root@kvms12:~# fdisk /dev/sda Welcome to fdisk (util-linux 2.29.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sda: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 522C931D-2290-431A-9477-788C76FCEE3B DeviceStartEndSectors Size Type /dev/sda1 2048 4095 20481M BIOS boot /dev/sda2 4096 19535871 19531776 9,3G Linux RAID /dev/sda3 19535872 5860532223 5840996352 2,7T Linux RAID Let op die "disklabel type: gpt". En dat startpunt van de eerste partitie. Dus ik ben terug bij af. Wat doe ik eerst: De 4 TB schijven opdelen in 2 of meer raid devices? Je hebt iets nodig voor tenminste /boot . Of is het 1 4TB raid device, waaroverheen LVM/crypt zijn gang gaat? Dan moet /boot al ergens anders staan. Je moet kunnen booten. Dank voor het meedenken! Een alternatief is nog om het OS niet te encrypten, maar er bovenop een of meerdere virtuele machines te maken en die te encrypten. Er zijn ook nieuwere methoden waar ik geen ervaring mee heb, LVM kan ook RAID, en BTRFS kan ook RAID en wellicht ook encryptie. Groet, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://vandervlis.nl/
Re: debian freezing
On Mon, 17 Oct 2022 13:05:14 +0200 Pierre Frenkiel wrote: > Since I installed Debian11, it happens from time to time (generally > when I leave the system unattended), that everything freezes: > > keyboard and mouse. > > I found on several blogs some silly recommendations, involving typing > something. I say "silly" because in that case in I can't do anything: > > neither with the keyboard nor the mouse Ah, the good old 'Keyboard error: Press F1 to continue' trouble. > > when I say "frozen" it means "frozen" (may-be "dead" would be a > better word, as the computer doesn't answer to ping) > > and the only thing I can do is reboot, being after that obliged to > re-install. As others have said, it shouldn't be necessary. If your computer fails to reboot after the problem, there is the way to begin troubleshooting. I think you have to be fairly unlucky to get a file vital to operation damaged in a crash. > > I tried running the screensaver,but the problem remained. > > Has anybody a solution? > As the others have said, hardware is the most likely problem. Some component being more stressed than with previous versions, some new driver with a bug, some item being used it a way that it wasn't in the last version, etc. Having said that, my netbook occasionally doesn't wake up after suspend, in fact it never goes to sleep properly. The computer's status LED stays at 'run' on suspend, does not change to 'standby', and nothing ever works again. Only recoverable by use of the Big Red Switch, which these days is just a matter of holding down the power button. Boring. But this occurrence is rare enough that it's not easily investigated (whoever said 'Insanity is doing the same thing over and over and expecting different results' had never had to repair an intermittent fault. Nor rolled dice, either, despite also having said 'God does not play dice'). I doubt that you will find the logs useful. When this has happened to me, the logs just stopped at the crash, they never recorded anything useful just before. Sorry I can't be of more help, but this kind of thing is very rare these days, even with Windows, so there's not really a general solution, or even a likely way to troubleshoot. One long shot: it's worth opening up and clearing out any dust you find, Debian 11 might just be stressing the CPU a little more, enough to cause thermal trouble in something else due to increased heat. In that case, the CPU should detect the higher temperature and slow down, so it probably isn't that which is failing. If it's a desktop, it's worth reseating all the connectors, which is also worth doing with a laptop but is usually much more difficult. -- Joe
Re: Mouse / Tablet
On Mon, Oct 17, 2022 at 01:12:50PM +, Maude Summerside wrote: > Hi, > > Does someone has some knowledge how to do some custom configuration for > a specific mouse / tablet ? > > I have a tablet that gets recognized properly like a pointing device but > I'd like to modify some parameter. Mostly rotate the X and Y axis. > > Thanks > -- > Polyna-Maude R.-Summerside > -Be smart, Be wise, Support opensource development > Hi :) Which pointing device is it recognised as - which driver is loaded? You may find there's a way to pass arguments to, say, a synaptics driver or whatever. More information would be helpful if you have it. With every good wish, as ever, Andy C.
Mouse / Tablet
Hi, Does someone has some knowledge how to do some custom configuration for a specific mouse / tablet ? I have a tablet that gets recognized properly like a pointing device but I'd like to modify some parameter. Mostly rotate the X and Y axis. Thanks -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development
Re: debian freezing
Le 17/10/2022 à 13:05, Pierre Frenkiel a écrit : Since I installed Debian11, it happens from time to time (generally when I leave the system unattended), that everything freezes: keyboard and mouse. I found on several blogs some silly recommendations, involving typing something. I say "silly" because in that case in I can't do anything: neither with the keyboard nor the mouse when I say "frozen" it means "frozen" (may-be "dead" would be a better word, as the computer doesn't answer to ping) and the only thing I can do is reboot, being after that obliged to re-install. I tried running the screensaver,but the problem remained. Has anybody a solution? Thanks in advance Best regards Pierre Frenkiel Hello, the issue you describe is very often hardware specific, so giving as many information as possible will increase the possibility to "ring a bell" with someone on this list. The most common I have seen are bugs in some CPU sleep state, graphic driver that crash and put the graphic server in an irrecoverable state and lock up the GPU. Huge memory leak in a program can also lead to what you describe, if the kernel oom doesn't kick in or does but kills an essential part of the session. Did you try to look into your system logs at a time right before the freeze?
Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
Hi, David Wright wrote: > they are no longer Debian logos. You > should give names to your edited files that indicate what they are: > /your/ images for /your/ derivative. Add them to the archive and > change the symlinks there. I found https://wiki.debian.org/Derivatives/Guidelines which Mario Marietto should check. Naming of files is not mentioned, afaics. But there is much emphasis on not using "Debian" in the name of the "business". This demand applies to various software packages and artwork, too: https://wiki.debian.org/Derivatives/Guidelines#De-.2FRe-branding I wonder whether a preseeded Debian Live ISO constitutes a derived distro and Mario Marietto's preseeding project qualifies as "business". The changes of which i know use an official Debian mechanism to shorten or hardcode the installation process. The Live personality is completely unchanged, afaik. So for now the only non-Debian thing is the title "BridgeVmOS Debian Custom" in https://ibb.co/GHHDQ3H It looks like a project name and thus could be regarded as "business". I wonder whether a title like "Debian , preseeded by BridgeVmOS" would be ok. Well, before following the Guideline advise "Consult the DebianProjectLeader meanwhile on a case-by-case basis" Mario Marietto should probably list the changes in his ISO towards the original ISO. I know of: - Introducing a preseed file. - Changing logo files in the initrd. - (Packing up the ISO with xorrisofs options which are equivalent to those currently used by Debian Live, as far as boot capabilities are concerned. But Debian could move to other layouts for booting.) Such a list could then be the base of decisions. Have a nice day :) Thomas
Re: debian freezing
Am 17.10.2022 um 13:05 schrieb Pierre Frenkiel: > Since I installed Debian11, it happens from time to time (generally when > I leave the system unattended), that everything freezes: > > keyboard and mouse. > > I found on several blogs some silly recommendations, involving typing > something. I say "silly" because in that case in I can't do anything: > > neither with the keyboard nor the mouse > > when I say "frozen" it means "frozen" (may-be "dead" would be a better > word, as the computer doesn't answer to ping) > > and the only thing I can do is reboot, being after that obliged to > re-install. > > I tried running the screensaver,but the problem remained. > > Has anybody a solution? > > Thanks in advance > > Best regards > > Pierre Frenkiel > > Hello Pierre, your description might feel correct, from the user perspective. But it is lacking valuable information. I am not a guru (only second year at using debian), but i am surprised that you feel the urge to reinstall each time. That removes the traces of the previous problem, which can quite likely be found in the system logfiles. So i suggest, you explain a little, why you want to reinstall instead of just rebooting and logging in, when you would be able to inspect the system a little further. As i began with my new computer, i had similar problems. It was somewhat better after i installed from a DVD with nonfree firmware included. Only after several months, i discoverd a bad setting in computer setup (BIOS) that was configured by the vendor for the purpose of making Windows users happy, was causing MY problems. What may be your problem could be anything from hard- to software, but i suggest you have a look at /var/log/syslog and at dmesg while your computer is running fine. And let us know, what you found.
Re: debian freezing
On 2022-10-17 at 07:05, Pierre Frenkiel wrote: > Since I installed Debian11, it happens from time to time (generally > when I leave the system unattended), that everything freezes: > > keyboard and mouse. Do the lights stay on (frozen), or do they go out? Meaning the NumLock / CapsLock / ScrollLock lights on the keyboard, and the laser underneath your mouse (assuming you don't have an old-style ball mouse, or a trackball, or similar). > I found on several blogs some silly recommendations, involving typing > something. I say "silly" because in that case in I can't do > anything: > > neither with the keyboard nor the mouse At a guess, this "something" might involve the so-called magic SysRq key? > when I say "frozen" it means "frozen" (may-be "dead" would be a > better word, as the computer doesn't answer to ping) > > and the only thing I can do is reboot, being after that obliged to > re-install. Wait, reinstall? This was sounding a bit like a state I've managed to get the system into at various times in the past, where everything's wedged hard (the lights remain but won't toggle, for example), and a hard power-cycle was necessary to get out of it - but I was always able to boot back up and run the system normally afterwards; no reinstall was required. What is it you observe which leads you to conclude that a reinstall is needed at this point? > I tried running the screensaver,but the problem remained. > > Has anybody a solution? Not with that little information. The only things I can suggest would be to find ways of getting more information. Depending on how the system is configured, there might be copies of the logs from before the freeze left even after new logs are begun when you boot up again. Some of them (from X-related logs to the ones holding dmesg or similar) may be relevant, if you can find them. If the boot process does wind up blowing away those logs, you may still be able to get access to them by booting to a live-media environment and looking at the hard drive from there. Failing that, you may be able to get some information out by setting up a process to dump the contents of those logs to another location every so often in a loop, waiting for the problem to reproduce, and then checking that location after the next boot. However, if the problem happens abruptly enough and is a hard-enough freeze that there's no time for anything to get logged (never mind for anything to be copied from the logs to another location) before all processing effectively halts, none of those are likely to help you. -- 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: vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
Hoi Geert, en anderen, Op 16-10-2022 om 22:43 schreef Geert Stappers: On Sun, Oct 16, 2022 at 10:05:07PM +0200, Paul van der Vlis wrote: Op 16-10-2022 om 12:52 schreef Gijs Hillenius: Hallo Acht jaar geleden installeerde ik deze raid1: lsblk --fs NAME FSTYPELABEL MOUNTPOINT sdb ├─sdb1 linux_raid_member harde-schijf:0 │ └─md0ext4/boot ├─sdb2 linux_raid_member harde-schijf:2 │ └─md2 │ └─md2_crypt (dm-1) swap[SWAP] └─sdb3 linux_raid_member harde-schijf:1 └─md1crypto_LUKS └─md1_crypt (dm-0) ext4/ sda ├─sda1 linux_raid_member harde-schijf:0 │ └─md0ext4/boot ├─sda2 linux_raid_member harde-schijf:2 │ └─md2 │ └─md2_crypt (dm-1) swap[SWAP] └─sda3 linux_raid_member harde-schijf:1 └─md1crypto_LUKS └─md1_crypt (dm-0) ext4/ En nu moet ik die herbouwen, met twee nieuwe en grotere schijven. Ik weet niet (meer) in welke stap ik de / /boot en swap partities definieer. Maak ik 1 raid partitie op beide schijven, en verdeel ik daarna met lvm+encryptie de schijf in 3 partities? Of moet ik elke harde schijf in 3 verdelen, en van elke 2 gelijke partities dan één raid1 partitie maken? Als ... ... Ik zou hem maken ... zou ik dus ... naar ... ... En verder testen ... Ik zou tijd nemen om e-mail te beantwoorden. Dit zijn ingewikkelde dingen die ik ook niet dagelijks doe. En sindsdien heeft Debian ook niet stilgestaan. Ik denk dat Gijs er toch wel wat aan heeft. Groet, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://vandervlis.nl/
debian freezing
Since I installed Debian11, it happens from time to time (generally when I leave the system unattended), that everything freezes: keyboard and mouse. I found on several blogs some silly recommendations, involving typing something. I say "silly" because in that case in I can't do anything: neither with the keyboard nor the mouse when I say "frozen" it means "frozen" (may-be "dead" would be a better word, as the computer doesn't answer to ping) and the only thing I can do is reboot, being after that obliged to re-install. I tried running the screensaver,but the problem remained. Has anybody a solution? Thanks in advance Best regards Pierre Frenkiel
Re: vraag over raid1 - Debian 11 (her)installatie .. wanneer definieer ik swap en /boot en / (root)?
[...] knip >> En nu moet ik die herbouwen, met twee nieuwe en grotere schijven. >> Ik weet niet (meer) in welke stap ik de / /boot en swap partities >> definieer. >> Maak ik 1 raid partitie op beide schijven, en verdeel ik daarna met >> lvm+encryptie de schijf in 3 partities? >> Of moet ik elke harde schijf in 3 verdelen, en van elke 2 gelijke >> partities dan één raid1 partitie maken? > > Als je grotere schijven wilt kunnen gebruiken dan 2TB dan moet je UEFI > gebruiken en dan heb je GPT en een "BIOS boot" partitie nodig. Vaak is > die maar 1 MB groot. Ik zou hem maken op zowel sda1 als sdb1. Alleen > die op sda1 zal worden gebruikt, maar ik zou later als de boel klaar > is met dd de inhoud van sda1 kopieren naar sdb1, en op sdb ook grub > installeren. Ah, Paul, dank voor die uitleg! Het BIOS is van 2012/2014, en al heeft het UEFI in de naam (16Mb AMI UEFI Legal BIOS with GUI support) zal dat wel de reden zijn dat mijn huis-nas voorlopig niet wil booten. Wellicht kan ik booten vanaf een USB-dingetje. Gisteren prikte ik twee 4TB schijven in de kast. Met de Debian 11 installer heb ik daar 1 4TB raid1 device van gemaakt. Vervolgens liep ik helemaal vast in het instellen van de LVM/encrypted ; ergste was nog dat ik de indeling niet ongedaan kreeg. Maar ... De automatische optie in het menu blijkbaar wel: Raid device #0 #1 1.0 MB K biosgrub #2 512.0 MB ext #3 4.0 TB (hey, waar is de swap?) Maar bij het installeren van grub ging dat alsnog mis, het wilde niet in /dev/sdax noch /dev/sdbx. Dus ik ben terug bij af. Wat doe ik eerst: De 4 TB schijven opdelen in 2 of meer raid devices? Of is het 1 4TB raid device, waaroverheen LVM/crypt zijn gang gaat? Dank voor het meedenken!
Re: Ya hay decisión (era: [OT] Debian decide sobre su política de paquetes firmware «non-free»)
O 16/10/22 ás 16:25, Camaleón escribiu: 2. Sólo habrá un medio de instalación oficial de Debian, con paquetes libres y no libres mezclados, pero en teoría el usuario podrá desactivar la instalación de paquetes propietarios antes de iniciar el proceso de instalación (queda por ver cómo de efectivo resultará la pretensión y cómo lo expondrá el instalador sencillo dirigido a usuarios noveles). Me gustaría pensar que no sería difícil crear un instalador "semioficial" sin los paquetes privativos. Pero también es lo que dice Simon McVittie (https://lists.debian.org/debian-vote/2022/10/msg00013.html), alguien se tiene que encargar de eso. 3. El instalador informará de los paquetes propietarios que se van a instalar (en tiempo rela) y una vez instalado el sistema, se podrá consultar posteriormente alguna especie de archivo de registro o similar con los paquetes que se hayan instalado desde «non-free». También piensan sacar el firmware hacia una sección «non-free-firmware» nueva. Sigo manteniendo la idea de que se deberían aprovechar las categorías, y hacer que APT pueda filtrar la lista de paquetes según la configuración. Si al menos la opción predeterminada hubiera sido que el instalador no instalara paquetes propietarios SALVO que el usuario lo seleccionara a conciencia, ESPECÍFICAMENTE, pues hubiera sido una transición un poco más entendible. Como la opción estará en el GRUB, no veo mucho problema. Se puede discutir si descargar, pero no instalar, código no libre va en contra de la filosofía del software libre. A efectos prácticos, yo diría que no hay problema. Pero no, ahora de manera predeterminada si el kernel necesita algún binario propietario se instalará, salvo que el usuario diga EXPRESAMENTE que no. Juraría haber oído que algún firmware, como el de los dispositivos de audio, se va a incluir sí o sí, para los invidentes. En fin... qué se le va a hacer. Ceder a estar alturas no me complace lo más mínimo. :-( ¹https://www.debian.org/vote/2022/vote_003#outcome Saludos,
