Heiko Wundram (Beenic) wrote:
Hey all!
I'm currently working on a project using zlib and bzlib, and I'm currently
slightly stomped by the fact that both define the input buffer in their
stream structure as non-const.
I think they're not defined as const just to maintain
compatibility with ol
Michael W. Lucas wrote:
Hi,
Runing -current i386 as of February 19.
Tried to use an ath wireless on my laptop, it wouldn't associate using:
# ifconfig ath0 ssid GoAway wepkey 0xdeadbeef1234567890deadbeef wepmode on
Set "wlandebug scan+auth+assoc", got the following in
/var/log/messages. (I'v
On Thu, Feb 21, 2008 at 10:29:40PM +0100, Bartosz Giza wrote:
> Hi,
>
> I have found quite interesting feature on one of router that lately i have
> taken to administer.
> What i knew was that file /var/run/dmesg.boot holds data from kernel buffer
> that is taken right after file system(s) are m
Hi,
I have found quite interesting feature on one of router that lately i have
taken to administer.
What i knew was that file /var/run/dmesg.boot holds data from kernel buffer
that is taken right after file system(s) are mounted.
Lately i have found that one router writes to this file data from
On Feb 21, 2008, at 2:09 AM, Oliver Fromme wrote:
Actually I don't plan to use a bitblit function at all,
because it's not really feasible in standard VGA modes.
What do you mean by that?
Maybe we have different understandings what bitblit means.
My understanding is that bitblit is a raster
[EMAIL PROTECTED] wrote:
> ari edelkind <[EMAIL PROTECTED]> writes:
> > Keep in mind that ptrace(PT_ATTACH,...) will fail if a process is
> > already being traced. As for core files, a process can use
> > setrlimit(RLIMIT_CORE,...) to disable core dumps, and individual memory
> > pages may be encr
Dag-Erling Smørgrav wrote:
> ari edelkind <[EMAIL PROTECTED]> writes:
> > Keep in mind that ptrace(PT_ATTACH,...) will fail if a process is
> > already being traced. As for core files, a process can use
> > setrlimit(RLIMIT_CORE,...) to disable core dumps, and individual memory
> > pages may
On Thu, Feb 21, 2008 at 10:53:15AM +0100, Heiko Wundram (Beenic) wrote:
> Before I go and test whether bzlib modifies the input buffer for temporaries
> (by simply passing it data in a RO segment and checking whether I get a
> SIGSEGV), is there anyone out there who's hit the same "problem" befor
ari edelkind <[EMAIL PROTECTED]> writes:
> Keep in mind that ptrace(PT_ATTACH,...) will fail if a process is
> already being traced. As for core files, a process can use
> setrlimit(RLIMIT_CORE,...) to disable core dumps, and individual memory
> pages may be encrypted or unloaded, to be decrypted
"Thiago Damas" <[EMAIL PROTECTED]> writes:
> And if you make a wrapper, and execute like a shell script:
>
> #!/usr/local/bin/mysecyritywrapper
> <...encryted code goes where...>
>
> In this way. it'll be hard to use truss, ktrace, strace etc...
Uh, no, not at all. Not even a little. Hint: 'kt
Hi,
Runing -current i386 as of February 19.
Tried to use an ath wireless on my laptop, it wouldn't associate using:
# ifconfig ath0 ssid GoAway wepkey 0xdeadbeef1234567890deadbeef wepmode on
Set "wlandebug scan+auth+assoc", got the following in
/var/log/messages. (I've trimmed to 100 lines, th
hello
i am using OpenBSM on System with jails
part of praudit output / action write file in jail
--
header,176,10,open(2) - write,creat,trunc,0,Thu Feb 21 13:45:06 2008, +
501
msec,argument,3,0x81ed,mode,argument,2,0x601,flags,path,//site/svn/de
Cristian, good day.
Thu, Feb 21, 2008 at 01:57:08AM +0200, Cristian KLEIN wrote:
>> Yes, please, try the mentioned patch and report back ;))
>
> Sorry for the really long delay.
No problems ;))
> The patch works perfectly on my Fujitsu-Siemens V5545.
Thanks for the report! Norikatsu already k
Marcel Moolenaar wrote:
> On Feb 20, 2008, at 12:08 PM, Oliver Fromme wrote:
> > By the way: Will the standard i386 /boot/loader work
> > on an EFI machine, or does it require a different loader
> > binary?
>
> It needs a different loader. If you want to support EFI
> the right way, it als
Hey all!
I'm currently working on a project using zlib and bzlib, and I'm currently
slightly stomped by the fact that both define the input buffer in their
stream structure as non-const. Generally, I'd assume that the input buffer is
never changed (by any of the compression/decompression functi
On Wed, Feb 20, 2008 at 01:44:42PM -0800, Marcel Moolenaar wrote:
>control over everything. On top of that, we can't use any
>code in the loader from the kernel, so whatever support we
>add, we need to add to the kernel too.
We can't re-use the same executable bytes but, with care, we
should be ab
16 matches
Mail list logo
