On Fri, Nov 11, 2022 at 10:41:15PM +, r0ller wrote:
> Running 32 bit win stuff does not work with that.
I'm running 32-bit only WINE programs in a 32-bit NetBSD chroot
(using sandboxctl). It works okay:
https://washbear.neocities.org/wine-sandbox.html
>> My guess is that the buffer you're testing with is near the top of
>> the address space, within ~1GB of address 0x, and what
>> you're seeing is due to wraparound.
> Thanks for that analysis--address-wrapping was my first guess too,
> but, I didn't have the time to confirm it: the 1GB
On Mon, 14 Nov 2022, Mouse wrote:
My guess is that the buffer you're testing with is near the top of the
address space, within ~1GB of address 0x, and what you're
seeing is due to wraparound.
Thanks for that analysis--address-wrapping was my first guess too, but,
I didn't have the
On Mon, Nov 14, 2022 at 09:33:07AM -0800, Michael Cheponis wrote:
> *# scsictl sd1 format/dev/rsd1: device had unknown status 4*
Is there any other message (on console) ?
There are 3 cases that produce a 'status 4':
- "have short sense" (printed only with SCSI debugging)
- "passthrough: adapter
Jan Schaumann wrote:
> PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND
> 21048 nobody420 316M 14M parked 5:28 7.32% 7.32% httpd
> 17677 nobody420 318M 14M parked 5:25 6.69% 6.69% httpd
> 16398 nobody410 319M 17M parked
*# scsictl sd1 format/dev/rsd1: device had unknown status 4*
The dd trick seems to work only if the diskette is pre-formatted.
great suggestions, thank you. I'll keep whacking at this.
-Mike
On Mon, Nov 14, 2022 at 9:11 AM Michael van Elst wrote:
> michael.chepo...@gmail.com (Michael
michael.chepo...@gmail.com (Michael Cheponis) writes:
>I would think 'fdformat' would work, but...
>*arm64# ./fdformat -f /dev/rsd1
>*fdformat: Device `/dev/rsd1' does not support floppy formatting:
>Inappropriate ioctl for device*
Try 'scsictl sd1 format'.
> Or is UINT_MAX not guaranteed to fit in size_t
I _think_ there is no guarantee that UINT_MAX fits in a size_t. But,
upthread, I see...
> Turn out, on ARM, strnlen(3) is written in assembly and this always
> returns `maxlen' for any value of `maxlen' > ~1GB.
Not quite.
I have a guest login
On Mon, Nov 14, 2022 at 09:48:50AM -0500, Greg Troxel wrote:
> That's why it is harder to meet the spec than it first seems. C
> doesn't offer UB for such arguments, so it should be fixed. (I'm not
> asking anyone to do the work - just to agree it's broken.)
I am not sure it is broken, but how
Martin Husemann writes:
> On Mon, Nov 14, 2022 at 08:17:32AM -0500, Greg Troxel wrote:
>> I am not arguing against fixing the code to be sane. I am just raising
>> the other question about maybe strnlen needs fixing.
>
> "s + maxlen" (for most s) wraps around on 32bit architectures so the
>
On Mon, Nov 14, 2022 at 08:17:32AM -0500, Greg Troxel wrote:
> I am not arguing against fixing the code to be sane. I am just raising
> the other question about maybe strnlen needs fixing.
"s + maxlen" (for most s) wraps around on 32bit architectures so the
typical implementation will notice
I found 2 old amd64 floppy images from 2.0. No idea why I still have these:
-rwxr--r-- 1 andy andy 1474560 Nov 30 2004 boot1.fs
-rwxr--r-- 1 andy andy 1474560 Nov 30 2004 boot2.fs
Can you try writing a file of that size to one of those /dev/rsd files
using dd?
(The man page for
Martin Husemann writes:
> On Mon, Nov 14, 2022 at 01:22:54PM +0100, Marko Bauhardt wrote:
>> I configured to not use the system strnlen as you suggested. this works fine.
>> i'm able to fetch my mails.
>> THX!!
>
> The patch is the better solution, the length passed to strnlen is
> obviously
On Mon, Nov 14, 2022 at 01:22:54PM +0100, Marko Bauhardt wrote:
> I configured to not use the system strnlen as you suggested. this works fine.
> i'm able to fetch my mails.
> THX!!
The patch is the better solution, the length passed to strnlen is
obviously bogus.
Martin
> RVP hat am 14.11.2022 08:46 CET geschrieben:
hey rvp
you are the greatest! awesome.
> ...Turn out, on ARM, strnlen(3) is written in assembly
> and this always returns `maxlen' for any value of `maxlen' > ~1GB. > The fix
> is either:
>
> a) Configure isync-1.4.4 to _not_ use the system
I would think 'fdformat' would work, but...
*[ 1063553.609981] umass1 at uhub2 port 3 configuration 1 interface 0*
*[ 1063553.612982] umass1: TEACV0.0 (0x0644) TEACV0.0 (0x), rev
1.10/2.00, addr 3*
*[ 1063553.620984] umass1: using UFI over CBI with CCI*
*[ 1063553.621985] atapibus0 at umass1:
16 matches
Mail list logo
