Language:

en_US

switch to room list switch to menu My folders
Go to page: First ... 25 26 27 28 [29] 30 31 32
[#] Sun May 29 2022 13:48:14 UTC from darknetuser

[Reply] [ReplyQuoted] [Headers] [Print]

2022-05-28 12:48 from IGnatius T Foobar
Yeah, that'll be a pain in the neck to pull back apart after Broadcom,

like all of VMware's previous owners, realizes that it was a bad idea.




I was about to ask how profitable VMware is nowadays that containeritation is going everywhere else :-)

[#] Sun May 29 2022 13:50:46 UTC from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

Sort of odd question:

How do you bill for containers? With a VM its pretty easy. 'you get x resources, you pay me y dollars a month hosting fee". 



[#] Sun May 29 2022 20:02:18 UTC from zelgomer

[Reply] [ReplyQuoted] [Headers] [Print]

2022-05-29 13:50 from Nurb432 <nurb432@uncensored.citadel.org>
Sort of odd question:

How do you bill for containers? With a VM its pretty easy. 'you get x
resources, you pay me y dollars a month hosting fee". 


The container providers I've seen or used work the same way.

[#] Sun May 29 2022 20:18:18 UTC from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

For us "chargebacks"  to the agencies are important. We are in effect a 'hosting service' to them and they have their own budgets to pay for resource use.  ( or if they buy dedicated servers, but most have stopped doing that )

"hard" fees are of course the easiest, but when you are talking true shared resources, it gets harder. 



[#] Wed Jun 01 2022 14:25:27 UTC from DutchessMike

[Reply] [ReplyQuoted] [Headers] [Print]

I continue to use VMWare but for what I use it for (software development), there are other options.  I'm considering VirtualBox at the moment.

 



[#] Wed Jun 01 2022 20:12:12 UTC from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

kvm for the win. Both server and desktop. 



[#] Wed Jun 01 2022 21:30:26 UTC from zelgomer

[Reply] [ReplyQuoted] [Headers] [Print]

2022-06-01 20:12 from Nurb432 <nurb432@uncensored.citadel.org>
kvm for the win. Both server and desktop. 


Seconded. I've never used anything else but I like KVM so I'll ignorantly die defending it.

[#] Tue Jun 14 2022 06:14:02 UTC from darknetuser

[Reply] [ReplyQuoted] [Headers] [Print]

2022-06-01 17:30 from zelgomer
2022-06-01 20:12 from Nurb432 <nurb432@uncensored.citadel.org>

kvm for the win. Both server and desktop.


Seconded. I've never used anything else but I like KVM so I'll
ignorantly die defending it.



I have used Virtual Box on the desktop and while it was usable back in the day... if you are using Linux then KVM is just more convenient.

Also, what the Qubes distribution does with Xen is quite impresive. If you have the equipment necesary to run it you should check it out if just to see what they are doing.

[#] Tue Jun 14 2022 13:03:05 UTC from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

VirtualBox is the only one I find usable on my 'doze machine at work, because it has a NAT driver that masquerades as a userspace application. If I use anything else it gets blocked when I'm on the company VPN (which is pretty much always).

On a Linux machine, however ... nothing beats KVM.

[#] Sun Jun 19 2022 20:55:30 UTC from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

While im not fond of VB now ( especially after oracle ate them ), i agree on windows its one of the better choices you have.

I used to run it on Linux in the old days so i could have my 'shop supported windows vm', but got tired of things breaking every time a new kernel came out. And KVM was maturing about the same time.  Switched over, never looked back. On the server side, i was still using the free xenserver, but after i switched my desktop, that went out the window too. Both for consistency, and citrix was starting to pull features out of free.. Took a bit to redo things for my customers but it was worth the effort in the end. ( soon after that i moved servers to proxmox, instead of 'raw' kvm. )

On my personal machine at the office the only thing i lost was accelerated graphics inside the windows VM, but for my use case, that really didnt matter. Video was fast enough for the occasional training video we had to watch. ( now every week.. arrgh )

Tue Jun 14 2022 09:03:05 AM EDT from IGnatius T Foobar
VirtualBox is the only one I find usable on my 'doze machine at work, because it has a NAT driver that masquerades as a userspace application. If I use anything else it gets blocked when I'm on the company VPN (which is pretty much always).

On a Linux machine, however ... nothing beats KVM.

 



[#] Tue Jun 21 2022 15:37:16 UTC from LoanShark

[Reply] [ReplyQuoted] [Headers] [Print]


we've discussed that ad nauseum, but I got kinda fed up with VirtualBox. Went for native Linux boot / occasional dual boot. Never looked back. It's more difficult to set up on a laptop, satisfactorily anyway, but once you do it, it's the best way to get a *usable* Linux env--run Linux on the bare metal.

[#] Wed Jun 22 2022 20:15:00 UTC from IGnatius T Foobar

[Reply] [ReplyQuoted] [Headers] [Print]

Yeah. And I like it as a native environment anyway, so I might swap things around at some point and make Windows the virtual machine on top of Linux.
I'm going to be doing more stuff with our cloud team and their entire tool chain is Linux, so it might make sense. (Although the official setup guide specifies WSL2, and some really ugly hacks to make it work with our VPN, and an even uglier hack to make VS Code on Windows work inside the WSL2 filesystem ... at least one person on that team is running a real VM, and I am too.)

I just have to be sooper careful because I can't reload the machine if I brick it. Our internal IT people make you send the machine back to them and they cross-ship you a fresh one. I'm not willing to deal with that because my current machine is *way* nicer than the standard one, because it was all they could get at the time.

I think the procedure would go something like this:

1. Turn off Bitlocker
2. Create a recovery stick
3. Shrink the C: partition
4. Boot into Linux and "install alongside" Windows. I believe this means they share an EFI partition.
5. Boot the installed Linux. At this point it should be a dual boot machine.
6. Set up virtualization to run the Windows image, either directly from its old partition or by cloning it.

Cisco's really awful VPN client is probably going to throw a monkey wrench into the works, though.

[#] Wed Jun 22 2022 20:50:42 UTC from Nurb432

[Reply] [ReplyQuoted] [Headers] [Print]

Dude at work just got an M1 macbook.

Found out 1/2 of what he needs isn't native ARM yet.  Including fusion, so no VMs for him.

And from what i gather Linux is not ready ( since its all proprietary stuff, and of course Apple isn't forthcoming so its all manually reverse-engineered.. ) and no KVM support on the M1 anyway.



[#] Fri Jul 01 2022 21:43:11 UTC from zelgomer

Subject: Remote storage client-side encryption recommendations?

[Reply] [ReplyQuoted] [Headers] [Print]

Man this post has been a long time in the making. I keep writing giant life story posts and then trying to cut them down to something easier to swallow, then giving up, thinking about it for a few days, then making another attempt. I think I've finally narrowed my thoughts down to a single brief question:

What do you guys use for personal off-site backup? My requirements are something between 50-100GB, client-side encrypted, infrequent access (only need to update it maybe once or twice a month). I just want to satisfy the "-1" part of the "3-2-1" rule--3 backups, 2 local on separate media and 1 off-site. The problem is that it includes sensitive personal information, hence I want client-side encryption.

At the moment I'm leaning toward using dump/restore and piping it through gpg -c for symmetric encryption, then sending that to some VPS. If I go this route I think I will probably use the incremental feature; however, it doesn't track when files are renamed or deleted, so when I restore what I'll have is the union filesystem including every file name that ever existed. I suppose I can mitigate that by doing a new full backup once a year or so.

The other problem I'm grappling with is choosing and remembering the symmetric encryption passphrase. I already use a password manager so that I don't have to do this kind of thing, but the password manager database is included in this backup, so I can't rely on that (if I'm restoring from backup then that likely means my local password db is gone). I guess I will just have to accept having another password to remember. And if it's stored on a VPS then I will need to be able to access that without a password manager, too.

Any tips or experiences you would like to share here?

[#] Fri Jul 01 2022 22:21:17 UTC from Nurb432

Subject: Re: Remote storage client-side encryption recommendations?

[Reply] [ReplyQuoted] [Headers] [Print]

In the distant past i put a 1TB ARM NAS NFS export sort of device at my mother's place ( a SBC + USB drive..). A VPN connected it to my network here, to keep it easy and so transfers were encrypted. RSYNC my backup drive every so often to it.

 

Now i have a drive locked up at work. Bring it once a month or so to mirror my backup drive that is here at the house, which is a weekly mirror of an onsite 'working' backup ( so 3 levels deep ) the 2 'real' backup drives stay unplugged when not in use. All 3 are 8 TB drives.  The 'office copy' = full disk hidden partition via veracrypt.   Local copies, nothin. 

+ a every so often an extra RSYNC of my home directory to a 500gb m.2



[#] Fri Jul 01 2022 22:46:02 UTC from darknetuser

Subject: Re: Remote storage client-side encryption recommendations?

[Reply] [ReplyQuoted] [Headers] [Print]

What do you guys use for personal off-site backup? My requirements are

something between 50-100GB, client-side encrypted, infrequent access

(only need to update it maybe once or twice a month). I just want to

satisfy the "-1" part of the "3-2-1" rule--3 backups, 2 local on
separate media and 1 off-site. The problem is that it includes
sensitive personal information, hence I want client-side encryption.



For non system files or files that are not going to change during backup, then rclone may be workable since it features client-side encryption. You can use rclone to upload data to any standarized file storage service since rclone supports all the popular ones (such as ftp, sftp, webdav or whatever have you). Maybe you may try it with the Backbaze backup provider. I ran the numbers back in the day and they are a bit cheaper than operating your own NAS for small business use.

I am old school myself and just dump everything to a local hard drive. Then I move the drives off site in a van. Not fancy but it is kind of reassuring since everybody knows how the procedure goes XD

[#] Fri Jul 01 2022 23:34:11 UTC from Nurb432

Subject: Re: Remote storage client-side encryption recommendations?

[Reply] [ReplyQuoted] [Headers] [Print]

Last job i had where i was the CTO, that is what we did. Rotated 2 copies off site. Was in a deposit box at our bank.

My understanding is we use tape where im at now. Guy comes by once a week and takes them off site. 

Fri Jul 01 2022 06:46:02 PM EDT from darknetuser Subject: Re: Remote storage client-side encryption recommendations?

I am old school myself and just dump everything to a local hard drive. Then I move the drives off site in a van. Not fancy but it is kind of reassuring since everybody knows how the procedure goes XD

 



[#] Sat Jul 02 2022 00:15:10 UTC from zelgomer

Subject: Re: Remote storage client-side encryption recommendations?

[Reply] [ReplyQuoted] [Headers] [Print]

Maybe I'm over thinkig it but I kind of wanted something in the cloud or at least far from me so that in the case of a natural disaster it has a good chance of not being impacted. You might say "if you're ever caught up in a natural disaster your data will be the least of your worries" but I think of it more like in that situation anything you can save would be just that much less to replace or mourne.

[#] Sat Jul 02 2022 00:58:06 UTC from Nurb432

Subject: Re: Remote storage client-side encryption recommendations?

[Reply] [ReplyQuoted] [Headers] [Print]

What i used to do at my moms would work with a VPS too..   rsync will travel across SSH too ( i just wanted the VPN to avoid opening up incoming ports )

Or if you dont like rsync could just compress your stuff into a single file ( zip, tar, whatever ), encrypt then sftp it up to your VPS storage. ( could be done all via a script )

Fri Jul 01 2022 08:15:10 PM EDT from zelgomer Subject: Re: Remote storage client-side encryption recommendations?
Maybe I'm over thinkig it but I kind of wanted something in the cloud or at least far from me so that in the case of a natural disaster it has a good chance of not being impacted. You might say "if you're ever caught up in a natural disaster your data will be the least of your worries" but I think of it more like in that situation anything you can save would be just that much less to replace or mourne.

 



[#] Sat Jul 02 2022 01:02:39 UTC from Nurb432

Subject: Re: Remote storage client-side encryption recommendations?

[Reply] [ReplyQuoted] [Headers] [Print]

Random thought. Something like ipfs might work too.  ( https://ipfs.io/ )   



Go to page: First ... 25 26 27 28 [29] 30 31 32