Marzec « 2016 « Różności …

Różności …

31 marca 2016

BI outer join

Zaszufladkowany do: BI — Tagi: — Jacek @ 08:12

22 marca 2016

grub crypt

Zaszufladkowany do: Linux — Tagi: — Jacek @ 15:25

– ENCRYPTED filesystem

– partition encryption

sudo cryptsetup luksOpen /dev/sda1 dowolna_nazwa
sudo mkdir /media/my_device
sudo mount /dev/mapper/dowolna_nazwa /media/my_device
sudo umount /media/my_device
sudo cryptsetup luksClose dowolna_nazwa

To automatically put it in the /media location, use the udisks tool

sudo udisks --mount /dev/mapper/my_encrypted_volume


sudo mount /dev/sdXY /mnt

sudo mount –bind /dev /mnt/dev &&
sudo mount –bind /dev/pts /mnt/dev/pts &&
sudo mount –bind /proc /mnt/proc &&
sudo mount –bind /sys /mnt/sys

sudo chroot /mnt

grub-install /dev/sdX
grub-install --recheck /dev/sdX





menuentry “Windows 10″ {

set root=’(hd0,2)’
chainloader /EFI/Microsoft/Boot/bootmgfw.efi


grub-mkconfig -o /boot/grub/grub.cfg

powstaje /boot/grub/grub.cfg

Windows 10 dual boot

This is what I did:

  • I booted into my Ubuntu installation using the trick of the F9 key in the start up to be able to choose the boot loader.
  • Once in Ubuntu, I opened a terminal.
  • Using the command below, I checked where Windows boot loader was located:
    $ sudo efibootmgr -v
  • In my case, the original boot loader was in here: /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi . Please note that in your computer it might be in a different place. If so, you will need to adjust the commands below.
  • As per Rod’s recommendation in his answer (the one about how to repair the boot loader manually), I made a backup of that file by moving it one level down:
    $ sudo cp /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi /boot/efi/EFI/Microsoft/bootmgfw.efi
  • Finally, I copied GRUB2′s boot loader in that place, “tricking” the system into loading the boot loader I wanted instead of Windows’ original boot loader.
    $ sudo cp /boot/efi/EFI/ubuntu/grubx64.efi /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi

So finally I had my dual boot working with GRUB2. In case Windows overwrites the boot loader again after an update (as it did with me), I already know the steps to get grub back to its place.

Thanks, it helped, however I could not boot into Windows. At startup, it starts GRUB and in GRUB, the ‘Windows Boot Manager’ option goes to GRUB menu again (expectable as this links to the same .efi file). It looked like that issue though I was not lucky with boot-repair. I solved it by going to Ubuntu, in /etc/grub.d/ filling the file 40_custom by copying the Windows Boot entry I had in my ubuntu paste and editing the url of .efi file to point to the backup of bootmgfw.efi. So the menuentry contains chainloader /EFI/Microsoft/bootmgfw.efi – Vince Jan 8 ’15 at 0:23
pavilion F10 – bios, F9 – boot menager

11 marca 2016

Hot to read windows key from linux

Zaszufladkowany do: Linux — Tagi: — Jacek @ 08:43

cat /sys/firmware/acpi/tables/MSDM

8 marca 2016

Linux – check architecture

Zaszufladkowany do: Linux — Tagi: — Jacek @ 07:41

uname –a (x86_64 – 64 BIT) (i686 – 32 BIT)

uname -m


file /sbin/init

3 marca 2016

linux change hostname

Zaszufladkowany do: Linux — Tagi: — Jacek @ 17:47
hostname NEW_NAME
sysctl kernel.hostname
sysctl kernel.hostname=NEW_NAME


Strona startowa: