There was already a GPT partition there from last time, so it was used. The installer didn't ask (I was hoping it would) and just went along with what was there.
Hmm, didn't know this option existed. Maybe it should be clarified directly after install or on first boot.
I've got a directory /etc.old-to-3.7.4 there. Shouldn't it be in there?
I don't see many diffs, exccepting timestamps.
Personally I think it better to have no printer than have a printer show up that doesn't work anymore (which was the case in the previous upgrade). It makes it all much clearer. Hence my "good!".
I don't agree. In this case the changes were minor but I also have an install on which I work on source code, test things and/or have some very non-current apps running like proprietary Siemens emulators and such.
I would hate to have to reconfigure or reinstall them all.
So yes, I'm all in favour of keeping that as an option!
Pretty good
I have a slightly annoying issue.... I run from USB live (with persistence) One could make the bold assumption that settings should be persistent between sessions.... But every time I have to enter EVERY setting
the installer is pre-translated, your country is autodetected, so german on the fly for german people lol
note: the "terrible" sentences are probably due because the original english sentences are wrong spelt, is important to make the english ones correct first, before to try to translate to german (and then wait for the pretranslations which should be 95% good)
hum, that is not totally correct, I mean, the installer installs in a different way depending of you booted the computer from the bios... example: if you boot in EFI mode, an install with EFI support is made. In other words, you should boot with the wanted bios setting -before- to install elive
thanks for report this one, i didn't noticed... this is due to missing audio clips in the other themes, these errors should not appear in fact, but you can simply ignore them or disable
noted - let's see how it can be fixed...
if you re-login in desktop, your GTK selected theme is maintained?
they are included by default, only 2 extra (neededs) are installed
which ones you suggest should be removed?
all the borders are provided by e16, except for the apps that are run without borders (like chromium) because they wants to have their own ones (a stupid thing because this is a job of the window manager, not applications independently)
scite .conkyrc
search for "temp" and change the values to see if is assigned to a wrong one
@Thanatermesis
AM I right saying the persistence work "after" the 1st reboot ?
But someone booting in persistence mode, making some customization, and rebooting, won't have those config saved, but the next time yes ?
it is a bit lighter and more optimized too, some applications are also different, the build is more ready for low end machines but i think that it can be optimized even more, so yes you can help suggesting changes on it to make it lighter
@maxinou will need this one for one of its computers
I saw the same but just putting the audio files where they are expected is not the solution. Actually I don't like my interfce making too much noise, so I disable that anyway.
Wouldn't it be better to have 32_bit somewhere in the iso naming scheme here?
It' s going to get messy keeping them apart.
decreased the multiple waiting times (untested, i dont know how fast/slow is now)
yes it does, the time was 10 minutes, i decreased it to 6 minutes now
mmmh, i see what you mean, there's 3 windows that shows at start, but in fact the ones for keyboard and language are secuential so there should be not a problem with them
reiser4 should be faster but maybe for a few things are not (i have reported every detail to the dev), but in my experience ext4 was faster (building packages, isos, etc...), so my root filesystem is reiser4 which is "why not?" and my home is ext4 (which is used for all those tasks, not the root partition, that is only for the os)
this animation is the "requires attention" notification (when somebody call your name for example)
same for terminals, try the bell (after to run, focus your mouse to another window):
sleep 4 ; echo -e "\a"
yeah that is e17 and its emodules, they are not in e16, so you should use an external tool instead, maybe you found one from apt-get that will stay at your trayer
or, just use (with maybe more options):
setxkbmap fr
that's fast too
well, we can just and simply use the Suggest section for that
yes that is a difficult thing because:
things to add will require extra resources / disk space, etc... (for example, I would have liked to include freecad, as a really-good cad alternative, but it is too massively huge and so is not good to have by default because of this. Daemons / services will add extra ram resources too, etc
it is really useful for everyone to have by default?
it matches the generic taste of most users if that way?
how much difficult (or too easy) is to implement? for example "flint" is a nice feature that has been directly added because its at the same time a pretty small package, and pretty needed/wanted for most
etc
About the "votes", we can use that section of the forum that way (activating votes if they are not activated for that section already), but at the moment there's (we) are not much people so votes are very low right now
note that this is a very complex thing not easy to benchmark, for example "write something" is not enough, let's say, a plain big file is just a plain big file, filesystems acts in a much more complex way (sorting files, organizing them (defrag) when writing, finding them by their hash, async features, etc...) in fact there's not a really good way to run a benchmark for these things
so this concludes in a very simple thing: the best benchmark is just the "real usage benchmarks"
for example, I do a lot of package building, copyng tons of files in a bunch, using rsync... I should then instead just benchmark the same "runs" between one filesystem or other
by other side, a good & generic benchmark that can be done would be to compile a package, not very big but that requires compiling... let's say thunar for example. For that, "apsrc thunar" in a temporal dir (enable deb-src repos), make sure that you have the dependencines installed (dpkg-checkbuilddeps), and then "dpkg-buildpackage -us -uc -b", since this worked in a -first- time, reboot the computer (to ensure caches are cleaned up), and boot again, download the sources, and run the benchmark "time dpkg-buildpackage -us -uc -b", it will show the time needed to build - This is a very good generic benchmark because the filesystem is pretty used for this task, searching libs, files, writing a few ones, etc...
hum.. can somebody tell me the steps to reproduce? the installer should not be the cause (pre-closes nm-applet if running, before to run it) @yoda
it is on clean installs
mmh, there should be only EFI or BIOS partitions, on GPT disks (none of these on msdos disks), so, if you booted in EFI you need an EFI partition, if you booted on legacy you need a bios partition, and yeah they are detected and used automatically by the installer if you had them previously
hum, yes but this should contain the previous system so probably more than just the "cups" dir has changed... use "meld dir1 dir2" for that, its much friendlier and useful
yeah but i need to know first how that (wrong) printer was configured, if recyclated from previous system or autodtected/added by elive, and then in any of these cases fix / improve that
sorry! i meant "first option", so we all agree then
hi @Hammer459, the persistence has been not very good tested yet! the last time i tried it in recent beta's it was unable to create the persistence partition (because of the new EFI structure on the live media), I need to work more on that
then i think it should be considered BETA and not ALPHA anymore
yep, that also, it works after the 1st boot FROM a persistence already created (so this means, the 3rd boot), so:
boot and create the persistence partition from the auto tool
reboot and start using the system, NOW the things starts to be recorded
reboot: your settings and files and everything should be available because was started to record previously
also i have not tested it with e16 too, since i was unable to make it working with the auto tool in my last test
yes, i need to work on that because requires a TON of work lol (website with all its elive plugins recognizing the new structures, giving the downloads, uploading tools, building tools, usb-bootable-elive tool, etc etc)
hum, not really, because a "raw write" is just that and it doesn't use any filesystems complexities, it mostly just writes on disk like every fs does. NOW: if you are copying a big directory with lots of files (specially small ones), then the filesystem works more, organizing the files in the new places, etc...
Thanks a lot @Thanatermesis I'll download it immediately (I'll ask keyra for zsync, I don't know how it works), but I'm very curious to know why my Intel Atom 2600N is recognised as 32bit only.... it's strange.... I'll try it, and for that you say that is even more optimized I must say that today I work some time with my 3.0.6 (doesn't work with 3.0.6 since some weeks while testing 3.7.x and I had been still surprised how fast 3.0.6 is in my low HP Now I'll alternate test between 32 and 64 bit releases, nice!!!
We should've done that the previous time. Then I deleted the old default printer and made a new (identical one). This time there was no old printer at all so I made a new one ...... identical to the old one.
So an Alpha is now my main work machine. Crazy. So fast. Dell XPS 13. I kinda like the Winter theme and no issues yet, but as I will be using it constantly now, likely will report some soon...incredibly promising so far -
Not 100%.
I think the "user-only" option is very nice if you want to rehabilitate a completely messed up system. Otherwise one would be copying back all the junk that caused the mess in the first place.
I doubt that persists on an installed system after a reboot.
The better systemwide (debian)GUI option is to use "sudo dpkg-reconfigure keyboard-configuration" as already mentioned here: Howto use E16 as your daily desktop - intro first steps
I do not think the time is right for testing e17/e22 yet but that is for Thana to decide.
As long as we're in alpha/beta testing I think that the live-boot shouldn't even offer the option of chosing but go straight into e16....for now.
The user always will have the option to log out and then log into the other DEs. Allowing to chose at first boot just creates expectations which cannot be upheld in a short timeframe.
It makes forum posts messy getting the two (or three) mixed up ...... methinks a separate e17/e22 beta testing howto wiki entry would be good too.
That way e17 lovers can help each other out in creating own modules, fixes and suggestions until @Thanatermesis starts working on it.
lol
32Bit special build 
Now I'll alternate test between 32 and 64 bit releases, nice!!!
