To accommodate release/machine differences, /mnt/noasks is now /mnt/livecd-config/RELEASE/MACHINE/noasks.
usbfadm newdrive will create the noasks file in the new location.
For backward compatibility, /boottmp/rc will read the noasks into either the old or new location at boot time.
If there are noasks in both the old and new locations, rc will display a warning message and stop the non-interactive boot.
Distribution image changes
The disk partitioning of the distribution images for the i386 and amd64 platforms has been changed from Hybrid MBR to traditional MBR.
This distribution image contains an EFI Sys partition, so it can be booted from either Legacy BIOS or UEFI as before.
Furthermore, once a Hybrid MBR has been created, it has been very difficult to change its contents, but from this release it is now possible to make changes to the partition using OpenBSD's fdisk and disklabel tools.
usbfadm feature additions
On the amd64 platform, when executing the newdrive subcommand, it is possible to create media that can be booted from either the Legacy BIOS or UEFI by selecting UEFI as the boot method and MBR as the partitioning method.
In this case, the Legacy BIOS bootloader will be installed at the same time.
A new expand sub-command has been added.
This allows you to expand the data storage partition to the maximum possible capacity.
There are two ways to expand a partition: growfs, which preserves the data in the partition, and newfs, which formats a new partition. Naturally, all existing data will be lost if you use newfs. However, newfs will create a file system with parameters appropriate to the size of the expansion.
In the auto-startup file "noasks", it is possible to specify the parameters required for startup to eliminate manual input. For storage devices and data storage devices, DUIDs*1 are now added as comment lines.
The DUID is the actual value of the device that has been remastered, so it can be used by commenting it out.
This noasks file is automatically generated when you run the newdrive subcommand of the usbfadm utility or the expand subcommand with the newfs option selected.
moved /usr/fuguita/etc to /etc/fuguita.
This is so that FuguIta-related configuration files can be edited in boot mode 1.
In addition, /etc/netconfs has been moved to /etc/fuguita/netconfs.
There are some incompatibilities when the previous saved files in this release are loaded in boot mode 3. To fix this problem, please do the following.
1. Move /usr/fuguita/etc to /etc/fuguita.
2. Move /etc/netconfs to /etc/fuguita/netconfs.
3. Modify the symbolic link /etc/myname to point to /etc/fuguita/netconfs/NETCONF-NAME/myname. NETCONF-NAME is the name of the network configuration, as specified in gennetconf. NETCONF-NAME is "default" if it has not been changed from the settings for a new boot (boot mode 0, 1, 2).
4. usbfadm sync to save the changes and reboot.
(If usbfadm sync cannot be executed, please perform steps 1 to 3 for the data already saved in the USB flashdrive)
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
