Python 3.4 test image

[knc1]

I need the help of some people familar with Python to do some testing for me.

The requirements for the attachment here are:
An Intel cpu, Linux based computer, running a version 3.0 or newer kernel.

The attachment is for an Intel based machine, since the Kindles are a bit harder to use as test machines.

Although I am most interested in problems with this build of Python (since I am not a Python user), please report any problems here.

One time de-compression of the attachment:

core2quad images $ gunzip rootfs.ext3.gz

Mount the image and ready it to run;
Mount point names of user's choice:

core2quad new-i386 $ sudo mount images/rootfs.ext3 /mnt/kpw
core2quad new-i386 $ sudo mount --bind /dev /mnt/kpw/dev
core2quad new-i386 $ sudo mount --bind /sys /mnt/kpw/sys
core2quad new-i386 $ sudo mount --bind /proc /mnt/kpw/proc

Make the image the current root filesystem:

core2quad new-i386 $ sudo chroot /mnt/kpw sh

Try anything, but what I really need are people to check out the Python build.
I.E:

/ # python
Python 3.4.3 (default, Jul  8 2015, 08:48:25) 
[GCC 4.9.3] on linux
Type "help", "copyright", "credits" or "license" for more information.

Do whatever it is that Python users do.

>>> quit()

Exit from the file system test image:

/ # exit

Take down the test image:

core2quad new-i386 $ sudo umount /mnt/kpw/dev
core2quad new-i386 $ sudo umount /mnt/kpw/sys
core2quad new-i386 $ sudo umount /mnt/kpw/proc
core2quad new-i386 $ sudo umount /mnt/kpw

If more free space is required in the test image, with the file system image un-mounted:
The count=20 increases the file system size by 20M, use whatever size you need.

core2quad images $ dd if=/dev/zero of=rootfs.ext3 bs=1M count=20 oflag=append conv=notrunc
20+0 records in
20+0 records out
20971520 bytes (21 MB) copied, 0.0448278 s, 468 MB/s

Make sure the file system is clean:

core2quad images $ e2fsck -f rootfs.ext3
e2fsck 1.41.14 (22-Dec-2010)
rootfs.ext3: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs.ext3: 1063/1472 files (0.5% non-contiguous), 23874/28381 blocks

Now do the actual file system size increase:

core2quad images $ resize2fs rootfs.ext3
resize2fs 1.41.14 (22-Dec-2010)
Resizing the filesystem on rootfs.ext3 to 48860 (1k) blocks.
The filesystem on rootfs.ext3 is now 48860 blocks long.

[knc1]

The above build includes the CFFI Python module.
Ref: http://eli.thegreenplace.net/2013/03...types-and-cffi

The ability to directly use definitions from C header files makes forensic scripting for binary files much easier.

So anyone that can test out that module, please do.

[Li Mike]

AMD can you?

[knc1]

Originally Posted by Li Mike

AMD can you?

Probably, what do you want done?

I don't use Python, and there are a shit-load of optional modules in both the standard library and the general (?external?) modules.
Or whatever it is that the two sorts of external options are called in en_Python.

- - - - -

Whatever "set" of options get recommended here is what will end up in my next ARMhf set of add-ins (the first one did not include Python).