Bug 3226 - able to install / (or other partition) to network mounts during install
Summary: able to install / (or other partition) to network mounts during install
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-30 11:37 CET by AL13N
Modified: 2023-09-24 22:13 CEST (History)
2 users (show)

See Also:
Source RPM: drakx-installer-stage2
CVE:
Status comment:


Attachments

Description AL13N 2011-10-30 11:37:24 CET
Description of problem:

In installer, when seeing overview of disks in the custom partitioner, there is currently no way to mount network disks so you can install on it.

Steps to Reproduce:
1. start DVD installer
2. go to custom partitioner screen
3. you get an error, because no disks/partitions have been found. no way to list network disks on there.
AL13N 2011-10-30 11:37:38 CET

Blocks: (none) => 1994

Comment 1 Manuel Hiebel 2011-10-30 11:50:27 CET
You mean in the stage2 ?

What do you mean with "no way to mount network disks so you can install on it" ?
Install on remote disk ?

Source RPM: (none) => drakx-installer-stage2
Severity: normal => enhancement

Comment 2 Manuel Hiebel 2011-10-30 11:50:50 CET
Ah sorry I have not see the URL.
Comment 3 AL13N 2011-10-30 13:05:31 CET
I mean during partitioning stage, so that you can set up a PXE nfs install, for instance.
Manuel Hiebel 2011-10-30 20:33:40 CET

Assignee: bugsquad => thierry.vignaud

Manuel Hiebel 2012-04-25 22:32:16 CEST

Blocks: 1994 => (none)

Comment 4 Marja Van Waes 2012-05-26 13:06:45 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Manuel Hiebel 2012-06-12 21:26:50 CEST

URL: http://mageia.org/wiki/doku.php?id=networked_diskless_install => (none)
Keywords: NEEDINFO => (none)

Comment 5 katnatek 2023-09-24 21:20:41 CEST
@David Walser this look like need to be closed as wontfix also, what you think?

CC: (none) => j.alberto.vc, luigiwalser

Comment 6 David Walser 2023-09-24 21:38:56 CEST
There's no reason to close it.
Comment 7 katnatek 2023-09-24 21:55:12 CEST
(In reply to David Walser from comment #6)
> There's no reason to close it.

What about the 11 years of be inactive?
Does some one work on this?

I don't know much of pxe's installations but is not more common boot a image from a pxe server in the machine to install and continue like if you boot the netinstall image?

What this suggest (if i understand) is a sort of remote installation that assume the user knows exactly in what hardware is installing and could be hard to debug or just be sure all goes right if the remote machine is far from the machine that triggers the install
Comment 8 David Walser 2023-09-24 22:07:55 CEST
There is no specific reason that we haven't fixed this other than nobody has taken on the task of trying to fix it.  If Mageia is going to improve and survive, we will need new developers who can take on things like this.  Until then, bugs like this can continue to lie dormant.

There are legitimate situations where a computer has no local storage, but can boot and run an OS from networked storage, and that is what this bug is attempting to address.
Comment 9 katnatek 2023-09-24 22:13:23 CEST
(In reply to David Walser from comment #8)
> There is no specific reason that we haven't fixed this other than nobody has
> taken on the task of trying to fix it.  If Mageia is going to improve and
> survive, we will need new developers who can take on things like this. 
> Until then, bugs like this can continue to lie dormant.
> 
> There are legitimate situations where a computer has no local storage, but
> can boot and run an OS from networked storage, and that is what this bug is
> attempting to address.

Thanks for the information, lets see how many time sleeps again

Note You need to log in before you can comment on or make changes to this bug.