Old Archive freebsd 9 packages

X

xxmcvapourxx

Hi all,
I'm trying to install sudo I get command unknown and also for nano.

I'm trying to use the old archives but I'm getting 550 failed to change directory. I'm using VMware. I don't want to upgrade to latest this is for a project. I did have an old post exactly the same but I never managed to get it to work now I'm trying again.

I'm stuck here I've looked everywhere.
 

Attachments

  • Capture.PNG
    Capture.PNG
    19.3 KB · Views: 220
  • Capture.PNG
    Capture.PNG
    2.9 KB · Views: 187
FreeBSD 9.0 has been end-of-life since March 2013 and is not supported any more.
forums.freebsd.org

Topics about unsupported FreeBSD versions

The FreeBSD Forums cater primarily to end-users and systems administrators. As such, the Forums focus almost exclusively on FreeBSD versions that are officially supported according to the official FreeBSD website. Since resources are scarce, the FreeBSD Forums strongly suggest that anyone asking...
forums.freebsd.org forums.freebsd.org


xxmcvapourxx said:
I'm trying to use the old archives but I'm getting 550 failed to change directory
Click to expand...
There's this thing called case sensitivity.

xxmcvapourxx said:
I don't want to upgrade to latest this is for a project.
Click to expand...
What project?
 
Oh damn I didn't see that. Thanks for letting me know, project for cyber security to find vulnerabilities in old FreeBSD 9 and 10 my teacher asked me to setup FreeBSD 9 and 10 on VMWare.
 
You can just try to build current ports on it, but don't be surprised to run into build problems…
 
SirDice said:
That's going to be the number one issue. You can easily get an old ports tree to work but it's likely those old upstream distfiles have all disappeared by now.
Click to expand...
I've done builds on ports tree from release of 9.3-R recently (a month or two ago) (I needed openssl and curl and something else, don't remember), there was no distfiles problem.
 
In terms of digital preservation, perhaps the archives should store distfiles as well as the precompiled packages (that can ultimately be built from the distfiles).

Either way, distfiles can generally be tracked down. It will just be a pretty painstaking manual task. Luckily you have the hash so you can check if any crusty files are indeed the correct ones. Sometimes you can even google the hash and find some guys personal distfile archive.

I used to maintain a fairly old install of FreeBSD 9.1 (for an aging PC before it broke) so did have to faff about occasionally if I did need new software.
 
kpedersen said:
In terms of digital preservation, perhaps the archives should store distfiles as well as the precompiled packages (that can ultimately be built from the distfiles).
Click to expand...
FreeBSD (their repositories) doesn't store distfiles at all, they're always downloaded from their upstream sources. It's been said before, FreeBSD is not a museum, why would they need to "preserve" old upstream distfiles? They only preserve their own stuff (FreeBSD itself), nothing more.
 
SirDice said:
They only preserve their own stuff (FreeBSD itself), nothing more.
Click to expand...
Yeah, very true. Though they do seem to go some distance in preserving some packages: http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/9.1-RELEASE/packages/All

Rather than these, they could just provide a matching ports snapshot, the distfiles and then users of any architecture could build the packages themselves. As it stands the FreeBSD project has to archive 3rd party packages for every architecture.
 
You must log in or register to reply here.
Back
Top