IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Both Xfce-based images have been falling back to
a completely wrong Monospace font alias implementation
at least for ASCII part which resulted in hard to read
Serif font in Terminal (even if e.g. Cyrillics are OK);
adding Liberation seems to work around this.
Too bad this commit didn't hit the recent starterkits.
The goal of implementing rescue_remote was regular-rescue.iso
indeed; so let's both add it and bump the default boot timeout
to 600 deciseconds, that is, a minute: 20 seconds might be way
too low for some slow IP-KVM/iKVM use cases.
It's all started with glebfm@ wondering why
kernel-modules-v4l-std-def ends up installed
with altlinux-p7-server-ovz.iso; this has been
tossed in by kernel-modules-staging-std-def
which has been requested by +wireless.
WiFi support is nice to have handy when one hits
a wifi-only device and no means to bring networking
up (the infamous "unzip.zip" situation) but it's
a bit too much to force a bunch of extra drivers
specifically known for sub-par or unknown quality
onto everyone installing an ALT Linux based server.
So let's contain that feature to desktop/rescue images
and exclude it from their common base with server ones.
It's been added to al of tde-based images
but it looks like LiveCDs make more sense,
and it's the regular-tde.iso that hits both
regular builds and starterkits; let's put it
there and hope it gets spotted appropriately.
It's been both somewhat problematic as of plymouth-0.9.x
due to broken rendering and explicitly asked for by asy@
regarding sysv-tde starterkit which makes sense for an
image targeting low-resource systems as well.
It's been noted by aris@ that the experimental
regular-leechcraft.iso lacks both upower and bluez;
let's try and add those missing to all of regular
desktop images.
This is our answer to this VZstats FAQ entry:
Q: Why is it opt-out rather than opt-in?
A: We just don't have a good place
(such as installer or some GUI)
to ask you for opt-in.
Well ALT Linux got one. :)
sem@ noted that it had to be dropped from xfce4-full metapackage
as this package is built on top of gstreamer 0.10 and the API it
uses was dropped from gstreamer 1.0 so it's gonna die some day;
upstream recommends xfce4-pulseaudio-plugin but it's not suitable
to some of us, like Speccyfighter; well let's add the good ol'
plugin to sysv based flavour for now and see how it holds.
Shame on me, gnustep mixin is only used in gnustep flavour
while wmaker one is used in both gnustep and wmaker flavours.
So the default serif fonts in regular-wmaker.iso were still ugly.
I don't know of [k]powersave interactions with systemd
and the rest of that ilk, let's be cautious and only provide
it for sysv-tde images which have been actually tested
by Speccyfighter who asked for this package.
Can't tell for sure but something seems to break
suspend menu option (hibernate isn't supported in
all of the regular builds/starterkits just yet).
This refactoring is aimed at both providing reasonable
alterator package set in server-ovz (and server-hyperv)
while purging the install-time modules from plain server
as these were useless without a frontend package like
the web-based alterator-fbi.
It used to run NM without any kind of applet which is
not exactly usable unless it's DHCP over Ethernet there;
provide connman and qconnman-ui (applets on the road).
This has been proposed for server-hyperv by lewellyn@freenode
last summer, looks like a reasonable default for all of the
server images as those interersted in bridge setup are going
to do a few more things anyways.
This image has been cleaned up somewhat thoroughly
regarding its installed package base but partitioning
has remained poorly generic with swap etc; it's now
been set to use 3/4 Gb as a minimum (to fit 1Gb VMs
or USB sticks just fine) with the only partition
created being root one; those wishing something else
are welcome to go ahead and partition by hand anyways.
See also https://bugzilla.altlinux.org/30024
propagator-20150306-alt1 and make-initrd-propagator-0.25-alt1
have made it actually possible to use resulting LiveCD images
along with USB flash media to achieve data persistence that's
been long available for BIOS boot mode (see also #28289).
This isn't perfect but let's try flipping the switch:
all desktop regular builds are now "live_rw" by default
in EFI mode.
This requires mkimage >= 0.2.17.
This image doesn't deign to waste one's time by presenting
them with a bootloader menu and a few other things;
make it even less verbose where not neccessary.
xpra.org and winswitch.org are wonderful applications
helping one working with X11 apps all over the place,
running those on local and remote desktops and servers
with persistent sessions.
These aren't exactly trivial to plan and use but icewm
isn't for newbies either; thus these seem like nice match
for an "X11 thin client" image.
Size addition is ca. 50 Mb as of today which is a lot
but worth it.
This project has evolved/merged into LXQt which has been
packaged for both p7/t7 and sisyphus by now, no need to
carry on deprecated bits.
NB: 0.6.x still have it as t6/p6 still bear razorqt.
The issue at hand is that some sneaky stage3 alterator modules
seem to have tossed alterator-browser-qt (thus libqt4* and friends)
into base server installations; while this must be solved in within
package base and should be worked around by server feature probably
let's start out with leaf targets.
epiphany (or fontconfig?) insists on URW fonts for rendering
webpages like http://opennet.ru which hurts my eyes; looks like
/etc/fonts/conf.d/60-alt-post-user.conf would override these
with e.g. Liberation or Dejavu (with the latter being inferior
to the former, IMHO).
...so that regular builds really have common ground again,
which is something that got broken with regular-jeos introduction;
adjusted jeos and builder flavours to make use of this.
There's considerable confusion accumulated over the
expansion of regular builds with non-GUI targets:
- bare meant quite a lot including wireless;
- base meant GUI base actually,
so rescue, server, and especially jeos images had to
either cope with the bloat or start from scratch.
Let's fix "base" first...
Looks like QEMU 2.2.0 gets surprised with some kernel module
that udev tries to load during "Populating /dev:" boot stage;
dropping *both* +vmguest and +wireless dependencies does help
while switching to un-def kernel flavour doesn't (as is or with
any single one of these two deps removed).
Thanks user who reported the problem at opennet.ru
(alias "myhand").
altlinux-p7-kde4-20141212 images had a problem:
- the generic starterkit profile is tuned
for modest disk space consumption;
- KDE4 is quite extensive;
- kde4-regular subpackage tosses in most of KDE4 SC
...thus the livecd wouldn't autopartition enough
space for root filesystem when being installed.
volumes-profile-lite specifies 10Gb rootfs currently
which is just fine (-kdesktop one starts with 30Gb),
let's use it until vm-profile management is imported
into mkimage-profiles or things are redone completely.
There's no more livecd-gnome3-nosetup, it's been renamed
to setup-gnome3-done with no P:/O: to reduce repo spam.
Should have cherry-picked this into master back then :-/
There's GNOME 3.8 in p7/branch and it has no initial setup tool
thus no disabler is needed anyways; I've fixed this a while ago
but seem to have managed to lose the commit somehow :-/
So ALT Linux has got decent build tools but no one even knows
about those, right? And starting to use those is somewhat tedious
as it requires ALT installation with a specially crafted user account?
live-builder.iso has been useful enough to consider including its
relative into starterkits skipping regular builds for roughly the
same reasons as those for installers: we're better off helping users
to get onto the stable platform bandwagon than having them excited
with Sisyphus just to hit some wall down the road (even if we warn
of these walls well in advance most of the time), and while packages
tend to get into branches via sisyphus repo it's still better to stay
on the safe side with what we make easily available.
