Reputation
2,003
Top tag
Next privilege 2,500 Rep.
Create tag synonyms
Badges
3 11 19
Impact
~271k people reached

Apr
12
comment How do I get a yum repo to work in a Docker container?
Why would you need to give docker containers separate IPs manually, if they reside on different VMs? In production you can just use IPs of VMs and docker containers can be mapped to VM's external ports. Or you can just assign server names to each of your containers. In development (if you run both containers on the same physical machine) and your consumer container needs to access repository container, just use docker run -d --link=repository:repository consumer-image so that --link flag passes server name of repository into consumer's /etc/hosts.
Feb
3
awarded  Notable Question
Dec
29
revised Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
added 55 characters in body
Dec
29
revised Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
added 11 characters in body
Dec
29
comment Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
@mikeserv thanks for your suggestion, mike. Luckily, DVD image did the trick, while CD image, apparently, doesn't support 32-bit UEFI. Got my Jessie up and running as well as Windows 8.1.
Dec
29
revised Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
edited title
Dec
29
answered Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
Dec
29
revised Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
added 55 characters in body
Dec
29
revised Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
added 518 characters in body
Dec
28
asked Debian 8 Jessie CD-image-based liveUSB/installer won't boot in UEFI mode with 32-bit UEFI firmware
Dec
3
comment How does Linux load the 'initrd' image?
@CMCDragonkai Yes, stage2 bootloader is in the filesystem (namely, in /boot partition). Kernel is not loaded at this point - it's grub's stage1.5, who's accessing stage2 in the /boot filesystem (e.g. in /boot/grub file) via its minimalistic filesystem drivers. Kernel will also be able to read from /boot partition, but it will happen later, after execution of grub2 code and load of kernel and after kernel reads initramfs. Are you speaking of init.sh of the initramfs? It resides in /boot partition of your hard drive, then stage2 of grub puts it into RAM and Kernel reads it from RAM.
Nov
9
awarded  Famous Question
Nov
3
awarded  Famous Question
Sep
19
awarded  Nice Answer
Sep
15
awarded  Yearling
Sep
14
accepted Debian alternatives system: programs with the same name and priorities
Sep
14
comment Debian alternatives system: programs with the same name and priorities
@Jasen thanks for clarification.
Sep
14
revised Debian alternatives system: programs with the same name and priorities
added 142 characters in body
Sep
14
comment Debian alternatives system: programs with the same name and priorities
Thanks for the answer, Gilles! So, what's the purpose of alternatives system, if it doesn't allow to switch symlink for different programs?
Sep
13
asked Debian alternatives system: programs with the same name and priorities