netdev - Re: [PATCH] RDS is not Radio Data System

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180805101945.GA4056@oracle.com>
Date:   Sun, 5 Aug 2018 06:19:45 -0400
From:   Sowmini Varadhan <sowmini.varadhan@...cle.com>
To:     Pavel Machek <pavel@....cz>
Cc:     santosh.shilimkar@...cle.com,
        kernel list <linux-kernel@...r.kernel.org>,
        Netdev list <netdev@...r.kernel.org>
Subject: Re: [PATCH] RDS is not Radio Data System

On (08/05/18 08:59), Pavel Machek wrote:
> Getting prompt "The RDS Protocol" (RDS) is not too helpful, and it is
> easily confused with Radio Data System (which we may want to support
> in kernel, too).
> 
> I wonder if option should be named NET_RDS, instead?

RDS has been around for a while now (since 2.6). How will you
rename proposal manage backward compatibility? Why can't you call
your new option CONFIG_RADIO  or similar instead?

Are we going to rename NFS* to NET_NFS* because someone decided
to reuse the NFS acronym? 

> And this sounds like a good idea:
> -	tristate "The RDS Protocol"
> +	tristate "The Reliable Datagram Sockets (RDS) Protocol"

surn that sounds fine.

--Sowmini