On Thu, 2009-08-13 at 10:51 -0400, Brian Utterback wrote:
> And it wouldn't have to be forever, anyway. If you specify the
> redirects via "permanent relocation", then after a while many of the
> sources will note the move and update bookmarks, etc. Then a little
> time later, you examine the logs and see which pages are still getting
> traffic to the old URL and which do not. It is likely that the number
> of URLS still getting traffic will be much smaller than the total
> number of pages, so you whittle the redirect database down to just
> those and go back to your plan A for the rest. I bet the resulting
> database will be much smaller than the original one was.
Some of the links will be impossible to update.
For instance, the "zpool" and "zfs" commands embed:
http://www.opensolaris.org/os/community/zfs/version/N
and
http://www.opensolaris.org/os/community/zfs/version/zpl/N
(see "zpool upgrade" and "zfs upgrade", respectively).
Even if new versions of the command are updated, there are tons of
copies of those URL's embedded in OS install DVD's we've given away and
on systems which have been installed but which are unlikely to be
upgraded.
How do we get a commitment that a particular URL is stable enough to
embed in a binary which may get copied billions of times and which may
not be updated for a decade or two?
- Bill
_______________________________________________
website-discuss mailing list
[email protected]
