debug.mpsafevm=1 by default on sparc64,
ixgb(4) MPSAFE,
core dump of natd(8) w/ -reverse fixed,
libarchive zip support improved, and
rexecd(8) root login problem fixed.
pictured here. We might want to show a real CDROM layout here.
Also clarify that whatever's in the floppies/ directory is primarily
useful to users who actually need to boot from floppy to start an
installation.
disk names.
"Approximately three...floppies" is kind of weird to me, so substitute
"several" here instead. We already mention that a floppy disk set
requires three disks elsewhere, so we're not really losing any
content.
bloat on disc1.
- Output a message letting the user know that we are generating MD5 sums
during the long pause after the last mkisofs invocation in the iso.1
target.
MFC after: 3 days
- When a separate livefs ISO is used, change the name of the tree directory
to be R/cdrom/livefs and change the name of the iso to livefs.iso rather
than using disc2. Instead, disc2 is now always going to be the packages
disc regardless of the presence of a separate livefs which makes things
simpler.
- Build a very simple disc2 tree under R/cdrom that just includes the
cdrom.inf file that the packages need. Also, build a disc2.iso image
in the iso.1 target. Disc 2's volume label is "FreeBSD_Packages".
- Retire CD_EXTRA_BITS and replace it with CD_PACKAGE_TREE. CD_EXTRA_BITS
was specific to disc1, but CD_PACKAGE_TREE instead should point to a
directory that has disc1 and disc2 subdirectories that contain the extra
bits for each image.
- Rename the bootonly volume label to "FreeBSD_bootonly" and just hardcode
the disc1 and livefs volume names and iso suffixes.
there are still a couple of places under src/release such like fixit.profile
assumed that system binary can be retrivied from /stand(ex: boot with the
live CD and run "disklabel -e" in the fixit CD shell).
Since /stand is still functional in fixit floppy, and there are more than
one places in src/release needs to be updated(document for example) if we
want to make use of something like /mnt2/rescue/vi. This commit try to
deal with aforementioned inconsistency with minimal effort by simply
create a symbolic link to /rescue.
Reviewed by: jhb, sam (mentor)
bunch of append calls when adding more ports to an existing list.
- Remove the compatXY packages from disc1 as they are only intended for use
on 5.x (6.x doesn't have them as dists anymore) and on 5.x they aren't
packages but are old-fashioned distribution tarballs anyway.
misread print-cdrom-packages.sh).
- Include x11/xorg-manpages and devel/imake-6 since xorg doesn't pull those
in as requirements. Not including manpages is a bug IMO.
- Add security/freebsd-update to disc2, not sure why I left this one out
but I did by accident.
Reported by: kensmith (2), cpercival (3)
The new system tries to be more automated so that there is less work for
the re's to do. It also no longer uses a /usr/ports tree as its input,
but uses the generated package build including its INDEX file as its input.
It parses the INDEX file, determines which packages should go on which ISO
images, and then builds full-fledged trees of packages that can be added
as an argument to mkisofs along with the tree built by 'make release' to
build a full CD image. The INDEX files in the populated trees are
generated with volume media number to make use of sysinstall's multiple
volume support so that the user is kindly prompted to insert the
appropriate disc for a package if it is not on the current disc. There is
still some more tweaking to be done here, but this part needs to be
committed. This stuff will all be used to prep the 5.4 release as well.
Tested by: kensmith, others on re@
Reviewed by: re
pgrep(1) and pkill(1) -S, -F, -i, -j, and -o option, and
ps(1) -o jid.
Update release notes:
Use &man.acpi.fujitsu.4; entity, and
s/Rockridge/RockRidge/.
For both KDE and GNOME notes, fix upgrading instructions and point
users to the Web pages for these respective projects. [1]
Discussed with: marcus [1]
release documentation snapshots, force URLS_ABSOLUTE. This
allows us to relocate HTML renderings anywhere without worrying
about breaking relative links to pages on the Web site. This can
happen when we use &base; as part of a URL.
I wonder if we should do this for all release documentation builds,
but I'm not quite sure what all the cases are.
MFCs noted: tcpdrop(8).
Updated release notes: Mention ath_rate_sample rate control module,
libthr stack size update, Xorg 6.8.2.
Fixed a minor grammo in introduction, also adjust wording in pointers
to snapshots.
snapshots, instead point them at a Web page on the main FreeBSD
site that gives more information on the monthly (RE-created) snapshots
plus pointers to the jp.freebsd.org and se.freebsd.org snapshots.
