Same with -s option where you will select the target window with `xprop` command.
The pause/unpause is done by the `kill` command of course.
This title was not set by me.
4,309 karma · joined September 1, 2012
BLOG: https://vermaden.wordpress.com/ TWIT: https://twitter.com/vermaden
DESC: FreeBSD BSD UNIX Linux Backup Restore Storage Clusters Distributed Desktop Laptop X11 ThinkPad AMIGA Shell POSIX ZSH ZFS
Same with -s option where you will select the target window with `xprop` command.
The pause/unpause is done by the `kill` command of course.
This title was not set by me.
The `nice` (or also `idprio` on FreeBSD) will only lower the priotiry in the queue for CPU time, which means that if nothing else will need CPU it will still get as much CPU time as it wants, thus still eating battery time.
Works great on FreeBSD as well.
https://vermaden.wordpress.com/2018/06/28/freebsd-desktop-pa...
... and if Redshift seems too 'bloated' with too much dependencies there is OpenBSD style SCT - Set Color Temperature:
https://www.tedunangst.com/flak/post/sct-set-color-temperatu...
https://vermaden.wordpress.com/2018/04/06/introduction-to-ha...
The systemd implementation is just bad - http://without-systemd.org/wiki/index.php/Arguments_against_...
What about ip/ifconfig or netstat/ss?
Deprecating good old tools by rewriting them over and over again with new bugs and not covering full features of the original instead of improving the well tested tools.
https://www.freebsd.org/news/press-rel-1.html
FreeBSD can be several times faster then Linux when it comes to network stack:
https://pbs.twimg.com/media/CzFfTSRUQAATwaq.jpg
But often Linux is faster, you just need to find benchmark that favorites one or another, both are fast in general.
Yes, its currently little older, but they catching up ;)
> The FreeBSD website states that Wayland is not ready for general use. Wayland has been 'enabled' in many Linux distributions for years, but it took a long time to remove all the wrinkles.
I haven't used it, so I do not know how mature it is.
> I wonder: did you actually run a full GNOME desktop on Wayland on FreeBSD for a couple of months?
I run 'light' with openbox/tint/dzen and do not prefer Desktop Environments, besides, for me it does not matter if it runs on X11 or on Wayland as the end result is the same, but as I did not used Wayland I will stop with conclusions here.
> Linux is far more popular and most likely audited more as a result of that. So, it is not surprising that it has more CVEs. Also, the Linux kernel is a fair bit larger, supports more architecture, and more hardware, which means more surface.
Microsoft Windows is magnitudes more popular then Linux, yet it has less holes, so its not only popularity.
https://www.cvedetails.com/product/17153/Microsoft-Windows-7...
This was true until drm-next-kmod and drm-stable-kmod ports appeared. Now you have very similar Linux and FreeBSD graphics experience.
> This also means relatively limited support for Wayland, so you have to use X11, which is insecure.
Wayland is enabled by default since recently.
As we talk about security...
* Linux - Vulnerabilities (2103) - https://www.cvedetails.com/vendor/33/Linux.html * FreeBSD - Vulnerabilities (368) - https://www.cvedetails.com/vendor/6/Freebsd.html
About 7 times more on the Linux side, do not mix X11 into that :)
FreeBSD as every system has its limitations, that is for sure, but as I track its developments of the span of 15 years its just getting better and better, in all aspects - including desktop.
Of course there are 'environments' where its all or nothing like 'mobile', Linux has most of the market here with Android while FreeBSD has nothing.
As everything in our lives, some prefer Linux, some prefer FreeBSD, some OpenBSD, some macOS, etc.
> Systemd has the same problem iproute2 has: a learning curve of an integral part of the OS.
Its not the learning, its just broken and I will not waste my or your time to discuss this again. ;)
> As for snapshots, Windows, macOS, and Nix have that as well.
Can you boot from them and preserve fully working UNMODIFIED system after upgrade? Nope. That is the difference in ZFS Boot Environments.
I also used Mac OS X (it was called that way before it became macOS) and I also liked it, but I feel on FreeBSD more 'at home'.
Regards, vermaden
Yes, it takes more time to create your desktop then just install Elementary OS or Ubuntu where someone else made that for You, but once You have your configuration files, its similar experience.
On a new box You just install it, add needed packages and put your configs in the ${HOME} directory, same for FreeBSD, same for Ubuntu.
You will also 'lose' less time later since You will have bulletproof upgrades with ZFS Boot Environments (sysutils/beadm) and a lot more stable environment - no rush changes - no systemd - no ifconfig/ip problem - no netstat/ss problem - etc.
https://slideshare.net/anandology/ten-reasons-to-prefer-post...
Firefox with all blocking plugins takes regularly about 1.5-2.5 GB RAM on my machine, even with 5-10 tabs only.
I would like to see 13" model with full size keyboard (not the 11.6 one with crippled/squeezed keys) and at least Full HD screen.
Having 1366x768 resolution in 2018 is misunderstanding to say the least.
𝗨𝗣𝗗𝗔𝗧𝗘 𝟭 - 𝗦𝘆𝘀𝗩 𝗜𝗣𝗖 𝗶𝗻 𝗝𝗮𝗶𝗹𝘀
𝗨𝗣𝗗𝗔𝗧𝗘 𝟮 - 𝗦𝗲𝘁𝘂𝗽 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗦𝗼𝗰𝗸𝗲𝘁𝘀
> Lenovo's lightweight ThinkPad ticks all the boxes of a great work notebook.
Except one, keyboard.The ThinkPad 25 Anniversary Edition is the only real proffessional laptop available because it also has proffessionnal keyboard.
While 'dstat' gives some information its usefulness (at least for me) is far from 'gstat' outout.
These are 'gstat' and 'top -m io' commands, both I/O related.
Often in top/htop there is not much happening but the server is very slow, a lot of the times its because of I/O operations.
The 'gstat' command will tell You (besides other useful statistics) how much the storage devices are loaded:
# gstat
dT: 1.001s w: 1.000s
L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name
1 9679 9614 4807 0.1 63 671 0.2 82.3| ada0
0 0 0 0 0.0 0 0 0.0 0.0| ada0p1
0 65 0 0 0.0 63 671 0.2 1.4| ada0p2
0 0 0 0 0.0 0 0 0.0 0.0| ada0p3
0 0 0 0 0.0 0 0 0.0 0.0| gpt/boot
0 65 0 0 0.0 63 671 0.2 1.5| gpt/sys
0 0 0 0 0.0 0 0 0.0 0.0| gpt/local
0 0 0 0 0.0 0 0 0.0 0.0| zvol/local/SWAP
The 'top -m io' show which processes does how much I/O: # top -m io -o total 10
last pid: 51154; load averages: 0.31, 0.31, 0.28 up 3+18:01:00 14:58:15
54 processes: 1 running, 53 sleeping
CPU: 2.4% user, 0.0% nice, 15.3% system, 5.3% interrupt, 77.1% idle
Mem: 345M Active, 1236M Inact, 153M Laundry, 2158M Wired, 3903M Free
ARC: 834M Total, 46M MFU, 295M MRU, 160K Anon, 5006K Header, 488M Other
67M Compressed, 274M Uncompressed, 4.08:1 Ratio
Swap: 4096M Total, 4096M Free
PID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND
51021 vermaden 6005 16 6005 0 0 6005 99.92% dd
51154 vermaden 8 9 5 0 0 5 0.08% top
51036 vermaden 6 10 0 0 0 0 0.00% xterm
50907 vermaden 0 0 0 0 0 0 0.00% zsh
50905 vermaden 0 0 0 0 0 0 0.00% xterm
50815 vermaden 0 0 0 0 0 0 0.00% zsh
50813 vermaden 0 0 0 0 0 0 0.00% xterm
50755 vermaden 0 0 0 0 0 0 0.00% tail
41780 vermaden 0 0 0 0 0 0 0.00% leafpad
41255 vermaden 29 11 0 0 0 0 0.00% firefox
Another command that is very useful on FreeBSD is 'vmstat -i' which show how much interrupts are happening: # vmstat -i
interrupt total rate
irq1: atkbd0 75135 0
irq9: acpi0 2575929 8
irq12: psm0 135060 0
irq16: ehci0 1532065 5
irq23: ehci1 3265677 10
cpu0:timer 102772345 317
cpu1:timer 94199942 291
irq264: vgapci0 370466 1
irq265: em0 7017 0
irq266: hdac0 1904427 6
irq268: iwn0 148690342 459
irq270: sdhci_pci0 147 0
irq272: ahci0 20875039 64
Total 376403591 1161
I always suffer when I have to debug Linux systems because of lack of these commands.Regards, vermaden