How an e3 impact on cost. Less core higher freq. More cheap?

file names are just metadata in unix like OSes. when you create a file you can reference it by a number of file names. names include paths for the sake.

when you create an hard link you just increase by one the reference count of the pointers to a file content. hard links are nice but not necessarily the right thing. Maybe you just want a lightweight version of them, named symbolic link. among other things symlinks do not increase the ref count for a file.

basically now you are referencing a given file by 2 names.

more here(it is freebsd but applies to linux too)

Try to virtualize two of them and start with keeping them update, make them be aware of each other (via host name resolution) try generate and explort ssh keys, enter from one machine into another via ssh.
Maybe make one nfs server and try to mount nfs exports from the other machine.
If you have a nas also try to mount shares (even smb://)

More clear: xdg is a desktop standard. Any cmd line app will not mind about it. sym Links fix this.

@JaredBusch yes both work according to a standard in linux. I usually prefer symlinks because they are more transparent: it is a fs level thing not an app thing.

Honestly this seems more messy than symlinking imho

@scottalanmiller said in The Quintessential Linux Desktop Experiences:

@matteo-nunziati said in The Quintessential Linux Desktop Experiences:

still young but this is the reference kde now.

Not really. It's a secondary KDE bolt on to Ubuntu bypassing the mainline Kubuntu. openSuse remains the only major distro building with KDE in mind.

Yes opensuse is the only mainstream imho. But neon is no customization at all. Pure kde

Still prefer mate over xfce. But xfce is my home desktop and it is good.

Basically nowdays my daughter simply opens chrome. I always poke a lot with shell so any de is ok!

I worked on a gnome3 de. It was good but there was too much of win key to go around apps...

@travisdh1 said in Supermicro SuperServer E200-8D and E300-8D – review:

@DustinB3403 said in Supermicro SuperServer E200-8D and E300-8D – review:

@travisdh1 Yeah I saw that, which was why I was asking about it.

Just taking a quick look at the pricing, you can get those smaller Dell servers with 4 3.5" bays for less, at least in the US.

that's a main problem here in Italy. If you ask for a street price for dell or hpe you go cheeper then supermicro (and local SLA is better).

still young but this is the reference kde now.

@NashBrydges said in Best CRM tools:

I installed Odoo a few days ago with plans to go poke around in there but haven't had time to. Not so much just CRM but more of an ERP solution that includes CRM but if all you want is CRM, you can just install that module.

https://www.odoo.com/

It is open source as well.

https://github.com/odoo/odoo

+1 for odoo. Unfortunately it has almost no support in Italy.

We're moving to a local erp. Crm alone was not good and we have chosen to avoid to write connectors with other management apps.

just discovered this reseller they provide NBD support on selected EU countries for supermicro.
they also suggest you to buy spare parts for replacement like fans, power suppliers, hdd, in the while NBD passes... basically they replace your backup NBD, with the exception that if you lose the mobo or the raid controller you need to wait NBD.

@matteo-nunziati more accurate: VM can re-enter the host, the host can't re-enter in VMs. just double-checked.

@JaredBusch I run some production machines with macvtap/VEPA: they cannot talk with host or to each other but I'm too lazy and my env is small so it is ok.

I use this as:

• I do not need the VM to talk with the host via LAN
• everytime a VM has to talk to another VM I use internal virtual network to avoid virt2virt network traffic outside the host.
  this also allows me to contact the host via the internal LAN (which should be there on 192.168.100.0/24)
  
  [sorry details in Italian]

side note: what actually happens is than in a macvtap interface traffic can't re-enter the NIC: if you had 2 NICs, VMs on NIC1 can talk to other VMs or host via NIC2.

this should be ok for creating a bridge

None of these solves?

what a mess...

@scottalanmiller GOSH! the feature list is so small compared to a full windows that I was sure that was only the licensed stuff!

@scottalanmiller said in Open Storage Operating Systems for SAM-SD:

Why Windows?
Windows is, along with Solaris, the most expensive option on this list. Rather unique in being non-free. But with the excellent features that it provides for the right scenario it can easily be the best choice, especially if your needs are for SMB 3 support.

which feature set/role is required for a windows NAS? this is what comes with hyper-v server 2016 (which is free). also you can now put starwind free on it and get a free non supported OS/application.
[never used just asking out of curiosity]

@scottalanmiller said in SAM-SD Hardware Server Vendors:

@matteo-nunziati said in SAM-SD Hardware Server Vendors:

a concern about supermicro in Italy is the lack of onsite support.

In Italy that might be an issue. In the US they have onsite support.

so they seem great, considering the gear/price ratio!