Is v13.0 still usable?

K

krini

Hello

Due to special circumstances, I would need to setup a FreeBSD 13.0 system.

Is 13.0 "usable" in the sense that I can use the package manager (pkg), or ports for installing software? pkg would be my preferred choice.

I setup a 13.0 machine and installed the simple text editor 'nano' using pkg, but I get this error:
Code: 
root@bsd1:~ # nano
ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/bin/nano not found

If a simple thing like installing 'nano' doesn't work, then I am very doubtful that I can get everything I want to work on the system...
 
There is no pkg repository for this version. I guess it's the same for ports. So, no way, unless you find somewhere the corresponding port tree.
 
You can always check the appropriate ports tree out of git.

The biggest problem with running a backdated ports tree is that many distfiles will have disappeared.
 
some packages are available on distribution disk/iso
older distfiles used to work with MASTER_SITE_FREEBSD
Code: 
20:59:53] [ooak!root]/usr/ports/lang#cd  ../www/node
[21:00:10] [ooak!root]/usr/ports/www/node#make fetch MASTER_SITE_FREEBSD=1
===>  License MIT accepted by the user
=> node-v0.10.26.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/node-v0.10.26.tar.gz
node-v0.10.26.tar.gz                            6% of   12 MB  107 kBps 01m52s^C
this is a Makefile from 2014 on freebsd 9 :)
 
covacat said:
some packages are available on distribution disk/iso
older distfiles used to work with MASTER_SITE_FREEBSD
Code: 
20:59:53] [ooak!root]/usr/ports/lang#cd  ../www/node
[21:00:10] [ooak!root]/usr/ports/www/node#make fetch MASTER_SITE_FREEBSD=1
===>  License MIT accepted by the user
=> node-v0.10.26.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/node-v0.10.26.tar.gz
node-v0.10.26.tar.gz                            6% of   12 MB  107 kBps 01m52s^C
this is a Makefile from 2014 on freebsd 9 :)
Click to expand...

Cool. I suppose it isn't trivial to recognize old distfiles for purging.
 
You can do something like this:
Code: 
fetch https://archive.freebsd.org/old-releases/ISO-IMAGES/13.0/FreeBSD-13.0-RELEASE-amd64-dvd1.iso.xz
xzcat FreeBSD-13.0-RELEASE-amd64-dvd1.iso.xz > 13.0.iso
mdconfig -a -t vnode -f 13.0.iso
mount -t cd9660 -r /dev/md0 /cdrom
cd /cdrom/packages
Below this dir. you will find all the packages available at the release time of 13.0. You can then pkg install what you want. Make sure you download the right iso for your machine architecture!
 
krini said:
I setup a 13.0 machine and installed the simple text editor 'nano' using pkg, but I get this error:
Click to expand...
It installed packages built for 13.3, which won't work on 13.0.

bakul said:
Before this dir. you will find all the packages available at the release time of 13.0.
Click to expand...
The DVD image only contains a selection of packages.
 
What are the circumstances? You could, worst case, always build everything you need from source without using ports or pkg at all. That could be legitimate in some really wonky one-off edge case that's essentially a throwaway. Depends on "circumstances" though. The more you can share about those, the better the quality of the advice you'll get here.
 
Yea pkg spits out a version mismatch warning but allows you to proceed.

But hooking up the internet to a 13.0-RELEASE version could be considered careless.
 
bvdw78 said:
What are the circumstances? You could, worst case, always build everything you need from source without using ports or pkg at all. ...
Click to expand...
That's not actually easy. Say for example there is a piece of software called foobar. When 13.0 came out, foobar was at version 4. Today foobar is at version 7, and at the time 13.3 first came out, it was at version 6. To create a realistic 13.0 system, you need to download the source code of foobar 4. But that source code may not even exist any longer, or it may be very hard to find, or you may have to consult archives. And then foobar 4 may require blatz 17, but today blatz is at 29, and the maintainer of blatz was abducted by space aliens (more civilized than being run over by a bus), and nobody knows where to find a tarball of blatz 17. So re-creating ancient software may be a complex voyage of discovery, a field trip into the past, a task of archeology.
 
krini said:
Hello

Due to special circumstances, I would need to setup a FreeBSD 13.0 system.

Is 13.0 "usable" in the sense that I can use the package manager (pkg), or ports for installing software? pkg would be my preferred choice.

I setup a 13.0 machine and installed the simple text editor 'nano' using pkg, but I get this error:
Code: 
root@bsd1:~ # nano
ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/bin/nano not found

If a simple thing like installing 'nano' doesn't work, then I am very doubtful that I can get everything I want to work on the system...
Click to expand...
Don't use pkg if you want to use something as old as 13.0-RELEASE. You'll have to use ports, and compile them from ground up. It's not impossible, but would take at least a week on a capable machine. ralphbsz already described in general terms what OP is gonna face. Major difficulties, all stemming from the "need" to use a base that is as out out of date as 13.0-RELEASE.

It's gonna be less work to set up a brand new machine/VM with exact same functionality, but up-to-date components. With up-to-date components, it's easier to troubleshoot and find help upstream, too. ?
 
What includes the installation DVD? Is there for example postfix or is it possible to install latest postfix on 13.0-RELEASE?
 
6502 said:
What includes the installation DVD? Is there for example postfix or is it possible to install latest postfix on 13.0-RELEASE?
Click to expand...
dont.
just dont.

Even if it is included in the DVD, that version is over 3 years old and contains several known vulnerabilites that *will* be exploited.

Again: there is *NO* valid reason to still use 13.0-RELEASE, *especially* for something that is connected to the internet and gets hit with as much noise as a mailserver.
IF for some reason you have some proprietary binaries that really only work on 13.0 (e.g. some dumb hard-coded version check), then run that in a jail - but the host and *especially* programs that are in ports should run a supported release and a current, patched version.
 
You must log in or register to reply here.
Back
Top