After fiddling about a bit this morning I was able to join a WebEx meeting
using Chrome. Type in the URL bar:
chrome://apps/
And click on the Cisco WebEx app.
If it's not there click on Web Store then select "App" on the left button
and search for "WebEx". Install the app. (the APP, not the extension!!)
Another way I commonly use WebEx is from my Android phone and tablet.
https://www.theregister.co.uk/2017/03/21/dns_records_more_revealing_than_you_think_says_german_boffin/
uas_eh_abort_handler = many drive problems, issue went away when I swapped cables.
This happen with a brand new cable. Over many years as a sys admin I've seen the bad SCSI (now USB) cable issue pop up again and again, with no rhyme or reason. Known good cables fail out of the blue. New out of the bag cables are bad. Lesson learned, always have spare cables on hand, not just as many as you need, always buy extras, from different sources, and keep them handy.
openSUSE Tumbleweed RPMs install on Fedora 25, who knew!?!?!
There's lots of advice out there as to how to change your default boot kernel, and none of it works. At least not on Fedora 25. What does work is install "grub-customizer" and use that to change the boot order. No need to "update MBR", I didn't and the order stuck.
There is an issue with kernel 4.13.16-100, doesn't see my second monitor like 4.9.6-200 does. So I'm just staying with 4.9.6-200 until I do the F25 to F27 upgrade, then I'll dig into the hows/whys if my second monitor isn't seen.
yum updateinfo list - very useful command, had not used before, try and see.
Today's PSA:
[568049.151349] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[568364.120021] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[568679.139156] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Unreadable time stamps on your dmesg (Captain's log) output?
This is what we call "Unix Stardates", or seconds since the kernel started. There's an easy solution,
use "dmesg -T" to produces a coherent time/date format:
[Fri Mar 23 14:33:20 2018] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[Fri Mar 23 14:38:35 2018] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[Fri Mar 23 14:43:50 2018] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Not to be confused with "Unix Time" (seconds since 1 January 1970), which is really a Doctor Who thing.
Mounting Nero! This maybe a disc image with .nrg or .cdi, the file comand shows:
locnar<80># file Image1.cdi
Image1.cdi: Nero CD image at 0x4B000 UDF filesystem data (version 1.5) '071215_0244'
Mount as shown below:
mount -o "loop,offset=307200" imagename.nrg /mount-point
mount -o "loop,offset=307200" Image1.cdi /mnt/sysimage
uas_eh_abort_handler = many drive problems, issue went away when I swapped cables.
This happen with a brand new cable. Over many years as a sys admin I've seen the bad SCSI (now USB) cable issue pop up again and again, with no rhyme or reason. Known good cables fail out of the blue. New out of the bag cables are bad. Lesson learned, always have spare cables on hand, not just as many as you need, always buy extras, from different sources, and keep them handy.
openSUSE Tumbleweed RPMs install on Fedora 25, who knew!?!?!
There's lots of advice out there as to how to change your default boot kernel, and none of it works. At least not on Fedora 25. What does work is install "grub-customizer" and use that to change the boot order. No need to "update MBR", I didn't and the order stuck.
There is an issue with kernel 4.13.16-100, doesn't see my second monitor like 4.9.6-200 does. So I'm just staying with 4.9.6-200 until I do the F25 to F27 upgrade, then I'll dig into the hows/whys if my second monitor isn't seen.
yum updateinfo list - very useful command, had not used before, try and see.
Today's PSA:
[568049.151349] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[568364.120021] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[568679.139156] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Unreadable time stamps on your dmesg (Captain's log) output?
This is what we call "Unix Stardates", or seconds since the kernel started. There's an easy solution,
use "dmesg -T" to produces a coherent time/date format:
[Fri Mar 23 14:33:20 2018] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[Fri Mar 23 14:38:35 2018] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[Fri Mar 23 14:43:50 2018] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Not to be confused with "Unix Time" (seconds since 1 January 1970), which is really a Doctor Who thing.
Mounting Nero! This maybe a disc image with .nrg or .cdi, the file comand shows:
locnar<80># file Image1.cdi
Image1.cdi: Nero CD image at 0x4B000 UDF filesystem data (version 1.5) '071215_0244'
Mount as shown below:
mount -o "loop,offset=307200" imagename.nrg /mount-point
mount -o "loop,offset=307200" Image1.cdi /mnt/sysimage
