Hello Sirs at OpenBSD
this brief report is not a proper “bug”, but definitely a drawback to be taken
into account for new users: I tried everything possible but cannot make the
OpenBSD installation work on my laptop through a burned USB drive (3 GB).
Description:
- the system where I burn the
On 2019/06/06 12:03, ravi new wrote:
> Hi all,
>
> I am using OPEN BSD 5.6. It was installed on VM and pf.conf modified with
> new rule which passes traffic from internet to client running on 8080 port.
> Everything is working fine.
>
> But ,Same openbsd 5.6 installed on physical hardware with tw
nd relinked manually. I'm
not attaching them to this because obviously they're too big but here's the
relink.log:
drogo# cat /srv/broken-20190606/kernel/GENERIC.MP/relink.log
(SHA256) /bsd: OK
LD="ld" sh makegap.sh 0x gapdummy.o
ld -T ld.script -X --warn-common -nop
Unrelated to my other syspatch email, I ran syspatch inside a chroot (same
server so ignore the identical hostname) and this happened:
drogo# syspatch
Get/Verify syspatch65-002_srtp.tgz 100% |*| 4316 KB
00:04
Installing patch 002_srtp
Get/Verify syspatch65-003_mds.tgz
On Thu, Jun 06, 2019 at 10:18:46PM +0300, cho...@jtan.com wrote:
> Unrelated to my other syspatch email, I ran syspatch inside a chroot (same
> server so ignore the identical hostname) and this happened:
>
> drogo# syspatch
> Get/Verify syspatch65-002_srtp.tgz 100% |*| 43
Antoine Jacoutot writes:
> That is because 001 only includes kernel object files which you do not have
> since you run under a chroot and didn't extract /usr/share/relink/kernel.tgz
> So syspatch(8) considers you don't have that "set" installed.
> syspatch-003 on the other end includes a header cha
On Fri, Jun 07, 2019 at 02:49:32AM +0300, cho...@jtan.com wrote:
> Antoine Jacoutot writes:
> > That is because 001 only includes kernel object files which you do not have
> > since you run under a chroot and didn't extract /usr/share/relink/kernel.tgz
> > So syspatch(8) considers you don't have th
