Hi.
On Mon, Sep 11, 2023 at 09:28:15AM +0200, Thomas Schmitt wrote:
> how to get rid of voluminous desktop stuff without colateral damage ?
I'd start with:
apt purge libgtk-3-0 libqt*
Possibly followed by:
apt autoremove --purge
It's assumed that you read through the list of packages
On 9/11/23 09:28, Thomas Schmitt wrote:
Hi,
how to get rid of voluminous desktop stuff without colateral damage ?
Does somebody here have experience to share about de-GNOME-ing a
virtual Sid system ?
Reason why i ask:
A dist-upgrade of my virtual Sid lasted nearly 2 hours and used up 4.5 GiB
Hi,
how to get rid of voluminous desktop stuff without colateral damage ?
Does somebody here have experience to share about de-GNOME-ing a
virtual Sid system ?
Reason why i ask:
A dist-upgrade of my virtual Sid lasted nearly 2 hours and used up 4.5 GiB
of its virtual disk. (About half of this
El 16/8/23 a las 14:21, Guido Ignacio escribió:
Me mandaron un equipo para que deje solo MATE como desktop y veo que
tiene instalado gnome y todo lo que instala el tasksel.
Hay alguna forma de limpiar a gnome del sistema y las dependencias que
instala? Obvio sin afectar a MATE
Gracias
Me mandaron un equipo para que deje solo MATE como desktop y veo que tiene
instalado gnome y todo lo que instala el tasksel.
Hay alguna forma de limpiar a gnome del sistema y las dependencias que
instala? Obvio sin afectar a MATE
Gracias
Brad McDonald wrote:
> IS there any way to make multiple selections of a file,it's dependencies
> and dependant packages rather than one by one as that is very slow.For
> example 3 nights ago I installed all the "electrical" by first the named
> folder then the dependencies then the dependant
On 6/12/23 20:44, Brad McDonald wrote:
IS there any way to make multiple selections of a file,it's dependencies and dependant
packages rather than one by one as that is very slow.For example 3 nights ago I installed
all the "electrical" by first the named folder then the dependencies then the
IS there any way to make multiple selections of a file,it's dependencies
and dependant packages rather than one by one as that is very slow.For
example 3 nights ago I installed all the "electrical" by first the named
folder then the dependencies then the dependant packages.The following 2
nights I
Am Fri, Mar 03, 2023 at 10:09:42PM +0700 schrieb Max Nikulin:
> On 02/03/2023 22:27, Christoph Brinkhaus wrote:
> > Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin:
> > > On 28/02/2023 17:25, Christoph Brinkhaus wrote:
> > > > I will just inform about the status. Everything is fine
On 02/03/2023 22:27, Christoph Brinkhaus wrote:
Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin:
On 28/02/2023 17:25, Christoph Brinkhaus wrote:
I will just inform about the status. Everything is fine now. A word
about systemd-networkd-wait-online: With this service running there
Am Thu, Mar 02, 2023 at 09:26:33PM +0700 schrieb Max Nikulin:
> On 28/02/2023 17:25, Christoph Brinkhaus wrote:
> > I will just inform about the status. Everything is fine now. A word
> > about systemd-networkd-wait-online: With this service running there
> > has been even a delay of 1-2 seconds
On 28/02/2023 17:25, Christoph Brinkhaus wrote:
I will just inform about the status. Everything is fine now. A word
about systemd-networkd-wait-online: With this service running there
has been even a delay of 1-2 seconds when switching from one console
to a different one (the consoles when X is
Am Sun, Feb 26, 2023 at 01:21:07PM -0600 schrieb David Wright:
Hello David and Max,
> On Sun 26 Feb 2023 at 19:08:01 (+0100), Christoph Brinkhaus wrote:
> > Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin:
> > > On 25/02/2023 19:49, Christoph Brinkhaus wrote:
> > > > Now there are
Hi.
On Mon, Feb 27, 2023 at 10:53:24PM +0100, Geert Stappers wrote:
> (Meanwhile solved with denyinterface in /etc/dhcpcd.conf)
>
>
> > Long story short, consider running "systemctl mask dhcpcd" unless you
> > need dhcpcd to work in a way described above.
>
> The laptop does need to
Hi.
On Sun, Feb 26, 2023 at 05:25:09PM +0300, Reco wrote:
> On Sun, Feb 26, 2023 at 03:14:22PM +0100, Geert Stappers wrote:
> > On Sun, Feb 26, 2023 at 04:01:06PM +0300, Reco wrote:
> > > On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
} } } } } Have you tried `journalctl
On Sun 26 Feb 2023 at 19:08:01 (+0100), Christoph Brinkhaus wrote:
> Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin:
> > On 25/02/2023 19:49, Christoph Brinkhaus wrote:
> > > Now there are no messages reported by journald as above.
> >
> > I am curious if fixing unbound and so
Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin:
> On 25/02/2023 19:49, Christoph Brinkhaus wrote:
> > Now there are no messages reported by journald as above.
>
> I am curious if fixing unbound and so network-online.target helped to avoid
> 169.254.x.y address in your case. Can
On Sun 26 Feb 2023 at 22:11:30 (+0700), Max Nikulin wrote:
> On 26/02/2023 18:18, Geert Stappers wrote:
> > AIUI is systemd-networkd the main player, dhcpcd some helper
> > and NetworkManager for contact with user.
>
> First of all, I would not touch dhcpcd.conf for a while.
>
> Is it assumed
Am Sun, Feb 26, 2023 at 10:33:19PM +0700 schrieb Max Nikulin:
> On 25/02/2023 19:49, Christoph Brinkhaus wrote:
> > Now there are no messages reported by journald as above.
>
> I am curious if fixing unbound and so network-online.target helped to avoid
> 169.254.x.y address in your case.
I am
On 25/02/2023 19:49, Christoph Brinkhaus wrote:
Now there are no messages reported by journald as above.
I am curious if fixing unbound and so network-online.target helped to
avoid 169.254.x.y address in your case. Can fetchmail work without a
kludge you added to achieve some delay? My
On 26/02/2023 18:18, Geert Stappers wrote:
AIUI is systemd-networkd the main player, dhcpcd some helper
and NetworkManager for contact with user.
First of all, I would not touch dhcpcd.conf for a while.
Is it assumed that ovs-system should get its IP address from DHCP?
If I understand it
Hi.
On Sun, Feb 26, 2023 at 03:14:22PM +0100, Geert Stappers wrote:
> Hi.
>
> On Sun, Feb 26, 2023 at 04:01:06PM +0300, Reco wrote:
> > On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
> > > Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: carrier acquired
> > > Feb 24
Hi.
On Sun, Feb 26, 2023 at 04:01:06PM +0300, Reco wrote:
> On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
> > Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: carrier acquired
> > Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: IAID cb:93:09:25
> > Feb 24 22:24:15 trancilo
Hi.
On Sun, Feb 26, 2023 at 12:18:52PM +0100, Geert Stappers wrote:
> Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: carrier acquired
> Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: IAID cb:93:09:25
> Feb 24 22:24:15 trancilo dhcpcd[1175]: ovs-system: adding address
>
On Sat, Feb 25, 2023 at 09:42:49AM +0700, Max Nikulin wrote:
> On 25/02/2023 04:43, Geert Stappers wrote:
> > Having `apt purge avahi-autoipd` still gets me "auto IPv4 address"
> >
> > Ideas how to avoid it are welcome.
>
> Have you checked "journalctl --boot" for logs which component assigns
>
Am Fri, Feb 24, 2023 at 07:41:26PM +0100 schrieb Christoph Brinkhaus:
I reply to myself thanking Max.
> Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin:
> > On 22/02/2023 23:45, Christoph Brinkhaus wrote:
> > > Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin:
> > > > On
On Fri, Feb 24, 2023 at 9:51 PM David Wright wrote:
>
> On Fri 24 Feb 2023 at 22:43:49 (+0100), Geert Stappers wrote:
> > [...]
> I see you rebooted, and you get the same address. It's ambiguous as
> to why: it could have been stored, which makes things more efficient
> when a number of machines
really used
> > in the way they were intended, but just as more flexible desktops.
>
> Having `apt purge avahi-autoipd` still gets me "auto IPv4 address"
>
> Ideas how to avoid it are welcome.
>
>
>
> $ dpkg -l '*avahi*ip*'
> Desired=Unknown/
On 25/02/2023 04:43, Geert Stappers wrote:
Having `apt purge avahi-autoipd` still gets me "auto IPv4 address"
Ideas how to avoid it are welcome.
Have you checked "journalctl --boot" for logs which component assigns
169.254.x.y address and for various errors related to network?
I am not
ts, or the
> sysadmin has to choose it off their own bat. But I guess their are
> a lot of laptops, now they are affordable, that aren't really used
> in the way they were intended, but just as more flexible desktops.
Having `apt purge avahi-autoipd` still gets me "auto IPv4 address"
On Fri 24 Feb 2023 at 19:41:26 (+0100), Christoph Brinkhaus wrote:
> Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin:
> > On 22/02/2023 23:45, Christoph Brinkhaus wrote:
> > > Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin:
> > > > On 22/02/2023 01:26, Christoph
Am Fri, Feb 24, 2023 at 10:09:34PM +0700 schrieb Max Nikulin:
> On 22/02/2023 23:45, Christoph Brinkhaus wrote:
> > Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin:
> > > On 22/02/2023 01:26, Christoph Brinkhaus wrote:
> > > > [Unit]
> > > > Description=A remote mail retrieval and
On 22/02/2023 23:45, Christoph Brinkhaus wrote:
Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin:
On 22/02/2023 01:26, Christoph Brinkhaus wrote:
[Unit]
Description=A remote mail retrieval and forwarding utility
After=network-online.target opensmtpd.service unbound.service
On 22/02/2023 19:40, Greg Wooledge wrote:
On Wed, Feb 22, 2023 at 02:04:58PM -0500, Jeffrey Walton wrote:
Maybe the 'w' is not matching anything.
I thought eth0 and wlan0 went the way of the dinosaurs. I thought with
Consistent Network Device Names and biosdevname, the name will begin
with a
On Wed, Feb 22, 2023 at 02:04:58PM -0500, Jeffrey Walton wrote:
> Maybe the 'w' is not matching anything.
>
> I thought eth0 and wlan0 went the way of the dinosaurs. I thought with
> Consistent Network Device Names and biosdevname, the name will begin
> with a 'p' or 'em', not a 'w', and based
On Wed, Feb 22, 2023 at 1:43 PM David Wright wrote:
>
> On Tue 21 Feb 2023 at 13:48:58 (-0500), Jeffrey Walton wrote:
> > On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
> > wrote:
> > > [...]
> > > > But backing up... I suspect there's something wrong with your static
> > > > ip address
On Wed 22 Feb 2023 at 17:45:40 (+0100), Christoph Brinkhaus wrote:
> Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin:
> > On 22/02/2023 01:26, Christoph Brinkhaus wrote:
> > > > > I have no idea if it is possible to estimate a DHCP response
> > > > > time.
> >
> > Since static IP
On Tue 21 Feb 2023 at 13:48:58 (-0500), Jeffrey Walton wrote:
> On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
> wrote:
> > [...]
> > > But backing up... I suspect there's something wrong with your static
> > > ip address assignment. The address is already taken, the netmask is
> > > wrong,
Am Wed, Feb 22, 2023 at 10:24:59PM +0700 schrieb Max Nikulin:
> On 22/02/2023 01:26, Christoph Brinkhaus wrote:
> > > > I have no idea if it is possible to estimate a DHCP response
> > > > time.
>
> Since static IP address is assigned, it does not matter. I expected DHCP
> configuration and that
On 22/02/2023 01:26, Christoph Brinkhaus wrote:
I have no idea if it is possible to estimate a DHCP response
time.
Since static IP address is assigned, it does not matter. I expected DHCP
configuration and that delay may be noticed in `journalctl -b 0` logs.
[Unit]
Description=A remote
On Tue, Feb 21, 2023 at 01:48:58PM -0500, Jeffrey Walton wrote:
> On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
> wrote:
> > [...]
> > > But backing up... I suspect there's something wrong with your static
> > > ip address assignment. The address is already taken, the netmask is
> > >
On Tue, Feb 21, 2023 at 1:26 PM Christoph Brinkhaus
wrote:
> [...]
> > But backing up... I suspect there's something wrong with your static
> > ip address assignment. The address is already taken, the netmask is
> > wrong, or the gateway is wrong.
> >
> > Looking back through this thread, I did
Am Tue, Feb 21, 2023 at 01:06:01PM -0500 schrieb Jeffrey Walton:
> On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus
> wrote:
> > Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin:
> > > On 20/02/2023 21:44, Christoph Brinkhaus wrote:
> > > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700
Hi.
On Tue, Feb 21, 2023 at 06:44:38PM +0100, Christoph Brinkhaus wrote:
> I have no idea if it is possible to estimate a DHCP response time.
sudo nmap --script broadcast-dhcp-discover
Reco
On Tue, Feb 21, 2023 at 12:45 PM Christoph Brinkhaus
wrote:
> Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin:
> > On 20/02/2023 21:44, Christoph Brinkhaus wrote:
> > > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max > > > > Perhaps to
> > > get rid of 169.254.x.y addresses, it
Am Tue, Feb 21, 2023 at 11:00:56PM +0700 schrieb Max Nikulin:
> On 20/02/2023 21:44, Christoph Brinkhaus wrote:
> > Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin:
Hello Max,
> > > Perhaps to get rid of 169.254.x.y addresses, it is enough to properly
> > > configure network
On 20/02/2023 21:44, Christoph Brinkhaus wrote:
Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin:
Perhaps to get rid of 169.254.x.y addresses, it is enough to properly
configure network interface, either to ensure that DHCP server is available
or to assign a static address. After
ght see whether you have
any packages installed that match "ovs", "ovn", "openvswitch", or
similar, and if so either remove them (if you don't need them) or
investigate the configuration settings they may offer.
--
The Wanderer
The reasonable man adapts him
On Mon, Feb 20, 2023 at 9:28 AM wrote:
>[...]
> --
> rhk
>
> (sig revised 20221206)
>
> If you reply: snip, snip, and snip again; leave attributions; avoid HTML;
> avoid top posting; and keep it "on list". (Oxford comma (and semi-colon)
> included at no charge.) If you revise the topic, change
Am Mon, Feb 20, 2023 at 09:59:20AM +0700 schrieb Max Nikulin:
Hi Max,
> On 19/02/2023 23:35, Christoph Brinkhaus wrote:
> > Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
> > > Having installed package openvswitch-switch and doing `ip route` I do get
> > >169.254.0.0/16 dev
On Monday, February 20, 2023 04:05:19 AM to...@tuxteam.de wrote:
> On Mon, Feb 20, 2023 at 02:42:59AM -0500, Jeffrey Walton wrote:
> > On Mon, Feb 20, 2023 at 2:27 AM wrote:
> [...]
>
> > > That's what Microsoft calls them. I prefer the RFC's IP4LL.
> >
> > And Wireshark
On Mon, Feb 20, 2023 at 02:42:59AM -0500, Jeffrey Walton wrote:
> On Mon, Feb 20, 2023 at 2:27 AM wrote:
[...]
> > That's what Microsoft calls them. I prefer the RFC's IP4LL.
>
> And Wireshark (https://wiki.wireshark.org/APIPA.md) and Cisco
>
On Mon, Feb 20, 2023 at 2:27 AM wrote:
>
> On Mon, Feb 20, 2023 at 12:53:25AM -0500, Jeffrey Walton wrote:
> > On Sun, Feb 19, 2023 at 11:22 AM Geert Stappers
> > wrote:
> > >
> > > Having installed package openvswitch-switch and doing `ip route` I do get
> > >
> > > 169.254.0.0/16 dev
On Mon, Feb 20, 2023 at 12:53:25AM -0500, Jeffrey Walton wrote:
> On Sun, Feb 19, 2023 at 11:22 AM Geert Stappers wrote:
> >
> > Having installed package openvswitch-switch and doing `ip route` I do get
> >
> > 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
>
> Those
On Sun, Feb 19, 2023 at 11:22 AM Geert Stappers wrote:
>
> Having installed package openvswitch-switch and doing `ip route` I do get
>
> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
Those are called "APIPA's". Automatic Private IP Addressing (APIPA).
The host parts
On 20/02/2023 01:57, Geert Stappers wrote:
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovs-system: Failed
to update link state, ignoring: No such file or directory
feb 19 18:46:18 trancilo systemd-networkd-wait-online[601]: ovs-system: Failed
to update link state, ignoring: No
On Mon 20 Feb 2023 at 09:59:20 (+0700), Max Nikulin wrote:
> On 19/02/2023 23:35, Christoph Brinkhaus wrote:
> > Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
> > > Having installed package openvswitch-switch and doing `ip route` I do get
> > >169.254.0.0/16 dev ovs-system
On 19/02/2023 23:35, Christoph Brinkhaus wrote:
Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
Having installed package openvswitch-switch and doing `ip route` I do get
169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
Please have a look at
Am Sun, Feb 19, 2023 at 07:57:56PM +0100 schrieb Geert Stappers:
Hi Geert,
> On Sun, Feb 19, 2023 at 12:21:36PM -0500, Stefan Monnier wrote:
> > >> Having installed package openvswitch-switch and doing `ip route` I do get
> > >> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric
On Sun, Feb 19, 2023 at 12:21:36PM -0500, Stefan Monnier wrote:
> >> Having installed package openvswitch-switch and doing `ip route` I do get
> >> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
> >>
> >> What can be done to prevent that "zeroconf"
> >> configures
>> Having installed package openvswitch-switch and doing `ip route` I do get
>> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
>>
>> What can be done to prevent that "zeroconf"
>> configures interface `ovs-system`?
>
> Please have a look at https://wiki.debian.org/Avahi.
Am Sun, Feb 19, 2023 at 05:21:47PM +0100 schrieb Geert Stappers:
Hello Geert,
> Having installed package openvswitch-switch and doing `ip route` I do get
> 169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
>
> What can be done to prevent that "zeroconf"
> configures
Hi,
Having installed package openvswitch-switch and doing `ip route` I do get
169.254.0.0/16 dev ovs-system scope link src 169.254.201.7 metric 1004
What can be done to prevent that "zeroconf"
configures interface `ovs-system`?
Groeten
Geert Stappers
--
Silence is hard to parse
Georgi Naplatanov wrote:
...
> - install needed packages you uninstalled in previous step. In this
> step Debian will install packages from testing and you probably won't
> have problems.
>
> Good luck!
what i would do before anything else is create a new
partition with plenty of space and
On Thu, 24 Nov 2022 at 13:27, Amn wrote:
> What a mess I got myself into.
Hi, here is some more background explanation about this situation.
https://wiki.debian.org/DontBreakDebian
Thanks everyone.
What a mess I got myself into. However, I have decided to take Georgi
Naplatanov suggestion.
On 11/23/22 3:17 p.m., The Wanderer wrote:
On 2022-11-23 at 15:11, Amn wrote:
Hi folks, I thought it would be a good idea to install the sid
packages, but a lot of things are not
On 11/23/22 22:11, Amn wrote:
Hi folks, I thought it would be a good idea to install the sid packages,
but a lot of things are not working properly, so I would like to go back
to stable source packages only. How can I do that?
As other users said there is not reliable way to downgrade your
On Wed, 23 Nov 2022 15:11:10 -0500
Amn wrote:
> Hi folks, I thought it would be a good idea to install the sid
> packages, but a lot of things are not working properly, so I would
> like to go back to stable source packages only. How can I do that?
Back up and re-install Bullseye. Downgrading
On Wed, Nov 23, 2022 at 03:11:10PM -0500, Amn wrote:
> Hi folks, I thought it would be a good idea to install the sid packages, but
> a lot of things are not working properly, so I would like to go back to
> stable source packages only. How can I do that?
>
> Thanks!!
>
Hi Amn,
You can't,
On 2022-11-23 at 15:11, Amn wrote:
> Hi folks, I thought it would be a good idea to install the sid
> packages, but a lot of things are not working properly, so I would
> like to go back to stable source packages only. How can I do that?
I can think of two possible approaches, both of which come
Hi folks, I thought it would be a good idea to install the sid packages,
but a lot of things are not working properly, so I would like to go back
to stable source packages only. How can I do that?
Thanks!!
On 25/10/2022 15:50, jeremy ardley wrote:
My only problem now is the annoying NetworkManager icon in the Mate
panel. I want to remove it and I have gone through various advice pages
but nothing seems to work. The NetworkManager icon seems permanently
wedged into the panel.
Something like
is the annoying NetworkManager icon in the Mate
panel. I want to remove it and I have gone through various advice pages
but nothing seems to work. The NetworkManager icon seems permanently
wedged into the panel.
Is there any straight forward way to remove the NetworkManager icon?
Perhaps
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
ch ones have and have not already been cleaned up in this way.
>
> (Note: The rest is all speculative extrapolation from that starting
> point, and does not necessarily reflect what he actually thinks,
> *especially* if that starting point is not valid.)
>
> Thus, he wants to run
e had no exif
>>> tag in it. This turned out to be false. exif writes those words
>>> every time.
>>
>> IMO it shouldn't write anything if nothing happens and in
>> particular it shouldn't take time, which it does. Every time.
>
> I won't ask why you
On Mon 26 Sep 2022 at 21:31:55 (+0200), Emanuel Berg wrote:
> Greg Wooledge wrote:
>
> >> Look more, quote less ...
> >>
> >> for f in **/*.jpg; do exif --remove -o $f $f; done | grep
> > 'Wrote
> >> file' | wc -l # 2277 (1
debian-user wrote:
>> In programming the focus is perhaps better, for something
>> idempotent, something like: Do it the first time.
>> Don't screw it up the second time? And don't do the
>> computing if it doesn't need to be done?
>
> Sorry, but idempotence says nothing at all about
>
> In programming the focus is perhaps better, for something
> idempotent, something like: Do it the first time. Don't screw
> it up the second time? And don't do the computing if it
> doesn't need to be done?
Sorry, but idempotence says nothing at all about computational
efficiency or cost.
Greg Wooledge wrote:
>> Look more, quote less ...
>>
>> for f in **/*.jpg; do exif --remove -o $f $f; done | grep
> 'Wrote
>> file' | wc -l # 2277 (1st invocation)
>>
>> for f in **/*.jpg; do exif --remove -o $f $f; do
ell
> >>
> >> Look again!
> >
> > Look at it? I'll quote it in full (attached).
>
> Look more, quote less ...
>
> for f in **/*.jpg; do exif --remove -o $f $f; done | grep 'Wrote
> file' | wc -l # 2277 (1st invocation)
>
&
Curt wrote:
> One "programming" example given on that same Wikipedia page
> was that if you applied an update operation to Lutz
> Mueller's email address in a database (*ich habe
> Kopfschmerzen*!) that same update applied a second or third
> time (ad infinitum) would produce identical results.
ook more, quote less ...
for f in **/*.jpg; do exif --remove -o $f $f; done | grep 'Wrote
file' | wc -l # 2277 (1st invocation)
for f in **/*.jpg; do exif --remove -o $f $f; done | grep 'Wrote
file' | wc -l # 2277 (2nd invocation)
> Please—there's no ma
mick.crane wrote:
>> I have now clarified to the best of my ability the meaning
>> of that word and I think that will help people understand
>> at last why incorrect tech information, actually
>> disinformation at that point, can't be allowed in software
>> documentation. I get it now that this
.org (Postfix) with QMQP
id EF8442074B; Wed, 21 Sep 2022 07:02:38 + (UTC)
[ … ]
Mail-Followup-To: debian-user@lists.debian.org
To: debian-user@lists.debian.org
From: Emanuel Berg
Subject: exif --remove not idempotent, and a Debian man page bug
Date: Wed, 21 Sep 2022 09:02:09 +0200
Messag
On Sunday, September 25, 2022 08:42:57 AM The Wanderer wrote:
> On 2022-09-25 at 08:22, rhkra...@gmail.com wrote:
> > Oops, ignore that previous response ...
> >
> > On second thought, what hede wrote is correct, it is just stated in a
> > way that I wasn't famiiar with (and I haven't had my
On 2022-09-25, Emanuel Berg wrote:
> The Wanderer wrote:
>
>> If the nature of operation O is such that objects B and
>> C are guaranteed to always be identical, no matter what
>> object A was, then operation O is categorized as
>> being idempotent.
>
> It has to do with the number of times it is
On 2022-09-26 06:42, Emanuel Berg wrote:
<...>
I have now clarified to the best of my ability the meaning of
that word and I think that will help people understand at last
why incorrect tech information, actually disinformation at
that point, can't be allowed in software documentation. I get
it
David Wright wrote:
>> See the first post ...
>
> The OP didn't contain any exif output, only a couple of
> command lines, apparently written in zsh shell
Look again!
> The focus of the thread seems to have changed to the meaning
> of a word in the Subject, and an old email address that
> might
On Sun 25 Sep 2022 at 07:52:38 (+0200), Emanuel Berg wrote:
> Greg Wooledge wrote:
> > If I had the first inkling of a clue what an exif tag
> > actually *was* I might try testing it myself. I'm gathering
> > that it has something to do with JPEG images, based on the
> > *.modified.jpeg default
> rhkramer wrote:
>
> > An operation that produces the same results no matter how
> > many times it is performed.
>
> Yeah, obviously it is a term from math and in practical and
> applied engineering as is programming I thought of
> a definition (not really) like this
>
> - apply once, you
The Wanderer wrote:
> If the nature of operation O is such that objects B and
> C are guaranteed to always be identical, no matter what
> object A was, then operation O is categorized as
> being idempotent.
It has to do with the number of times it is applied,
abs(x) = abs(abs(x)) =
rhkramer wrote:
> An operation that produces the same results no matter how
> many times it is performed.
Yeah, obviously it is a term from math and in practical and
applied engineering as is programming I thought of
a definition (not really) like this
- apply once, you get the change
- apply
Am 25.09.2022 14:42, schrieb The Wanderer:
On 2022-09-25 at 08:22, rhkra...@gmail.com wrote:
On second thought, what hede wrote is correct, it is just stated in a
way that I wasn't famiiar with (and I haven't had my morning coffee
yet)
Are you sure?
Meanwhile, I do think my description was
On 2022-09-25 at 08:22, rhkra...@gmail.com wrote:
> Oops, ignore that previous response ...
>
> On second thought, what hede wrote is correct, it is just stated in a
> way that I wasn't famiiar with (and I haven't had my morning coffee
> yet)
Are you sure?
Because it doesn't seem to match my
day, September 24, 2022 09:17:31 AM hede wrote:
> > "Idempotent" means, that a task with the same input data and the same
> > config (for example to remove a tag via exif-tool) results in the same
> > output data. Is this the case here?
>
> That is not my understa
On Saturday, September 24, 2022 09:17:31 AM hede wrote:
> "Idempotent" means, that a task with the same input data and the same
> config (for example to remove a tag via exif-tool) results in the same
> output data. Is this the case here?
That is not my understanding
;> aspect, though.
>
> Ikr? Since it doesn't work! Just remove it.
It does work: it works to identify which of the people with the
referenced name is the one who is being referred to, because only one of
those people either has or formerly had that address.
As I said in
Greg Wooledge wrote:
>> The "-o" means: "Write output image to FILE". And it does
>> so, as far as I can see.
>
> The question is whether specifying "-o f f" where the output file
> has the same name as the input file actually overwrites the original
> input file. Another person reported that it
hede wrote:
> "Idempotent" means, that a task with the same input data and
> the same config (for example to remove a tag via exif-tool)
> results in the same output data.
Determinism.
--
underground experts united
https://dataswamp.org/~incal
1 - 100 of 3257 matches
Mail list logo
