Hi!
> > This is prototype of userland swsusp. I'd like kernel parts to go in,
> > probably for 2.6.16. Now, I'm not sure about the interface, ioctls are
> > slightly ugly, OTOH it would be probably overkill to introduce
> > syscalls just for this. (I'll need to add an ioctl for freeing memory
> > in future).
>
> I'm curious on the restrictions the userspace part would have to accept.
> Can /usr/swsusp.c write to a file? Currently, you allow it, but I doubt
No. Writing to file would trash the filesystem. But you can bmap the file,
then write to the block device.
> whether it would be wise to write to a file after you've snapshotted
> kernel's filesystem state. OTOH, I don't want to reserve a partition just
> for the image. Can userspace allocate memory after ioctl(SYS_FREEZE)?
Better avoid memory allocation.
> I have userspace supported encryption of the image in mind.
Yes, that should be feasible.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
