[DragonFlyBSD - Bug #1865] (Closed) Own DragonFly ELF brand name

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Sat Nov 27 08:41:55 PST 2021

Issue #1865 has been updated by tuxillo.

Description updated
Category set to Userland
Status changed from New to Closed
Assignee changed from 0 to mathias
% Done changed from 0 to 100

No longer the case, closing:

$ cat /proc/curproc/etype 
DragonFly ELF64

Bug #1865: Own DragonFly ELF brand name

* Author: matthias
* Status: Closed
* Priority: Normal
* Assignee: mathias
* Category: Userland
* Target version: 6.2

if you look at @/proc/<pid>/etype@/ on a common DragonFly system, you'll
see either "FreeBSD ELF32" or "FreeBSD ELF64".  Is there any real reason
why there is no "DragonFly ELFXX" ?

If no, what about the following patch: http://pastebin.com/HdA67VZW ?

Works fine here.


You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list