usly not Free in the Debian sense but I don't see any
reason why it shouldn't be in the non-free repo.
As Graham noted upthread, we do host our own .deb package repo -- but we only
have x86 packages, so it would make me very happy to see tarsnap be included
in Debian and built for other
hat we want under exactly the right conditions, in a
way which isn't possible with a high level tool which does everything.
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
; if that has any
meaning for debian.
On 07/04/11 01:38, Jari Aalto wrote:
> forwarded 632585 Colin Percival (upstream)
> thanks
>
> 2011-07-03 22:04 Sebastian Andrzej Siewior :
> | Package: bsdiff
> | Version: 4.3-10
> | Severity: wishlist
> | Tags: patch
> |
>
ately I haven't had the {time, money} to make the necessary
adjustments.
--
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lis
Tomasz K?oczko wrote:
> On Wed, 5 Jul 2006, Colin Percival wrote:
>> I moved FreeBSD's nologin to /usr/sbin two years ago, because
>> 1. nologin needs to be statically linked to avoid linker environment
>> security issues,
>
> Key word in this case is "avoidi
#x27;s no
reason for it to be on the root filesystem -- in single user mode,
users who aren't supposed to be allowed to login will never get to
the point of running a shell (nologin or otherwise).
In short, under the BSD hierarchy rules, nologin should be in /usr/sbin;
any systems behaving otherwise ar
Daniel Baumann wrote:
> Colin Percival wrote:
>>I don't think I need to explain the problem any further...
>
> Nevertheless, maybe you can give me a hint why you obviously don't want
> the text to be part of bsdiff?
I don't like having my work copied without my
7 matches
Mail list logo
