![]() ![]() Note that my information may be incorrect or incomplete for others: hence the advice about the clone and/or backup. I created my clones and backups using dd. The first step was to work with a clone, or at least have a good backup, of the source drive. (I could use GParted or the Disks utility to see whether the drive was GPT or MBR, a/k/a msdos.) (Later, I found that DiskGenius appeared to be able to achieve such conversions, in either direction.) There were potentially two necessary edits: first, remove any existing line(s) relating to the previous swap partition (or, if desired, comment it out by adding a # in front of it), and then add a line for the new partition, reading as follows: /swapfile none swap sw 0 0Īs indicated above, I ran free and swapon commands again after reboot, to confirm that the changes were permanent.Īs a possible final step, Linux Uprising ( 2018) suggested an additional step to prevent an unnecessary startup delay (of ~15-20 seconds) on a system that would be hibernated.Īs part of an effort (discussed in another post) to clone a larger Ubuntu USB source drive to a smaller one, it seemed that I might need to convert the source drive from GPT to MBR partition structure. This edit was necessary because the changes just described were effective only for the current session. The final command shown above invoked gedit to open the /etc/fstab file. I didn’t plan to run many programs from this installation, and therefore could probably get by with even less I might want to increase it for an installation with a different purpose. I observed that Ubuntu reportedly defaulted to 2GB in new installations, and that It’s FOSS (Prakash, 2021) offered a helpful table indicating that, since I didn’t plan to hibernate, my 8GB RAM suggested a 3GB swap space. Some argued that no swap was required some advocated the old rule of 1.5x to 2x the amount of RAM in the system, especially if the system was going to be hibernated some said that you could probably hibernate successfully even if swap was less than RAM and so forth. Why set swap space at 2GB? A Reddit thread illustrated the range of opinions on the question of how much swap space to allocate. ![]() Repeating swapon -s and free -h (now, and again after reboot, below) confirmed that, unlike the situation at the outset, there was now swap space in use, with a size of 2097148 bytes. The swapon command enabled the swap file. The mkswap command marked the file as swap space. Repeating the ls command showed (at left) the effect of the chmod command. (Not sure why 2.5 instead of 2.0.) The chmod command made the swapfile accessible only to the root user, so that other users would not have access to sensitive data that it might contain at times. Re-running df -h confirmed that, suddenly, I had 2.5GB less available space. The ls line confirmed the existence of a 2GB swapfile. I chose to allocate 2GB in that line for reasons discussed below. ![]() The fallocate line was a safer and simpler alternative to the dd command recommended by many sources. In the output from df -h, as a convenient alternative to GParted, I could look for the boot partition (/) line, to see how much space I had available for swap. I couldn’t use swapoff because swapon had not given me a specific device to turn off. Swapoff would turn off the current swap device if I had one. The free command was another approach to the same end: in my case, it indicated that my swap space was zero bytes. In my machine, there wasn’t, so it displayed nothing. The swapon command would display something like /dev/sda5 if there was an active swap partition. ![]() This post describes how, after the cloning process was finished, I replaced the swap partition with a swap file on the target drive.įor this purpose, various sources (notably Kumar, 2021, and Linux Uprising, 2018) recommended the following commands: swapon -s I'm running popOS on an 圆4 computer.As part of an effort to clone a large Ubuntu installation into a small target drive, I had deleted the swap partition. I'm a linux noob, any help is appreciated. Here is the which dotnet: /usr/bin/dotnetĪnd my echo path: /home/robinson/.nvm/versions/node/v18.7.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/robinson/.dotnet/tools 6.0.8 įrom my googling, it seems it may be PATH issue, but I tried adding a few different paths and it still didn't work. Here is my dotnet -info: global.json file: Here is what happens when I try to do an apt install of the sdk(It shows already installed): sudo apt install dotnet-sdk-6.0ĭotnet-sdk-6.0 is already the newest version (6.0.400-1).Ġ upgraded, 0 newly installed, 0 to remove and 1 not upgraded. I had the dotnet sdk working just fine yesterday, today when I login to my PC, I update the system and VSCode and then when I tried running dotnet watch run, I got this error: * You intended to execute a. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |