linux-kernel - Re: New Wiki URLs?

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]

Date:   Fri, 1 May 2020 19:42:44 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     webmaster@...nel.org, linux-kernel@...r.kernel.org,
        linux-doc@...r.kernel.org,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        Johannes Berg <johannes@...solutions.net>,
        linux-wireless <linux-wireless@...r.kernel.org>
Subject: Re: New Wiki URLs?

[adding people + linux-wireless@ ]

Should we assume that the current wireless wiki URLs are more or less
permanent and so update lots of outdated references to them?

I see that the MAINTAINERS file is already updated.

Plus there is a request for redirects @kernel.org.


On 4/27/20 9:44 PM, Alexander Dahl wrote:
> Hello,
> 
> I noticed the kernel wiki URLs might have changed. The URLs now are
> like this:
> 
> https://wireless.wiki.kernel.org/en/users/drivers/b43
> 
> However in the kernel source code and in the kernel log output you
> find something like this:
> 
>     b43-phy1 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and do
>     wnload the correct firmware for this driver version. Please carefully read all instructions on this 
>     website.
> 
> (Notice the additional subdomain and the case change in the resource
> path.)
> 
> Some websites seem to link on those old URLs, see
> https://packages.debian.org/source/buster/b43-fwcutter for example.
> 
> Could the webmasters of kernel.org please configure some kind of
> redirects so people don't get 404 errors when looking for docs?
> 
> Bonus question: would it make sense to change all those URLs in the
> source (as in: send patches for that)? Then what URLs are supposed to
> be the right ones now?
> 
> Kind regards
> Alex


-- 
~Randy