On most Linux desktop environment, it’s easy to browse your $HOME directory. On the MacBook Air running OS X, the link to the home directory is not listed on “Finder” on the left column.
To add it, do the following
– Open the terminal
– Type the following
$ open ../
– Finder should now be showing all Home directories
– Drag and drop the Icon to the left sidebar
-Enjoy! 🙂
After much trial and error, managed to get bluetooth AD2P profile on my Raspberry Pi which I then connected to my car auxiliary (aux) input. I followed the tutorial found here.
On the Raspberry Pi, I make the bluetooth in “Discoverable” mode and launch a bluez-simple-agent to make the initial connection.
$Â sudo hciconfig hci0 piscan
$bluez-simple-agent
On my phone, just after having launched bluez-simple-agent, I can scan and connect.
And once connected, I need to link the bluetooth source to the Raspberry Pi audio output
pactl load-module module-loopback source=bluez_source.XX_XX_XX_XX_XX_XX sink=alsa_output.0.analog-stereo
I can play any songs on my phone and it plays on the car speakers 😛
After 10 – 20 secs, the sound would stop playing. Looking into /var/log/syslog, i found this
Feb 1 06:39:48 raspberrypi bluetoothd[2208]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/HFPAG
Feb 1 06:39:48 raspberrypi bluetoothd[2208]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/HFPHS
Feb 1 06:39:48 raspberrypi bluetoothd[2208]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSource
Feb 1 06:39:48 raspberrypi bluetoothd[2208]: Endpoint unregistered: sender=:1.36 path=/MediaEndpoint/A2DPSink
I don’t know yet why it happens but if i run this command just after pactl load module, it works fine 🙂
$ pactl subscribe
Not that awesome. A direct AUX connection sounds much better. I can hear quite some background noise. Is it due to the raspberry sound card, the bluetooth adapter or just some configuration? I don’t know. Anyways, I got a working prototype for now.
Free from physical chains. We are celebrating today, the 1st of February.
Government can at any point in time, put someone in jail for having different opinions, definition of “freedom”.
We are bound by chains. Written by lawyers. All laws being equal. Some more equal than others allowing “Human Rights” to be suspended.
Common ‘literate’ people can’t even read 1 single paragraph of the “Law” or “Acts” or dunno what the fuck they’re called. Yet, we are governed by it. Punished by it. Rewarded by it. Allowed to live by it.
Freedom is education. Not brainwashing.
Hack whatever you get. Learn, research. “Society” will of course not approve that. What happened to Galileo Galilei?
Be a Galileo Galilei!
It was a long time dream to set up Arch Linux. After 5 years of using Ubuntu, Kubuntu, Debian Servers that I managed to learn enough to be able to try Arch Linux. As the rumours say, the latter is not for the faint heart. Just copy pasting Arch Linux beginner’s installation guide won’t make it happen.
Arch has a beginner’s guide which I tried to follow. It all seemed to work perfectly until I rebooted the laptop. The UEFI bootloader was loaded but Arch was not starting.
I retried but this time following a YouTube tutorial. And it worked with some minor modifications. As I said, you need to understand what you’re doing. Following any guide blindly will not guarantee success.
I was very much surprised at how easy it was to connect the Live Distro from USB to WiFi.
# wifi-menu
And just followed the dialogue box. Entered the WiFi password and there you go! But once you installed the OS on your drive, you gotta install
“dialog” and “wpa_supplicant” package. To do so, I live booted with the Arch USB. Once the command prompt opened
# wifi-menu // Connect to wifi
# mount /dev/sda2 /mnt
# arch-chroot /mnt /bin/bash
# pacman -S dialog wpa_supplicant
# exit
# reboot
When you reboot, you’ll be able to run wifi-menu locally. What I did above was use the Live USB as OS, connect to WiFi then make it believe that the filesystem it is currently working on has changed to /mnt which is pointing to /dev/sda2. Might seem confusing at first but with experience, it’ll become natural 😉
pacman is the package manager. On Ubuntu and Debian, we know the famous apt-get and openSUSE’s zypper.
# apt-get install package
# pacman -S package# apt-get remove package
# pacman -R package# apt-get autoremove package
# pacman -Rs package# apt-get update && apt-get dist-upgrade
# pacman -Syu
apt-get is much easier and verbose for the newcomers.
By default, you get only a command prompt when installed. I forgot which commands I ran to get KDE up and running.
# pacman -S xorg sddm plasma
That’s it for this blog post. Do try Arch in a VM or a test laptop ONLY if you’re beginner like me. Partitioning is done in CLI and can result is screwing your whole Hard Drive.
Happy learning 😀
It made me very sad to read this morning that one of the founders of Debian has passed away. Yep. the IAN in DebIAN.
Official reason for his death is not yet known at the time of writing. His contribution in the open source community is priceless. Thanks a lot for that Ian.
If ever some people caused your death prematurely, hope they… you guess the rest.