Many thanks! Yes, a static binary is perfectly fine at this time :) A
couple of follow-up questions, if y'all would please indulge me:
1. Now that I am reminded of this handy new `readelf` tool, I go
running it on the new static executable I just generated.
```
$ cat exit.s # repeating for your
On Fri, 14 Apr 2017, Kartik Agaram wrote:
> I'm trying out a simple Assembly program on a freshly installed "OpenBSD
> openbsd 6.1 GENERIC#291 i386":
>
> --- begin exit.s
...
> --- end
>
> This program assembles and links without error. However when I try to
> run it, I get this:
>
> $ as exit
First: Great work, everyone. Tons of ground got covered.
vmm seems to not be respecting the "owner" directive until after I shut the
VMs down. It's completely plausible I'm doing something wrong. I haven't
messed with vmm in -CURRENT since mid-January. I'm using 6.1-RELEASE right
now.
On the host
I'm trying out a simple Assembly program on a freshly installed
"OpenBSD openbsd 6.1 GENERIC#291 i386":
--- begin exit.s
#
https://web.archive.org/web/20120509101207/http://lucifer.phiral.net/openbsdasm.htm
#
# $ as exit.s -o exit.o && ld exit.o -o exit && ./exit
.section ".note.openbsd.ident
Shoot, that was the old dmesg. Here's the upgraded one:
OpenBSD 6.1 (GENERIC.MP) #20: Sat Apr 1 13:45:56 MDT 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1996152832 (1903MB)
avail mem = 1931038720 (1841MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
This e-mail is complementary to the one i sent at dm...@openbsd.org.
After the completion of the installation process, everything works except:
-screen brightness controlled by the keyboard
-suspend/resume when i close the lid
Both minor issues were resolved when i suspended the laptop from the
> On 04/14/17 09:21, Theo de Raadt wrote:
> >> AFAICS there is no way to build a release without upgrading the base
> >> system first, i.e. you have to have root privileges.
> >>
> >> To keep things simple, I wonder if it would be possible to use these
> >> privileges to avoid the noperm partiti
Hi Paolo,
Check before you post - it *is* in /etc/skel/.Xdefaults[0] :^)
[0]
http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/etc/skel/dot.Xdefaults?rev=1.3&content-type=text/plain
Regards,
Raf
On Fri, Apr 14, 2017 at 10:19:44AM BST, Paolo Aglialoro wrote:
> Wouldn't the inclusion of t
Wouldn't the inclusion of this config (e.g. in skel) account for sane
defaults?
On Fri, Apr 14, 2017 at 7:01 AM, Theo Buehler wrote:
> On Fri, Apr 14, 2017 at 11:45:05AM +0800, Adam Steen wrote:
> > Hi
> >
> > I used to start X using startx and when opening terminal my .kshrc
> > would get run,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/14/17 09:21, Theo de Raadt wrote:
>> AFAICS there is no way to build a release without upgrading the base system
>> first, i.e. you have to have root privileges.
>>
>> To keep things simple, I wonder if it would be possible to use these
>> p
> AFAICS there is no way to build a release without upgrading
> the base system first, i.e. you have to have root privileges.
>
> To keep things simple, I wonder if it would be possible to use
> these privileges to avoid the noperm partition?
noperm is now so well established, we have already forg
Hi folks,
AFAICS there is no way to build a release without upgrading
the base system first, i.e. you have to have root privileges.
To keep things simple, I wonder if it would be possible to use
these privileges to avoid the noperm partition?
Regards
Harri
12 matches
Mail list logo
