[Bug 982914] New: 7.4.1. Configuring 802.1x Security
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=982914
Bug ID: 982914
Summary: 7.4.1. Configuring 802.1x Security
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
In section 7.4.1 under 'Procedure 7.8. For a wired connection...', '
Procedure 7.9. For a wireless connection...':
The 'Network Connections' dialogue can be accessed via:
activities --> applications --> sundry --> network connections, or via
nm-connection-editor
This is not specified at all in this section.
--
You are receiving this mail because:
You are the QA Contact for the bug.
7 years, 11 months
[Bug 982911] New: 7.3.3. Establishing a Mobile Broadband Connection
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=982911
Bug ID: 982911
Summary: 7.3.3. Establishing a Mobile Broadband Connection
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Under section 7.3.3, in 'Procedure 7.3. Adding a New Mobile Broadband
Connection', 'Procedure 7.4. Editing an Existing Mobile Broadband Connection':
network connection editor can also be found at:
activities --> applications --> sundry --> network connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
7 years, 11 months
[Bug 982910] New: 7.3.5. Establishing a DSL Connection
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=982910
Bug ID: 982910
Summary: 7.3.5. Establishing a DSL Connection
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
In section 7.3.5 under 'Procedure 7.6. Adding a New DSL Connection', 'Procedure
7.7. Editing an Existing DSL Connection':
These procedures could also specify that the network connections editor can be
accessed from:
activities --> applications --> Sundry --> Network Connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
7 years, 11 months
[Bug 1221780] New: how to identify firmware types, UEFI vs BIOS
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1221780
Bug ID: 1221780
Summary: how to identify firmware types, UEFI vs BIOS
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: bugzilla(a)colorremedies.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
I'm not finding advice in documentation to identify firmware type. Should we,
and if so where should it go?
Identifying firmware type comes in handy e.g. reinstalling grub, see bug
1220066.
The problem is, users overwhelmingly equate UEFI and BIOS, often referring to
it as UEFI BIOS, mainly because OEM's still call firmware updates "BIOS
updates".
Two possible ways to reliably identify UEFI vs BIOS firmware.
On an EFI system:
# ls /sys/firmware/efi
config_table efivars fw_platform_size fw_vendor runtime runtime-map
systab vars
On a BIOS system:
# ls /sys/firmware/efi
ls: cannot access /sys/firmware/efi: No such file or directory
----
On an EFI system:
# efibootmgr
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0000,0080
Boot0000* Fedora
Boot0080* Mac OS X
Boot0082*
BootD1A6* AST
BootFFFF*
On a BIOS system:
# efibootmgr
efibootmgr: EFI variables are not supported on this system.
Unknowns:
The first method always works since ls is for sure installed no matter what. I
need to test if efibootmgr is always installed, e.g. netinstall (?), it
definitely is always installed from lives. But if it's not installed, then it's
not a UEFI system.
How does coreboot firmware manifest? I think it's mainly a "better BIOS" and
should behave as such.
ARM firmware?
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years
[Bug 987301] New: Section 11.1.1 Figure 11.1 missing
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=987301
Bug ID: 987301
Summary: Section 11.1.1 Figure 11.1 missing
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Section 11.1.1 has a missing screenshot (Figure 11.1)
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 1 month
[Bug 983366] New: Cover Page says "Fedora 17" in 'header' logo
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=983366
Bug ID: 983366
Summary: Cover Page says "Fedora 17" in 'header' logo
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
Header logo on cover page of System Administrators guide says "Fedora 17" above
first line of text
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 1 month
[Bug 982894] New: 7.2.4. User and System Connections
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=982894
Bug ID: 982894
Summary: 7.2.4. User and System Connections
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: unspecified
Priority: unspecified
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
the network settings dialogue does not have tabs, instead, the identity section
of the dialogue is concerned with setting the connection to be available to all
users (or not)
--
You are receiving this mail because:
You are the QA Contact for the bug.
8 years, 1 month