TEHRAN (Tasnim) – The SARS-CoV-2 virus that caused the COVID-19 pandemic did not emerge naturally, but rather "from a US lab biotechnology," according to renowned economist and policy analyst Jeffrey Sachs. According to a report published in Russia Today, Sachs' remarks came at a conference hosted by the Spanish think tank the GATE Center in mid-June. The former director of The Earth Institute at Columbia University negated the results of the World Health Organisation (WHO)-China Joint Mission on Coronavirus Disease, The Tribune reported. The WHO had said on June 9 that its latest investigation into the origins of COVID-19 was inconclusive, largely because data from China was missing, another blow to its years-long effort to determine how the pandemic began. However, Sachs has claimed that as he chairs the COVID-19 commission at the prestigious medical journal, The Lancet, he had more information on the matter. “It is a blunder, in my view, of biotech, not an accident of a natural spillover,” he said. “We don’t know for sure,” he said, but nonetheless held that there was “enough evidence” to posit a further probe into the matter, even though it is “not being investigated, not in the United States, not anywhere.” It may be noted that earlier in May, Sachs, together with Neil Harrison, had published an article that called for “an independent inquiry into the origin of the SARS-CoV-2 virus. It alleged that “that there is much important information that can be gleaned from US-based research institutions, information not yet made available for independent, transparent, and scientific scrutiny.” On June 10, CBS News reported that the WHO is recommending in its strongest terms yet that a deeper probe is required into whether a lab accident may be to blame.

by Jeremy 'Jay' LaCroix Overview In a previous article, I showed you how to build your very own Nextcloud server. In this article, we're going to extend the storage for our Nextcloud instance by utilizing block storage. To follow along, you'll either need your own Nextcloud server to extend, or perhaps you can add block storage to a different type of server you may control, which would mean you'd need to update the paths accordingly as we go along. Block storage is incredibly useful, so we'll definitely want to take advantage of this. Let's begin! Setting up the block storage volume First, use SSH to log in to your Nextcloud instance: ssh If we execute df -h, we can see the current list of attached storage volumes: df -h One of the benefits of block storage, is that you can have a smaller instance (but still have a bigger disk). Right now, unless you're working ahead, we won't have a block storage volume attached yet, so create one within the Linode dashboard. You can do this by clicking on "Volumes" within the dashboard, and then you can get started with the process. Fill out each of the fields while creating the block storage device. But pay special attention to the region - you want to set this to be the same region that your Linode instance is in. After creating the volume, you should see some example commands that give you everything you need to set up the volume. The first command, the one we will use to format the volume, we can copy and paste that command directly into a command shell. For example, it might look similar to this: sudo mkfs.ext4 "/dev/disk/by-id/scsi-0Linode_Volume_nextcloud-data" Of course, that's just an example command, it's best to use the command provided from the Linode dashboard, so if you'd like to copy and paste - use the command that you're provided within the dashboard. At this point, the volume will be formatted, but we'll need to mount it in order to start using it. The second command presented in the dashboard will end up creating a directory into which to mount the volume: sudo mkdir "/mnt/nextcloud-data" The third command will actually mount the new volume to your filesystem. Be sure to use the command from the dashboard, the one below is presented only as an example of what that generally looks like: sudo mount "/dev/disk/by-id/scsi-0Linode_Volume_nextcloud-data" Next, check the output of the df command and ensure the new volume is listed within the output: df -h Next, let's make sure we update /etc/fstab for the new volume, to ensure that it's automatically mounted every time the server starts up: Go to Full Article

Everywhere Hotspots: Train Robberies in Los Angeles. Click here to read more...