FrostyPolicy

joined 1 year ago
[–] FrostyPolicy@suppo.fi 4 points 6 days ago

Daily rsync to a local nas and weekly backups to offsite with pika-backup.

[–] FrostyPolicy@suppo.fi 11 points 6 days ago (7 children)

What would you call it instead?

We already have (had) Iceweasel, IceCat and Waterfox among others. All nice word plays on the original Firefox name. LibreWolf follows along the same path.

[–] FrostyPolicy@suppo.fi 2 points 1 week ago (2 children)

Wikpedia puts it nicely:

"The concept of concurrent computing is frequently confused with the related but distinct concept of parallel computing,[3][4] although both can be described as "multiple processes executing during the same period of time". In parallel computing, execution occurs at the same physical instant: for example, on separate processors of a multi-processor machine, with the goal of speeding up computations—parallel computing is impossible on a (one-core) single processor, as only one computation can occur at any instant (during any single clock cycle).[a] By contrast, concurrent computing consists of process lifetimes overlapping, but execution does not happen at the same instant. "

[–] FrostyPolicy@suppo.fi -4 points 1 week ago* (last edited 1 week ago) (6 children)

A cpu (core) can only do one thing at a time. When you have multiple cores you can do multiple things at the same time. Multitasking in programming sense is a bad term, it's a term more for the masses.

Bit simplified:

  • concurrency: you seem to be doing multiple things at the same time. In reality they are run little by little one after another. Doesn't really speed things up.
  • parallelism: you actually run multiple things at the same time (multiple cpus/cpu cores required). If the code scales properly or is designed to truly run in parallel the speed up is relative to the number of cpus available.

Edit: It's much more complex subject then I've presented here.

[–] FrostyPolicy@suppo.fi 9 points 1 week ago

Excellent article. That's why I use OSS first and foremost as they don't have the incentive to bring in € instead they are more focused on a quality product.

[–] FrostyPolicy@suppo.fi 2 points 2 weeks ago

It is against the GDPR.

[–] FrostyPolicy@suppo.fi 121 points 2 weeks ago (19 children)

In the EU this kind of automatic opting-in to marketing/data sharing is against the GDPR as it requires explicit consent from user/customer. I'm in the EU and have those settings but they were both toggled off, as expected.

[–] FrostyPolicy@suppo.fi 8 points 4 weeks ago (1 children)

I stand corrected. I use Tumbleweed so have not kept up to date on that front.

[–] FrostyPolicy@suppo.fi 59 points 4 weeks ago (2 children)

OpenSuse is already by itself a well rounded distro. It supports multiple desktops out-of-the-box, is highly customizable so it doesn't really need forks.

[–] FrostyPolicy@suppo.fi 18 points 4 weeks ago (3 children)

SUSE Linux Enterprise isn't really a fork. OpenSuse Leap is to SLE a bit like Fedora is to Red Hat i.e. the community version which is then frozen at some point to build SLE.

23
submitted 5 months ago* (last edited 5 months ago) by FrostyPolicy@suppo.fi to c/linux@lemmy.ml
 

I have on the host machine two network interfaces. One is lan and the other is a wlan. For libvirt I have created a nat network which is bound to the wlan. From the guest I can access other machines in the network host wlan is connected to. Also DNS lookup works. The problem is that there's no connection to the internet at all, e.g. pinging something gives "Destination network unreachable". ~~This only happens when both network connection on the host are active.~~ Running qemu/libvirt on OpenSuse Tumbleweed.

The nat network in question:

<network>
  <name>natToWlan</name>
  <uuid>a44c939c-e6bf-44d0-8f86-376056d418a4</uuid>
  <forward dev="wlp19s0f4u1u1" mode="nat">
    <nat>
      <port start="1024" end="65535"/>
    </nat>
    <interface dev="wlp19s0f4u1u1"/>
  </forward>
  <bridge name="virbr1" stp="on" delay="0"/>
  <mac address="52:54:00:1f:64:95"/>
  <ip address="192.168.100.1" netmask="255.255.255.0">
    <dhcp>
      <range start="192.168.100.128" end="192.168.100.254"/>
    </dhcp>
  </ip>
</network>
view more: next ›