Language Selection

English French German Italian Portuguese Spanish

#fedora - You are always wrong

Filed under
Linux
Hardware
Web

I discovered this evening much to my dismay that the year and a half old western digital hard drive in my main laptop is dieing. All three of the Linux installs on the system failed in various ways (typically a sign of a hardware issue) so I grabbed the closest live CD and popped it in.

There was a few gigs of data on the drive I didn't have backed up, so I opened nautilus and navigated to my files.

Ahh right - the permissions of the hard drive made it so I could not read certain folders I needed access to. Not a problem, I'll just launch the file manager as root. I opened a terminal, typed in su followed by nautilus and was greet by a crash message.

Ahh right - nautilus doesn't like to be opened as super user if I recall correctly. It had been awhile since I had used a non-sudo distro, so I hopped into #fedora on freenode to ask how I could go about launching the file manager as super user.

Dear lord was that a mistake.




Take a breath, then respond

larrythefreesoftwareguy.wordpress: Many of you already know that I have been an active participant in the Fedora Project for several years; for those of you who don’t, that secret is now out (and, man, do I feel relieved admitting it!). I have also been a regular in many IRC channels, both Fedora and non-Fedora related, though I am not a regular in #fedora — in fact, I avoid #fedora for the same reasons Jeff outlines in his self-proclaimed “rant.”

That said, Jeff accurately points out a situation that has been a sticking point, and one that is being addressed and corrected, in the Fedora Project around the types of caustic responses that sometimes come up in #fedora. Also, while I don’t frequent the channel and usually find answers to my questions elsewhere — a good practice (and more on this later) — I can say that it’s something that has caused some of us in the Fedora Project some concern.

rest here

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.