In message: <[EMAIL PROTECTED]>
Bernd Walter <[EMAIL PROTECTED]> writes:
: On Sat, Mar 27, 2004 at 04:55:56PM -0700, M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > Bernd Walter <[EMAIL PROTECTED]> writes:
: > : I'm working on getting devd(8) usable for usb dev
Hackers--
I'm having major troubles upgrading my ports, and nearly all of them are related to
pthreads in some way or another. After trying to troubleshoot a lot of these
individually, I'm at the point of thinking I should redo my pthread libraries...it
seems like something's very messed up in
On Sun, Mar 28, 2004 at 01:31:03AM -0700, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Bernd Walter <[EMAIL PROTECTED]> writes:
> : On Sat, Mar 27, 2004 at 04:55:56PM -0700, M. Warner Losh wrote:
> : > In message: <[EMAIL PROTECTED]>
> : > Bernd Walter <[EMAIL P
Hi,
I have stuck with a problem with usb devices.
In case of FreeBSD 4.8, whenever a new USB device is attached to the system, no device
node is dynamically being created within the dev file system.
This is in contrast to the behavior there with FreeBSD 5.0 where a new device node is
being
Greetings,
A friend asked me to run some Linux source on FreeBSD. It simulates a data
pool management system he is using, and it includes a call msync(2) with
both the MS_ASYNC and MS_INVALIDATE flags. FreeBSD does not allow this.
(I tested it on my 4.8 system; I'll have access to a 5.1 system
On Sun, Mar 28, 2004 at 02:51:56AM -0800, jitendra pande wrote:
> Hi,
>
> I have stuck with a problem with usb devices.
>
> In case of FreeBSD 4.8, whenever a new USB device is attached to the system, no
> device node is dynamically being created within the dev file system.
>
> This is in co
In the last episode (Mar 27), Mark Terribile said:
> A friend asked me to run some Linux source on FreeBSD. It simulates
> a data pool management system he is using, and it includes a call
> msync(2) with both the MS_ASYNC and MS_INVALIDATE flags. FreeBSD
> does not allow this. (I tested it on my
Christoph P. Kukulies wrote this message on Sun, Mar 14, 2004 at 13:04 +0100:
> Some time ago I wrote a little program to scan a disk for the start of
> a FS. Unfortunately that program is also on the crashed disk :-O
Since you are on 4.8-R you can take a look at ffsrecov. I wrote this
program a
I had a hard drive failure. I'm trying to get as much data off it as
I can before I restore from backup. I have mounted the drive in
another box and I'm attempting to salvage what I can.
I thought I might be able to mark the bad sectors as bad, and get the
file system mounted.
Here is what fsk
On Sun, Mar 28 2004 (02:51:56 -0800), jitendra pande wrote:
> My application uses libusb for iinteracting with the usb devices...
> libusb on freeBSD 4.8 tries to find /debv/ugen0, /dev/ugen1 and so
> onhence couldn't able to detect more then one device.
...
> FreeBSD 4.8 and FreeBSD 5.0
Note
Hi,
I traced sshd using ktrace and it says:
..
10198 new CALL setuid(0)
10198 new RET setuid -1 errno 1 Operation not permitted
10198 new CALL execve(0x80485d0,0xbfbfed8c,0xbfbfed94)
10198 new NAMI "/home/new/new.pl"
10198 new RET execve -1 errno 13 Permiss
Please don't crosspost.
I don't think this is a topic for -current, so I've removed it.
On Mon, Mar 29, 2004 at 11:05:55AM +0900, Ganbold wrote:
> 10198 new CALL setuid(0)
> 10198 new RET setuid -1 errno 1 Operation not permitted
Your attempt to setuid(0) failed.
> 10198 new
On Mon, 29 Mar 2004, Ganbold wrote:
> Hi,
>
> I traced sshd using ktrace and it says:
> ..
> 10198 new CALL setuid(0)
> 10198 new RET setuid -1 errno 1 Operation not permitted
> 10198 new CALL execve(0x80485d0,0xbfbfed8c,0xbfbfed94)
> 10198 new NAMI "/home/ne
In the last episode (Mar 28), Sean Kelly said:
> On Mon, Mar 29, 2004 at 11:05:55AM +0900, Ganbold wrote:
> > 10198 new CALL setuid(0)
> > 10198 new RET setuid -1 errno 1 Operation not permitted
>
> Your attempt to setuid(0) failed.
>
> > 10198 new CALL execve(0x80485d0,0xbf
14 matches
Mail list logo
