Always wandering, always lost. Mostly quite happy.

 

LATEST POSTS

Go to Blog

Every Wednesday, I permit myself to have a day/half a day off to do anything that I want, as long as it's creative. This policy came from more than a year ago when I was my own boss, and I realised that I hated my boss. The exploitative bitch would not let me rest during weekends, yelled at me all the time, and didn't even pay me well.

The bitch and I had a conversation, and I told her that I would quit if she kept at it. I would find another boss, and she could get another minion. She gave me a long, steely stare. I stared back. Then, with a sigh, she asked me how she could improve my working conditions.

Wildcard Wednesday was then born. I could work my ass off every other day of the week, even weekends if I really had no choice, but Wednesdays were dedicated to gleeful creation and play. No work was allowed on Wednesdays, even though sometimes I sneaked an hour or two in (but never more than that). In the place of work, I made new dishes from scratch, played with my Snap Circuit renewable energy circuit board, and tinkered with random projects. I read books for leisure, doodled, and daydreamed.

It was really quite pleasant. My productivity went up during other days of the week. I gained some self-respect and balance. The inner bitch and I were friends again.

(As an aside, Wildcard Wednesdays drew inspiration from Awesome Mondays, devised by Eva and I when I was doing my PhD in Singapore. I always worked weekends, but on Mondays we would get a bottle of wine, some cheese and crackers, and whisk ourselves to a beach on Sentosa Island. We would set up our picnic on our matching sarongs, swim and laze around, get progressively tipsy, and then beat up coconut trees with beach towels. With all the vengeance directed at disappointing lovers, rejected publications, and a persisting fear of never amounting to anything important in life. Ah, Awesome Mondays.)

Wildcard Wednesday was shelved when I moved back into employment last year. Fast forward to this January, I left my job and am now my own boss again (at least until someone else pays for my time). I'm looking for research work, writing proposals for possible funding, and reading as much as I can. This time around, I'm not as crabby as before, since a year's detour into coordination and communication work served to confirm that I am really, ultimately, a researcher at heart, and that's where I want to work and play. The inner bitch is much less bitchy, and the reluctant employee, much less reluctant.

And, Wildcard Wednesday is back. The last few Wednesdays I had spent drawing mind maps of chapters in Sun Tzu's Art of War. Today I spent some of it reading up literature on resilience and systems thinking (ok this is kinda work), but I am also taking some time to write and to think. I'm looking forward to trying out a new recipe tonight, I haven't decided on what. When I close this post, I'll start browsing recipes.

It's a day like any other, but I have a glint in my eye, a smirk on my face. I'm inviting inspiration fairies to come plant ideas of mischief. The evening is still young. What shall we do, if we can do anything?

Screenshot at 2018-01-20 23-53-19

I'm adopting Leo's 8 year old Macbook Air from circa 2010, and its sluggishness provided the perfect excuse to tinker with Linux again. The hardware is still solid, and the specs are acceptable. The old boy has a few years more to go yet.

So from a few days ago I had been reading up on different distributions and then getting my hands dirty on the actual installation and customisations. After a few days of cracking my head on various seemingly trivial problems, I am finally at the stage where I am comfortable with my "new" computer, so I thought that I would jot down some notes for posterior's sake.

Choice of distribution

There are many. There is Ubuntu, which I tried several years ago and had a good experience with (but don't remember too much of), but I was afraid that it may be too bloated for the old machine. And then there are LXLE, Elementary OS, and Linux Mint that I had heard about that seemed to be viable alternatives.Ubuntu required 2 GB of RAM, Elementary OS 1GB, and LXLE only 500MB.

Eventually I decided to try out Elementary OS first. Elementary OS looked sleek and elegant at first glance, but soon started to get on my nerves. The language keyboard did not work, and keyboard hot keys did not make sense (I couldn't figure out how to switch between windows when an Alt-Tab or CMD-Tab should do the job). The localisation was very messy - when I tried to use the Chinese version to see if the language input worked, some items on the country menu were translated, some were not. Also, on top of that, there was something annoying about the interface being so simplistic, I felt that it was bordering on patronising. And that it called itself elementary in lower case just felt pretentious.

So I decided to try LXLE on Virtual Box. Somehow I took to it quite immediately - the desktop gave you everything that you needed on dropdown menus, neatly organised into applications and files. There was even a button that when you pressed it, it gave you a random wallpaper, which tickled me to no end. As if it was so efficient in its interface that it even found the space to give you that trivial functionality. The OS also came pre-installed with numerous applications, such as Libre Office, Mozilla SeaMonkey (first time I'd ever used it), and other nifty stuff.

I never made it to Mint. I decided to ditch Elementary, and go with LXLE.

LXLE: Installation problems

This was where my problems started with LXLE. I created a live USB, and LXLE worked fine when I booted from it. However when I tried to install it it would always break down at the very last bit, saying that "the 'grub-efi-amd64-signed' package failed into install into /target/", and that without the "GRUB boot loader" the installed system would not boot. The gibberish level of this one is just too high. I tried reinstalling it, same error message. I created the installer medium again, it didn't work. I tried installing an earlier, beta version of the .iso file, nope. I suspected that something was amiss with UEFI (now I know what it is, it's like BIOS but superior) but nope my system does support it, and the partitioning was done correctly.

Eventually through some hours of research I found an application called Boot Repair and I ran it on the system - it said something about lacking a 64-bit something (bear with my non-techie specificity), and so I tried to make another installer which was 64bit (previously I had used the 32-bit version), and this time it worked. That took about five hours of banging my head against the wall, and I finally made it at 2am.

Leo agreed that my stubbornness is useful sometimes.

Chinese/Japanese Input

So I went to bed, and this morning upon waking up I went straight to the computer and started working again. I must say that I quite like the LXLE interface, things are placed where they should be, and that gives me pleasure. The language input methods did seem to work at first glance, but I quickly realised that Pinyin was not available and I  don't know how to use the other ones. I tried ibus, I tried Fcitx. Neither gave me Pinyin. The organisation of LXLE on its language settings is also a little strange, as it was a little fragmented, spread over "Languages", "Ibus Preferences", "Fcitx Configuration", "Input methods"... and sometimes you have to restart after making some changes so that the input method options would show up. Patient trial and error was my friend.

Eventually I installed ibus-pinyin through Terminal (sudo does make me feel powerful) but for some reason it gave me Sun-Pinyin instead, which only had Simplified Chinese, while I prefer using Traditional Chinese. I poked around some more, and finally after restarting the computer I found Pinyin. I installed Japanese-Anthy through Terminal as well. I am now using Mozc as the Japanese input method. For the time being I am sorted, language-wise.

Installing applications

I realised that I don't actually use that many applications. What is indispensable to me is just Dropbox, and KeepassX. Seamonkey was pre-installed so I just started using it as the default browser. In the beginning I thought that I would have to do everything through Terminal, which made me nervous, but eventually I found the pre-installed Lubuntu Software Centre (a little like App Store) which made things much easier - and even for other command-line installations it was usually just short lines of code that I could copy and paste. I don't remember how it was in Ubuntu.

The Power Button

Having gone through the previous hurdles I was starting to feel confident, and decided to tackle one more important problem. The power button on the Macbook Air triggered an immediate shut down, no questions asked, and this is very dangerous since you could lose your work if you accidentally press it when you were pressing the Delete button, or your cat could trigger it easily when it is walking on your keyboard (which is not an infrequent happening in my household).

This little endeavour proved to be much more difficult than I thought it would be. I was instructed to download and install dconf Editor, which I did, with just a faintest idea of what it was - and I started to tinker with it, but I couldn't find this thing called gnome setting daemon. What's gnome? What's a daemon? Later on I found that there's this other thing called "Mate" which seems to be a similar something as Gnome, even though nothing happened after I changed the values in the dconf Editor. I was getting a little too far out of my depth.

In the midst of all this despair I sent a distress call to Pellaeon. While waiting for his reply, Leo helped me with a hack that I found online (this one) which instructed us to modify a certain logind.conf file, which stopped the immediate shutdowns, even if I felt a little insecure about changing some code that I had no idea about, since it might cause problems later on. We left the cafe, somewhat triumphant, and I collapsed into a deep sleep when we arrived home.

When I woke up, I saw that Pellaeon had replied my messages in a superbly comprehensive manner. I copy his explanations here for future reference:

  • GNOME is the name of the "desktop environment", it includes supporting programs for the desktop (such as drawing the windows outlines and toolbars), many basic functionalities (such as the system settings tool and text editor)
  • in the linux world, GNOME and KDE are the two major desktop environments
    they have the most development resources
  • They are also modular, so parts of them may be re-used by other projects
  • the LXDE reuses many parts of the GNOME desktop environment
  • LXDE and MATE are also desktop environments, they reuse parts from GNOME but combine them in different ways, so the interface looks different
  • "daemon" is basically a program constantly running in the background, for some service, imagine it as a shop that waits for customer 24h
  • in contrast to daemons, the applications are only opened by users while they need it and closed while they don't, such as your browser, documents editor, etc
  • daemons and applications are both programs
  • to build a desktop environment, many daemons are needed, for example, there is a daemon handling power button, lid open/close, power plug/unplug events
  • the daemon is called "dbus", it is the de facto desktop event handling daemon, used by both GNOME and KDE, and of course most of all the desktop environments
  • dconf stands for "dbus configuration" if i'm not mistaken, so dconf-editor is a editor to change dbus configurations
  • beside power change events, dbus also handles most of the desktop-related events , such as wifi scans, enable, disable, headphones/mic plug/unplug, device plug/unplug, keyboard layout management, printing, etc
  • it is basically a "message hub", it receives notifications of some event (such as power button press" and rewrite/block/re-broadcast the notifications to programs that "subscribes" themselves to the event
    org.gnome.settings-daemon is the name of the configuration value that decides the behavior when you press the power button
  • the configuration values are grouped in a hierarchical fashion
  • under "org.gnome" are all settings related to GNOME, and under settings-daemon are the configurations related to the GNOME settings daemon
  • so for example, the KDE settings are likely under "org.kde"
  • the problem with these configuration knobs is that, the paths/names may change from version to version
    LXDE might simply follow the settings of “org.gnome.settings-daemon.plugins.power” , or they might decide to use their own settings under "org.lxde.xxx.yyy.zzz"
  • so for your error message, it cannot find the path org.gnome.settings-daemon.plugins.power, there might be 2 possibilities:
    1. the org.gnome.settings-daemon.plugins.power knob have moved to some other path in your version of GNOME (that your version of LXDE is using)
    2. LXDE simply has its own knob somewhere
    or:
    3. LXDE doesn't allow you to customize the power settings behavior at all
    Can you try this? https://askubuntu.com/questions/568957/how-to-shut-down-lubuntu-immediately-with-the-power-button-instead-of-a-logout-m

So we undid the hack, and installed the XFCE Power Manager (as per the link sent by Pellaeon) which provides a GUI for all the tweaking to happen. I am very satisfied with the outcome.

Current Status

I'm still having to get used to Hotkeys that are a little different from what I had in Mac OS, but all in all everything works like a breeze. I like the task bar, which Mac OS didn't have, which I didn't know that I missed. I like the different work spaces as they're laid out more intuitively than in Mac. There are small things that I still need to tweak, such as the volume buttons on the keyboard not working anymore, but those are not high priority.

Using LXLE now somehow brings me back to perhaps 15 years ago when I was tinkering with my first computer, when things crashed, and working with the PC had some element of learning and risk when you didn't know what you were doing, but 硬着头皮 did it anyway. Nowadays everything works and you don't even think about it anymore.

I think I'm going to enjoy my new old computer :)

What is the purpose of having lots of input, if there is no output?

There hasn't been much time for introspection, but some thoughts have occupied my mind lately. There is an itch that I am longing to scratch, but every time I sit down in front of the computer I'm distracted by something. An email that I really should have written three days ago. Social media. Random YouTube videos. And I forget to scratch that itch. It grows, and eats at me.

It has become increasingly obvious. I am consuming too much, and creating too little. Interesting information flow through my brain, I am able to recall only fragments. I feel overwhelmed by all the stuff that come through, but don't have a structure that I can put them into, to digest and later search for. I imagine a filing system within my brain that doesn't work, with papers covering every available surface, the desk, the couch, even on top of the lamp shade. I'm standing in the midst of this mess, looking longingly at the cover pages and the unfinished drafts and I'm completely paralysed with what to look at first, because THERE IS JUST TOO MUCH.

Deep breath. You can do it. First take the bunch of papers off the lamp shade, and let the light shine through.

The solution, it seems, is to allocate time for output. The past two years I have set targets for number of books to read, and although those targets were always missed I did manage to read a good number of books (46 books in 2016, and 15 books in 2017, not counting the half-read ones). That was a progression from the realisation that I was consuming too much junk material online. I was also able to write reviews for all of the ones that I read, so there was some processing involved after the reading. But, the time allocated for consumption far outweighed the the time allocated for processing or creation.

With the number of unread books that are creeping onto my bed stand, my coffee table and my book shelves, it looks like I will never have the time to finish all that, not to mention make anything out of it. This has become a source of deep-seated anxiety. I want more time. I can never get more time.

This year, call it a resolution if you will, I will focus on balancing quality consumption, and creation. Note that I didn't put "quality creation". That is possibly for next year. This year, let's start with creating something, anything. We can't refine something that hasn't been created. This year, let's give time to creativity, imperfection, and play. Gleeful learning and unapologetic geekiness. Making things because, why not.

So here are the plans:

There will be no more piecemeal reading of non-fiction. I will group my readings and go at them with specific questions and ideas that I have in mind. Let's call it themed reading. I will take notes, draw mind maps, and in the end consolidate what I've learnt and main takeaways, and produce notes or sketches. Here are the topics that have interested me in the past few months:

  • Digital economy (gig economy, robotisation and dehumanisation, cryptocurrency)
  • Geopolitics (mainly between China and USA)
  • Brainworks (how the brain learns, the importance of sleep, effects of social media on the brain)
  • Art (the point of it, how to interpret art, art history)
  • Strategical thinking (Go, war strategies)
  • Living better (cleaning and decluttering, eating better, minimalism)

Language learning will continue, but will be output-oriented. I sometimes feel that language learning is also like pure consumption to me, even if there is more processing involved than just eating blindly. Maybe I enjoy it too much for it to seem like actual work, but there's also this nagging feeling that I could be retaining much more if I get more serious about those grammar drills and all the unread Japanese and Spanish books on my shelves. So here are some things that may help:

  • Note-taking while reading, translations and summaries on important ideas
  • Essay-writing/short story writing
  • Systematic grammar drills followed up with reading books in target language

I was thinking of going on but perhaps two main points are enough, for the time being. Better keep it simple, and just follow the main idea: allocate more time to process and create, and less time to read and watch mindlessly. I will report back.

----

P/s.

Just stumbled upon this video on Facebook, whose ability to read my mind continuously astounds me. Lisa Bu recommends "comparative reading", which is a useful concept to accompany my "themed reading". Maybe this can be applied on fiction!
;

`