Guilherme Cardoso luminoso
| $ # Use Live CD to boot | |
| $ sudo su # Switch to root | |
| $ fdisk -l # Get names of root, boot & EFI partition names. you can also use blkid | |
| $ mount /dev/mapper/fedora_localhost--live-root /mnt # mount root partition | |
| $ cat /mnt/etc/fedora-release | |
| Fedora release 31 (Thirty One) | |
| $ mount /dev/nvme0n1p2 /mnt/boot # mount boot partition | |
| $ mount /dev/nvme0n1p1 /mnt/boot/efi # mount EFI partition | |
| # Note: If you are not able to mount EFI partition ('Input/Output error'), | |
| # You may have to repair ESP file system or format ESP. |
These are the steps I followed enable VirtualBox on my laptop without disabling UEFI Secure Boot. They're nearly identical to the process described on [Øyvind Stegard's blog][blog], save for a few key details. The images here are borrowed from the [Systemtap UEFI Secure Boot Wiki][systemtap].
- Install the VirtualBox package (this might be different for your platform).
src='https://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo'
| ::########################################################################################################################## | |
| :: | |
| :: This script can ruin your day, if you run it without fully understanding what it does, you don't know what you are doing, | |
| :: | |
| :: OR BOTH!!! | |
| :: | |
| :: YOU HAVE BEEN WARNED!!!!!!!!!! | |
| :: | |
| :: This script is provided "AS IS" with no warranties, and confers no rights. | |
| :: Feel free to challenge me, disagree with me, or tell me I'm completely nuts in the comments section, |
| #!/usr/bin/env python3 | |
| # Combining coroutines running in an asyncio event loop with | |
| # blocking tasks in thread pool and process pool executors. | |
| # | |
| # Based on https://pymotw.com/3/asyncio/executors.html, but this version runs both | |
| # threads and processes at the same time and interleaves them with asyncio coroutines. | |
| # | |
| # All appears to be working. | |
| # |
Note: This guide may be slightly outdated. It may be still useful for older releases, but nowadays the vast majority of releases are correctly tagged as WEB-DL (unless it's RARBG/rartv). Protip: prefer looking at file names instead of release names, as they tend to be more accurate.
This is a short cheatsheet to help you determine whether a release from Amazon, Hulu, or Netflix contains the lossless/untouched (as in no further loss of quality compared to what the streaming services provide) video/audio or not. Most newer P2P releases are correctly tagged, but for older releases, it cannot be reliably determined based on the tags alone.
In most cases, non-lossless rips from these services are screen captures (which, when done by professional releasers, should be high quality and contain little to no glitches – see the history section for details), but in some cases they may be simply reencoded from the untouched stream, for example to crop black bars or reencode from a
Python docstrings can be written following several formats as the other posts showed. However the default Sphinx docstring format was not mentioned and is based on reStructuredText (reST). You can get some information about the main formats in that tuto.
Note that the reST is recommended by the PEP 287
There follows the main used formats for docstrings.
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |