Date: Thu, 29 Apr 1999 13:45:42 -0400 (EDT) From: Thomas Valentino Crimi <tcrimi+@andrew.cmu.edu> To: Emmanuel DELOGET <pixel@DotCom.FR> Cc: hackers@FreeBSD.ORG (FreeBSD Hackers Mail List) Subject: Re: Adding desktop support (please don't) Message-ID: <kr_9f6m00blN0So3A0@andrew.cmu.edu> In-Reply-To: <199904291323.NAA06412@excalibur.oceanis.net> References: <199904291323.NAA06412@excalibur.oceanis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Excerpts from mail: 29-Apr-99 Re: Adding desktop support .. by Emmanuel DELOGET@DotCom. > something else. In addition to icons, we could have a > generic way to handle any kind of ressources (dtd for usage > and so on). The dtd usage should definitely be in the ELF section (I doubt it would change on a per-user basis). So, definitely, lets not neglect what can be put in the ELF block.. One usefulness of keeping icons on the outside, as well, would be for datafiles. One could have a file(1)/mime based icon selection as well as icons given to particular long lived files (specialized project directories, whatever). ports could add in files for the data of particular packages, ghostscipt, lyx.. It's all up to how complex the db/libraries care to be. SPEAKING of which. Have any opinions been formed on the usefulness of capabilities? It'd be a major kernel hack, but this ELF section data would be very useful for holding such things, and an administrator could use it to selectively disable root-abilties of an SUID root executable according to policy, weird, but, if we were to every deal with capabilities (the REAL work), the interface ELF would provide would be fairly easy to implement and powerful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?kr_9f6m00blN0So3A0>