IRC channel logs
2025-02-25.log
back to list of logs
<Arsen>Pellescours: well linux is also implementing VPNs and disk encryption in kernel <Pellescours>yeah but why exposing the implementation to userspace? <Arsen>presumably offloading or such? <youpi>Arsen: offloading to the kernel is useful when it's the kernel that needs the result, not when it's userspace that needs it :) <youpi>you mean non-cpu encryption chips? <youpi>on x86 at least it's the cpu that provide the accelerated support for encryption <damo22>userspace can have cpu cycles too :P <ZhaoM>youpi: 'remap /bin/sh /bin/bash -- ls -lha /bin/sh' gave me <ZhaoM>-rwxr-xr-x 1 root root 1.3M Feb 16 17:57 /bin/sh <ZhaoM>/bin/settrans: fsys_goaway: (ipc/mig) server died <ZhaoM>Receive SIGILL when try to step over 473 <youpi>yes , it's expected: after the ls command finished, the translator exited <youpi>you can try to run /bin/bash instead and run ls in it <youpi>that's it yes, with pfinet instead of lwip. Probably you don't actually need to give it a /dev/eth0m actually, so probably can skip that part <Pellescours>if I have a disk image I want to mount, I know how to use storeio to create a "loop" device, but how do I mount the partition? Do I need to know the offset or is there a mechanism (a translator?) to mount the partition N? <youpi>you can tell storeio to offset into a partition <youpi>see e.g. showtrans /dev/wd0s1 <youpi>/hurd/storeio -T typed part:1:device:@/dev/disk:wd0 <Pellescours>I made : settrans --create -- /dev/loop9s1 /hurd/storeio -T typed part:1:file:@/root/test.img <Pellescours>I know that after the --create I can add a -gap, but I even if I add it it doesn’t work (but it works if I try to access to the whole disk) <youpi> settrans -ca disk /hurd/storeio -T typed file:disk.img <youpi> settrans -ca disk1 /hurd/storeio -T typed part:1:file:disk.img <youpi>this is what I had documented on the 64bit port page <youpi>I don't see why you added an @ ? <youpi>for the device type it's just to provide the master port to be used <Pellescours>because it was for wd0, I don’t know what is the effect of @ <Pellescours>I still have the Device size reported to be zero… emitted by mkfs.ext2 (I’m on debian hurd 32bit) <Pellescours>Ah my bad, actually it worked (once I fixed the image name)