disk/prep (and it's mates) are what you need for sdC0. man 8 prep.
brucee
On 18 January 2014 17:57, Yoann Padioleau wrote:
> Hi,
>
> Can someone explain how the partitions in /dev/sdC0/xxx are populated? Who
> create those device files? I have a small plan9 kernel running a small
> shell (sh.Z
Hi,
Can someone explain how the partitions in /dev/sdC0/xxx are populated? Who
create those device files? I have a small plan9 kernel running a small shell
(sh.Z)
in memory and when I do 'bind #S/sdC0 /dev/' I just see the 'data', 'ctl', and
'raw' files.
There is no 9fat or plan9 or whatever pa
On Fri, Jan 17, 2014 at 12:07 PM, wrote:
> just disassembled some code generated by 6c
> and found something funny. the debugger seems
> to print the operands of MOVLQSX in the wrong
> order.
*db.c are notoriously out of date an almost all platforms. I spent a
good chunk of time fixing up ARM (a
On Fri Jan 17 15:09:33 EST 2014, cinap_len...@felloff.net wrote:
> just disassembled some code generated by 6c
> and found something funny. the debugger seems
> to print the operands of MOVLQSX in the wrong
> order.
there may be more of these. maybe if , were replaced with →
- erik
just disassembled some code generated by 6c
and found something funny. the debugger seems
to print the operands of MOVLQSX in the wrong
order.
output of 6c -S:
MOVLQSX BP,CX
ADDQCX,AX
RET ,
output of acid:
foo+0x1a 0x00200042 MOVLQSX CX,BP
foo+0x1d 0x00200045
