September 30, 2013 at 20:44MagOS Linux (September release)
Of the many Linux distributions, I wanted to find something unusual and necessarily developed by our software engineers, original.
Magos turned out to be not quite a distribution in the usual sense, but a new step in living operating systems.
If you take Mandriva Linux, add linux-live.org scripts and add the modular architecture of slax ...
And then, of course, a little file processing - we get magos-linux ©
From standard live-image distros with preservation, MagOS differs in modularity, it doesn’t fit into squashfs the entire distribution kit, and each program has its own mem / loop segment, into which executable code is unpacked from the module on the fly.
Today an update came out.
One of the advantages of this approach is the possible acceleration of performance on high-end cpu, if the processor processes the unpacking of the module from .xzm faster than just reading from the media, naturally all available memory and more is used.
Since the whole system is kept in memory, fault-tolerance increases in some ways, since it is possible to change modules only under certain conditions, but there are also problems, because if the system fails, the memory will be cleared and the saved state will not remain on the disk, but also appear and new features. For example, you can create an integral module with all the necessary libraries.
The modules themselves are created on-the-fly during installation from the application center, or you can run the utility and it will convert the rpm package to a module, already converted modules can be downloaded from the repository.
In fact, each module has its own “file system” system and connects to the main aufs, like a live disk - live-cd, so the “installation” is also carried out by simply copying or removing the module from the system, because of which it is quite easy to assemble a permanent package programs.
---------------------------------------------- Screens --- ------------------------------------------- Screens ------ ---------------------------------------- Screens --------- -------------------------------------
in qemu - it is better to include KVM, in virtualbox PAE support.
you can write in the boot parameters
to disable compiz, if there is no support
for it depending on the hardware and loadable modules, loading takes some time;
this is a “non-lts” iso image of today's release, I gave 2 gigs and 4 kernels to the virtual machine, it booted up in about one and a half two minutes, the acceleration module, accelerates this time up to 20 seconds.
Since the development takes a lot of time, it was decided not to deal with your distribution, but to process another distribution first and it turned out to be easier to work with rpm, although in principle you can take any distribution - it’s a matter of people and time to complete the scripts, now it’s dew cloning, it used to be magic, and it started back in Mandraiva. There is a repository on github, mirrors on Yandex, but one of the interesting tasks was the creation of MagNet, a distributed network for storing modules and communication between users, now the concept is undergoing some changes. Together with the announced new cloud services, new opportunities for implementation have appeared.
One of the best decisions was to install the distribution in two clicks - unzip and run the script for changes in the bootloader, marking up the disk areas is not needed - it works with ntfs, vfat, ext3, everything works even on the current system, it is easily put on a flash drive, although there is potential implementation is possible for more serious tasks, but this will require a lot of development efforts, and testing and debugging are also necessary.
Now the work is focused on accelerating the start of the system to the DE level from 90 seconds to 20, as well as on the development of a converter into modules, fixing some errors.
Like a real openSource project, everything is done here freely.
With responsibility for everything good and bad, as usual - the GPL.
In its full form, the distribution takes the gig link to the mirror or the link to the BT tracker, since now the rosa lts (long-term-support) and fresh distributions are taken as the basis, then from the available desktops - gnome. kde. lxde. Tar.gz also contains scripts for converting to iso, so after correcting the configurations and changing the passwords, you can make your own disk image.
if you are interested in looking at the code or helping out, go to github.com/magos-linux , the main communication takes place on the forum .
The latest build is available on the torrent tracker.
Happy Linux!
PS
links and descriptions are also available on the wiki
github.com/magos-linux/
Magos turned out to be not quite a distribution in the usual sense, but a new step in living operating systems.
If you take Mandriva Linux, add linux-live.org scripts and add the modular architecture of slax ...
And then, of course, a little file processing - we get magos-linux ©
From standard live-image distros with preservation, MagOS differs in modularity, it doesn’t fit into squashfs the entire distribution kit, and each program has its own mem / loop segment, into which executable code is unpacked from the module on the fly.
Today an update came out.
One of the advantages of this approach is the possible acceleration of performance on high-end cpu, if the processor processes the unpacking of the module from .xzm faster than just reading from the media, naturally all available memory and more is used.
Since the whole system is kept in memory, fault-tolerance increases in some ways, since it is possible to change modules only under certain conditions, but there are also problems, because if the system fails, the memory will be cleared and the saved state will not remain on the disk, but also appear and new features. For example, you can create an integral module with all the necessary libraries.
Comment by Mikhail (author, developer):
Modules are layered on top of each other, the top layer wins (if there are 2 different files with the same path, it is accessible only from the top layer)
The modules themselves are created on-the-fly during installation from the application center, or you can run the utility and it will convert the rpm package to a module, already converted modules can be downloaded from the repository.
In fact, each module has its own “file system” system and connects to the main aufs, like a live disk - live-cd, so the “installation” is also carried out by simply copying or removing the module from the system, because of which it is quite easy to assemble a permanent package programs.
in qemu - it is better to include KVM, in virtualbox PAE support.
you can write in the boot parameters
no3ddesktop, xdriver=fbdevto disable compiz, if there is no support
for it depending on the hardware and loadable modules, loading takes some time;
this is a “non-lts” iso image of today's release, I gave 2 gigs and 4 kernels to the virtual machine, it booted up in about one and a half two minutes, the acceleration module, accelerates this time up to 20 seconds.
Since the development takes a lot of time, it was decided not to deal with your distribution, but to process another distribution first and it turned out to be easier to work with rpm, although in principle you can take any distribution - it’s a matter of people and time to complete the scripts, now it’s dew cloning, it used to be magic, and it started back in Mandraiva. There is a repository on github, mirrors on Yandex, but one of the interesting tasks was the creation of MagNet, a distributed network for storing modules and communication between users, now the concept is undergoing some changes. Together with the announced new cloud services, new opportunities for implementation have appeared.
One of the best decisions was to install the distribution in two clicks - unzip and run the script for changes in the bootloader, marking up the disk areas is not needed - it works with ntfs, vfat, ext3, everything works even on the current system, it is easily put on a flash drive, although there is potential implementation is possible for more serious tasks, but this will require a lot of development efforts, and testing and debugging are also necessary.
Now the work is focused on accelerating the start of the system to the DE level from 90 seconds to 20, as well as on the development of a converter into modules, fixing some errors.
Michael:
As for “from 90 seconds to 20” - these numbers are different on different machines.
And I would not say? that we are focused on this. We do not have many developers and everyone is engaged in what is interesting to him. In this case, Anton started with this module, in the future we will have to replace the equipment definition scripts and either it will go into the assembly, as our difference from the dew, or it will remain the same as in the dew.
Of the opportunities?
- loading from media to memory and removing media
- three (four for 2012) environments for user choice + rich set of applications, all with a total weight of about 1G
- configuration via ini file without changing distribution modules
- compiz effects slave. The tables are built-in and configured for use in KDE Gnome LXDE, they can be turned on from the first start
- the grub4dos bootloader's own modification with support for the control buttons in the graph. mode.
- Download over the network.
- the ability to turn the system into a server with ftp smb nfs dhcpd router freenx (terminal server) pxe (loading thin clients) sshd hostapd through editing one ini file
...
my options are limited in the meantime that I still
have a little more than is required to maintain the assembly in the current state, assembly releases occur once a month.
There will truly be development when there are developers like Anton (neobht) and Alexander (bether), ready to take on something and bring it to a working solution.
Like a real openSource project, everything is done here freely.
With responsibility for everything good and bad, as usual - the GPL.
In its full form, the distribution takes the gig link to the mirror or the link to the BT tracker, since now the rosa lts (long-term-support) and fresh distributions are taken as the basis, then from the available desktops - gnome. kde. lxde. Tar.gz also contains scripts for converting to iso, so after correcting the configurations and changing the passwords, you can make your own disk image.
if you are interested in looking at the code or helping out, go to github.com/magos-linux , the main communication takes place on the forum .
The latest build is available on the torrent tracker.
Happy Linux!
PS
links and descriptions are also available on the wiki
github.com/magos-linux/