After the eclipse, I’m sure that everyone will have a welding glass to try this with!
A couple of months ago, a former co-worker called me and asked if I would provide a reference for her in a job search (which I readily agreed to). Then she went on to ask me this, “This company wants to make me an offer and they called and asked me what I currently make, and asked for a copy of a paystub. What should I do?”
Personally, I find this question stupid. I’ve been asked it many times (including quite recently) and in all instances I’ve been surprised by it (doh!) and I’ve answered in what I now consider to be the wrong way.
Every hiring manager has a range of salaries that they are willing to pay for a position, and they have a range of bonuses, a range of stock options and other incentives. And then there’s the common incentives that everyone gets (401(k), vacation, …). So why even ask the question? Why not make an offer that makes sense and be done with it?
If you are a hiring manager / HR person on the hiring side, do you ask this question?
If you are a candidate, how do you handle this question?
In any event, here’s what I recommended to my friend, answer the question along these lines.
- I’m sure you are asking me this so you can make me a competitive offer that I’ll accept
- I’m also sure that you have a range for all the components of the offer that you intend to make to me; base pay, bonus, stock options, …
- So what I’ll tell you is what I am looking for in an offer and I’ll leave it to you to make me an offer based on the standard ranges that you have
- I am looking for a take-home pay of $ _____ each month
- Since you offer a 401(k) plan which I intend to contribute $ _____ to, that means I am looking for a total base pay of $ ______ per year.
- I am looking for a total annual compensation of $ ______ including bonuses
- In addition, I am looking for ______ days of vacation each year.
That’s it. When asked for a copy of current pay-stub or anything like that, I recommend that you simply decline to provide it and make it clear that this is not any of their business.
Now, whether one can get away with this answer or not depends on how strong your position is for the opening in question. Some companies have a ‘policy’ that they need this paystub/W-2 stuff.
Not providing last pay information and following their ‘process’ could make the crabby HR person label you ‘not a team player’ or some such bogus thing and put your resume in the ‘special inbox’ which is marked ‘Basura’.
In any event, this all was fine and my friend told me that she was given a good offer which she accepted.
How do you approach this question?
I agree with four of the five; I am not so sure about the raise the ISO thing.
No matter how many articles I read about Photoshop, I always end up learning something new.
This article about HSL is no exception.
This blog post is dedicated to Sean McGinnis, the PTL of the OpenStack Cinder project. If you are an OpenStack type, you should really follow him on Twitter and read his blog which he promises to spruce up.
IRC is the lifeblood of communication and collaboration in many open source ecosystems, like OpenStack.
One of the biggest issues in working in this environment is that IRC is inherently an asynchronous communications mechanism and if you aren’t on IRC, you aren’t plugged in.
A bouncer is a simple app that will keep a connection open to the IRC network and allow your device (phone, laptop, tablet) connect and disconnect at will, and easily catch up on what you missed.
There are many other ways to accomplish this, some leave an emacs session running on a machine and connect to it remotely. Whatever floats your boat.
But, you need a place to run this solution, I run mine on a Raspberry Pi.
To install and configure ZNC (my bouncer of choice) on my Raspberry Pi, I use this diskimage-builder element. (https://github.com/amrith/rpi-image-builder/tree/master/elements/rpi-znc)
Using this element is very straightforward, it is a dependency from rpi-generic and you can follow the simple image building tutorial here. Since I enable the log module on ZNC, I run my Raspberry Pi with a read-only MicroSD card and a writable root file system on a USB Flash Drive. Instructions for that setup are found here.
Once you boot the system with this image, you first configure znc.
Simple instructions on how to do this are in the element listed above (in the README file). Those steps are
sudo -u znc /usr/bin/znc –datadir=/var/lib/znc –makeconf
echo “PidFile = /var/run/znc/znc.pid” | sudo su \
– znc -s /bin/bash \
-c “tee -a /var/lib/znc/configs/znc.conf”
That’s it! You can now enable and launch the znc service. In my case, I configured ZNC to run with SSL on port 6697.
root@pi:/var/lib/znc# netstat -nl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp6 0 0 :::6697 :::* LISTEN
This means that I can get to the webadmin console simply by pointing my browser to
The only other thing that I do is to enable the log module which will persist IRC logs on the Raspberry Pi. I can search them later, I also setup logrotate to purge them periodically.
A Raspberry Pi (mine is an RPI 3) requires a MicroSD card to boot, but once booted it is not required any longer. This is great because while very convenient, a MicroSD card is not as robust and hardy as a regular SSD card or even a regular USB flash device.
One of the things that I therefore do is to run my RPI’s on either SSD or a USB thumb drive. I’ve also run mine with a 1TB external spinning rust disk with external power. The technique illustrated here works on all of these.
My earlier post described the RPI boot process. The picture here shows a simple MicroSD card image for an RPI. The disk is partitioned into two parts, the first partition is a small FAT32 LBA addressable partition and the second is a larger ext4 partition. The FAT32 partition contains the bootloader and the ext4 partition contains the root filesystem.
The thing that these two together is cmdline.txt which defines the root device with a declaration like:
Since the RPI always mounts the MicroSD card as /dev/mmcblk0 and the partitions are numbered p1, p2, and so on, this indicates that the root partition is the ext4 partition as shown above.
To move this to a different location is a mere matter of adjusting cmdline.txt (and updating /etc/fstab) as shown below.
Here is my RPI with a USB thumb drive running the root (/) filesystem.
As you can see, I have a USB drive which shows up as /dev/sda and the MicroSD card.
amrith@rpi:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 1 115.7G 0 disk └─sda1 8:1 1 115.7G 0 part / mmcblk0 179:0 0 29G 0 disk └─mmcblk0p1 179:1 0 100M 0 part /boot amrith@rpi:~$ blkid /dev/mmcblk0p1: LABEL="BOOT" UUID="E4F6-9E9D" TYPE="vfat" PARTUUID="01deb70e-01" /dev/sda1: LABEL="root" UUID="7f4e0807-d745-4d6e-af6f-799d23a6450e" TYPE="ext4" PARTUUID="88578723-01"
I have changed cmdline.txt as shown below.
amrith@rpi:~$ more /boot/cmdline.txt [...] root=/dev/sda1 rootfstype=ext4 [...]
and updated /etc/fstab (on the USB drive) as shown below.
amrith@rpi:~$ more /etc/fstab # fstab generated by rpi-base element proc /proc proc defaults 0 0 LABEL=BOOT /boot vfat defaults,ro 0 2 PARTUUID=88578723-01 / ext4 defaults,noatime 0 1
As you can see, I’ve also marked the MicroSD card (which provides /boot) to be readonly; in the unlikely event that I have to modify it, I can remount it without the ‘ro’ option and make any changes.
On the left hand side is the MicroSD card. Note that on the MicroSD card, in the FAT32 partition, cmdline.txt is in ‘/’ (there’s no /boot on the MicroSD card). the cmdline.txt points the root partition to /dev/sda1 which is the USB flash drive.
On the right hand side is the USB flash drive, it has an ext4 partition with an /etc/fstab entry which mounts the MicroSD card’s fat32 partition on /boot and mounts itself on /.
This works just as well with any external disk; just make sure that you have adequate power!
In Part 1 of this blog post I described the Raspberry Pi boot image structure (a very simple version) and provided a very brief description of how the boot process works.
This part talks about how you can build your own images for a Raspberry Pi and setups a framework for people to collaborate and share their image components with each other.
In subsequent blogs I’ll build on the concepts here and describe other more sophisticated configurations and progressively share more of the elements I have built for myself, cleaning them up, before I make them public.
This blog post is structured into three parts:
- Building your own images
- Writing your own elements
- Collaborating with elements
I build my own Raspberry Pi boot images from scratch. I do this so I can build images in a repeatable way, configuring the software I want in just the way I want it.
It is much more effective to do this, than to take an image from some other source and then remove things which I don’t want and work around the quirks of the person who build that image to begin with.
In doing this, I can control exactly what goes on the image and make sure that it comes out the exact same way each time.
My tool of choice (as I use this for work related things as well) is diskimage-builder. Like other image building tools, this one is quirky, but I’ve got to understand it and I prefer it to the pi-gen tool that is used to build the official Raspbian images.
Building your own images
This will work for you if you have any old Linux machine (I use an Ubuntu 16.04LTS x86_64 machine). A simple to follow Quick Start Guide is available here.
To a reasonably Linux savvy person, building your first image should take no more than 20 minutes and you can have your Raspberry Pi up and running on your own custom image in about 30 minutes.
The steps are simple:
- Clone the repository of tools and elements
- Install prerequisite software
- Build your image
- Install your image
- Have fun!
Writing your own elements
diskimage-builder is a very flexible tool and it is very easy to write elements once you understand the general flow of things. Like all image building tools, it uses two environments, a host environment and an image environment. Some tools make the image environment a chroot (like diskimage-builder) others use a VM or a docker container.
diskimage-builder works by allowing users to select elements, define dependencies between elements, and execute scripts provided in those elements in a deterministic order. Some of the scripts are executed in the host environment, others are executed in the image environment. Finally, it takes the image environment that was created and packages it up into the format of your choice.
I use diskimage-builder to make images for a cloud (and I use qcow2 for that). For Raspberry Pi, I use the ‘raw’ format which is nothing more than a disk image complete with MBR (boot record), partition table, and volumes.
To write your own element, you can follow along with one of the many elements provided and insert your own commands. It is a very short, and not very steep learning curve.
Collaborating with elements
I’ve shared (and I will continue to share) elements that build a basic Raspbian based image, a basic Debian based image, and elements that will install specific packages, configure WiFi, configure a secure user, and so on.
For example, consider the element rpi-generic which produces a Raspberry Pi image that I use as a basic building block for many of my applications. It does not, by itself, provide an operating system. So, I could choose either rpi-debian-core or rpi-raspbian-core. With just those two elements, I could execute the command
disk-image-create rpi-debian-core rpi-generic \
-a armhf -o debian -t raw -n
and this would produce a file (debian.raw) which was a properly bootable Raspberry Pi image.
The MicroSD card I use is often 8 or 16GB, the image (for speed) is just 2GB. So, when you install the image onto the MicroSD card, and you boot the machine for the first time, the software installed and configured by the rpi-resize-root element expands the root file system to take the full available space.
If someone else wrote an element that I wanted to use, all I would have to do is get that element (clone the repository that they shared) and tell diskimage-builder where to find the element!
As a practical matter, I have an element for my WiFi access point that I use at home (which I will share as soon as I can clean it up). That element is on my machine at /rpi-image-builder-private/elements/rpi-wifi-access-point.
The elements which I’ve shared on the rpi-image-builder repository are at /rpi-image-builder/elements/.
To build my WiFi access point, I specify:
I encourage you to write and share elements, and I believe that this will be a great way for all Raspberry Pi users to collaborate on their cool projects.