Answer the question
In order to leave comments, you need to log in
What prevents Multisystem under Ubuntu from "rolling out" an ISO image?
Hello.
I'm trying to create a multiboot disk using Multisustem from Ubuntu 14.04.2.
Multisystem launches a graphical interface, allows you to select the device on which I want to upload the image and asks if I want to install Grub2 on the device. After selecting the ISO image itself, the GUI window turns into a terminal with an invitation and nothing else happens.
Console output:
multisystem
Gtkdialog version: 0.8.3
LANG:ru_RU.UTF-8
LANGUAGE:en_US.UTF-8
LANGSEL:English|en|en_US.UTF-8|Ryan J Nicholson|[email protected]
device:
EXIT="abort"
device:/dev/sdd1
MESSAGES="Please select the USB volume
to use from the list below.
WARNING:
Grub2 will be installed in the MBR!
"
btmaj2=""
btuninstall2=""
checkupdate2="true"
device="/dev/sdd1"
lister_lang="English"
statusbar="Device:/dev/sdd1
"
theme_pixmap=""
EXIT="detection"
--2015-03-10 14:37:59-- http://liveusb.info/multisystem/version-multisystem.txt
Resolving liveusb.info (liveusb.info)... 92.243.9.215
Connecting to liveusb.info (liveusb.info)|92.243.9.215|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 32 [text/plain]
Saving to: ‘/tmp/multisystem/version-multisystem.txt’
100%[==============================================================>] 32 --.-K/s in 0s
2015-03-10 14:37:59 (2,95 MB/s) - ‘/tmp/multisystem/version-multisystem.txt’ saved [32/32]
ok
idgui:
grub-install: info: executing modprobe efivars 2>/dev/null.
grub-install: info: Looking for /sys/firmware/efi ...
grub-install: info: ... not found. Looking for /proc/device-tree ...
grub-install: info: ... not found.
Installing for i386-pc platform.
grub-install: error: install device isn't specified.
All
var:autorun.inf
var:boot
var:EFI
var:icon.ico
var:ubuntu-14.04.2-desktop-amd64.iso
var:ubuntu-14.04.2-desktop-i386.iso
EXIT="abort"
DAG:/media/nazarovd/MULTISYSTEM/ubuntu-14.04.2-desktop-amd64.iso
TIMER refresh true
TIMER refresh true
TIMER refresh true
TIMER refresh true
TIMER refresh true
EXIT="abort"
Answer the question
In order to leave comments, you need to log in
The decision turned out to be...strange.
I remembered that I used multisystem very actively before and there were no problems. And he stopped using it at about the same time as he began to study the possibilities of "
pumping" .bashrc Browsing came down to adding various convenient aliases, a multi-line command line prompt and a hack function that translates the carriage to a new line if the output of the program does not made. It looks like this:
function prompt_command {
# get cursor position and add new line if we're not in column first
echo -en "\033[6n" && read -sdR CURPOS
&& echo " ↵"
}
PROMPT_COMMAND=prompt_command
After commenting "PROMPT_COMMAND=prompt_command" multisystem stopped acting strange.
Most likely you need administrator rights to install the bootloadersudo multisystem
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question