Bulk renaming of "README.SuSE"

classic Classic list List threaded Threaded
31 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Bulk renaming of "README.SuSE"

Stefan Seyfried
Hi all,

Dominique is cleaning up packages and renaming "README.SuSE" files to
"README.SUSE".

While this is of course warrented in principle, there is one case to
consider.
If the README.SuSE is hugely outdated, then the wrong spelling at least
suggest that it is not new ;-)

My example is the ifplugd package.
I actually would not have expected anyone to still use this, but there
was a bugreport, so I recently added a trivial patch to increase a
netlink buffer size.

Looking at README.SuSE (which comes from the upstream tarball), I am not
even able to judge if this might actually work at all with todays
networking mess that's called wicked. So I'm not sure if it is a good
idea to suggest this file is relatively current by using the "new"
spelling, when it definitely is not.

Thanks for considering, and have a lot of fun... :-)
--
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:

> Hi all,
>
> Dominique is cleaning up packages and renaming "README.SuSE" files to
> "README.SUSE".
>
> While this is of course warrented in principle, there is one case to
> consider.
> If the README.SuSE is hugely outdated, then the wrong spelling at least
> suggest that it is not new ;-)
>
> My example is the ifplugd package.
> I actually would not have expected anyone to still use this, but there
> was a bugreport, so I recently added a trivial patch to increase a
> netlink buffer size.
>
> Looking at README.SuSE (which comes from the upstream tarball), I am not
> even able to judge if this might actually work at all with todays
> networking mess that's called wicked. So I'm not sure if it is a good
> idea to suggest this file is relatively current by using the "new"
> spelling, when it definitely is not.
>
> Thanks for considering, and have a lot of fun... :-)

I would suggest to not do automatic renaming, but manual renaming after
checking that the contents are (at least apparently) correct.

- --
Cheers,
        Carlos E. R.
        (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAloKHusACgkQtTMYHG2NR9VplACaA2z1XpmGE7M3Q1F2DSeH+nPi
GxMAni8n8eBAdC29qGNQkc16ecRra8hV
=Bs2/
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Dominique Leuenberger / DimStar
In reply to this post by Stefan Seyfried
On Mon, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:

> Hi all,
>
> Dominique is cleaning up packages and renaming "README.SuSE" files to
> "README.SUSE".
>
> While this is of course warrented in principle, there is one case to
> consider.
> If the README.SuSE is hugely outdated, then the wrong spelling at
> least
> suggest that it is not new ;-)
Neither is the correct spelling of SUSE being SUSE (and not SuSE)
anything new.. This dates back to 2004; giving maintainers 13 years to
clean up the naming of the README.SuSE -> README.SUSE should be really
enough.

If my renaming of the file does not serve anything more than
maintainers finally waiking up and validating the content of that file,
that's still a good win. As it means it's something maintainers
neglected for the last 13 years :)

Cheers
Dominique

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Martin Pluskal-2
In reply to this post by Carlos E. R.-2
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:

>
> On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
>
> > Hi all,
> >
> > Dominique is cleaning up packages and renaming "README.SuSE" file
> >
> >
> > Thanks for considering, and have a lot of fun... :-)
>
> I would suggest to not do automatic renaming, but manual renaming
> after
> checking that the contents are (at least apparently) correct.
Hi

1) Why do you assume its done automatically
2) Checking content of said files is of course not trivial amount of
work - how about instead of suggesting that someone else does more work
you do it?

Cheers

M

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Thorsten Kukuk
In reply to this post by Stefan Seyfried
On Mon, Nov 13, Stefan Seyfried wrote:

> Looking at README.SuSE (which comes from the upstream tarball), I am not
> even able to judge if this might actually work at all with todays
> networking mess that's called wicked. So I'm not sure if it is a good
> idea to suggest this file is relatively current by using the "new"
> spelling, when it definitely is not.

So, as good package maintainer, you should either remove that file from
the package list or add a hint to the README, that it could be outdated.

  Thorsten

--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Carlos E. R.-2
In reply to this post by Martin Pluskal-2
On 2017-11-14 11:19, [hidden email] wrote:

> On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
>>
>> On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
>>
>>> Hi all,
>>>
>>> Dominique is cleaning up packages and renaming "README.SuSE" file
>>>
>>>
>>> Thanks for considering, and have a lot of fun... :-)
>>
>> I would suggest to not do automatic renaming, but manual renaming
>> after
>> checking that the contents are (at least apparently) correct.
> Hi
>
> 1) Why do you assume its done automatically
Because the thread tittle has the word "Bulk".

> 2) Checking content of said files is of course not trivial amount of
> work - how about instead of suggesting that someone else does more work
> you do it?

Because I don't have access, sorry. OBS is a totally obscure art to me.


I can help, however, by reading such readmes on the packages I know
enough about and then telling someone if I consider it obsolete or current.

--
Cheers / Saludos,

                Carlos E. R.
                (from 42.2 x86_64 "Malachite" at Telcontar)


signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Martin Pluskal-2
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:

> On 2017-11-14 11:19, [hidden email] wrote:
> > On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
> > >
> > > On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
> > >
> > > > Hi all,
> > > >
> > > > Dominique is cleaning up packages and renaming "README.SuSE"
> > > > file
> > > >
> > > >
> > > > Thanks for considering, and have a lot of fun... :-)
> > >
> > > I would suggest to not do automatic renaming, but manual renaming
> > > after
> > > checking that the contents are (at least apparently) correct.
> >
> > Hi
> >
> > 1) Why do you assume its done automatically
>
> Because the thread tittle has the word "Bulk".
>
> > 2) Checking content of said files is of course not trivial amount
> > of
> > work - how about instead of suggesting that someone else does more
> > work
> > you do it?
>
> Because I don't have access, sorry. OBS is a totally obscure art to
> me.
>
>
> I can help, however, by reading such readmes on the packages I know
> enough about and then telling someone if I consider it obsolete or
> current.
That might be actually helpfull

M

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Bruno Friedmann-2
On mardi, 14 novembre 2017 13.21:43 h CET [hidden email] wrote:

> On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
> > On 2017-11-14 11:19, [hidden email] wrote:
> > > On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
> > > > On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
> > > > > Hi all,
> > > > >
> > > > > Dominique is cleaning up packages and renaming "README.SuSE"
> > > > > file
> > > > >
> > > > >
> > > > > Thanks for considering, and have a lot of fun... :-)
> > > >
> > > > I would suggest to not do automatic renaming, but manual renaming
> > > > after
> > > > checking that the contents are (at least apparently) correct.
> > >
> > > Hi
> > >
> > > 1) Why do you assume its done automatically
> >
> > Because the thread tittle has the word "Bulk".
> >
> > > 2) Checking content of said files is of course not trivial amount
> > > of
> > > work - how about instead of suggesting that someone else does more
> > > work
> > > you do it?
> >
> > Because I don't have access, sorry. OBS is a totally obscure art to
> > me.
> >
> >
> > I can help, however, by reading such readmes on the packages I know
> > enough about and then telling someone if I consider it obsolete or
> > current.
>
> That might be actually helpfull
>
> M

For each package containing a such obsolete content, just open a bug so
maintainer get warned directly (I guess some of them are no more on this ML).

Adding valuable and refreshed content will increase the chance to get a fix.
Help in doing and fixing shit is always appreciate in terms of contribution.

--

Bruno Friedmann
 Ioda-Net Sàrl www.ioda-net.ch
 Bareos Partner, openSUSE Member, fsfe fellowship
 GPG KEY : D5C9B751C4653227
 irc: tigerfoot


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Carlos E. R.-2
On 2017-11-14 13:27, Bruno Friedmann wrote:
> On mardi, 14 novembre 2017 13.21:43 h CET [hidden email] wrote:
>> On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
>>> On 2017-11-14 11:19, [hidden email] wrote:
>>>> On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
>>>>> On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:


>>>
>>> I can help, however, by reading such readmes on the packages I know
>>> enough about and then telling someone if I consider it obsolete or
>>> current.
>>
>> That might be actually helpfull
>>
>> M
>
> For each package containing a such obsolete content, just open a bug so
> maintainer get warned directly (I guess some of them are no more on this ML).
>
> Adding valuable and refreshed content will increase the chance to get a fix.
> Help in doing and fixing shit is always appreciate in terms of contribution.
Ok, I can do that. One bugzilla per file - is there a list of readmes?
Or I may just work on those I have installed on my main system, as those
are the ones of packages that I use.


Ok, I have these - notice the dates, most are recent:

Aug  7 11:21 /usr/share/doc/packages/WindowMaker-applets/README.SuSE
Oct 19  2016 /usr/share/doc/packages/WindowMaker/README.SuSE
Apr 26  2006 /usr/share/doc/packages/docbook-dsssl-stylesheets/README.SuSE
Oct  7  2016 /usr/share/doc/packages/docbook_3/README.SuSE
May 11  2016 /usr/share/doc/packages/html-dtd/README.SuSE
May 24  2004 /usr/share/doc/packages/i4l-base/README.SuSE
Jun 28  2016 /usr/share/doc/packages/ifplugd/README.SuSE
Sep 30  2016 /usr/share/doc/packages/isapnp/README.SuSE
Jun 11  2016 /usr/share/doc/packages/ispell-spanish/README.SuSE
Jun 27  2016 /usr/share/doc/packages/leafnode/README.SuSE
Oct  7  2016 /usr/share/doc/packages/openjade/README.SuSE
May 12  2016 /usr/share/doc/packages/sleuth/README.SuSE
Apr 28  2015 /usr/share/doc/packages/spamassassin/README.SuSE
May 10  2016 /usr/share/doc/packages/tkdiff/README.SuSE
Oct  7  2016 /usr/share/doc/packages/xmlto/README.SuSE

There are more files, for instance:

/usr/share/YaST2/theme/SuSELinux
/opt/kde3/share/apps/rekall/examples/mushroomDAT_en/SuSE-Novell-Logo.jpg
/usr/java/jdk1.8.0_151/jre/lib/fontconfig.SuSE.10.bfc
/usr/share/doc/packages/postfix/resto/SPAMASSASSIN+POSTFIX.SuSE
/usr/share/X11/fvwm2/pixmaps/openSuSE.xpm


And then there is SuSEfirewall2, but I doubt you want to touch that one :-)


--
Cheers / Saludos,

                Carlos E. R.
                (from 42.2 x86_64 "Malachite" at Telcontar)


signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Dominique Leuenberger / DimStar
On Tue, 2017-11-14 at 13:49 +0100, Carlos E. R. wrote:

> On 2017-11-14 13:27, Bruno Friedmann wrote:
> > On mardi, 14 novembre 2017 13.21:43 h CET [hidden email] wrote:
> > > On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
> > > > On 2017-11-14 11:19, [hidden email] wrote:
> > > > > On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
> > > > > > On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried
> > > > > > wrote:
>
>
> > > >
> > > > I can help, however, by reading such readmes on the packages I
> > > > know
> > > > enough about and then telling someone if I consider it obsolete
> > > > or
> > > > current.
> > >
> > > That might be actually helpfull
> > >
> > > M
> >
> > For each package containing a such obsolete content, just open a
> > bug so
> > maintainer get warned directly (I guess some of them are no more on
> > this ML).
> >
> > Adding valuable and refreshed content will increase the chance to
> > get a fix.
> > Help in doing and fixing shit is always appreciate in terms of
> > contribution.
>
> Ok, I can do that. One bugzilla per file - is there a list of
> readmes?
> Or I may just work on those I have installed on my main system, as
> those
> are the ones of packages that I use.
>
All README.SuSE in the distro can be found by:

wget http://download.opensuse.org/tumbleweed/repo/oss/ARCHIVES.gz
zgrep -P "README.SuSE" ARCHIVES.gz | \
  awk '{print $1": "$10}' | grep -v i586 | sort

Cheers
Dominique

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Jan Engelhardt-4
In reply to this post by Carlos E. R.-2

On Tuesday 2017-11-14 12:59, Carlos E. R. wrote:
>>>> Thanks for considering, and have a lot of fun... :-)
>>>
>>> I would suggest to not do automatic renaming, but manual renaming
>>> after checking that the contents are (at least apparently) correct.
>>
>> 1) Why do you assume its done automatically
>
>Because the thread tittle has the word "Bulk".

Bulk means mass, not automation. (Though automation is often used for
mass updates.)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Stefan Seyfried
In reply to this post by Bruno Friedmann-2
On 14.11.2017 13:27, Bruno Friedmann wrote:
> For each package containing a such obsolete content, just open a bug so
> maintainer get warned directly (I guess some of them are no more on this ML).

Well, I'll then just drop ifplugd when the bug-rate goes higher than "one bug per decade" ;-)

Which of course will also solve the issue of wrongly named and outdated documentation.

> Adding valuable and refreshed content will increase the chance to get a fix.
> Help in doing and fixing shit is always appreciate in terms of contribution.

Actually in this case, there wold need to be someone who actually uses ifplugd.
Ok, there must be *one* user at least (because of the "invalid buffer size" report), but AFAICT from the bug report, he
is not using it in the way README.S[uU]SE describes anyway.
--
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Simon Lees-3
In reply to this post by Carlos E. R.-2


On 14/11/17 23:19, Carlos E. R. wrote:

> On 2017-11-14 13:27, Bruno Friedmann wrote:
>> On mardi, 14 novembre 2017 13.21:43 h CET [hidden email] wrote:
>>> On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
>>>> On 2017-11-14 11:19, [hidden email] wrote:
>>>>> On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
>>>>>> On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
>
>
>>>>
>>>> I can help, however, by reading such readmes on the packages I know
>>>> enough about and then telling someone if I consider it obsolete or
>>>> current.
>>>
>>> That might be actually helpfull
>>>
>>> M
>>
>> For each package containing a such obsolete content, just open a bug so
>> maintainer get warned directly (I guess some of them are no more on this ML).
>>
>> Adding valuable and refreshed content will increase the chance to get a fix.
>> Help in doing and fixing shit is always appreciate in terms of contribution.
>
> Ok, I can do that. One bugzilla per file - is there a list of readmes?
> Or I may just work on those I have installed on my main system, as those
> are the ones of packages that I use.
>
Yep one bug per file, they will all have different maintainers. Start
with the ones you know, short of installing every package I don't think
there is a easy way to know unless we add a rpmlint warning / error for
them.

>
> Ok, I have these - notice the dates, most are recent:
>
> Aug  7 11:21 /usr/share/doc/packages/WindowMaker-applets/README.SuSE
> Oct 19  2016 /usr/share/doc/packages/WindowMaker/README.SuSE
> Apr 26  2006 /usr/share/doc/packages/docbook-dsssl-stylesheets/README.SuSE
> Oct  7  2016 /usr/share/doc/packages/docbook_3/README.SuSE
> May 11  2016 /usr/share/doc/packages/html-dtd/README.SuSE
> May 24  2004 /usr/share/doc/packages/i4l-base/README.SuSE
> Jun 28  2016 /usr/share/doc/packages/ifplugd/README.SuSE
> Sep 30  2016 /usr/share/doc/packages/isapnp/README.SuSE
> Jun 11  2016 /usr/share/doc/packages/ispell-spanish/README.SuSE
> Jun 27  2016 /usr/share/doc/packages/leafnode/README.SuSE
> Oct  7  2016 /usr/share/doc/packages/openjade/README.SuSE
> May 12  2016 /usr/share/doc/packages/sleuth/README.SuSE
> Apr 28  2015 /usr/share/doc/packages/spamassassin/README.SuSE
> May 10  2016 /usr/share/doc/packages/tkdiff/README.SuSE
> Oct  7  2016 /usr/share/doc/packages/xmlto/README.SuSE
>
> There are more files, for instance:
>
> /usr/share/YaST2/theme/SuSELinux
> /opt/kde3/share/apps/rekall/examples/mushroomDAT_en/SuSE-Novell-Logo.jpg
> /usr/java/jdk1.8.0_151/jre/lib/fontconfig.SuSE.10.bfc
> /usr/share/doc/packages/postfix/resto/SPAMASSASSIN+POSTFIX.SuSE
> /usr/share/X11/fvwm2/pixmaps/openSuSE.xpm
>
>
> And then there is SuSEfirewall2, but I doubt you want to touch that one :-)
>
Its going away oneday anyway :-)


--

Simon Lees (Simotek)                            http://simotek.net

Emergency Update Team                           keybase.io/simotek
SUSE Linux                           Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B


signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Michal Kubecek
On Tuesday, 14 November 2017 23:14 Simon Lees wrote:
> On 14/11/17 23:19, Carlos E. R. wrote:
> > And then there is SuSEfirewall2, but I doubt you want to touch that
> > one :-)
>
> Its going away oneday anyway :-)

I thought it is planned to be replaced by firewalld as soon as in 15.0.
Or is it only SLE15?

Michal Kubeček

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Werner Flamme
Michal Kubecek [15.11.2017 07:28]:

> On Tuesday, 14 November 2017 23:14 Simon Lees wrote:
>> On 14/11/17 23:19, Carlos E. R. wrote:
>>> And then there is SuSEfirewall2, but I doubt you want to touch that
>>> one :-)
>>
>> Its going away oneday anyway :-)
>
> I thought it is planned to be replaced by firewalld as soon as in 15.0.
> Or is it only SLE15?
>
> Michal Kubeček
>
Since Leap 15 will be based on SLE 15, it should be changed in both.
However, I guess that for compatibility reasons SuSEfirewall2 will still
be delivered, but not installed by default on new installations.

Unless someone found a foolproof way to convert the configs, there
should not be a replacement "by force" when upgrading ;)

Just my 2¢
Werner

--



smime.p7s (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Herbert Graeber-2
In reply to this post by Stefan Seyfried
Am 14.11.2017 um 15:07 schrieb Stefan Seyfried:

> On 14.11.2017 13:27, Bruno Friedmann wrote:
>> For each package containing a such obsolete content, just open a bug so
>> maintainer get warned directly (I guess some of them are no more on this ML).
> Well, I'll then just drop ifplugd when the bug-rate goes higher than "one bug per decade" ;-)
>
> Which of course will also solve the issue of wrongly named and outdated documentation.
>
>> Adding valuable and refreshed content will increase the chance to get a fix.
>> Help in doing and fixing shit is always appreciate in terms of contribution.
> Actually in this case, there wold need to be someone who actually uses ifplugd.
> Ok, there must be *one* user at least (because of the "invalid buffer size" report), but AFAICT from the bug report, he
> is not using it in the way README.S[uU]SE describes anyway.

ifplugd is used by wicked if you set "Activate Device" to "On cable
connect" in YaST. Currently ifplugd is installed by the enhanced_base
pattern. Maybe the wicked package should have "Requires: ifplugd", or at
least a "Recommends: ifplugd".

Herbert

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Stefan Seyfried
On 15.11.2017 10:39, Herbert Graeber wrote:
> ifplugd is used by wicked if you set "Activate Device" to "On cable
> connect" in YaST. Currently ifplugd is installed by the enhanced_base

This is totally crazy.
Like almost everything in wicked.
--
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Jan Engelhardt-4
On Wednesday 2017-11-15 12:43, Stefan Seyfried wrote:

>On 15.11.2017 10:39, Herbert Graeber wrote:
>> ifplugd is used by wicked if you set "Activate Device" to "On cable
>> connect" in YaST. Currently ifplugd is installed by the enhanced_base
>
>This is totally crazy.
>Like almost everything in wicked.

It's in the name, isn't it? ;-)
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Bulk renaming of "README.SuSE"

Michal Kubecek
In reply to this post by Stefan Seyfried
On Wednesday, 15 November 2017 12:43 Stefan Seyfried wrote:
> On 15.11.2017 10:39, Herbert Graeber wrote:
> > ifplugd is used by wicked if you set "Activate Device" to "On cable
> > connect" in YaST. Currently ifplugd is installed by the
> > enhanced_base
>
> This is totally crazy.
> Like almost everything in wicked.

AFAIK this is not really an invention of wicked. See ifcfg.template on
any pre-wicked openSUSE/SLE, we had STARTMODE="ifplugd" option long
before wicked was introduced. So wicked rather preserves the feature.

Michal Kubeček

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Maintainer for ifplugd needed (was: Bulk renaming of "README.SuSE")

Stefan Seyfried
On 15.11.2017 13:17, Michal Kubecek wrote:

> On Wednesday, 15 November 2017 12:43 Stefan Seyfried wrote:
>> On 15.11.2017 10:39, Herbert Graeber wrote:
>>> ifplugd is used by wicked if you set "Activate Device" to "On cable
>>> connect" in YaST. Currently ifplugd is installed by the
>>> enhanced_base
>>
>> This is totally crazy.
>> Like almost everything in wicked.
>
> AFAIK this is not really an invention of wicked. See ifcfg.template on
> any pre-wicked openSUSE/SLE, we had STARTMODE="ifplugd" option long
> before wicked was introduced. So wicked rather preserves the feature.

Yes.
But in the "good old days" sysconfig ifcfg-scripts were exactly this: bash scripts. They basically needed ifplugd to do
stuff like "cable hotplug detection".
Wicked, OTOH is compiled (C or C++?) code which could implement the ifplugd functionality easily in the wicked daemons
which are running anyway.
Just like NetworkManager is doing since its beginning.
Resorting to starting an extra daemon, its code being more than 10 years unmaintained, to handle cable hotplug is an --
how do I write it politely -- ... "strange" design decision.

But then the whole wicked invention was a strange design decision anyway and -- as Jan has already mentioned -- it's at
least aptly named.

BTW: in the last 10 years, the kernel and the network card drivers have moved on quite a bit, so even kiwi which
apparently uses "ifplugstatus" from the ifplugd package could just check /sys/class/net/$interface/carrier.

I'll file a drop request for Factory/ifplugd now. I am not going to maintain it (and help perpetuate this insanity) any
longer.

Users who really need this functionality in a separate daemon (I use it myself on systemd-less embedded systems) can
just use busybox' ifplugd implementation, which works well.

So if nobody takes maintainership of Base:System/ifplugd, it'll be history soon.

Have fun,

        seife
--
Stefan Seyfried

"For a successful technology, reality must take precedence over
 public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

12