ms. My specific issue has nothing to do
with systemd or FreeDesktop.ORG. I want the external reference removed.
If it stays it will only create confusion and misunderstanding.
Thank you,
Tomas Fasth
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Koch skrev 2012-05-22 09:18:
> Hi,
>
> I'm not sure, whether I should ask here. I already wrote a mail to
Tomas Fasth
> some weeks ago (I believe, can't find it anymore). I'd like to fix some
of the
> issues
The Fungi skrev:
> On Fri, Sep 16, 2005 at 09:34:30PM +0200, Tomas Fasth wrote:
> [...]
>
>>Pathan is a library that implements XPath functionality in c++. It
>>is available both as a separate tarball as well as bundled with the
>>Berkeley DB XML sources provided by Sle
dbxml where the source include both
pathan and xerces (and berkeley db, and xquery; in the same source,
sic; talk about bloat).
Any advice is welcome.
--
Tomas Fasth <[EMAIL PROTECTED]>
GnuPG Fingerprint: DC7B 9453 7F26 1BF9 6B21 9F90 C187 7355 9FE8 D504
signature.asc
Description: O
Martin Pitt skrev:
> Hi Tomas!
>
> Tomas Fasth [2005-08-23 9:31 +0200]:
>
>>As a side note, I have myself thought about extending pbuilder using
>>unionfs and overlays to avoid the tarball extraction for each build.
>
>
> Indeed I referred to the overhead o
ide note, I have myself thought about extending pbuilder using
unionfs and overlays to avoid the tarball extraction for each build.
--
Tomas Fasth <[EMAIL PROTECTED]>
GnuPG Fingerprint: DC7B 9453 7F26 1BF9 6B21 9F90 C187 7355 9FE8 D504
signature.asc
Description: OpenPGP digital signature
Package: wnpp
Severity: wishlist
Owner: Tomas Fasth <[EMAIL PROTECTED]>
* Package name: libpathan
Version : 2.0beta
Upstream Author : DecisionSoft Limited <[EMAIL PROTECTED]>
* URL : http://software.decisionsoft.com/pathan2Info.html
* License
architecture hppa
/usr/bin/fakeroot debian/rules clean
/usr/bin/fakeroot: line 152: 7689 Segmentation fault
FAKEROOTKEY=$FAKEROOTKEY LD_LIBRARY_PATH="$PATHS" LD_PRELOAD="$LIB" "$@"
Is this a known problem?
Does it require any further action by me?
Thanks
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek skrev:
> On Tue, Aug 02, 2005 at 03:01:39PM +0200, Tomas Fasth wrote:
>> Andreas Barth skrev:
>>> * Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 13:41]:
>>>> And even then, appearently the DAM works like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Barth skrev:
> * Thijs Kinkhorst ([EMAIL PROTECTED]) [050802 13:41]:
>
>>And even then, appearently the DAM works like this: I approve person X,
>>let's check his box, but I'll add the account at some point later on (this
>>takes weeks on aver
Package: wnpp
Severity: wishlist
Owner: Tomas Fasth <[EMAIL PROTECTED]>
* Package name: sdparm
Version : 0.93
Upstream Author : Douglas Gilbert
* URL : http://sg.torque.net/sg/sdparm.html
* License : GPL / FreeBSD
Description : Change and displa
Package: wnpp
Severity: wishlist
Owner: Tomas Fasth <[EMAIL PROTECTED]>
* Package name: dbxml
Version : 2.0.9
Upstream Author : Sleepycat Software <[EMAIL PROTECTED]>
* URL : http://www.sleepycat.com/download
* License : Sleepycat License, BS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello
My name is Tomas Fasth and I'm a Debian Developer. I just recently
made a Non Maintainer Upload of rdesktop version 1.4.0. This was
done with the explicit consent from Sam Johnston, the current
maintainer.
Sam indicated in a letter to me
. The sooner it it emptied of
| system wide environment settings the better.
So exactly where, according to you, is the proper place for a system
wide default umask property, if not /etc/login.defs?
Regards
- --
Tomas Fasth <[EMAIL PROTECTED]>
GnuPG 0x9FE8D504
-BEGIN PGP SIG
the source. It (pam_limits) already
(conditionally) support things like Linux system capabilities.
Should be able to handle support for umask as well, preferably
upstream. I have sent the authors (redhat staff) a query.
// Tomas
- --
Tomas Fasth <[EMAIL PROTECTED]>
GnuPG 0x9FE8D504
-BEGIN PGP SIG
a result of careful and thorough
system design. Environment variables are excellent for tailoring
user space activities. Umask (ulimit, nice) is kernel business,
belong in it's data structures and therefore manipulated only
through system calls.
// Tomas
- --
Tomas Fasth <[EMAIL PROTECTED]&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Branden,
Branden Robinson wrote:
| On Sat, Oct 16, 2004 at 01:28:31PM +0200, Tomas Fasth wrote:
|
|> What I don't understand is why you think the umask preference
|> should be applied differently depending on the type of
|> inte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Branden Robinson wrote:
| On Thu, Oct 14, 2004 at 12:14:58AM +0200, Tomas Fasth wrote:
[...]
|> I believe that /etc/login.defs _is_ the right place to define
|> the default umask property.
|
| It feels wrong to me to make display managers selec
rallel (e.g., how long do wait after a failed
login before displaying the prompt/greeter again?).
I believe that /etc/login.defs _is_ the right place to define the
default umask property.
// Tomas
--
Tomas Fasth <[EMAIL PROTECTED]>
GnuPG 0x9FE8D504
19 matches
Mail list logo
