Ir para o conteúdo
ou

Software livre Brasil

Tela cheia Sugerir um artigo
 Feed RSS

Blog

7 de Dezembro de 2009, 0:00 , por Software Livre Brasil - | Ninguém está seguindo este artigo ainda.
Mageia é um fork do Mandriva Linux, apoiada por uma organização sem fins lucrativos reconhecida e colaboradores eleitos. Mais do que apenas oferecer um sistema operacional livre, seguro, estável e sustentável, o objetivo é a criação de uma administração estável e confiável para orientar projetos colaborativos.

Este blog é alimentado pela comunidade aqui na rede SoftwareLivre.org e pelo feed do Planet Mageia English.

Mageia Blog (English) : Chronicle in May

25 de Maio de 2020, 16:19, por Planet Mageia (English) - 0sem comentários ainda

It’s been a very long time since you’ve heard from us on this blog. Now it’s time to give you some fresh news, because no matter what it seems, a lot of work has been done since then.

Organization

Many teams — the dev and QA teams in particular — are now working on a schedule for the upcoming Mageia 8. It is now available online. It seems this summer is going to be all about testing our new release!

You can already take part in the testing and check if all of our Drak tools are functioning properly, and help the QA team. The coming months should allow us to report any new bugs or update existing reports in our Bugzilla. If you are comfortable working with Perl, your coding skills will be much appreciated to help correcting all the known bugs in our Drak tools.

Infrastructure

Our “Mageia Planet” — which agregates blog articles from our active users — has just been updated and is now up and running. We have also updated the list of blogs that are featured on Mageia Planet. Please let us know if you are the owner of a blog about Mageia which can be added! Our main blogs version was also updated.

What is boiling in Cauldron?

The new 0.15 version of LXQt is now available. New versions of LXQt don’t come out so often, and we think this one could be interesting. What are your first impressions about it?

Also, we’ve got a lot of nice little dishes that are being prepared for the upcoming Menu… Plasma 5.18 LTS along with KDE 20.04 applications, Gnome 3.36, Cinnamon 4.6, all of which will be served with kernel 5.6…

Mageia 7 updates

A security alert has been published concerning our current version of LibreOffice, which is also EOL at the end of the month… Therefore, LibreOffice’s latest version 6.4.4 has been built and is currently being thoroughly tested.



Juan Luis Baptiste : New tool to update mageia docker images

14 de Abril de 2020, 17:02, por Planet Mageia (English) - 0sem comentários ainda

It took me a long time but finally I got some time to update our mageia docker images that were not updated since last year. One of the reasons for this is that the image update process is rather complicated, it has many steps to do to get the image built, tested and available at docker hub

So to improve this process I have written a new tool called build2relase. This script takes care of:
  • Building images for all supported mageia versions and for the hardware architectures they support.
  • Prepare git branches for commit as needed by upstream.
  • Push new images to github.
  • Update and push the docker official images library.
This tool simplifies the update process significantly, the only thing missing after running it is to create a pull request to merge the docker library changes on our fork upstream.  Now, to build all images is simplified to running this command:

    # ./build2release.sh -b -p -U -v

That command will build all images (-b), push them to github (-p) and update our docker-library/official-images fork (-U). With this  new tool updating images will be much faster and easier, which will mean image updates done more often, probablr once a month at least.



Bruno Cornec : Using zoom on Mageia 7

26 de Março de 2020, 14:22, por Planet Mageia (English) - 0sem comentários ainda

As lots of people confined in these difficult times, I’m working remotely. And here at home, as when I’m at work, I’m using a Linux machine to perform all my tasks. What else ?!!

Among the interactive tools I can use to interact wih my colleagues, there is Skype Enterprise (no luck on LInux, so using just a phone call, painful), HPE My Room (multi-platform with many features and usable on Mageia 7), Microsoft Teams (which is working nicely on Mageia 7 without issue, and you even have source code access under GPLv3 for an unofficial client), and the fully FLOSS Jitsi.

But some of my recent meeting requests were also using zoom. And while there is indeed a Linux client, due to libraries versions incompatibilities, it refuses to install on Linux, and even when forced to, doesn’t launch.

So I had to create a small Fedora:32 container, and with some suitable parameters, zoom is now working in it. To ease it, I have create a small script to launch the stuff:

#!/bin/bash
# Licensed under the GPLv3 🙂
mkdir -p /tmp/docker-fedora
export LUID=`id -u`
cd /tmp/docker-fedora
if [ ! -f zoom_x86_64.rpm ]; then
    wget https://zoom.us/client/latest/zoom_x86_64.rpm
fi
RD="/home"
WD="$RD/$USER/prj/fedora/"

cat > Dockerfile << EOF
FROM fedora:32
MAINTAINER bcornec@mageia.org
RUN dnf makecache
RUN dnf -y update || true
COPY zoom_x86_64.rpm /
RUN dnf install -y /zoom_x86_64.rpm
RUN dnf install -y pulseaudio pulseaudio-utils libglvnd-gles
RUN useradd $USER -u $LUID  -N -M -d $RD/$USER
RUN usermod -a -G audio $USER
RUN echo "$USER ALL=NOPASSWD:/usr/bin/dnf" >> /etc/sudoers
WORKDIR $WD
USER $USER
CMD zoom
EOF
stat=0
build=0
docker inspect pb:zoombuild 2>&1 > /dev/null
if [ $? -eq 0 ]; then
    if [ "$BASH_ARGV" = "-f" ]; then
        docker rmi pb:zoombuild
         build=1
    fi
else
     build=1
fi
if [ $build -eq 1 ]; then
    docker build --file=Dockerfile -t pb:zoombuild .
    stat=$?
fi
if [ $stat -eq 0 ]; then
    # Priviledge needed for zoom command in ctn
    docker run --device /dev/snd --device /dev/usb --rm -v $RD/$USER:$RD/$USER --cap-add=SYS_ADMIN -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v /run/user/$LUID/pulse/native:/run/pulse/native -e PULSE_SERVER=/run/pulse/native -e PATH=/usr/bin:$PATH -ti pb:zoombuild
fi

Just run that script and you can join a zoom conf call, benefiting from sound at least (I have no webcam to test the video at the moment).

So now, dear mageians no excuse to stay confined without contacts with your colleagues 😉



Olav Vitters : First responder: Fire alarm, iffy emergency exit doors

5 de Dezembro de 2019, 13:40, por Planet Mageia (English) - 0sem comentários ainda

Within Netherlands each company is by law required to have first responders. These handle various situations until the professionals arrive. It’s usually one of (possible) fire, medical or an evacuation. Normally I’d post this at Google+ but as that’s gone I’m putting the details on this blog. I prefer writing it down so later on I still can read the details.

November 6: P2000 warning

Within Netherlands any ambulance/fire department call is sent via the P2000 system. There’s various sites and apps which make that information easily available. I have one of these apps on my phone.

I noticed a Ambulance P2000 message for our postal code. The postal code could either be our building, or the one under construction next door. Until a few years ago P2000 would give the exact address, but due to privacy reasons nowadays it’s only the postal code. I ask security if there’s something. They’re not aware but they’ll monitor more closely (possibly ask around, e.g. reception might be aware).

A bit later security sees an ambulance arriving for the building under construction. The ambulance has difficulty getting to the right location due, for a while security was still under the impression it might be for our building. The building next door had various vans and construction stuff incorrectly being placed on the road. Things they should not have there, though they could’ve and should’ve cleared this while waiting for the ambulance to arrive.

November 11: Fire alarm

In the morning security had a talk with the construction crews next door about all the vans and so on blocking the road. Reoccurring problem mere days after their ambulance incident. This time they blocked way more of the road. Even the place near the goods elevator was blocked (registered fire department arrival location, plus where we direct all ambulances towards).

At 13:23 an automatic fire alarm for our building. Various people respond via walkie talkie. The location normally would require walking (running) up 7 floors; unfortunately this time I was on 6th floor. Arriving on the floor various indicator lights are indeed on, plus I meet various other first responders, plus security (who happened to be near the affected floor). We’re 4 in total.

The fire detector is located in a shaft. Opening this up requires special keys. Interestingly enough 3 out of the 4 responders are the ones who carry such keys. We open the shaft after doing a door check. The detector is one which detects smoke (security advised this); so it’s not the usual temperature sensitive one. The shaft itself is very warm, but there’s also some heating equipment in there. The heat combined with a detector which only responds to smoke gives us a suspicion that the heat is not indicative of anything. Despite that, there’s no indication of a reason for the detector to go off.

Two (me + another) are sent to investigate lower floors. We check one floor lower. Again we follow door procedure, accidentally open the wrong shaft, then the right one, nothing aside from heat. We try again another floor down, shaft is way cooler but nothing can be found. After communicating the latest finding we’re asked to regroup. After regrouping we decide to investigate the floor above.

On the floor above we notice some renovation going on (security is aware). But also an opened elevator shaft and some running equipment near that shaft. Opened shafts are very dangerous, it would allow any fire to easily spread within the building. This happened to a building 300m from our location.

As first responders this is the end of it. It was a fun exercise. Security however is not amused (understatement). Due to various rules no evacuation sound went off. Due to the fire detector being in a shaft any additional detector would’ve resulted in the automatic and legally unstoppable evacuation of the entire building.

As common in pretty much any bigger building, the fire detectors are linked to the fire department. After the detector went off the fire department call centre allowed us to investigate. There was some communication mishap in that call centre. While we were investigating the fire department crew showed up, lights and everything. This was quite visible for the next doors construction crew.. the ones who keep blocking the road. This was entirely unexpected, so it took a bit of time to talk to the fire department crew. The crew was however more than happy to wait for our investigation to be finished.

Iffy emergency exit doors

In case of a fire people are supposed to use the emergency stair cases. If you open any of such doors anywhere in the building security is immediately notified. This is for safety reasons; maybe something is wrong, there’s a real evacuation going on and it’s not something caught by the fire detectors or a call to security.

These emergency doors can also automatically unlock. Due to age, all over the building these doors are now automatically unlocking often. Leading to all kinds of false positives for security. A bit like a testcase failing because the hardware running the testcase is faulty.

I get asked a few times to manually close a few doors. A few times I notice. Many other times I do not notice the walkie talkie communication, nor my office phone or mobile being called. Oops.

I’m wondering if I can make calls from numbers to always be noisy. I often use vibrate/silent mode instead of e.g. do not disturb.

Eventually the problem is mostly fixed. It required the right company coming down various times.



Mageia Blog (English) : Mageia 6 End of Life – Time to Upgrade

2 de Dezembro de 2019, 22:33, por Planet Mageia (English) - 0sem comentários ainda

As you know, Mageia 7 was released this summer, followed shortly after by Mageia 7.1. It is time to say goodbye to Mageia 6 – updates have stopped, including security updates.
As usual, before the upgrade, do a backup of your data and documents.
You have a couple of ways to install Mageia 7:

1. Do a clean installation from Classical or Live media. In this case, you will keep the data in your /home if it is in a separate partition, as is usually the case – but do check! The root partition will be formatted during the installation process.

2. Upgrade from the command line, as described in our release notes.

3. Upgrade through the applet in the system tray. This option was disabled until recently as conflicts prevented the upgrade from completing successfully. These have been resolved, so you will now be offered an upgrade when you next update your Mageia 6 system.


Whichever method you choose, we highly recommend that you upgrade your system, as Mageia 6 is no longer supported and is no longer receiving any security updates.



Tags deste artigo: mageia