03.07.2020 18:54, Taylor R Campbell wrote:
The default location is /var/db/entropy-file, but if /var is on a
separate file system, the bootloader won't be able to get at it. So
in that case, sysinst tries to add
random_file=/etc/entropy-file
to /etc/rc.conf, and
rndseed
> Date: Thu, 18 Jun 2020 09:15:55 +0300
> From: Dima Veselov
>
> I have a small question why we have /etc/entropy-file in boot.cfg after
> every install but it always tries to update to /var/db/entropy-file on
> every build of -STABLE?
The idea of this logic in sysinst was
Greetings,
I have a small question why we have /etc/entropy-file in boot.cfg after
every install but it always tries to update to /var/db/entropy-file on
every build of -STABLE?
--
Sincerely yours,
Dima Veselov
Physics R&D Establishment of Saint-Petersburg University
> On May 7, 2020, at 11:34 AM, Martin Husemann wrote:
>
> It should do everything correctly, nothing special needed for 9.0 or newer.
Confirmed.
I was also able to roll my own with LVM.
Having a writable /dev on arm64 really helps :D
On Thu, May 07, 2020 at 10:58:03AM -0400, Eric S. Hvozda wrote:
> Do you still need to handcraft the partitioning as suggested in
> https://wiki.netbsd.org/users/spz/moderndisk/ or does sysinst do the
> correct things as of v9.0?
It should do everything correctly, nothing special needed for 9.0 or
>> On May 7, 2020, at 4:26 AM, Martin Husemann wrote:
>>
>> On Wed, May 06, 2020 at 05:55:08PM -0400, Eric S. Hvozda wrote:
>> It is know what installing boot blocks on the devices to supporting a
>> raid set with GPT is useless (i.e. does not work due to lack of
>> support)
>
> Missing conte
On Wed, May 06, 2020 at 05:55:08PM -0400, Eric S. Hvozda wrote:
> It is know what installing boot blocks on the devices to supporting a
> raid set with GPT is useless (i.e. does not work due to lack of
> support)
Missing context here. What machine are you trying to boot and what NetBSD
version?
O
> On May 6, 2020, at 6:10 PM, Chavdar Ivanov wrote:
>
> You don't boot KASLR this way.
>
> You put
>
> menu=Boot KASLR:rndseed /var/db/entropy-file;pkboot netbsd_kaslr
>
> in your boot.cfg and copy /usr/mdec/prekern to / .
>
> (I copy the KASLR kernel
> Then I saw PR #48702 filed in 2014.
I actually still have that in my local patch set, but a few years
later I realized that entropy-file on / would not work for people
with read-only / and securelevel 2, maybe that's why nobody ever
touched it. Before KASLR it was probably not a big d
no matter what I try, I cannot get GENERIC_KASLR to boot with this
> configuration.
>
> If I manually try to boot it via:
>
> boot kaslr
You don't boot KASLR this way.
You put
menu=Boot KASLR:rndseed /var/db/entropy-file;pkboot netbsd_kaslr
in your boot.cfg and copy /
to
the entropy file at boot time.
So I created the proper /var/db/entropy-file with rndctl( 8 ) on /dev/dk0;
still no luck.
So I come to a stand still with several questions:
* if my boot device and root device are not the same, can I not use
GENERIC_KASLR?
* it looks fairly important to h
stuck at "Loading /var/db/entropy-file" during boot.
The X4540 has a compact flash card which is used to install the OS onto,
so all of the hard disks may be used for other things. The X4540 guide
recommends to move /var and swap onto the hard disks after installation,
in order to prev
I have got 7.0.1-amd64 installed in our Sun Fire X4540. Now it's just
stuck at "Loading /var/db/entropy-file" during boot.
The X4540 has a compact flash card which is used to install the OS onto,
so all of the hard disks may be used for other things. The X4540 guide
recommen
13 matches
Mail list logo
