Odprtokodni pogled

Opensource view


Syndicate content
Your source for Linux and Open Source news, reviews, and howtos.
Posodobljeno: 42 min 9 sec nazaj

Leftovers: New Shows, Screencast and FUD

Čet, 04/04/2019 - 10:52

read more

10 Best File and Disk Encryption Tools for Linux

Čet, 04/04/2019 - 09:30

It wasn’t too long ago that we published a list of 10 cool command line tools for your Linux terminal. Today, we turn our focus to encryption methods as we bring you a list of the best file and disk encryption software for your Linux machine.

read more

Linux For A Slow Laptop

Čet, 04/04/2019 - 09:17

There are old laptops in each house that can no longer function fully. Using standard operating systems, for example, Windows or Linux becomes almost impossible. However, you can still use the old laptop effectively.

Now many distribution packages will make Linux for a slow laptop the best option in comparison with other operating systems.

Several Linux distribution packages will work effectively on slow laptops. We will consider the most successful ones.

read more

Programming: Tap-Hat, IBM, Python, Mozilla

Čet, 04/04/2019 - 04:39
  • Debug Raspberry Pi software, and more, with this hardware

    Not available quite yet, it is being designed in the UK by eCosCentric – the source of the eCosPro RTOS.
    Physically, it mates with the Raspberry Pi IO header, but extends away from the Pi (unlike a typical HAT which site over the Pi) to allow probing access to Pi components. Its stacking header allows further HATs to be connected over the Pi in the normal orientation.
    To use Tap-Hat, certain Pi IO pins have to be re-allocated for JTAG use – the firm’s own Redboot SD Card boot-loader supports this configuration of Pi JTAG pin map, and configures the CPU’s alternate pin mappings to match the Tap-Hat board’s jumper settings.
    Supported external JTAG debuggers include Lauterbach TRACE32, Ronetix PEEDI and Segger J-Link.

  • What’s Happening with RISC-V ?
  • IBM Clarifies Java Options Following Oracle License Crackdown

    IBM i shops that are wondering how to maintain their Java environments following Oracle’s recent decision to restrict access to Java runtimes and development tools should pay close attention to some recommendations that IBM is making concerning Java, particularly how it impacts Access Client Solutions (ACS).

    Oracle is slated to ship a critical security update for Java Standard Edition (SE) 8 in a week and a half. But unless you have bought a commercial license for Java SE 8, your business won’t be getting that update, which could leave your systems vulnerable. That’s because in late 2018, Oracle made some rather large changes to the way customers will receive patches and updates for the aging Java environment.

  • Plot the balance of power graph with python

    We are supposed to finish the previous Forex and Stock application project already but because it has been a while I am not writing anything on this website, therefore I would like to include another feature into the previous project just to let you know that this site is still active.

    The feature I am going to include in the ongoing project is the balance of power graph. The Balance of Power indicator measures the market strength of buyers against sellers by assessing the ability of each side to drive prices to an extreme level. The calculation is: Balance of Power = (Close price – Open price) / (High price – Low price) The resulting value can be smoothed by a moving average.

  • Python for NLP: Sentiment Analysis with Scikit-Learn

    This is the fifth article in the series of articles on NLP for Python. In my previous article, I explained how Python's spaCy library can be used to perform parts of speech tagging and named entity recognition. In this article, I will demonstrate how to do sentiment analysis using Twitter data using the Scikit-Learn library.

  • This Week in Rust 280
  • QMO: Firefox 67 Beta 6 Testday Results

    As you may already know, last Friday March 29th – we held a new Testday event, for Firefox 67 Beta 6.

    Thank you all for helping us make Mozilla a better place: amirtha V, Shanthi Priya G,  Rok Žerdin, Aishwarya Narasimhan, Mohamed Bawas.

    From Mozilla Bangladesh Community: Maruf Rahman, Sayed Ibn Masud, Reazul Islam.

read more

Ubuntu/Debian: Snapcraft Release and LTS Work by Mike Gabriel and Sylvain Beucler

Čet, 04/04/2019 - 04:34
  • Snapcraft 3.3

    snapcraft 3.1 is now available on the stable channel of the Snap Store. This is a new minor release building on top of the foundations laid out from the snapcraft 3.3 release.

    If you are already on the stable channel for snapcraft then all you need to do is wait for the snap to be refreshed.

  • Mike Gabriel: My Work on Debian LTS/ELTS (March 2019)

    In March 2019, I have worked on the Debian LTS project for 14 hours (of 10 hours planned plus 4 hours pulled over from February) and on the Debian ELTS project for another 2 hours (of originally planned 6 hours) as a paid contributor.

  • Sylvain Beucler: Debian LTS - March 2019

    In February I had requested to join the Debian LTS project, which extends the security support for past Debian releases, as a paid contributor.

read more

today's howtos

Čet, 04/04/2019 - 04:31

read more

Kernel: NVIDIA, Wayland and Intel

Čet, 04/04/2019 - 04:29
  • NVIDIA Fixes Flaws in Linux4Tegra Driver for Jetson AI Supercomputers

    NVIDIA released a security update for the Jetson TX1 and TX2 to patch vulnerabilities discovered in the Linux for Tegra (L4T or Linux4Tegra) driver package that could enable local attackers with basic user privileges to elevate privileges and to perform privilege escalation, denial-of-service (DoS) or information disclosure attacks.

    As described by NVIDIA, Jetson TX1 and TX2 are high-performance and low-power embedded AI supercomputers on a module designed to be used for compute-intensive deep learning and computer vision projects.

  • RFC: Wayland high-resolution wheel scrolling I've been trying to sort out the new hi-res wheel scrolling that was added to linux 5.0 but it's been a bit of a struggle to say the least. For the impatient, skip forward to the protocol diff but the background info is important. Everything below applies equally to horizontal and vertical scrolling, both directions and wheels and wheel tilts. The APIs that are involved for low-resolution wheel scrolling: kernel: - REL_WHEEL for every wheel click libinput uses pointer axis events for wheels: - pointer axis value: the movement of the wheel in degrees - pointer axis discrete value: the number of wheel clicks - pointer axis source: set to 'wheel' Usally this means you get discrete 1, value 15 for the standard 15-degree mouse wheel, discrete 2 value 30 is two wheel clicks within one hw frame. There is one implicit assumption here: the discrete value must be 1 or more for every event. Otherwise it's impossible to use the value and calculate the angle. More on that later. This API is effectively the same in the wayland protocol except for the unit of the 'value' which is is in screen coordinates, not degrees. wayland protocol: - pointer axis value: the movement in screen coordinates - pointer axis discrete: the number of wheel clicks - pointer axis source: set to 'wheel' The big difference here though: libinput's API is per-device, wayland's API is per wl-seat pointer. There's no way to tell in the protocol that you're scrolling simultaneously with wheels on two different mice. Let's see how the common compositors implement this: weston: - for source wheel, only the discrete value is handled and: - pointer axis discrete is sent as-is from libinput - pointer axis source is sent as-is from libinput - pointer axis value is always (discrete * 10) - otherwise the libinput pointer value (degrees) from a source wheel is ignored The magic multiplier 10 is afaik for historical reasons, weston used to do 10 so early libinput took that. When libinput switched to use physical dimensions instead of 10, that value was kept for backwards compatibility with existing wayland clients. mutter: - for source wheel, only the discrete value is handled and: - clutter-internal event for the discrete **direction** from libinput - i.e. discrete > 1 will still only generate one event,some events drop to the floor here for fast wheel movements - clutter-internal event with (value * 10) marked as 'emulated' but that event is ignored later when we're writing to the protocol - the discrete event is written as wl_pointer.axis_discrete and wl_pointer.axis with a value of 10 So, the same multiplier of 10 but fast scroll events with more than one click per frame appear to get dropped. kwin (through qtwayland): - doesn't handle discrete at all afaict - pointer axis events are passed through but I got a bit confused over the actual value written on the wire here. wlroots: - pointer axis discrete is sent as-is from libinput - pointer axis source is sent as-is from libinput - pointer axis value is sent as-is from libinput Because the physical angle is passed on from libinput as screen coordinates, this means wlroots has different scroll behaviour to GNOME/sway and it does scroll a larger distance for wheels with higher click angles. This is the opposite of the intended behaviour, manufacturers advertise these wheels as slow-scrolling wheels. Realistically though the physical movements is the same-ish and if a client uses discrete it doesn't matter anyway. xf86-input-libinput: - X devices need to set up a scroll distance for scroll motion, the driver uses 120 (since Feb, before it was 15). This means any multiple of 120.0 triggers legacy button emulation in the server, otherwise the number has no meaning. - for source wheel it uses the discrete value only, so effectively 120 * discrete. This driver had a division by 0 for discrete values of 0, fixed in the current release. More on this later. Let's look at how wheel events are processed in some of the clients: GTK: - for a discrete event, GDK_SCROLL_UP is passed on flagged as 'emulated' - the axis value is passed on as GDK_SCROLL_SMOOTH Qt: - doesn't handle discrete - multiplies the value by -12. This gives it a 120-based value which matches the Windows API provided the axis value is 10 of course. Qt on wlroots is probably off here. Xwayland: - X devices need to set up a scroll distance for scroll motion, Xwayland currently uses 1.0 for that. This means any multiple of 1.0 triggers legacy button emulation in the server. - wl_pointer.axis_discrete are used where available - wl_pointer.axis uses the value * 0.1. This effectively means Xwayland relies on the deltas to be 10 like in mutter/weston, X clients under wlroots will have off wheel click emulation. With me so far? Hooray, now let's introduce hi-res scrolling. All the examples below are for a quarter scroll wheel movement, i.e. you get 4 hi-res events for every 1 lo-res event. The kernel uses a fraction/multiple of 120 for logical clicks, same as the Windows API. So one wheel click is 120, half a click is 60, etc. I'm calling this 120-based value the v120 because I'm very creative. kernel: - REL_WHEEL for every wheel click - REL_WHEEL_HI_RES for every fraction of a wheel click (as portion of 120), so a quarter-wheel stop gives you a value of 30. - there is no guarantee that REL_WHEEL is sent every full 120 because e.g. Logitech mice may reset halfway through a wheel motion. So the two axes must be considered completely independent. libinput: Basically: the current API is fairly useless in handling fractional scroll because libinput uses physical distances. libinput could send four events: - value 3.75, discrete 0 - value 3.75, discrete 0 - value 3.75, discrete 0 - value 3.75, discrete 1 Which is technically correct. But callers have no reliable way how much of a fraction of a wheel the 3.75 represents until the first discrete event comes in. Guessing is unreliable, if you scroll faster you may get 2+ fractional units in one event. And mice may reset halfway through a scroll motion so you don't always get the same number of events per discrete. So libinput needs some extra API that gives us some baseline to compare values against, i.e. same as the kernel's 120-based API does. There are other problems, specifically related to sending discrete 0 events: weston: - Current weston: a discrete value of 0 ends up as value of 0 which weston treats as axis_stop event. So our event sequence is axis_source, axis_stop, pointer_frame. this breaks scrolling. mutter: - Current mutter: a discrete value of 0 ends up in noops. mutter still generates internal clutter events but they are never pushed onto the wire. The normal values are ignored, so we basically get low-res scrolling just as before. Note: this is based on reading the code, not test runs wlroots: - will forward value/discrete as it comes in from libinput kwin: - doesn't use discrete so won't be affected by changes xf86-input-libinput: - anything pre 0.28.2 will get a division by 0 - current state: discrete values of 0 end up as noops and we we get lo-res scrolling only So basically: if we change libinput to send discrete 0 events, we'll break weston and all but the most recent xf86-input-libinput. Code changes are needed just to cope with the different event sequence, let alone the actual hi-res bits. The solution to this is to add a new event, LIBINPUT_EVENT_POINTER_AXIS_WHEEL. That event provides libinput_event_pointer_axis_value_v120() which is basically a mirror of the kernel API. This event obsoletes POINTER_AXIS events for sources WHEEL and WHEEL_TILT, so callers should just ignore those if they support the new event. A branch for this is available here: https://gitlab.freedesktop.org/whot/libinput/commits/wip/hi-res-scrolling The event sequence would now be: - WHEEL: value 3.75, v120 30 - WHEEL: value 3.75, v120 30 - WHEEL: value 3.75, v120 30 - WHEEL: value 3.75, v120 30 - AXIS: value 3.75, discrete 1, v120 120 Implementation-wise: AXIS and WHEEL are independent, so there's no guarantee that they add up to the same 120 values. This new event is easy to add to compositors. Let's look at the Wayland protocol with the current API given hi-res scroll events: - value 3.75, no discrete event - value 3.75, no discrete event - value 3.75, no discrete event - value 3.75, discrete 1 This is assuming 15 degrees/4 == 3.75 but if the compositor force wheels to a scale of 10, the value would be 2.5. Qt: - doesn't use discrete so won't be affected by changes GTK: - generates 4 GDK_SCROLL_SMOOTH events, - generates 1 GDK_SCROLL_DOWN event ('emulated') - GTK doesn't really care as such about whether the distance-to-wheel is 10 or something else, it'll just have different scroll distances (e.g. under wlroots). Afaict this works correctly (tested with stock F29 nautilus) Xwayland: - current Xwayland: values are handled as fraction as before, so we get 3 smooth-scroll events at 25%. Event 4 has a discrete event which is handled as full event, so we scroll by a logical click. Total distance is 175%. This means: Xwayland cannot work at all without any extra wayland protocol unless it assumes factor 10 is the base unit. So we have at least one ubiquitous Wayland client that cannot handle it. And the issues are very similar to the ones libinput's API has, added to that is that you cannot guarantee that two events come from the same device. What we need is a new event, but I'm struggling to add this to the wayland protocol in a good way, mostly for backwards-compatibility reasons. Much of the below would be easier to solve if we can say "if you claim to support wl_pointer version 8, you get different behaviour for axis events". I don't think we can trust clients to handle this correctly, I got burned by those assumptions before (in XI2). So I'm ruling out changing any of the existing protocol behaviour. My current idea is to add a wl_pointer.axis_v120 event: wl_pointer.axis_source wheel wl_pointer.axis_v120 30 wl_pointer.frame wl_pointer.axis_source wheel wl_pointer.axis_v120 30 wl_pointer.frame wl_pointer.axis_source wheel wl_pointer.axis_v120 30 wl_pointer.frame wl_pointer.axis_source wheel wl_pointer.axis 10 wl_pointer.axis_discrete 1 wl_pointer.axis_v120 30 wl_pointer.frame Main problems here: this puts a fair bit of implementation requirements on the compositor - skip source/v120/frame for clients < supported version. wl_pointer.source cannot currently occur on its own, it requires a wl_pointer.axis event in the current protocol. Same with axis_discrete. Empty frames are allowed, I think, but pointless. It also puts a bit of extra logic in the client, you need to remember if you've seen a v120 in this frame and discard the axis/axis_discrete events. If not, then axis events must be processed as normal. A possible workaround would be to add v120 to all axis frames (including touchpad scrolling) but that would then put the compositor in charge of deciding what distance is a wheel click and encodes that information in the protocol. The v120 event must also carry the equivalent to the wl_pointer.axis value so that can be passed on into existing code. So the above would have a v120 event with v120 value of 30 and an axis value of 2.5 (if enforcing 10 units per wheel click). Because the hi-res and lo-res sources are independent, we need to allow for a 0-value v120 event, which basically just tags that frame as The compositor also need to *always* send v120 events for wheel/tilt sources because otherwise the client code becomes even more of a nightmare. Where not backed by libinput the compositor needs to handle that itself. Anyway, the below is the best I've come up with so far though I haven't implemented it client-side yet. I'd really appreciate any feedback and/or epiphanies. Cheers, Peter
  • High Resolution Scroll Wheel Support Being Worked On For Wayland

    The high resolution scrolling support in Linux 5.0 has been a headache to say the least. After being ejected from Linux 4.20 following early fall-out, the support was merged for Linux 5.0 but the user-space support has yet to stabilize.

    Red Hat input expert Peter Hutterer who has been involved in this high-resolution scroll wheel support for the likes of Logitech and Microsoft mouse referred to the situation as "a bit of a struggle to say the least."

  • Intel Wi-Fi 6 AX200 Launches With Linux Support In Tow

    The product page does list Linux support that comes as little surprise these days. In fact, back in January we wrote about Linux support for these new Intel adapters within the "IWLWIFI" driver and that enablement is now present in the Linux 5.1 kernel.

read more

Unix vs Linux: 7 Key Differences You Should Know About

Čet, 04/04/2019 - 04:22

Basically, GNU Project wanted to make an operating system similar to Unix, but at the same time separate from it. Like it shouldn’t contain any code from Unix so that it could be further modified and distributed without limitations as free software. Since their own kernel was incomplete, the GNU Project accepted the Linux kernel, and they generated operating system GNU/Linux.

Also: The Differences Between Linux and Windows Containers

read more

The end of the desktop?

Čet, 04/04/2019 - 04:16

I’ve been predicting for a while that Microsoft is moving us away from its PC-centric Windows operating system to a cloud-based rental version of Windows.
Now, with the Windows Virtual Desktop beta finally showing up, we’re a step closer to the death of the PC.
I’m old enough to remember how the PC changed everything. Before it, computer users depended on time-sharing systems and dumb terminals, and the companies or schools that owned the centralized computing power called all the shots. After it, we all had our own computing power right on our desks, to do with as we pleased.
The arrival of the beta Windows Virtual Desktop is a harbinger of the end of the PC era. We’re about to take a big step back to the centralised/controlled past.
And maybe that’s OK for most people. I’ve noticed that, even as our lives become ever more centred around technology, fewer people actually are interested in the technology itself. Oh, they love using it, but understanding it at a deep level? Not so much.
Of course, at one time, to get any work done with a computer, you first had to learn a lot, about computers, operating systems, commands and more. Eventually, “friendly” became the most important adverb in computing circles, and we’ve reached the point in user-friendliness that people don’t even talk about it anymore.
Today, Google has shown with its Chrome OS that most of us can pretty much do anything we need to do on a computer with just a web browser.

read more

O-RAN Alliance starts software group at Linux Foundation

Čet, 04/04/2019 - 03:59

The O-RAN Alliance and the Linux Foundation announced the creation of the O-RAN Software Community (O-RAN SC), to help develop open source software for the O-RAN Alliance's open network architecture. The initial set of software projects may include near-real-time RAN intelligent controller, non-real-time RAN intelligent controller, cloudification and virtualization platforms, open central unit, open distributed unit, and a test and integration effort to provide a working reference implementation.

Working with other adjacent open source networking communities, the O-RAN SC will enable collaborative development across the full operator network stack, the groups said. It will be sponsored at the Linux Foundation by the O-RAN Alliance.

read more

Linux Gaming Won't Find A Mainstream Audience Until 3 Things Happen

Čet, 04/04/2019 - 03:55

I've been Windows-free for about 8 months, and I recently published a rather controversial article outlining my experience. Those impressions, however, were largely based on using Ubuntu as my daily driver. I received constructive feedback from the community and challenged myself to start exploring and contrasting the user experience on several other popular Linux distributions like Fedora, Manjaro and Linux Mint.

Currently I'm 4 distributions deep in a study that spans a total of 9 and I can already report a sobering reality: it's remarkably elegant on some (at times easier than Windows), but it's also notably inconsistent.

read more

Anniversary of LF Networking

Čet, 04/04/2019 - 03:43

  • LF Networking Passes One-Year Mark with Expanded Cross-Community Momentum

    LF Networking (LFN), which facilitates collaboration and operational excellence across networking projects, today announced continued community momentum, including further collaboration with Standards bodies, evolution of compliance programs, new project milestones, and increased integration with adjacent communities. Formed in January 2018, LFN is focused on nurturing integration, efficiencies and member engagement across FD.io, OpenDaylight, ONAP, OPNFV, PNDA, Tungsten Fabric, and SNAS as well as the broader open source networking ecosystem. As the projects are hosted under the same umbrella, LFN builds upon synergies to enable rapid innovation and adoption.
    “We are thrilled to have recently celebrated our first year as an umbrella organization, bringing continued growth across the ecosystem supporting the end-to-end open source networking stack,” said Arpit Joshipura, general manager, Networking, Automation, Edge & IoT, the Linux Foundation. “The LFN community — along with other ecosystem partners, including standards bodies — has truly come together to evolve the future of open source networking.”

  • LF Networking Expands OVP Program for Compliance and Verification, Eases Telco Interoperability & Deployment

    Open Networking Summit North America — April 3, 2019 — LF Networking (LFN), which facilitates collaboration and operational excellence across networking projects, today announced expansion of its OPNFV Verification Program (OVP) to include Virtual Network Function (VNF) compliance testing. The expanded OVP, created in conjunction with the ONAP testing community, now includes publicly-available VNF compliance test tooling based on requirements developed within ONAP, as well as a Verified Labs Program and the induction of the University of New Hampshire-Interoperability Lab (UNH-IOL) as the first OPNFV Verified Lab.

    Initially developed to simplify validation testing of commercial NFVI/VIM products based on OPNFV, the expanded program now covers interoperability with ONAP-compliant on-boarding requirements using both Heat and TOSCA package validation. The first of its kind, OVP combines open source-based automated compliance and verification testing for multiple parts of the NFV stack specifications established by ONAP, multiple SDOs such as ETSI and GSMA, and the LF Networking End User Advisory Group (EUAG). Demonstrating the readiness and availability of commercial products based on these requirements improves time-to-market, reduces costs, and improves the overall quality of NFVI and VNF deployments.

read more

Proprietary WPS Office 2019 For Linux

Čet, 04/04/2019 - 03:35
  • WPS Office 2019 For Linux Released with Improved HiDPI Support

    WPS office for Linux 2019 was released with numerous new features and performance improvements. Here’s how to install it in Ubuntu 18.04.

  • WPS Office 11 (2019) For Linux Released

    WPS Office for Linux version 11 (or 2019) was released the other day with new features and improvements, including support for high resolution screens, skin support, and interface updates.

    WPS Office, formerly known as Kingsoft Office, is an office suite for Windows, Linux, Android and iOS, that includes three components: WPS Writer, WPS Presentation and WPS Spreadsheet. The suite is compatible with Microsoft Office formats PPT, PPTX, DOC, DOCX, XLS and XLSX, for both reading and writing.

read more

Security: Updates, Patches and Browsers

Čet, 04/04/2019 - 03:28

read more

What Linux Journal's Resurrection Taught Me about the FOSS Community

Čet, 04/04/2019 - 02:52

I'd like to point out a few things in this image. First, check out that leet green-on-black theme! Second, notice the GNOME foot in the top-left corner. This was early GNOME 1, back when it used Enlightenment as its window manager. Next, notice the top Netscape Navigator window open to Slashdot. If you are new to the FOSS community, Slashdot was the Hacker News of its time (or Reddit, or Digg, or Fark—depending on when you started arguing about technology news on the internet). Check out the specs on the server for sale in the banner ad: 266MHz processor, 32MB RAM, 2GB storage and 2GB of bandwidth.

The window below the top Netscape window is another Netscape window with a full chat application implemented inside the browser with Java. I know what you are thinking: that server in the ad only had 32MB of RAM, and you need two or three gigabytes of RAM to run a JavaScript chat application inside a browser, but I assure you, it was possible with Java.

Back in the 1990s, you would install Linux from a set of three or four floppy disks (unless you used SUSE, which required about a dozen). The user interface for the install was a curses terminal console that you would navigate with a keyboard. This install assumed that you were well familiar with disk partitioning, OS internals, networking and Linux overall. When you completed the install, you normally would reboot into a console. If you wanted to get a GUI, you then needed to configure obscure X11 configuration files by hand—that is, if your graphics hardware worked under Linux at all.

Because of how much deep Linux knowledge you needed to install and use Linux back then, a number of Linux Users' Groups (LUGs) sprung up around the country. These groups would meet and share tips and overall knowledge about Linux, and they started a new phenomenon: Installfests. During an Installfest, new Linux users would bring their computer to the LUG, and the experts would try to get Linux installed and working on it. Often experienced users also would bring their own computers to get help with that one piece of stubborn hardware they couldn't get working.

read more

Silverblue's Anniversary

Čet, 04/04/2019 - 02:41
  • Matthias Clasen: Silverblue at 1

    The recent F30 beta release is an good opportunity to look back. What have we achieved?

    When we set out to turn Atomic Workstation into an every-day-usable desktop, we had a list of items that we knew needed to be addressed. As it turns out, we have solved most of them, or are very close to that.

    Here is an unsorted list.

  • Fedora Toolbox is now just Toolbox

    Fedora Toolbox has been renamed to just Toolbox. Even though the project is obviously driven by the needs of Fedora Silverblue and uses technologies like Buildah and Podman that are driven by members of the wider Fedora project, it was felt that a toolbox container is a generic concept that appeals to a lot many more communities than just Fedora. You can also think of it as a nod to coreos/toolbox which served as the original inspiration for the project, and there are plans to use it in Fedora CoreOS too.

read more

MX Linux MX-18 & 10-year-old EeePC netbook - Fantastic

Čet, 04/04/2019 - 02:39

I am more than happy with the outcome of this experiment. I really didn't know what to expect, and I thought the MX Linux would give pretty much the same results as the rest. But no. This is a true old-device Linux, and this is where it shines when the rest don't even dare step out into the sunlight. And there are no compromises. The frugality does not impact usability in any way. You still get great looks, excellent modern software, and solid hardware compatibility. Plus, of course, blazing nimble for a 10-year relic.

MX Linux MX-18.1 Continuum has restored life to my netbook. It runs beautifully fast, it's elegant, loaded with real, practical goodies. The tremendous part is really the speed. This mini-laptop was weak even when I bought it, but to be able to keep using it in a nice fashion a decade later is truly an achievement. I want to thank all of you for your suggestions, and the MX Linux team for their excellent little product. Powerrr!

read more

Programming: PyCharm 2019.1.1, Python Bits and Linux C Programming Tutorial

Čet, 04/04/2019 - 02:37

read more