- amd64 is no longer a new thing and is now the largest-used FreeBSD platform,
so make its description self-contained and not dependent on i386.
- Use a single list of all the other names for amd64 and add x86-64 as the
first alias in the list.
- Mention multi-core and SMT (not just SMP) for amd64. Also note that amd64
requires ACPI and supports booting from both UEFI and legacy BIOS.
- Note that FreeBSD/amd64 runs on laptops and desktops.
- Remove outdated lists of processors. Instead, simply claim that
amd64 runs on all Intel and AMD 64-bit x86 CPUs. Similarly, simplify
the list for i386 to just require an FPU and CMPXCHG. Add VIA to the
vendors for i386.
- For i386, trim language about SMP. It's not that novel and the smp@ list is
not a useful reference. Do mention multi-core and SMT.
- Only claim that i386 motherboards with PCI are well-supported. Clarify
that there is limited support for AGP and ISA and that ISA support really
means LPC support. Remove EISA, VLB, and MCA which are all either removed or
barely present.
- Don't mention PCCARD for i386 laptops.
- Simplify language about ACPI for i386.
- Note that i386 only boots via BIOS and doesn't support booting via UEFI.
Reviewed by: imp, gjb (earlier version), emaste
Differential Revision: https://reviews.freebsd.org/D28720
Currently '/usr/local/bin/python3.7' is used as the value of
PYTHON_CMD. Right now this works because 3.7 is the default version of
Python 3 in the ports tree. However, at some point in the future, this
will be undoubtedly be changed.
It is also possible that users already might be building versions
newer than the default port/package, which needs to be an supported as
well.
In addition, the FDP recommends installing the 'python3' package. This
meta port/package depends on the default version of python, and
automatically creates a symlink to the default version.
With all this in mind, use '/usr/local/bin/python3' is used as the value
of PYTHON_CMD, since this means that the instructions will work
irrespective of which version is assigned.
In order for hugo to build all links correctly, it is necessary to
define baseURL - but in order to do this, we need some way of adding a
hostname. This change adds the HOSTNAME variable to accomplish this.
Another advantage is that if HOSTNAME is set to something other than
localhost, hugo can be run on a different (more powerful) machine which
can shorten the time it takes to build.
A note about this will need to be added to the FDP later.
The gitref macro added in commit fb36cfdfb2 handles changes in both src,
doc and ports trees, takes up less space, and is quicker to write, so
update all uses of the commit shortcode.
While here, also update the canonical sample that's commented out.
Also re-arrange some items which were initially placed in the wrong
sections.
Since the shortcode is now no longer used, remove it.
Pursuant to the DocBook->AsciiDoctor migration, status reports are
similarily moving from MarkDown to AsdiiDoctor, as there should be no
functional change in how report entries are handled by commiters or
contributors.
While here, remove sample file that has never been referred to anywhere,
and update the README used by the status project team.
With this extension a git hash can be easily referenced.
The porters handbook versions chapter uses this extension
as an example in the FreeBSD 14.0 version table.
An example of use
gitref:hash[repository="src|doc|ports",length=hash-longitude]
The repository should be src, doc or ports.
And if no length it's specified the macro will use 12 characters
of the specified hash.
PR: 253050
Submitted by: jhb@
The package name 'hugo' refers to emulators/hugo, a PC Engine
(TurboGrafx 16) emulator, whereas the hugo that is required by the new
framework is www/gohugo. A similar case applies with the package name of
AsciiDoctor, which is 'rubygem-asciidoctor'.
Therefore fix package names so they refer to proper ones.
PR: 253470
Add release notes for bin/calendar, usr.bin/gh-bc (contrib/bc), and
the new getlocalbase() function in libutil
This is the first commit regarding actual changes of base components
in this document and I'm not sure about the style and format expected.
Feel free to edit and adapt the text from this commit (or let me know
how it should be changed) to make it better align with later additions
to this file.
Approved by: re
