Unless you already had loopback devices, this should give you a /dev/loop0 that corresponds to the whole “disk” and /dev/loop1 that is the filesystem (the part we want to expand). The 512 probably won’t change, but the start of the filesystem can and does change. The numbers (131072 and 512) must match the ones highlighted in step 3. First, we need to mount the image as though it were a set of disks: losetup -f -show -raspbian-jessie.img However, the filesystem won’t know about it yet. The base filesystem isn’t very large, so let’s make it bigger: dd if=/dev/zero bs=1M count=2048 >-raspbian-jessie.img The first partition is the boot partition and the second is the filesystem. I/O size (minimum/optimal): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id Type Sector size (logical/physical): 512 bytes / 512 bytes Here’s the output, with the important parts in bold: Disk -raspbian-jessie.img: 3.7 GiB, 3934257152 bytes, 7684096 sectors The command you want to run is: fdisk -lu -raspbian-jessie.img We need a few numbers from the img file and yours may be different than mine, depending on what you downloaded. You can then unzip it, to create an IMG file. Make a working directory and download a Pi image in zip format. Here’s how you install what you need: apt-get install qemu qemu-user-static binfmt-support Step 2. This combination will let Linux recognize alien executables and run them transparently. You need a static copy and the binfmt-support package. QEMU is the emulator that lets you run–among other things–ARM executables on the PC. Your PC probably has some sort of Intel processor in it. The method I’ll talk about works on Kubuntu, but should also work on most other Debian-based systems, including Ubuntu. For the most part, you should find the process similar. If you insist on using Windows, you can find a ready-to-go project on Sourceforge. Since I use Linux, I’m going to focus on that. Of course we would be delighted to see you build the Pi equivalent of the Tamagotchi Singularity but that’s a bit beyond the scope of this article. Or you just want to leverage your large computer to simplify development. This might be useful if you don’t have a Pi (or, at least, don’t have it with you). If you use Linux or Windows on your desktop, you can use QEMU to execute Raspberry Pi software virtually. There is, however, an in-between solution that has the added benefit of upping your skills: emulate a Pi on your desktop. However, sometimes you really need to run code on the actual platform. The converse of that is you can do a lot of development on a Linux desktop and then move things over to the Pi once you get the biggest bugs out. WoR-flasher has officially been tested using the 32-bit version of the Raspberry Pi OS (and that's what I used to create some install media, too), but it should run without issue on any Debian-based Linux distributions.One of the nice things about the Raspberry Pi is that it runs Linux and you can do a lot of development right on the board. Microsoft only sells licenses of the ARM versions of Windows to OEMs. The script's creator argues that it violates no laws or Windows licensing agreements since it downloads all its code directly from Microsoft's servers and installs Windows in an unlicensed, deactivated state, just as it would install on a regular x86 PC without a product key. WoR-flasher has a simple UI that can create ARM Windows install media, which can then be booted up on a Raspberry Pi for installation in the same way a USB stick created with Microsoft's tools can install Windows on an x86 PC. But if you're curious, a new script called "WoR-flasher" (that's Windows on Raspberry) simplifies the process. Installing the ARM versions of Windows 10 or Windows 11 to a cheap Raspberry Pi board has been possible for a long time but has always required more time and patience than it's worth.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |