Re: Deprecation of Anaconda boot parameters without inst. prefix

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

 



On Thu, Aug 13, 2020 at 9:43 AM <jkonecny@xxxxxxxxxx> wrote:
>
> On Thu, 2020-08-13 at 09:22 -0400, Stephen John Smoogen wrote:
> > On Thu, 13 Aug 2020 at 08:58, Fabio Valentini <decathorpe@xxxxxxxxx>
> > wrote:
> > > On Thu, Aug 13, 2020 at 2:16 PM <jkonecny@xxxxxxxxxx> wrote:
> > > > Hello everyone,
> > > >
> > > > Anaconda team has decided to deprecate use of Anaconda kernel
> > > > boot
> > > > parameters without 'inst.' prefix. As you may already know you
> > > > can
> > > > specify Anaconda kernel boot parameters both with and without
> > > > 'inst.'
> > > > prefix (e.g. 'inst.repo=' or 'repo='). This deprecation means
> > > > that when
> > > > you use Anaconda option without the 'inst.' prefix you will now
> > > > get a
> > > > warning. We are *not* disabling parameters without a prefix yet.
> > > >
> > > > The reason for this is keep running into parameter conflicts with
> > > > other
> > > > projects. As an example there is 'debug' parameter for both
> > > > kernel and
> > > > us, so when you want to enable kernel debugging in installation
> > > > environment you will also enable Anaconda debug mode.
> > > >
> > > > Because of this I have created the following pull request for
> > > > Anaconda:
> > > >
> > > > https://github.com/rhinstaller/anaconda/pull/2786
> > > >
> > > >
> > > > In case you have any objections please start discussion either on
> > > > the
> > > > pull request or here.
> > > >
> > > >
> > > > Best regards,
> > > > Jirka
> > >
> > > This may be a stupid question, but why are parameter namespaced
> > > with
> > > "inst." and not with "anaconda."? Is this a historical artifact?
> > > "inst" is a pretty generic term as well, and "anaconda" would
> > > definitely not lead to parameter overloading on the kernel cmdline.
> > >
> >
> > I think inst was meant to be universal so that debian etc could use
> > it. However I will say if I have to type 20 anaconda.<item>=<flag> on
> > a serial terminal like I have to for the inst.<item>=<flag> I will
> > quickly be looking for any other installer to use. I regularly end up
> > with enough redraw problems because the line went over whatever SOL
> > or
> > the HTML-console thinks a line should be and clearing the entire line
> > so I can't see what I am typing.
>
> I wasn't in the team when the decision to use `inst.` was made.
> However, I agree with Stephen that it's just shorter and some people
> have to write this a lot and lot of times. Also, it could be used for
> multiple installers if they want to.
>

It was intended to be a standard interface. And I'm pretty sure these
flags were created at around the same time that Anaconda was being
ported to Debian and having a generic prefix meant that
debian-installer could implement it. I don't know if d-i today
actually *does* have these, but I'm pretty sure that was the reason.

Though the cross-installer compatibility idea inspired the creation of
kickseed[1] for Debian and Ubuntu years later, too..

[1]: https://launchpad.net/kickseed

-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
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




[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