| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 27 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 40:38:21 |
| Calls: | 631 |
| Calls today: | 2 |
| Files: | 1,187 |
| D/L today: |
24 files (29,813K bytes) |
| Messages: | 174,719 |
I just made an 'offline' installation of FreeBSD 15.0-ALPHA2 with these options selected:
- Use PKGBASE.
- Do 'Offline' install.
- Auto ZFS with Partition Scheme: GPT (BIOS+UEFI)
- Add '+lib32' to wanted sets.
After reboot I want to see what PKGBASE packages are installed (and maybe remove some of them) but I am not able to because pkg(8) is not bootstrapped ... why? This is OFFLINE installation. These are bad defaults.
root@A2:~ # pkg info
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]:
memstick too i hope?
or any installer which contains pkgbase?
or perhaps any installer?
i don't get why this decision was made. you can always upgrade pkg.
but what if it's truly offline?
i never understood why pkg is not in base. after all that's like most important tool ever. especially now
yeah, everyone can take src and build whatever installer they want
but hell with those defaults
only reason here is that pkg should always be latest and can't in
some cases be upgraded?
at least give me reasons i can disagree with!
On 9/16/25 15:16, vermaden wrote:The various FreeBSD-15.0-*-*-*-*-*[0-9]-memstick.img* (when the
I just made an 'offline' installation of FreeBSD 15.0-ALPHA2 with these options selected:
- Use PKGBASE.
- Do 'Offline' install.
- Auto ZFS with Partition Scheme: GPT (BIOS+UEFI)
- Add '+lib32' to wanted sets.
After reboot I want to see what PKGBASE packages are installed (and maybe remove some of them) but I am not able to because pkg(8) is not bootstrapped ... why? This is OFFLINE installation. These are bad defaults.
root@A2:~ # pkg info
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]:
I'm planning on adding pkg to the pkgbase repository on disc1 and dvd1.
Colin Percival <cperciva_at_tarsnap.com> wrote:
I'm planning on adding pkg to the pkgbase repository on disc1 and dvd1.
So: memstick too?
On 9/16/25 16:57, Mark Millard wrote:
Colin Percival <cperciva_at_tarsnap.com> wrote:
I'm planning on adding pkg to the pkgbase repository on disc1 and dvd1.
So: memstick too?
Yes. "memstick" contains exactly the same bits as "disc1" -- the only >difference is how it boots. And for that matter, any modern system should >work just fine with the "disc1" image on a USB disk; we might get rid of >"memstick" in 16 since it's pointless duplication.
On September 17, 2025 3:27:58 AM GMT+03:00, Colin Percival <cperciva@tarsnap.com> wrote:
Yes. "memstick" contains exactly the same bits as "disc1" -- the only
difference is how it boots. And for that matter, any modern system should >> work just fine with the "disc1" image on a USB disk; we might get rid of
"memstick" in 16 since it's pointless duplication.
that would mean that people who sometimes slightly modify installers now need to make their own custom full installer images?
at minimum one needs to extract it
maybe not even bad i think...
but i'm surprised that it's memstick that goes first and not discs. except longer shelf life (nearly forever if you press it) and being physically readonly, i don't know how many installs are done from *actual* cd(-r) / dvd(-r). sometimes you don't even have reader nor writer nor blanks. MODERN hw, right?