Want to learn how to cover all the #observability basics in your #DevOps role?
From #kubernetes to #VMs, #ePBF to #OTEL: check out the article from #Coroot co-founder Peter Zaitsev to learn how #FOSS can propel you from guessing to knowing the root cause of service issues: https://t.ly/VX3t4
Recently wrote about the old debate VMs vs containers: https://shivering-isles.com/2025/04/kubernetes-vms-vs-containers
And how I moved a lot of my #Kubernetes workloads from #Containers to #VMs without losing any of the benefits of Containers and Kubernetes.
#Video: #VirtualBox #Disk vergrössern.
Ist es dir auch schonmal so gegangen, dass die #virtuelle #Festplatte in #VirtualBox vollgelaufen ist? Genau das ist mir auch passiert und daher möchte ich dir in diesem Video erklären, wie du diese vergrössern kannst.
In der Welt der #Virtualisierung ist es nicht ungewöhnlich, auf #Speicherplatzprobleme zu stossen, insbesondere wenn man intensiv mit virtuellen Maschinen ( #VMs ) arbeitet.
Genetec, VMS oltre la videosorveglianza: Violazione della sicurezza perimetrale, furto o tentativo di accesso non autorizzato.La capacita’ di rispondere tempestivamente ed efficacemente a qualsiasi incidente...
#Genetec #sicurezzaperimetrale #VMS #protezioneprove #integritàdati http://dlvr.it/TKDJZH
The VMS Engineering See Figure 1 suggested software product report (SPR) response email, from 1982:
Suggested New SPR Wording, or We're VMS and You're Not.
VMS Version 3:
Please stop submitting SPR's. This is our system. We designed it, we built it, and we use it more than you do. If there are some features you think might be missing, if the system isn't as effective as you think it could be, TOUGH! Give it back, we don't need you. See figure 1.
---------------------------
! - !
! { } !
! | | !
! | | !
! .-.! !.-. !
! .-! ! ! !.-. !
! ! ! ! ; !
! \ ; !
! \ ; !
! ! : !
! ! | !
! | | !
! !
---------------------------
Figure 1.
Forget about your silly problem, let's take a look at some of the features of the VMS operating system.
1. Options. We've got lots of them. So many in fact, that you need two strong people to carry the documentation around. So many that it will be a cold day in hell before half of them are used. So many that you are probably not going to do your work right anyway. However, the number of options isn't all that important, because we picked some interesting values for the options and called them...
2. Defaults. We put a lot of thought into our defaults. We like them. If we didn't, we would have made something else be the default. So keep your cotton-picking hands off our defaults. Don't touch. Consider them mandatory. "Mandatory defaults" has a nice ring to it. Change them and your system crashes, tough. See figure 1.
3. Language processors. They work just fine. They take in source, and often produce object files as a reward for your efforts. You
don't like the code? Too bad! You can even try to call operating system services from them. For any that you can't, use the assembler like we do. We spoke to the language processor developers about this, they think a lot like we do, they said "See figure 1".
4. Debuggers. We've got debuggers, one we support and one we use. You shouldn't make mistakes anyway, it is a waste of time. We don't want to hear anything about debuggers, we're not interested. See figure 1.
5. Error logging. Ignore it. Why give yourself an ulcer? You don't want to give us the machine to get the problem fixed and we probably can't do it anyway. Oh, and if something breaks between 17:00 and 18:00 or 9:30 and 10:30 or 11:30 and 13:30 or 14:30 and 15:30 don't waste your time calling us, we're out. See figure 1.
6. Command language. We designed it ourselves, it's perfect. We like it so much we put our name on it, DCL-- Digital's Command Language. In fact we're so happy with it, we designed it once for each of our operating systems. We even try to keep it the same from release to release, sometimes we blow it though. See figure 1.
7. Real time performance. We got it. Who else could have donebsuch a good job? Sobthe system seems sluggish with all those priority 18 processes, no problem, just make them priority 1. Anyway, real time isn't important anymore like it used to be. We changed our group's name to get rid of the name realtime, we told all our realtime users to see figure 1 a long time ago.
In conclusion, stuff your SPR. Love VMS or leave it, but don't complain.
One of the lesser-known units of time measurement is the microfortnight.
The microfortnight unit exists in VAX/VMS because the console hardware clock interrupts used in the VAX-11/730 console measure elapsed time in a unitthat differs from a second. This hardware interrupt frequency choice affects timeouts related to console operations.
(Note: Once VAX/VMS is booted, things related to timekeeping and timers all work as expected, and seconds are a second in length. But when running the console program, not so much.)
This also led to the creation of the SD730 Fixed Head Solar Horologue option; a sundial intended to assist with tinekeeping.
Nu tu qrwa qrwa... Bando dar kažką šnekėt apie patogų ir kokybišką viešąjį 🤦♂️ Blet nuo žiedo antra stotelė ir vis tiek sugeba atvažiuot 4 min per anksti. Gerai, kad buvo išlipančių ir įlipančių, bo nebūčiau spėjęs atbėgt. Negana to, tai pasirodo bilieto pirkimo visas procesas per m.Ticket užtrunka ~5 min kol atsiranda app'se. Apie akmens amžiaus iOS interface'ą ant Android gal jau nesikartosiu...
🌘 VMS 的規模有多大？
➤ 追蹤 VMS 程式碼規模的演變
✤ https://vmssoftware.com/resources/blog/2025-03-31-how-big-is-vms/
本文探討了 VMS 作業系統的程式碼規模問題，作者追溯了過去 35 年來人們對此問題的疑問。透過統計 15 個代表性系統元件在四個不同版本 (V6.2, V7.2, V8.2, V9.2-3) 中的原始碼行數，作者試圖量化 VMS 的規模。 統計結果顯示，僅這 15 個元件的原始碼行數在 V8.2 到 V9.2-3 之間幾乎增三倍，且 C 語言程式碼的比例逐漸增加。 作者也觀察到不同元件的變更幅度不一，並鼓勵讀者分享對未來研究的建議。
+ 「這篇文章很有趣，能讓我更瞭解 VMS 這個老牌作業系統的複雜性。」
+ 「雖然數據只涵蓋了 15 個元件，但已經足以顯示 VMS 的規模和維護成本之高。」
#軟體工程 #作業系統 #VMS
Verkehrsverbund Mittelsachsen erhöht Ticketpreise für Bus und Bahn
#Bahn #Bus #Mittelsachsen #Nahverkehr #Preiserhöhung #Ticket #Ticketpreis #VMS #Verkehrsverbund #ÖPNV
Finally managed to perform my first legacy #VMS install from scratch with simh, tape distributions, fingers, eyeballs and my braincell. This included generating a standalone backup image from scratch & learning how to use that to list contents & eventually identify the filespec to use. I tried with several versions & tape images but it put up quite a fight. It took quite a bit of perseverance. So far I'd only installed from ISOs or using online guides, never entirely unassisted... Until now.
What do you miss in #Proxmox or #XCPng?
My customers often told me, that when migrating from #VMware based setups, they would miss something like #DRS. As a result I published #ProxLB as a load balancer. Now, I do the same for #DPM and also some other things. What do you miss or what stops you or your business from switching to Proxmox or XCPng?
#virtualization #hypervisor #cloud #vms #homelab #features #opensource #coding
Did I just do a #Markdown conversion of Mark Russinovich’s seminal 1998 article on #WindowsNT (and by extension, all modern versions of #MicrosoftWindows)’ debt to #DEC’s #VMS #OperatingSystem? Just so I could have a decent copy apart from the dusty carried-over archived version at https://www.ITProToday.com/server-virtualization/windows-nt-and-vms-the-rest-of-the-story ?
Why yes, yes I did. Why not?
Rustacean!
You want easy #VMs with a hypervisor you can contribute to?
#rust #virtualization #qemu
https://github.com/cloud-hypervisor/cloud-hypervisor
XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
You guys! I just got my #VMS Hobbyist License email!
I've always wanted to teach myself more about VMS. It's always impressed me in quite a number of ways.
Not least of which is the fact that it's really truly honest to god self documenting. The built in help system is seriously incredible. Deep and broad.
Not sure what I'll DO with it mind you, but I definitely plan to spin one up and run it. Maybe even connect it to the emulated DECNET if I get good enough at it :)
I don’t suppose anybody has had any luck running the Fender Tone app on Linux, perhaps in Wine or some such, and has written about it somewhere? I’m not finding much on the internets.
Hashtag smorgasbord:
#Fender #FenderTone #MusicProduction #Wine #VMs
It is a rare day. Rosenkrantz has been resetting to firmware so we bought another VAX 4000-60 to try sort it out and this one is the cleanest we've ever seen.
#retrocomputing #vax #vms #openvms #vintagecomputing #community
