On 18/04/2023 11:47, David Wright wrote:
On Mon 17 Apr 2023 at 15:26:58 (-0700), David Christensen wrote:
I have never seen a document that completely and accurately explains,
in computer engineering and science terms, the design and
implementation of the boot processes for Debian (or FreeBSD,
I've subscribed to a bug at 09:09:57 UTC and received a
"Please confirm subscription" message from bendel.debian.org
two minutes later. Fine.
I've subscribed to 3 more bugs at 10:01:05 UTC, but I haven't received
any "Please confirm subscription" messag
On Tuesday 18 April 2023 12:47:44 am David Wright wrote:
> > I have never seen a document that completely and accurately explains,
> > in computer engineering and science terms, the design and
> > implementation of the boot processes for Debian (or FreeBSD, or
> > Windows, or macOS) for all the pos
On 4/17/23 21:47, David Wright wrote:
On Mon 17 Apr 2023 at 15:26:58 (-0700), David Christensen wrote:
I have never seen a document that completely and accurately explains,
in computer engineering and science terms, the design and
implementation of the boot processes for Debian (or FreeBSD, or
On Mon 17 Apr 2023 at 15:26:58 (-0700), David Christensen wrote:
> On 4/17/23 07:41, David Wright wrote:
> > On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
> > > On 4/16/23 22:08, Max Nikulin wrote:
> > > > On 17/04/2023 09:18, David Christensen wrote:
> > > > > On 4/16/23 03:41,
update GRUB
> > > > > *** I tried a second time, same as above being super careful, same
> > > > > result.
> > > > >
> > > > > I then booted with my default system, ran grub-install /dev/sde &&
> > > > > update-
On 4/17/23 03:35, Max Nikulin wrote:
My point is that UEFI and MBR install may have different behavior. You
might underestimate role of implicit conventions and agreements.
I used to think that d-i would inform me and get my permission before
making changes to my computer.
It is unfortuna
On 4/17/23 07:41, David Wright wrote:
On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
On 4/16/23 22:08, Max Nikulin wrote:
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" S
e
list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Presumably we are now back to talking about Grub.
If you still have access to the bookworm system, you can check whether
it claimed to have completed installing Grub succe
On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
> On 4/16/23 22:08, Max Nikulin wrote:
> > On 17/04/2023 09:18, David Christensen wrote:
> > > On 4/16/23 03:41, Max Nikulin wrote:
> > > > On 16/04/2023 05:51, David Christensen wrote:
> > > > > When I moved the 2.5" SATA SSD to a ho
On 17/04/2023 15:27, David Christensen wrote:
On 4/16/23 22:08, Max Nikulin wrote:
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer
...
The SSD
On 4/16/23 22:08, Max Nikulin wrote:
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer
and configured BIOS Setup:
"Boot" -> "UEFI Boot" -> "E
On 17/04/2023 09:18, David Christensen wrote:
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer
and configured BIOS Setup:
"Boot" -> "UEFI Boot" -> "Enable"
The SSD would not boot.
New
On 4/16/23 03:41, Max Nikulin wrote:
On 16/04/2023 05:51, David Christensen wrote:
I installed a 2.5" SATA SSD, inserted a debian-11.6.0-amd64-netinst
CD, booted the CD, and installed Debian:
"Debian GNU/Linux UEFI Installer menu" -> "Install"
...
"Partitioning method" -> "Manua
led Grub on /dev/sde.
> > Which method did you use to boot the "default" system (which I assume
> > is bullseye, in a different partition on one or other of the disks),
> > in view of the rather sparse menu from grub.cfg on the new system?
> I boot with the &
grub.cfg on the new system?
I boot with the "old" GRUB menu as explained above...it has Several
operating systems listed, my old default OS is still at the top of the list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Pr
grub.cfg on the new system?
I boot with the "old" GRUB menu as explained above...it has Several
operating systems listed, my old default OS is still at the top of the list.
back to the WiFi dongle, again the obscure firmware was properly installed
Is this a Bug or a user/hardware issue?
Pr
not expect that shim is booted with no user
action when a disk is installed into another computer.
-rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
-rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
-rwxr-xr-x 1 root root 845480 Mar 16 22:19 mmx64.efi
-rwxr-xr-x 1 root root 93424
7My reason for suggesting changing debconf priority to low was that
perhaps additional questions might have uncovered some strangeness in the
installer. It was not intended to fix this bug but only as a means to
further analyze the bug. Apparently those on this list failed to
understand but
On Sat, Apr 15, 2023 at 07:09:58PM -0400, rhkra...@gmail.com wrote:
> On Sat, Apr 15, 2023 at 03:37:54PM -0400, Greg Wooledge wrote:
> > On Sat, Apr 15, 2023 at 07:20:58PM +0200, Geert Stappers wrote:
> > > [1] I needed a websearch on S.W.A.G. Did find
> > > - Sharing Warmth Around the Globe
> >
> it. This is a defect with d-i:
> >
> > 2023-04-15 15:10:34 root@taz ~
> > # ls -ld /mnt/nvme0n1p1/EFI/debian
> > drwxr-xr-x 2 root root 4096 Mar 16 22:19 /mnt/nvme0n1p1/EFI/debian
> >
> > 2023-04-15 15:10:36 root@taz ~
> > # ls -l /mnt/nvme0n1p1/EFI/debian
> > total 5892
> > -rwxr-xr-x 1 root root 108 Mar 16 22:19 BOOTX64.CSV
> > -rwxr-xr-x 1 root root 84648 Mar 16 22:19 fbx64.efi
> > -rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
> > -rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
> > -rwxr-xr-x 1 root root 845480 Mar 16 22:19 mmx64.efi
> > -rwxr-xr-x 1 root root 934240 Mar 16 22:19 shimx64.efi
> >
> >
> > So, I agree that d-i "Install" choice has bug(s) when installing
> > Debian into a computer with multiple storage devices.
>
> Cheers,
> David.
>
>
gt; 2023-04-15 15:10:34 root@taz ~
> # ls -ld /mnt/nvme0n1p1/EFI/debian
> drwxr-xr-x 2 root root 4096 Mar 16 22:19 /mnt/nvme0n1p1/EFI/debian
>
> 2023-04-15 15:10:36 root@taz ~
> # ls -l /mnt/nvme0n1p1/EFI/debian
> total 5892
> -rwxr-xr-x 1 root root 108 Mar 16 22:19 BOOTX64.CSV
> -rwxr-xr-x 1 root root 84648 Mar 16 22:19 fbx64.efi
> -rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
> -rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
> -rwxr-xr-x 1 root root 845480 Mar 16 22:19 mmx64.efi
> -rwxr-xr-x 1 root root 934240 Mar 16 22:19 shimx64.efi
>
>
> So, I agree that d-i "Install" choice has bug(s) when installing
> Debian into a computer with multiple storage devices.
Cheers,
David.
On Saturday, April 15, 2023 03:37:54 PM Greg Wooledge wrote:
> I think it's either "Stupid Wild-Ass Guess" or "Silly Wild-Ass Guess".
In my experience (and usage) it was "Scientific Wild Ass Guess".
--
rhk
| No entity has permission to use this email to train an AI.
:10:36 root@taz ~
# ls -l /mnt/nvme0n1p1/EFI/debian
total 5892
-rwxr-xr-x 1 root root 108 Mar 16 22:19 BOOTX64.CSV
-rwxr-xr-x 1 root root 84648 Mar 16 22:19 fbx64.efi
-rwxr-xr-x 1 root root 121 Mar 16 22:19 grub.cfg
-rwxr-xr-x 1 root root 4150720 Mar 16 22:19 grubx64.efi
-rwxr-xr-x 1 ro
On Sat, Apr 15, 2023 at 07:20:58PM +0200, Geert Stappers wrote:
> [1] I needed a websearch on S.W.A.G. Did find
> - Sharing Warmth Around the Globe
> - Sealed With A Gift
> - Stolen Without A Gun
> - So What? Another Giveaway?
> - Sub-Watershed Advisory Group
> - Some Women Are Great
> - Souvenir
On Sat, Apr 15, 2023 at 06:24:34PM +0100, Andrew Wood wrote:
> On 15/04/2023 18:20, Geert Stappers wrote:
> > On Sat, Apr 15, 2023 at 11:02:02AM -0400, Jude DaShiell wrote:
> > > On Sat, 15 Apr 2023, Geert Stappers wrote:
> > > > On Sat, Apr 15, 2023 at 10:36:14AM +0100, Andrew Wood wrote:
> > > >
You've never seen debian main menu in the installer. That's selection 19
on that main menu and selection 21 helps big time with debugging since you
choose that to save log files and selection 3 under that will save logs to
/var/log/installer directory. Two ways to get to main menu. First and
slo
On 15/04/2023 18:20, Geert Stappers wrote:
Time will tell if original poster shares information
on whether or not if priority for debian-install was changed.
Nothing was changed. I dont even know what that is. Ive installed Debian
on many systems over the past 12 years and have never alter
Default priority if memory serves is
> medium.
Time will tell if original poster shares information
on whether or not if priority for debian-install was changed.
> > Please make it possible to reproduce what is encountered.
> > Yeah, I would like to known what happened
> > and I
On 15/04/2023 14:12, Geert Stappers wrote:
Way before "grub install" should have been asked
On which disk to install
I do read "two devices were effected", I think it is the same error of
On which disk to install
If you mean did it install Debian on the NVme ssd then no, the
A s.w.a.g. here. Priority of questions asked was not set to low in the
main menu. I routinely change that to low when doing a debian install and
preserve logs for future reference. Default priority if memory serves is
medium.
-- Jude "There are four boxes to be used in
defense of liberty: soa
On Sat, Apr 15, 2023 at 10:36:14AM +0100, Andrew Wood wrote:
> Ive just used the Debian 11 installer ISO running from a USB stick to do an
> install (AMD64/UEFI) on another USB stick to use as a 'portable PC'.
>
> When it got to the Grub install stage I was expecting it to ask me which
> disk I wa
Ive just used the Debian 11 installer ISO running from a USB stick to do
an install (AMD64/UEFI) on another USB stick to use as a 'portable PC'.
When it got to the Grub install stage I was expecting it to ask me which
disk I wanted Grub installed on as it has in the past but instead it did
not
Apr 10 07:50:28 gar kernel: watchdog: BUG: soft lockup - CPU#15 stuck
for 26s! [kworker/15:2:1033]
Apr 10 07:50:28 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4
dns_resolver nfs lockd grace fscache netfs rfkill qrtr
n one or other of the disks),
in view of the rather sparse menu from grub.cfg on the new system?
> back to the WiFi dongle, again the obscure firmware was properly installed
>
> Is this a Bug or a user/hardware issue?
Presumably we are now back to talking about Grub.
If you still
Pankaj Jangid writes:
> I just discovered that there is no "input source" for Hindi (language)
> or Devanagari Script. Which package should I file the bug against?
>
> In Debian 11.6, the input source was present and switching with
> Super+Space was working just fine.
I just discovered that there is no "input source" for Hindi (language)
or Devanagari Script. Which package should I file the bug against?
In Debian 11.6, the input source was present and switching with
Super+Space was working just fine.
I have upgraded to "bookworm"
mware was properly installed
Is this a Bug or a user/hardware issue?
" are processor code names. For the Core
2 Duo E8400 this is "Wolfdale" according to ark.intel.com
Do I need to worry about those microcode bugs?
Your CPU us far older than the ones affected by the microcode bug. It
does not have a code name matching one of the listed ones. I
> I have no idea whether my old processor is a "CoffeeLake" or a "Skylake" or
> something else. It is a pc that I bought in 2008, I think (and still
> working just fine).
For those kinds of questions, I find Wikipedia to be the most helpful
source of info.
Stefan
Jesper Dybdal composed on 2023-03-19 19:00 (UTC+0100):
> /proc/cpuinfo says:
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 23
>> model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
> Do I need to worry about those microcode bugs?
IIRC, I have 3 E8400
On 2023-03-19 at 14:00, Jesper Dybdal wrote:
> I am planning to upgrade from Buster to Bullseye, and trying to prepare
> for any problems.
>
> The release notes say
>> The intel-microcode package currently in bullseye and buster-security
>> (see DSA-4934-1 (https:
>> //www.debian.org/security/2
our CPU us far older than the ones affected by the microcode bug. It does
not have a code name matching one of the listed ones. I'd conclude that your
CPU is not affected.
HTH
Linux-Fan
öö
pgpVU7E3j6RtC.pgp
Description: PGP signature
I am planning to upgrade from Buster to Bullseye, and trying to prepare
for any problems.
The release notes say
The intel-microcode package currently in bullseye and buster-security
(see DSA-4934-1 (https:
//www.debian.org/security/2021/dsa-4934)) is known to contain two
significant bugs. For
ation to
> skip the generation of the error. Do you confirm that you are following
> this approach ?
That's certainly what I would do. There are four workarounds listed at
https://bugs.launchpad.net/oem-priority/+bug/1842320/comments/125
three of which seem simple: MODULES=dep, COMPRESS=,
an
On Tue, 14 Mar 2023 Mario Marietto wrote:
No problem. But without offence,what you are suggesting to me is not to
make something to understand what's the real problem and why it's
happening,
I believe that the locution above --"make something to understand"--
paraphrases "diagnose".
but you a
On Tue, 14 Mar 2023 Mario Marietto wrote in reply to Andrew Cater:
--> *Which* Debian .iso did you install with ?
debian-live-11.5.0-amd64-xfce.iso.
Is there a way to upgrade this to the version that you have
suggested ? I prefer to learn how to upgrade it than to make a
fresh installation. I w
s correct ?
>
I am suggesting a re-install with a more current Debian version. 11.5 was
released in September last year, 11.6 in December last year. Each point
release brings fixes.
If you are installing from an old medium and one that I can no longer find,
I can't remember all of the bug fixe
No problem. But without offence,what you are suggesting to me is not to
make something to understand what's the real problem and why it's
happening,but you are suggesting to change something in my configuration to
skip the generation of the error. Do you confirm that you are following
this approach
Andrew M.A. Cater composed on 2023-03-14 22:02 (UTC):
> I would suggest that you try with the netinst for the main Debian installer.
> Other larger media are also available.
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.6.0+nonfree/amd64/
> has iso-cd and iso-d
On Tue, Mar 14, 2023 at 09:23:32PM +0100, Mario Marietto wrote:
> --> *Which* Debian .iso did you install with ?
>
> debian-live-11.5.0-amd64-xfce.iso. Is there a way to upgrade this to the
> version that you have suggested ? I prefer to learn how to upgrade it than
> to make a fresh installation
show three variants of the kernel - which one came from the original
> .iso
>
> All the very best, as ever,
>
> Andy Cater
> >
>
> >
> > On Mon, Mar 13, 2023 at 8:48 PM davidson wrote:
> >
> > > On Mon, 13 Mar 2023 Mario Marietto wrote:
> > > > He
's apology for posting the following question
> > off-topic in another thread]
> > >
> > > "I've just installed Debian 11
> > > and I see that it is affected by the bug
> > > explained here :
> > >
> > > https://bugs.launchpa
Mario Marietto's apology for posting the following question
> off-topic in another thread]
> >
> > "I've just installed Debian 11
> > and I see that it is affected by the bug
> > explained here :
> >
> > https://bugs.launchpad.net/oem-priori
On Mon, 13 Mar 2023 Mario Marietto wrote:
Hello to every Debian user.
[elided: Mario Marietto's apology for posting the following question
off-topic in another thread]
"I've just installed Debian 11
and I see that it is affected by the bug
explained here :
https://bugs.la
see that it is affected by the bug
explained here :
https://bugs.launchpad.net/oem-priority/+bug/1842320
I see that the bug has been fixed on Ubuntu. Do you confirm that,to fix
it,I just need to install the package
"grub-efi-amd64_2.06-2ubuntu14.1_amd64.deb" with the command &qu
On Thu, Mar 02, 2023 at 09:52:35AM +0800, Jeremy Ardley wrote:
> On 2/3/23 05:51, Greg Wooledge wrote:
> > unicorn:~$ namei -l ~/.ssh/config
> > f: /home/greg/.ssh/config
> > drwxr-xr-x root root /
> > drwxr-xr-x root root home
> > drwxr-xr-x greg greg greg
> > drwxr-xr-x greg greg .ssh
> > -rw-r--
On Wed, Mar 1, 2023 at 8:53 PM Jeremy Ardley wrote:
> [...]
> However I've found the cause of the problem, but not necessarily
> resolved the bug.
>
> For some reason on my journey /etc/ssh/ssh_config had acquired
>
> UserKnownHostsFile /etc/ssh/ssh_k
-- 1 jeremy jeremy 567 Dec 11 11:47 id_rsa.pub
However I've found the cause of the problem, but not necessarily
resolved the bug.
For some reason on my journey /etc/ssh/ssh_config had acquired
UserKnownHostsFile /etc/ssh/ssh_known_hosts
changing to
# UserKnownHostsFile /et
On 2/3/23 05:52, Jeffrey Walton wrote:
On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
I may have found a bug in openssh.
[...]
I have created a ~/.ssh/config file with contents
Host jeremy_client
HostName client.example.com
User jeremy
IdentityFile ~/.ssh
On Wed, Mar 01, 2023 at 04:52:57PM -0500, Jeffrey Walton wrote:
> On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
> >
> > I may have found a bug in openssh.
> > [...]
> > I have created a ~/.ssh/config file with contents
> >
> > Host jeremy_clie
On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
>
> I may have found a bug in openssh.
> [...]
> I have created a ~/.ssh/config file with contents
>
> Host jeremy_client
> HostName client.example.com
> User jeremy
> IdentityFile ~/.ssh/com.example.jer
On Wed, Mar 01, 2023 at 02:43:38PM -0700, Charles Curley wrote:
> On Thu, 2 Mar 2023 03:48:49 +0800
> jeremy ardley wrote:
>
> > 2. The known hosts file used is /etc/ssh/known_hosts rather that
> > ~/.ssh/known_hosts - which causes a permissions error
>
> I am not seeing that, for either root o
On Wed, Mar 1, 2023 at 2:49 PM jeremy ardley wrote:
>
> I may have found a bug in openssh.
>
> I raise it here as the ssh mailing list is actually a newsgroup that
> no-one seems to use.
You might give comp.security.openssh a try:
https://groups.google.com/g/comp.security.ss
On Thu, 2 Mar 2023 03:48:49 +0800
jeremy ardley wrote:
> 2. The known hosts file used is /etc/ssh/known_hosts rather that
> ~/.ssh/known_hosts - which causes a permissions error
I am not seeing that, for either root or my regular non-root user.
You indicated you created your ~/.ssh/config as s
I may have found a bug in openssh.
I raise it here as the ssh mailing list is actually a newsgroup that
no-one seems to use.
I can ssh jer...@client.example.com without the issue
I have created a ~/.ssh/config file with contents
Host jeremy_client
HostName client.example.com
User
On 27/02/2023 19:58, Jonathan Dowland wrote:
I see the maintainer has
uploaded a new version with a fix for your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't noticed the difference, and it
seems only the former
On 28/02/2023 09:00, John Crawley wrote:
On 27/02/2023 19:58, Jonathan Dowland wrote:
I see the maintainer has
uploaded a new version with a fix for your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't notice
On 27/02/2023 19:58, Jonathan Dowland wrote:
I see the maintainer has
uploaded a new version with a fix for your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't noticed the difference, and it
seems only the former
your issue (--execute), but
they have pointed out that the original bug was complaining about
something different (-c): I hadn't noticed the difference, and it
seems only the former is a policy violation in their eyes. I hope
the action properly addresses *your* issue.
(They didn't merge your MR a
hes, make any other necessary changes), and raise a
"Merge Request" on Salsa, pointing back at the Debian bug. Then the work
required to integrate the fix is as small as possible.
I've done this. [1]
Have you tried emailing the python packaging maintainers? They're listed
as
Hi,
[ honouring Reply-To as set ]
I might have missed many nuances in the situation but from what I've
read, here's what I observe.
On Thu, Feb 23, 2023 at 11:23:26AM +0900, John Crawley wrote:
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901245
This is the "righ
s.
There is an existing bug [3] with the title "Handling of -e violates policy for
x-terminal-emulator" - the issue was fixed upstream some time ago but the bug
remained open. The bug has now returned with the same result of breaking compliance with
Debian Policy.
I was unsure whether
I suspect you just need firmware-linux installed if it isn’t already.
That’s if that hardware requires the Radeon firmware.
On Mon, Feb 20, 2023 at 5:48 AM Felix Miata wrote:
> Omoikane Omake composed on 2023-02-19 21:50 (UTC+0300):
>
> > Excuse me for my broken English.
> > I don't know what ex
Omoikane Omake composed on 2023-02-19 21:50 (UTC+0300):
> Excuse me for my broken English.
> I don't know what exactly is cause of problem.
> Old notebook eMachines d620 with radeon x1200, rs960m.
> Driver works but no hardware acceleration.
> Because of that some programs do not work properly.
>
On 19/02/2023 18:50, Omoikane Omake wrote:
Hello.
Excuse me for my broken English.
I don't know what exactly is cause of problem.
Old notebook eMachines d620 with radeon x1200, rs960m.
Driver works but no hardware acceleration.
Because of that some programs do not work properly.
For example, geeq
Hello.
Excuse me for my broken English.
I don't know what exactly is cause of problem.
Old notebook eMachines d620 with radeon x1200, rs960m.
Driver works but no hardware acceleration.
Because of that some programs do not work properly.
For example, geeqie segfault, vlc crashed when opening file,
f
found a problem, or
> type
> 'other' to report a more general problem. If you don't know what package the
> bug is in, please contact debian-user@lists.debian.org for assistance.
> > other
> Please enter the name of the package in which you have found a problem,
x27;t know what package the
bug is in, please contact debian-user@lists.debian.org for assistance.
> other
Please enter the name of the package in which you have found a problem, or
choose one of these bug categories:
1 amprolla Everything related to amprolla
2 arm-sdk The ARM S
another excellent example why your posts are almost always worth reading.
thank you! :)
On Thu, Jan 19, 2023 at 02:00:00PM +0100, DdB wrote:
> Am 19.01.2023 um 13:13 schrieb Greg Wooledge:
> > The fact that this *appears* to work is what causes so much confusion.
> > It will "work" some of the time, but not all of the time, and you'll
> > get different results depending on which direc
On Thu, Jan 19, 2023 at 02:00:00PM +0100, DdB wrote:
[...]
> I was really curious, how Greg would put words to this one. And i gotta
> applaud: Such unambiguous explanations, and so circumspect at the same
> time. Even understanding the basis for confusion, i could learn
> something new from this
Am 19.01.2023 um 13:13 schrieb Greg Wooledge:
> The fact that this *appears* to work is what causes so much confusion.
> It will "work" some of the time, but not all of the time, and you'll
> get different results depending on which directory you're in, on which
> computer.
>
> Bash has two other
On Thu, Jan 19, 2023 at 07:13:46AM -0500, Greg Wooledge wrote:
[...]
> So, just to add to the list of people who've already said it: always
> quote the patterns that you pass to apt list, because you want apt
> to use them directly, without your shell interfering.
And, if in doubt, just replace
On Thu, Jan 19, 2023 at 12:11:43PM +0100, Christoph Brinkhaus wrote:
> For curiosity If have done a small test as below.
> Unfortunately there are a few outputs in German. For this comparisons
> the exact meanings of the German text has no importance at all.
>
> 1. The first command of the origina
llo together,
> > > listing packages in apt with ”sudo“ in the title returns different output
> > > (bash commands at the end of the email). I would fill a bug report, but
> > > I'm not sure whether to address it to grep or apt. How do you see this?
> > >
ash commands at the end of the email). I would fill a bug report, but I'm
> > not sure whether to address it to grep or apt. How do you see this?
> >
> > Kind regards
> > Julian Schreck
> > --
> > $ apt list sudo* vs. $ apt list | grep "^sudo[a-z-]
Am Thu, Jan 19, 2023 at 09:10:30AM +0100 schrieb js-p...@online.de:
Hello Julian,
> Hello together,
> listing packages in apt with ”sudo“ in the title returns different output
> (bash commands at the end of the email). I would fill a bug report, but I'm
> not sure whether to a
19.01.23, 09:10 +0100, js-p...@online.de:
Hello together,
listing packages in apt with ”sudo“ in the title returns different output (bash
commands at the end of the email). I would fill a bug report, but I'm not sure
whether to address it to grep or apt. How do you see this?
To me it
Am 19.01.2023 um 09:10 schrieb js-p...@online.de:
> Hello together,
> listing packages in apt with ”sudo“ in the title returns different output
> (bash commands at the end of the email). I would fill a bug report, but I'm
> not sure whether to address it to grep or apt. Ho
Hello together,
listing packages in apt with ”sudo“ in the title returns different output (bash
commands at the end of the email). I would fill a bug report, but I'm not sure
whether to address it to grep or apt. How do you see this?
Kind regards
Julian Schreck
--
$ apt list sudo* vs.
x but everybody is unsure when it will find it's way into
mainline.
Thank You again, David & have a nice day, Y'all,
Martin
On 2023-01-15 12:04, David wrote:
Hi list readers
A FYI: I am far from expert in these things but I noticed that a kernel
with a known bug affecting AMD graphic
Hi list readers
A FYI: I am far from expert in these things but I noticed that a kernel
with a known bug affecting AMD graphics is about to enter the unstable
distribution [1], and possibly the testing distribution as well.
[1]:"""
I would like to upload linux version 6.1.
Greg wrote:
>On Wed, Jan 11, 2023 at 10:42:31PM +, Tim Woodall wrote:
>> On Tue, 10 Jan 2023, songbird wrote:
>>
>> > kudoes to everyone who helped with this in getting it done, finding
>> > bugs, fixing problems, converting code, updating docs and testing. :)
>> >
>>
>> What does debian u
On Wed, Jan 11, 2023 at 10:42:31PM +, Tim Woodall wrote:
> On Tue, 10 Jan 2023, songbird wrote:
>
> > kudoes to everyone who helped with this in getting it done, finding
> > bugs, fixing problems, converting code, updating docs and testing. :)
> >
>
> What does debian use for moinmoin? Is
On Tue, 10 Jan 2023, songbird wrote:
kudoes to everyone who helped with this in getting it done, finding
bugs, fixing problems, converting code, updating docs and testing. :)
What does debian use for moinmoin? Is the debian wiki stuck on buster?
kudoes to everyone who helped with this in getting it done, finding
bugs, fixing problems, converting code, updating docs and testing. :)
songbird
Hi all, thanks for your time! Please let me know if this isn't the right
spot for this, or if I should file a bug.
I'm on debian buster, package versions for ones in question are:
systemd - 241-7~deb10u8
prometheus-node-exporter - 0.17.0+ds-3+b11
dbus - 1.12.20-0+deb10u1
pacemaker
rhkramer writes:
> Some examples from (simple) math include adding zero or multiplying by
> 1.
Those are respectively the additive and multiplicative identities. They
are, of course, idempotent but not good examples because they never
change the operand even on first application.
A better examp
On Mon, Sep 26, 2022 at 07:27:45PM -0400, The Wanderer wrote:
> My guess is: there's a collection of image files which (occasionally?)
> gets added to, he wants to clean up this data from the files in that
> collection that have it, and he doesn't want to have to keep track of
> which ones have and
301 - 400 of 5957 matches
Mail list logo
