looking
Monday, February 2 2015
SystemD 2015
[16:47:22] matt [wronka.org]/Psi+ http://ma.ttias.be/whats-new-systemd-2015-edition/
Unix: Do one thing well.
SystemD: Why do one thing, when you could be doing other things as well?
I'm not a huge fan of SystemD, in fact, I was considering switching back to FreeBSD for my home workstations to avoid it. However, there were some points in the notes on the 2015 roadmap which might actually be useful for the specific usecase I have for GNU/Linux.
Booting a standard GNU/Linux distro with a read-only root (e.g. from NFS) is frustrating; it doesn't work well, and even though many of the caveats are documented around the Web, it seems like there's always something that doesn't quite work. FreeBSD, for what its worth, booted diskless quite nicely when I was comparing the two about two years ago. In the end, I went with USB boot images for each node at home.
Looking at the roadmap, the 2015 plan for SystemD seems to be moving towards a system which is better designed for read-only root by default, which would be neat, and hopefully mean once the system is configured, bitrot would be less of an issue.
[16:47:22] matt [wronka.org]/Psi+ http://ma.ttias.be/whats-new-systemd-2015-edition/
Unix: Do one thing well.
SystemD: Why do one thing, when you could be doing other things as well?
I'm not a huge fan of SystemD, in fact, I was considering switching back to FreeBSD for my home workstations to avoid it. However, there were some points in the notes on the 2015 roadmap which might actually be useful for the specific usecase I have for GNU/Linux.
Booting a standard GNU/Linux distro with a read-only root (e.g. from NFS) is frustrating; it doesn't work well, and even though many of the caveats are documented around the Web, it seems like there's always something that doesn't quite work. FreeBSD, for what its worth, booted diskless quite nicely when I was comparing the two about two years ago. In the end, I went with USB boot images for each node at home.
Looking at the roadmap, the 2015 plan for SystemD seems to be moving towards a system which is better designed for read-only root by default, which would be neat, and hopefully mean once the system is configured, bitrot would be less of an issue.
Monday, August 11 2014
[23:08:08]
matt [wronka.org]/Lilith
Looking at the diagrams on the Lytro Web site for the Illum camera, it actually looks quite nice, with both a manual zoom and a manual focus ring.
Wednesday, May 2 2012
Tizen
[03:59:28] matt [wronka.org]/Psi.generay Looking at the Tizen site, the first thing I looked at was the devices page which contains no devices, but target platforms (Smartphone, In-Vehicle, Tablet, Netbook); it reminds me of MeeGo 18 months ago.
I look forward to Nokia's next platform 18 months down the road, for Smarphone, In-Vehicle, Tablet, and Netbook devices.
https://www.tizen.org/devices
[03:59:28] matt [wronka.org]/Psi.generay Looking at the Tizen site, the first thing I looked at was the devices page which contains no devices, but target platforms (Smartphone, In-Vehicle, Tablet, Netbook); it reminds me of MeeGo 18 months ago.
I look forward to Nokia's next platform 18 months down the road, for Smarphone, In-Vehicle, Tablet, and Netbook devices.
https://www.tizen.org/devices
Friday, July 9 2010
[00:29:44]
matt [wronka.org]/Merch
Jamie upgraded her EeePC yesterday from Karmic to Lucid. It went surprisingly smooth, although the EeePC ACPI scripts packqage is apparently broken (depends on ACPI-base or some other packqage is apparently broken (depends on ACPI-base or some other packqage that's not there, and wireless was broken. Looking on the webs; I found various people people saying that it didn't work out-of-the-box with "fixes" ranging from ndiswrapper to pulling source from version control. The latter seemed odd as it'd been working in Karmic. Finally a poster indicated that his problem was caused by the wireless card being disabled in the BIOS .... sure enough, rebooting and looking in the BIOS config it turned out that was what happened, oddly.