Re: F41 Change Proposal: Anaconda as native Wayland application (System Wide)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2024-06-04 at 12:08 -0500, Jason L Tibbitts III wrote:
> > > > > > Jiri Konecny <jkonecny@xxxxxxxxxx> writes:
> 
> > Hi, the only change should be that you will change "vnc --connect"
> > with the new API we will provide and also use RDP as your client
> > instead of VNC.
> 
> Thanks.  I don't particularly care about VNC itself; I just wanted to
> make sure that it was known that someone does use "--connect" to do a
> "client-initiated" display connection.
> 
> Off topic, I know, but what I really wish existed was some kind of
> deployment console.  Early in the kickstart process, the machine
> being
> installed would contact a server, pass hardware info and wait.
I think we already send some (configurable) identifier when talking to
DHCP [0], which could be used to forward a matching kickstart to the
machine. I'm not sure but we might even do something similar in the
call trying to fetch the kickstart over network ?

[0] https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst-dhcpclass
Not the same thing you suggest, but close. And of course I guess one
could generate specific images with Image Builder with the right
kickstart baked in.

>   The
> server would pass back the rest of the kickstart file (after
> potentially
> getting admin input) and the installation would continue.  Output
> would
> be logged in a way that the server can present to the admin, and
> potentially the graphical (or perhaps the text) UI could be passed
> through.
> 
> Years ago I had hacked something implementing a little of this which
> just worked in %pre but it ended up being less useful than the system
> I
> use now.  And really, I don't think that deployments like mine (maybe
> a
> couple hundred machines) are very common so there's probably no
> point.
> But it's an interesting problem to think about.
> 
>  - J<
> --
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux