Installer of 20210225 snapshot works with monochrome mode

[Yasuhiro Kimura]

I created VirtualBox VM on Windows host and tried to make clean
install of 14-CURRENT with iso image of 20210225 snapshot
(FreeBSD-14.0-CURRENT-amd64-20210225-bf667f282a7-256946-disc1.iso). Then
installer worked with monochrome mode as following.

https://www.utahime.org/FreeBSD/install-snapshot-020210225.01.png
https://www.utahime.org/FreeBSD/install-snapshot-020210225.02.png
https://www.utahime.org/FreeBSD/install-snapshot-020210225.03.png

If I start `bsdinstall` after installation is completed, then it works
normal color mode. So it seems bug of install image.

---
Yasuhiro Kimura
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Git, shallow clone hashes, commit counts and system/security updates

[Graham Perrin]

On 02/03/2021 05:42, Kevin Oberman wrote:

Re: Panic after updating from source

On Mon, Mar 1, 2021 at 6:31 PM Michael Sierchio  wrote:


…

You need to be aware that the shallow clone hash will not include the
commit count which will be used in future security updates to make it easy
to check whether your system needs to be updated or not. A full clone does
require more space, but I was surprised at how little extra space it
requires. Warner  is updating his git mini-guide to point out this issue.
If you run STABLE, it's a really significant concern. You can convert the
shallow clone to a full one with "git fetch --unshallow". This will take
some time to run.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-questi...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions


Drawing the above (with a change of subject line) to the attention of 
the freebsd-current list.


Thank you, Kevin and Warner.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS-UP: PIE enabled by default on main

[John Kennedy]

On Sun, Feb 28, 2021 at 09:40:54AM -0500, Shawn Webb wrote:
> ... The point of ASLR is to combine it with W^X. Without W^X, ASLR makes
> no sense. FreeBSD recently gained a W^X implementation that requires
> opt-in. ...

  I'm not plugged into the right places to catch some of these things up
front.  Like PIE, I trip across how to enable them after the fact by finding
people talking about it here.

  My google-fu is getting a lot of bad hits, but I assume this is referring
to making writable memory non-executable (above and beyond malloc()'s M_EXEC
flag with it's disclaimers).  What are the keyword/feature/knobs to get
better informed and opt-in?

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: No serial console: VBE not available

[Toomas Soome via freebsd-current]

> On 1. Mar 2021, at 12:34, Harry Schmalzbauer  wrote:
> 
> Am 26.02.2021 um 17:58 schrieb Toomas Soome via freebsd-current:
>>> On 26. Feb 2021, at 18:54, O. Hartmann  wrote:
>>> 
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA256
>>> 
>>> hello,
>>> 
>>> running a FreeBSD appliance on top of a PCengines APU2C4 with the latest 
>>> seabios
>>> (apu2_v4.13.0.3.rom). The PCengines boot image layout is based on 
>>> pmbr/gptboot (GPT patition
>>> scheme), via nanoBSD the latest pmbr/gptboot binaries are applied taken 
>>> from the 13-STABLE
>>> tree (or 14-CURRENT).
>>> 
>>> It doesn't matter whether I put these lines into /boot/loader.conf:
>>> 
>>> boot_serial="YES"
>>> comconsole_speed="115200"
> :
> :
> :
>> 
>> You are missing this one:
>> commit 61c50cbc096d28e44cb8b627e524ae58158c423a
> 
> Actually stable/13 is missing this.
> It was merged to releng/13.0, but not to stable/13 as far as my git skills 
> last:
> https://cgit.freebsd.org/src/log/stand/i386/libi386/vidconsole.c?h=stable%2F13
>  
> 
> 

.oO totally my bad, I have missed push… fixed, sorry.

thanks,
toomas




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: No serial console: VBE not available

[Harry Schmalzbauer]

Am 26.02.2021 um 17:58 schrieb Toomas Soome via freebsd-current:

On 26. Feb 2021, at 18:54, O. Hartmann  wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

hello,

running a FreeBSD appliance on top of a PCengines APU2C4 with the latest seabios
(apu2_v4.13.0.3.rom). The PCengines boot image layout is based on pmbr/gptboot 
(GPT patition
scheme), via nanoBSD the latest pmbr/gptboot binaries are applied taken from 
the 13-STABLE
tree (or 14-CURRENT).

It doesn't matter whether I put these lines into /boot/loader.conf:

boot_serial="YES"
comconsole_speed="115200"

:
:
:


You are missing this one:
commit 61c50cbc096d28e44cb8b627e524ae58158c423a


Actually stable/13 is missing this.
It was merged to releng/13.0, but not to stable/13 as far as my git 
skills last:

https://cgit.freebsd.org/src/log/stand/i386/libi386/vidconsole.c?h=stable%2F13

Thanks,
-harry
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"