i have installed antix15 on (sda1) and also added antix15 unpacked iso as a frugal install menu entry on (sda2)
if i boot antix15 frugal i can install it on sda1

but if i boot antix16 as a frugal also from sda2 i cant install to sda1
at option 1a, choose disk for installation, i cant select anything, on 15 i could see the hdd
on next page option 2a (root) partition, in the select box it says: partition info fatal error: device /dev/ is not a block device

is this a bug or a feature?

is there any major architecture change in antix 16 that could cause this?
how it mounts stuff or something?

i use this feature (install on the same hdd) as a backup to use or reinstall the os on some old pcs wich boot slow from usb
and obviously to show people the superiority of linux in general and antix in particular, since not all distros have all these features
live,frugal,repair,recover,imge(clone),install from hdd

thank you for your hard work

maybe reading these topics again will jog your memory
couple-of-questions-t5154.html
adding-frugal-install-menuentry-t6301.html
grub-help-t6102.html

"is there any major architecture change in antix 16 that could cause this?"
I don't think so. If there is, I've never noticed.

what do you mean ?
i was asking about some feature working in antix15 and NOT working in antix16

jog your memory == if you got it working previously but now can't recall the steps, revisiting your earlier posts could be helpful

at option 1a, choose disk for installation, i cant select anything, on 15 i could see the hdd

I'm grabbing at straws. Is the target drive unmounted when you launch the installer?
Maybe your antiX16 bootline specifies mount=all, but your earlier bootline did not, and installer ignores currently mounted partitions?

i double checked on 2 systems
heres the thing i have a grub entry pointing to /sda2/antix
and i just change files
antix15 and antix16
they both boot correctly

first partition is not mounted in both

in 16 i cant install
but,like i said it somehow doesent see the target, there is an error

partition info fatal error: device /dev/ is not a block device

was it actually partition-info fatal error: device /dev/ is not a block device
I guess it must have been that.
partition-info is a system command employer by the installer

How large is your intended target partition?
Asking because the installer currently rejects partitions smaller than 4Gb

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/anticapitalista/MX-installer/blob/master/minstall.cpp#L2344"
linktext was:"https://github.com/anticapitalista/MX-i ... .cpp#L2344"
====================================


Anyhow, I did find a couple of committed changes which occurred after antiX15 release which may have introduced a bug:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/anticapitalista/MX-installer/commit/a356755c6ab89278a3dfcdbc9c148e0f735c32f9"
linktext was:"https://github.com/anticapitalista/MX-i ... 0f735c32f9"
====================================


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/anticapitalista/MX-installer/commit/d8857635b99210f13a569dbae011321c045295a4"
linktext was:"https://github.com/anticapitalista/MX-i ... 1c045295a4"
====================================


I'll ask Adrian, the installer author, to followup.

partitions are bigger than 30gb
i thought installer was some scripting language bash/perl not c

See the red text in my post above?
This link will show you the exact line (within partition-info) where the error is triggered:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux/partition-info/blob/master/partition-info#L259"
linktext was:"https://github.com/antiX-Linux/partitio ... -info#L259"
====================================


I contacted Adrian, who replied"yeahbut... partition-info is BitJam's script". So, I've PMed BitJam and asked him to visit this topic.

Months later, revisiting because zimp has referenced this topic, I notice the linked line number is no longer accurate"#L259" so, to clarify, am pasting the suspect portion of the code

The reported error message partition-info fatal error: device /dev/ is not a block device
suggests that the string passed as an argument in the call to `partition-info` is, literally, a 5-character string"/dev/"

// disk selection changed, rebuild dropdown menus
void MInstall::on_diskCombo_activated(QString)
{
QString drv = QString("/dev/%1").arg(diskCombo->currentText().section("", 0, 0));

rootCombo->clear();
swapCombo->clear();
homeCombo->clear();
swapCombo->addItem("none - or existing");
homeCombo->addItem("root");
removedItem ="";

// build rootCombo
QStringList partitions = getCmdOuts(QString("partition-info -n --exclude=all --min-size=4000 %1").arg(drv));
rootCombo->addItems(partitions);
if (partitions.size() == 0) {
rootCombo->addItem("none");
}