@scottalanmiller said in Debian File Server File Recovery:

@coliver said in Debian File Server File Recovery:

@dafyre said in Debian File Server File Recovery:

@travisdh1 said in Debian File Server File Recovery:

@stacksofplates said in Debian File Server File Recovery:

@dafyre said in Debian File Server File Recovery:

@stacksofplates said in Debian File Server File Recovery:

@wirestyle22 said in Debian File Server File Recovery:

We finally found the replication point and recovered the file. One thing I noticed working here is that the VM's are not named the host names. I looked for it for hours across all of our subdomains and could not find it. I had to go through each individual VM and eventually found it.

We still have some old Unix white beards that do this. It annoys the crap out of me. He just set up a server and called it Odin.....

That's all fine and good as long as odin.mydomain.net actually resolves to that actual server, lol.

Ya it just annoys me ha. Everything else is named by purpose.

Our one server... it got names Zues. Of course we knew it was going to be just the 1 server for the foreseeable future.

If you must use Planets, Greek gods, Mythical creatures, et al... Please make sure they are pselled correctly to avoid further confusion.

I don't understand the reason to do that over function. I'd much rather name a server WDS01 then Ptah01.

Potato01
Cauliflower7
Aubergine4

0_1492100279356_9660920a9d8c26fc005ebb1ca5f8dfe4.jpg

@Pete-S said in Xen Orchestra - Community Edition - Installing with Yarn:

@travisdh1 said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@travisdh1 what issue are you referring too? As far as I recall everything that is needed is included in the appropriate script install/upgrade

It's git, not the scripts. Since you need to have your git user information entered for it to work, would be good to have it added to the instructions.

I don't understand. Do you have to have a github account and be logged in to be able to download anything from github?

I can reach this without being logged in:
https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh

No you don't have to actually have an account, it's a git requirement to put something in there though and we don't autofill that information in case someone wants to supply their account details.

@scottalanmiller said in A quick settings question on Debian 2.x:

@art_of_shred said in A quick settings question on Debian 2.x:

@scottalanmiller said in A quick settings question on Debian 2.x:

Did it work?

Not confirmed yet, but I'll post when I know.

Thanks

From what I can tell, yes it worked. That's both the no sleep and no login password required.

@Dashrender said in Installing XiVO on Scale:

@scottalanmiller said in Installing XiVO on Scale:

@Dashrender said in Installing XiVO on Scale:

@scottalanmiller said in Installing XiVO on Scale:

0_1475526986064_Screenshot from 2016-10-03 13-33-00.png

I don't understand what it's asking - Numbers internal start/end Numbers interval start/end?

Yeah, it's is a multi-tenant system so it needs info about individual organizations that will be handled by the system. Threw me too.

OK well now I'm even more lost. Internal Calls context I took to mean the extensions of the phones in your facility - OK pretty straight forward, you're allowing for extensions 1000-2000, but what are InCalls Context? I have no idea what that even means?

Inbound calls and outbound calls respectively.

Context is an Asterisk term.

Remember, the issue is NOT a violation of the ZFS licensing, it is a violation (supposedly) of the Linux licensing. It is Linux being violated, not ZFS according to the FSF.

Codename: Init Freedom

I think Landscape does this plus a lot more. I think it's free for 10 physical and 10 virtual machines, but I don't know the cost after that.

There are some Juju charms that you can create a Landscape setup with pretty easily.

@scottalanmiller said:

For home laptop use (non-gaming) be sure to check out PC-BSD. It's screaming fast, super stable and very responsive.

In this particular article it was a solid, but not fastest, performer in the transcoding benchmarks they ran, which were about as close to web serfing and video watching. PC-BSD is the fastest bar none if you're compiling software or iops intensive workloads.

That's what I felt like, a full decade!! I really did feel like it was brand new when I started at CitiGroup, just a couple weeks before that. I was managing OF systems then.

Well... plug-in downloaded source, compiled, installed and activated.
In "Setting/Plugins" I can see now the "backup-reports" and "transport-email" plugins.
I made some simple test with "Backup Jobs" and all seems ok.

Thanks guys.

Maybe your package repo is out of date, I tried this just now on my Mint desktop and it worked fine... but the direct links that you show do not exist.

Try this then try the ppa add command again...

sudo apt-get update

@scottalanmiller said:

It's true, I'm a huge ARM fan.

I thought that about you...

@PSX_Defector said:

But FreeBSD came out AFTER 4.1BSD, which is where the great schism started. Next started their work on Mach/Darwin a few years before FreeBSD came about. There is plenty borrowed from FreeBSD but it's still running kernels that are nothing like FreeBSD.

Yes, the ported the Mach kernel to the FreeBSD ecosystem. But the bulk of the code is from FreeBSD, not from Next/Mach. The OSX project started long after both FreeBSD and Next were established. That Next was older isn't really a big deal. OSX was much later. At the time, around 1999, they made a big deal that it was mostly FreeBSD with the Mach kernel swapped out for the old kernel.

Not totally unlike the Dragonfly project. Based on FreeBSD but taking the kernel in a different direction.

@Breffni-Potter said:

But Soviet Russia will invade, We need to beat Al-Qaeda, ect.

They know they are attacking Americans. There can't honestly be any confusion about what they are doing.