跳至主要内容

博文

目前显示的是 五月, 2020的博文

org2jeklly is changing... excerpt: Some change breaks my current workflow, and the workaround

publish failure in org2jeklly 0.25 Some time ago, I started using org2jeklly to publish my blogs. All went well until someday I did a package upgrade for all my emacs packages… My publishing start to fail, there's no markdown file produced after I run `M-x org2jeklly-publish`… There's `org-export-process exited abnorml` message in Message buffer. org-export-process exited abnormally issue Several hours of debug show that the "org-export-process" related issue was caused by there's no correct org asynchronous export setting. To fix it, add the following snippet to .emacs: (custom-set-variables '(org-export-async-init-file "~/.emacs.d/org-async-init.el" )) And create a "~/.emacs.d/org-async-init.el" with following contents: ( require ' package ) ( setq package-enable-at-startup nil) (package-initialize) ( require ' org ) ( require ' ox ) ( setq org-export-async-debug t) no markdown genera

Device excluded by a filter excerpt: pvcreate encounter an error on newly prepared hard drive

Device /dev/sdc excluded by a filter The title is one of the several issues I met when preparing new hard drives for my Linux Host. By looking at `/etc/lvm.conf` I am 100% sure that there's no filter setup. It turns out to be the Filesystem magic bits were remaining on my used harddrives which prevent the pvcreate command to run. Those magic bits won't be erased by `parted` tool. One must explicitly invoke `wipefs` command against the drive for magic bits cleanup. wipefs -a /dev/sdc Once did this, the `pvcreate` is happy processing the hard disk for physical volume creation.