Skip to main content

Current Mandriva situation

These last days, numerous rumors have been spread about Mandriva’s situation. Out of respect for our clients and community, we want to clear the situation.

Mandriva has always been involved in investment and aquisition processes. Over the past years, Mandriva bought Edge-IT, Conectiva and Linbox FAS. Today, Mandriva is in takeover talks with various investors. These discussions concerning new investments in Mandriva are not new, they have happened all throughout the life of the company, and there are still going on today. We want to stress out the fact that Mandriva has not been bought by anybody.

Like many other companies, Mandriva has been impacted by the economic slow-down and took advantage of this period to develop and improve its products: an operating system dedicated to a uniquely ergonomic server (MES5.1), the most reliable free machine-management software on the market (Pulse2), Mandriva Smart Desktop to simplify the use of office desktops, education-dedicated distribution. Mandriva is also involved in many research projects, and is constantly working with the community to increase the efficiency and ease-of-use of its distribution.

We are beginning to harvest the results of this development work with hundreds of thousands of PCs using the Mandriva OS sold in South America, Asia and rapid sales of Pulse2 and MES5 in Europe. So it is unsurprising that Mandriva has once again attracted the interest of industry decision-makers.

Arnaud Laprévote
Mandriva’s CEO

Source

Comments

Masokis said…
wow.. peminat mandriva..
masokis pernah guna..tp kejap je..
lebih minat oshirix
zamri said…
Ya. Terpulang kepada kecenderungan dan minat masing2. Yg penting Linux. :)

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy

postfix - mailbox size limit and message size limit

postfix is my MTA of choice. I use it for my mailserver because its simplicity , security and sendmail-compatible (the widely used smtp in the world but not as secure). It is also extensible by plugging other servers for various purposes (antispam, antivirus,database etc).

I had one problem with file attachment larger than 10MB. Users couldn't send it although I have setup squirrelmail (SM) to be able to attach files summed up more than 20MB and I had modified php settings as per here. The problem was not in SM setting. It was postfix. By default, attachment size that can be sent by postfix is 10MB ~ 10240000 byte. How did I know it? I looked in log file (for my system it is in /var/log/mail/errors. For other system, the file to look is /var/log/maillog). The line looked like this:

Feb 26 16:30:53 webmail postfix/sendmail[30775]: fatal: me@mymailserver.org(74): Message file too big


Solution
Open /etc/postfix/main.cf with a text editor of choice and find message_size_limit directive an…