Re: [gentoo-user] force re-cythonizing in an ebuild
On Mon, 18 Nov 2019 14:35:18 +0100, Helmut Jarausch wrote: > does anybody know how to force to recompile (by cython) any .pyx file. How about this? find -xdev / -name '*.pyx' | xarge emerge --oneshot --ask -- Neil Bothwick There are two kinds of people in this world: Those who are good with words, and those who are... erm... thingy pgpvn0psJOSd5.pgp Description: OpenPGP digital signature
Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]
On Sunday, 17 November 2019 20:35:33 GMT n952162 wrote: > On 11/17/19 16:06, Mick wrote: > > You keep top-posting and inverting the logical Q/A flow of this thread ... > > > > On Sunday, 17 November 2019 12:53:51 GMT n952162 wrote: > >> Ah, now I see. Yes, in that respect, that is, if you don't have a > >> chance to get /forcefsck written. > > > > Running fsck manually with various options and then trying to recover > > various superblock locations could get you farther than simply running > > fsck in an accepting fashion. > > Have you had any experience with this? I spent days search for that > superblock once, even writing a pgm to search for the magic number, > after working with dump2fs, and never got anywhere. I'd sure like to > hear that somebody had success with it. Yes, I vaguely remember using it in the past. Some heavy handed user pressed the power button, leaving the fs dangling. Through trial & error I found a backup superblock listed by dumpe2fs, which worked and allowed the fs to be accessed with minimal loss of data. I don't know if this would be the case under all eventualities. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] force re-cythonizing in an ebuild
Hi, does anybody know how to force to recompile (by cython) any .pyx file. Background I'm trying to install packages like sci-libs/scikit_image under Python3.8 Many thanks for a hint, Helmut
Re: [gentoo-user] power button to shutdown for openrc? [SOLVED]
On 17/11/19 20:35, n952162 wrote: >> >> Needless to say, you would not try this on the original partition, but a >> backup image you can create with ddrescue and friends. In any case, >> running >> fsck.ext4 -n (or -E nodiscard) should not cause any fs losses, unless the >> disk/hardware is faulty. Hence working on a backup image is the safest >> option. >> > > Thanks for the tip about ddrescue. I'll throw in another tip, about dm-verity. If you haven't met it, it's part of the block-management layer. It's new so I don't know much about it but I'm personally excited about its capabilities for raid recovery and stuff like that. Basically, on top of your block device you would create a dm-verity device. I don't know whether you can, but if you can't it needs adding - you want to create a device in corrupted mode where any read access will trigger a read error. As ddrescue copies your old device across it will reset the integrity layer. So when you go to read your device image, any attempt to read a successfully recovered block will be fine, any attempt to read a block that couldn't be recovered will trigger a read error. Cheers, Wol
