Hi,
I got my system up and running.
It was a problem with the efi boot details. I had installed the latest
kernel (not manually) and that install process somehow messed up the efi
boot as it existed. After boot was broken, the console would show what it
was going to boot but the xen never loaded.
Hi,
I'm in the process of uploading various salt configurations, which you
may find interesting.
The files are in https://github.com/unman/shaker.
There's configuration for salting various useful stuff:
A caching proxy,
A version of split-ssh,
Multiple sys-usb using various controllers (specific
On Wed, Feb 10, 2021 at 08:30:22AM -0500, jon will wrote:
> So I was trying to make a blackarchlinux and Kali templates (because my job
> is a pen tester). I don't know why but after installing tools on
> blackarchlinux and Kali I cant start the template. When I boot it up I get
> can not connect t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2/10/21 3:05 AM, Ranjeet Shetye wrote:
> Hi,
>
> Is there a standard HOWTO I can follow to fix the boot process (to go from a
> grub / xen.cfg that fails to LUKS decrypt and load unencrypted rootfs)
>
> I am reasonably knowledgeable about Linux
So I was trying to make a blackarchlinux and Kali templates (because my
job is a pen tester). I don't know why but after installing tools on
blackarchlinux and Kali I cant start the template. When I boot it up I
get can not connect to qrexec agent for 60 sec, see
/var/log/xen/console/guest/gues
Is there a standard HOWTO I can follow to fix the boot process (to go
from a grub / xen.cfg that fails to LUKS decrypt and load unencrypted
rootfs)
Not that I know. Would be helpful, indeed.
Unfortunately the grub update for the kernel upgrade seems to have
messed up the boot process. How d
On 2/10/21 4:05 AM, Ranjeet Shetye wrote:
> Hi,
>
> Is there a standard HOWTO I can follow to fix the boot process (to go
> from a grub / xen.cfg that fails to LUKS decrypt and load unencrypted
> rootfs)
>
> I am reasonably knowledgeable about Linux. Gaps exist in my knowledge
> regarding BIOS an