mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: replace broken specification URL
Date: Fri, 9 Sep 2016 10:16:46 +0200	[thread overview]
Message-ID: <c7b4c63e-af53-401c-3854-d3edea258e53@free-electrons.com> (raw)
In-Reply-To: <1467470971.2400.7.camel@HansenPartnership.com>

Hi James,

Thank you very much for your help...

On 02/07/2016 16:49, James Bottomley wrote:
> On Sat, 2016-07-02 at 08:56 +0200, Michael Opdenacker wrote:
>> The t10.org website containing SCSI-2 draft specifications now
>> requires to be from a member company to access the documents.
>>
>> This replaces the now broken link with another public resource
>> where the specifications can be found.
> Just because T10 implemented a pay wall for standards, doesn't mean
> they're not still the definitive source.
>
> Adding a note about where you can get free versions is a useful
> service, please do, but we have to keep the official links.  To be
> honest the Duisberg site doesn't seem useful because it only has the
> CAM standard.

Understood. I found another location where all the documents seem to be 
available:
http://www.csit-sun.pub.ro/~cpop/Documentatie_SMP/Standarde_magistrale/SCSI/
>
> The Wayback machine is more useful because it keeps a copy of the site
> (with the attached standards) just before the paywall went up:
>
> https://web.archive.org/web/20080828112749/http://t10.org/drafts.htm

However, the PDF file from 
https://web.archive.org/web/20080828112749/http://t10.org/ftp/t10/drafts/cam/cam-r12b.pdf 
fails to load at a 130810 byte limit. Other people have reported a 
similar file size issue in the past.

So, should we only that the cam-r12b document can be found from 
http://www.t10.org/t10docs.htm (registration required)?, and tell that a 
copy can be found on 
http://www.csit-sun.pub.ro/~cpop/Documentatie_SMP/Standarde_magistrale/SCSI/?

I'm trying to fix broken links in kernel documentation, which I publish 
on http://free-electrons.com/kerneldoc/ . I have a broken link checker 
for the http://free-electrons.com/ website, and it finds all the broken 
links on http://free-electrons.com/kerneldoc/ . That's a good thing, 
isn't need, but it means I have to get rid of the broken links :)

Thanks again for your help,

Cheers,

Michael.

-- 
Michael Opdenacker, CEO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-09-09  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02  6:56 Michael Opdenacker
2016-07-02 14:49 ` James Bottomley
2016-09-09  8:16   ` Michael Opdenacker [this message]
2016-09-09 22:53     ` Tyrel Datwyler
2016-09-14 17:00     ` Martin K. Petersen
2016-09-15 12:33       ` Michael Opdenacker
2016-09-15 13:03         ` Michael Opdenacker
2016-09-15 14:06           ` Martin K. Petersen
2016-09-16  1:00             ` Laurence Oberman
2016-09-16  0:57           ` Laurence Oberman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c7b4c63e-af53-401c-3854-d3edea258e53@free-electrons.com \
    --to=michael.opdenacker@free-electrons.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®