On Wed, Dec 6, 2017 at 7:02 PM, Michael Watters wrote:
> On 12/4/17 7:03 PM, Michael Catanzaro wrote:
>> On 12/04/2017 03:11 PM, Chris Murphy wrote:
>>> Also, for any kind of early boot troubleshooting even once a user is
>>> created, systemd emergency and rescue targets only accept root user
>>>
On 12/4/17 7:03 PM, Michael Catanzaro wrote:
> On 12/04/2017 03:11 PM, Chris Murphy wrote:
>> Also, for any kind of early boot troubleshooting even once a user is
>> created, systemd emergency and rescue targets only accept root user
>> login. If root user is disabled, it's impossible to do such ea
On Mon, 2017-12-04 at 16:09 +0100, Jan Kurik wrote:
> === Language and Keyboard Layout ===
>
> Although we do not propose it at this time, language and keyboard
> layout selection should be presented to the user *before* entering the
> live session, as it is currently too difficult for users to ch
On 04/12/17 16:09 +0100, Jan Kurik wrote:
> === Language and Keyboard Layout ===
>
> Although we do not propose it at this time, language and keyboard
> layout selection should be presented to the user *before* entering the
> live session, as it is currently too difficult for users to change
> the
On Tue, Dec 05, 2017 at 04:14:54PM -0700, Chris Murphy wrote:
> On Tue, Dec 5, 2017 at 8:12 AM, Michael Catanzaro
> wrote:
> >
> >
> > On 12/05/2017 07:30 AM, Dominik 'Rathann' Mierzejewski wrote:
> >>
> >> Then why disable root at all? What if there are no local user accounts,
> >> only via a di
On Tue, Dec 5, 2017 at 8:12 AM, Michael Catanzaro wrote:
>
>
> On 12/05/2017 07:30 AM, Dominik 'Rathann' Mierzejewski wrote:
>>
>> Then why disable root at all? What if there are no local user accounts,
>> only via a directory service and network is down? This change is clearly
>> not well thought
On Tue, Dec 05, 2017 at 07:28:54AM +, Zbigniew Jędrzejewski-Szmek wrote:
> We currently only allow root to log in emergency or rescue mode,
> following what sysvinit systems did traditionally. We simply call
> sulogin, and that's the only thing it allows. I'd like to see this
> changed to allow
>
>
>> Since the first account will always be an administrator, you can log in
> to that account and use sudo -i to get a root prompt (after first boot).
>
>
A walk around can be to set the root password to match the first user of
the system? This way su -c command and sudo command will work with t
On 12/05/2017 12:58 PM, Tomasz Torcz 👁️ wrote:
This is not really true. First boot certainly allowed to configure
(in GUI)
access to directory services. It was hidden in a bit misleading
“Enterprise
login” button, see for example this screenshot:
https://www.linuxtechi.com/wp-content/uploa
On Tue, Dec 05, 2017 at 09:12:41AM -0600, Michael Catanzaro wrote:
> On 12/05/2017 07:30 AM, Dominik 'Rathann' Mierzejewski wrote:
> > Then why disable root at all? What if there are no local user accounts,
> > only via a directory service and network is down? This change is clearly
> > not well th
On Tue, Dec 5, 2017 at 1:42 PM Matthew Miller
wrote:
> On Tue, Dec 05, 2017 at 06:36:56PM +, Stephen Gallagher wrote:
> > > > OK, the impact on the Workstation netinstall will have to be
> > > > considered. Changing the netinstall would make this harder, as it
> > > > means we can't use the W
On Tue, Dec 05, 2017 at 06:36:56PM +, Stephen Gallagher wrote:
> > > OK, the impact on the Workstation netinstall will have to be
> > > considered. Changing the netinstall would make this harder, as it
> > > means we can't use the Workstation kickstart.
> > It's preferable to do things in the p
On Tue, Dec 5, 2017 at 1:09 PM Matthew Miller
wrote:
> On Tue, Dec 05, 2017 at 11:06:06AM -0600, Michael Catanzaro wrote:
> > OK, the impact on the Workstation netinstall will have to be
> > considered. Changing the netinstall would make this harder, as it
> > means we can't use the Workstation k
On Tue, Dec 05, 2017 at 11:06:06AM -0600, Michael Catanzaro wrote:
> OK, the impact on the Workstation netinstall will have to be
> considered. Changing the netinstall would make this harder, as it
> means we can't use the Workstation kickstart.
It's preferable to do things in the productimg overr
Reindl,
I'm fairly confident that the Workstation WG decided to share the
netinstall image with Fedora Server, and not have a separate netinstall
for Workstation. I'm not inclined to do enough archaeology on our old
meeting minutes to prove this. Perhaps I am simply misremembering. Or,
perhap
On 12/05/2017 10:42 AM, Matthew Miller wrote:
I think the Workstation netinstall image should be consistent with the
Live
Workstation install.
Oh wow. I did not know about this. I thought we had decided to produce
only a single netinstall image for Fedora.
OK, the impact on the Workstation
On Tue, Dec 5, 2017 at 11:42 AM, Matthew Miller
wrote:
> On Tue, Dec 05, 2017 at 09:18:30AM -0600, Michael Catanzaro wrote:
>> I think the change page is already clear that only Workstation
>> should be affected, but it is unclear about how netinstall should be
>> handled. Since we only have one n
On Tue, Dec 05, 2017 at 09:18:30AM -0600, Michael Catanzaro wrote:
> I think the change page is already clear that only Workstation
> should be affected, but it is unclear about how netinstall should be
> handled. Since we only have one netinstall installer and I believe
> it uses Server branding,
On 12/05/2017 01:18 AM, Zbigniew Jędrzejewski-Szmek wrote:
Does it mean that just visiting a spoke will cause it to be written
to /etc/sysconfig/anaconda to suppress it in g-i-s?
Or does the user actually have to configure something there?
Just visiting a spoke (already) causes that to be writt
On 12/05/2017 08:42 AM, Peter Robinson wrote:
Agreed, we also need to ensure the server use case doesn't regress,
including the text/console variant.
This change should only affect live installs of Workstation. Fedora
Server should not be affected in any way.
I think the change page is alr
On 12/05/2017 08:38 AM, Richard W.M. Jones wrote:
Will this work for people who don't use GNOME?
This change only affects Fedora Workstation, and only live installs of
Workstation, so all affected users will be using GNOME.
___
devel mailing list
On 12/05/2017 07:30 AM, Dominik 'Rathann' Mierzejewski wrote:
Then why disable root at all? What if there are no local user accounts,
only via a directory service and network is down? This change is
clearly
not well thought-out. If anything, the redundancy should be reduced on
the GNOME side,
On 12/05/2017 02:03 AM, Samuel Sieb wrote:
On 12/04/2017 03:51 PM, Michael Catanzaro wrote:
On Mon, Dec 4, 2017 at 2:55 PM, Samuel Sieb wrote:
This can be a problem if the graphical interface doesn't work on the
first boot for some reason. The user is now left with no way to login
to fix th
On Tue, Dec 5, 2017 at 2:38 PM, Richard W.M. Jones wrote:
> On Mon, Dec 04, 2017 at 04:09:25PM +0100, Jan Kurik wrote:
>> = System Wide Change: Reduce Initial Setup Redundancy =
>> https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy
>>
>> Change owner(s):
>> * Michael Catanzaro
>>
On Mon, Dec 04, 2017 at 04:09:25PM +0100, Jan Kurik wrote:
> = System Wide Change: Reduce Initial Setup Redundancy =
> https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy
>
> Change owner(s):
> * Michael Catanzaro
>
> Currently there is a high level of redundancy between the Anac
On Tuesday, 05 December 2017 at 08:28, Zbigniew Jędrzejewski-Szmek wrote:
[...]
> This has been under discussion for a while [at least 1,2,3].
> We currently only allow root to log in emergency or rescue mode,
> following what sysvinit systems did traditionally. We simply call
> sulogin, and that's
On Tue, Dec 05, 2017 at 01:35:03PM +0100, Martin Kolman wrote:
> On Tue, 2017-12-05 at 07:18 +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Mon, Dec 04, 2017 at 04:09:25PM +0100, Jan Kurik wrote:
> > > = System Wide Change: Reduce Initial Setup Redundancy =
> > > https://fedoraproject.org/wiki/Ch
On Tue, 2017-12-05 at 07:18 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Mon, Dec 04, 2017 at 04:09:25PM +0100, Jan Kurik wrote:
> > = System Wide Change: Reduce Initial Setup Redundancy =
> > https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy
> >
> > Change owner(s):
> > * Mich
On 12/04/2017 03:51 PM, Michael Catanzaro wrote:
On Mon, Dec 4, 2017 at 2:55 PM, Samuel Sieb wrote:
This can be a problem if the graphical interface doesn't work on the
first boot for some reason. The user is now left with no way to login
to fix things.
Since the first account will always be
On Mon, Dec 04, 2017 at 06:03:42PM -0600, Michael Catanzaro wrote:
> On 12/04/2017 03:11 PM, Chris Murphy wrote:
> >Also, for any kind of early boot troubleshooting even once a user is
> >created, systemd emergency and rescue targets only accept root user
> >login. If root user is disabled, it's im
On Mon, Dec 04, 2017 at 04:09:25PM +0100, Jan Kurik wrote:
> = System Wide Change: Reduce Initial Setup Redundancy =
> https://fedoraproject.org/wiki/Changes/ReduceInitialSetupRedundancy
>
> Change owner(s):
> * Michael Catanzaro
>
> Currently there is a high level of redundancy between the Anac
On 12/04/2017 03:11 PM, Chris Murphy wrote:
Also, for any kind of early boot troubleshooting even once a user is
created, systemd emergency and rescue targets only accept root user
login. If root user is disabled, it's impossible to do such early boot
troubleshooting. So I think systemd needs a w
On Mon, Dec 4, 2017 at 2:55 PM, Samuel Sieb wrote:
This can be a problem if the graphical interface doesn't work on the
first boot for some reason. The user is now left with no way to login
to fix things.
Since the first account will always be an administrator, you can log in
to that account
On Mon, Dec 4, 2017 at 2:36 PM, R P Herrold wrote:
> On Mon, 4 Dec 2017, Chris Murphy wrote:
>
>> >> === Root Account ===
>
group. We will remove the root password creation spoke.
All Workstation installs will have no root password set by
default, as in Ubuntu. Having a root passwor
On Mon, 4 Dec 2017, Chris Murphy wrote:
> >> === Root Account ===
>>> group. We will remove the root password creation spoke.
>>> All Workstation installs will have no root password set by
>>> default, as in Ubuntu. Having a root password is not
>>> useful for nontechnical users, and it is con
On Mon, Dec 4, 2017 at 1:55 PM, Samuel Sieb wrote:
> On 12/04/2017 07:09 AM, Jan Kurik wrote:
>>
>> === User Account ===
>>
>> others will not. We will remove the user account creation spoke in
>> Anaconda. All users will create the first user account using
>> gnome-initial-setup, and all initial
On 12/04/2017 07:09 AM, Jan Kurik wrote:
=== User Account ===
others will not. We will remove the user account creation spoke in
Anaconda. All users will create the first user account using
gnome-initial-setup, and all initial users will be added to the wheel
group. Of course, this can be easily
37 matches
Mail list logo
