Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - filip

#46
Artwork & Screenshots / Re: Februar 2016 Screenshot Tema
February 04, 2016, 11:56:22 PM
Quote from: jedi on February 04, 2016, 11:44:19 PM
Here you go...



Beatifull! Great job jedi!  :)
#47
VSIDO Changes / Re: New Test ISO's
February 04, 2016, 11:37:21 PM
Quote from: VastOne on February 04, 2016, 03:20:16 AM
I have created new ISO's to test the VirtualBox Guest Additions

If you have and use VirtualBox, please download either of the ISO's to help test them

They only used an additional 2 MiB on the ISO sizes and the benefits for me during the build is tremendous

Awesome! :)

QuoteFilip will should also be happy... :D

Don't mention it...  :D :D :D

Just to confirm, there are no more tint issues, and GA work like a charm ( VBox 5.14 )! :)


#48
VSIDO Discussions / Re: TRIOS linstaller questions
February 04, 2016, 11:29:15 PM
Another update ( "mia8-dev" ):

- Added "--quet" argument to "mkfs.jfs", which prevents it from hanging when formating partitions which allready have an FS ( otherwise mkfs would ask for confirmation, which cannot be provided through installer ).
- Fixed mount options for all FS's, so no more failed mounting ( btrfs, jfs and xfs in particullar ).

So, right now all supported file systems ( exluding ntfs, fat & hfs+ ) are fully usable for a root partition ( both formating and mounting ). :)

Upgrade is strongly recommended for anyone planning to use btrfs, jfs or xfs for root ( otherwise, no rush ). :)

Quote from: jedi on February 04, 2016, 02:15:42 AM
@filip, love your avatar!!!  8)

Thanks jedi! :)
#49
How To's / Re: How To: Building the VSIDO Installer
February 04, 2016, 10:49:08 PM
@Misko pretty much said it all. :)
Thanks for sharing and for the effort!

Few notes along the way:

@VSUDO config:

To avoid having to change it on every rebuild, you can do it once, build the packages and then tuck away somewhere the "linstaller-config-trios" ( you can change the "trios" to "vsido" in debian/control ).
You can then re-use it, since it doesn't have a versioned dependencies, so should work with any new version of the installer. :)

@UEFI:

You can also delete all those lines, instead of commenting them ( which is a pain whenever there's more than 2-3 of them, for me atleast :D ).

@pkg installation:

A (much) easier way would be to put them all in a script:
echo '#!/bin/bash
sudo dpkg -i python-t9n
sudo dpkg -i python-keeptalking
sudo dpkg -i python-libbricks
sudo dpkg -i keeptalking
sudo dpkg -i bricks
sudo dpkg -i linstaller-modules-base
sudo dpkg -i linstaller-frontend-cli
sudo dpkg -i linstaller-frontend-glade
sudo dpkg -i linstaller
sudo dpkg -i linstaller-config-trios
sudo dpkg -i linstaller-session
sudo dpkg -i live-config-linstaller' >> /tmp/install-installer && chmod +x /tmp/install-installer && /tmp/install-installer

^ copy/paste all at once. :)

Cheers!
#50
VSIDO Discussions / Re: TRIOS linstaller questions
February 02, 2016, 09:52:05 PM
Important heads-up.
I've commited a fix for a nasty bug introduced in a recent commit ( "mkfs" detection ), which caused installer to freeze completely if user tried to edit a partition which contains a file system whose "mkfs" was not found.

What happens is that installer tries to preset a format box to the file system that partition in question allready contains ( when you edit an existing "ext4" partition, format box gets preset to "ext4" ).
So, instead of trying to preset an non-supported FS ( and turn into ice cube along the way ), it first checks to see whether or not that particular FS is supported ( meaning that "mkfs" for that FS exists ).

So, new ( still testing ) version is released.

Also, issues with xfs & reiserfs are now fixed.

Update at will. :)

For detailed changelog see here ( versions "mia6" and "mia7" are new ).
Cheers! :)
#51
VSIDO Changes / Re: VSIDO new linstaller Discussion
February 02, 2016, 04:34:44 PM
Quote from: VastOne on February 02, 2016, 03:12:06 PM
Quote from: Snap on February 02, 2016, 07:02:36 AM

@PackRat: You are right. I'm too used to su-to-root, so I hardly ever use sudo for anything.

About the welcome script, I think the it didn't popped up after these two last installs. I might be wrong. I have a pretty crap memory.

@snap

If you elect to change the root pw from the installer, it will fail as it is designed to work with sudo enabled.  I would hear more about su-to-root as a possible replacement specific to vsido-welcome needs (and anything/everything else related to sudo)

Quote from: filip on February 02, 2016, 02:43:51 PM


GRUB is hidden by default, if there are no other OS's found.
However, this behaviour can be disabled with a seed.
[module:bootloader]
should_hide_menu = False


:)

Btw, (holding) "Shift" is the key to display GRUB.

@root pass:

I'm looking into what can be done about it, but it seems that both Debconf and user-setup were designed around Debian default of not having a root pass at all ( empty one ), or there is a bug in either one.
I might be wrong though, so when I have a more definitive answer, I'll let you know. :)

I will add the seed for grub to show up, that is the expected or 'normal' behaviour we here have been used to

On the root pw issue, is it a problem enough to change it?  The message during install is clear enough in stating the sudo functions will be removed and it is recommended NOT doing that.  IMO, anyone with knowledge enough to make this choice 'should' know the consequences behind this choice.  It is especially important to make the decision to enable root on a 'when needed' moment IMO.

Perhaps adding a more information on how easy it is to enable root password after install (ie sudo passwd root)

I am not sure what the solution is but like the discussion about it and encourage more

@filip, I did find a slick fix for fluxbox on the tint2 issue on the live-cd.  I hope you got to see this as well

Good idea on adding info about enabling root after install. I'll add to the installer as well. :)

@su-to-root:

I guess you guys probably know about it, but I'll mention it just in case.
sudo -i
... can be used for the same "effect". Meaning that you get a root (login)/prompt, same as with "su".

@Flux:

I've seen it, but didn't have time to download.
Will do later today & report back. :)
#52
VSIDO Changes / Re: VSIDO new linstaller Discussion
February 02, 2016, 02:43:51 PM
Quote from: VastOne on January 31, 2016, 12:30:26 AM
@Filip

Thank you for the feedback.  Regarding VBox Guest Additions, they fall just outside of the 'need vs want' space saving situation... They take up a huge space on an ISO for a small amount of people to benefit from.. I like them too and set them up if I need them... it is that easy, but it is not feasible to have them on the ISO

Interesting that a logout did not resolve the tint2/X issue.. on every test I ran with it that worked.  The install worked and that is what matters.. By restarting FluxBox from the right click menu options you can reset tint2 as well

I am a huge fan of IgnorantGuru, the dev of SpaceFM and several other incredible viable tools.. We have used SpaceFM from day one here and really I could not see ever using any other file manager

We already use SMTube as part of SMPlayer ...

Apt is that way by design knocking off 40 MiB of space on the ISO using bleachbit before building does this... Sorry!

Great feedback!

@vbox:

Yeah, I tought it's probably a space issue.

@IG:
Indeed. Guy has really awesome ideas, and even more awesome way of implementing them in practice ( I'm talking about spacefm primarily ).
Making the thing lightweight, fast and simple like it is, and at the same time having the level of customization and advanced features it has, is beyond words really.

I, for example, do most of the dev work inside it. Since using plugins I can do a lot of stuff, ranging from building packages, interacting with git, having an app menu, comparing files etc, all without the need to frequently switch to other applications or terminal(s).

@apt:

I tought it perhaps got left out unintentionally.
Certanly not a problem, and there's certanly no need to be sorry! :)

Quote from: PackRat on February 01, 2016, 12:21:40 PM
Quote from: VastOne on February 01, 2016, 04:00:13 AM
^ That is new... I have only seen it as of today and only in using the Automatic partitioning option.. Did you use that one or Manual partitioning?

I always use manual partitioning.

The hidden grub timeout is set for 2 seconds - which is probably enough time to use the key binding to get to the menu if you want to boot a different kernel or rescue mode - what is that key combo, ESC? However, since VSIDO is somewhat unique in installing memtest by default, you may want to go back to the usual visible grub menu option.

@Snap - yes, not having any users in the sudoers file is the norm if you enable the root password during install - the fine print after you switch the button to "on" points out that sudo for users is disabled when root password is enabled.

GRUB is hidden by default, if there are no other OS's found.
However, this behaviour can be disabled with a seed.
[module:bootloader]
should_hide_menu = False


:)

Btw, (holding) "Shift" is the key to display GRUB.

@root pass:

I'm looking into what can be done about it, but it seems that both Debconf and user-setup were designed around Debian default of not having a root pass at all ( empty one ), or there is a bug in either one.
I might be wrong though, so when I have a more definitive answer, I'll let you know. :)
#53
VSIDO Discussions / Re: TRIOS linstaller questions
January 30, 2016, 11:30:33 PM
Quote from: VastOne on January 30, 2016, 10:52:25 PM
I like git...  ;D

Issue is resolved as my flaky gtk theme was the culprit
@git:
Even better. :)

@themes:

I certanly don't expect you to change theme over trios-info issue itself, however if you do so and given the fact that you seem to like them Dark ones, to maybe ease the search I can recommend two:
Arc
and Vertex

Both are maintained and support gtk 3.18 ( Arc for 3.20 is also being worked on ). :)
#54
VSIDO Discussions / Re: TRIOS linstaller questions
January 30, 2016, 10:47:22 PM
Quote from: PackRat on January 30, 2016, 04:58:02 PM
RE - Memory reporting; looks to me like it is reporting the free memory, not the used:
Quote from: misko_2083 on January 30, 2016, 05:04:19 PM
Quote from: VastOne on January 29, 2016, 09:56:05 PM
^ Fantastic... Let me know when they are there and I can begin the testing.  Also keep in mind I am available at any time for any type of testing your team may need.  I do not know code as well as you all but I can track down issues and troubleshoot as well as anyone... though Misko is incredible and tough to beat!  :)
I was just lucky. :D

@Mr. Spock "Live long and prosper."  ;D

@trinfo-gtk
          @PackRat thank you for reporting @memory info

           @Disk info That needs a fix too now it says "200G MB"

@Filip nice @args. Easier to do it in *-base, turning refind part the same way could be usefull
@trinfo
Fixed both RAM & Disk usage. :)
As usual, pull latest version from git.

@refind:
Indeed. I'll see what I can do. :)

Quote from: VastOne on January 30, 2016, 09:43:01 PM
Quote from: filip on January 30, 2016, 04:42:57 PM

It's best to open a issue on GitLab ( you need to be registered first ).
Here: https://gitlab.com/trios-linux/trios-info/issues

@Crash:
Either gtk (css) causes it, or it's threading that's misbehaving. I'll look into it. :)
Though one information would help. Does it crash each and every time, or randomly ( if randomly, then it's likelly to be threading issue )?

I did register and submit this as an issue and yes it does happen every single time I run it.. it seems to make it to the very end and crashes

Edit -

I notice the same thing on memory...

Tnx! :)
Btw, I forgot to mention, you can also report (any) issues on our forums, if you prefer it that way or find it easier over git ( although GitLab makes it a bit easier for us to track them ).
#55
VSIDO Discussions / Re: TRIOS linstaller questions
January 30, 2016, 05:00:55 PM
Quote from: VastOne on January 30, 2016, 03:33:26 PM

The X11 / Tint2 issue is related only to VirtualBox... any mass changes to X and there is a few days for the devs to catch up on V-Box environments  .. Not a systemd issue yet

What will you do when X is consumed by systemd?  I see all hell breaking loose if that happens

As RatMan said, triosinfo is a great tool

Good   :D :D

@X:
Well, it's unlikelly since it needs to run on BSDs, OpenSolaris/Indiana and such, so sysd will probably remain an optional feature. :)
Besides that it still is a pain for everyone not using systemd, since it forces you to rebuild X packages for your self, and maintain them ( and there is allready a longish list )....

@PackRat:

Ahh, forgot about that. I've spotted it some time ago on Manjaro ( changes in the "free" output layout are the cause ), but forgot to fix it.
Will do in the next couple of days... :)
#56
VSIDO Changes / Re: VSIDO new linstaller Discussion
January 30, 2016, 04:49:58 PM
All good.

Except that I forgot about: http://vsido.org/index.php?topic=1124.msg12625#msg12625
So I didn't get a network, but it's my mistake...

What's important is that installer now correctly appends to GRUB_CMD:



:)
#57
VSIDO Discussions / Re: TRIOS linstaller questions
January 30, 2016, 04:42:57 PM
Quote from: VastOne on January 30, 2016, 03:51:30 PM
@PackRat... pastebinit is also a requirement in order to pastebin it... (terrible I know)  ???

@Filip... Where should reports be sent?  I have a crash using triosinfo


 


Works perfectly for  Full System Report but crashes hard when using the Hardware Report from Detailed Report Menu

trinfo-gtk

(trinfo-gtk:30444): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:3922:29: Junk at end of value

(trinfo-gtk:30444): Gtk-WARNING **: Theme parsing error: unity.css:111:9: 'shade' is not a valid property name
**
Gtk:ERROR:/build/gtk+3.0-SLiI62/gtk+3.0-3.18.6/./gtk/gtkcssinheritvalue.c:33:gtk_css_value_inherit_free: code should not be reached
**
Gtk:ERROR:/build/gtk+3.0-SLiI62/gtk


It's best to open a issue on GitLab ( you need to be registered first ).
Here: https://gitlab.com/trios-linux/trios-info/issues

@Crash:
Either gtk (css) causes it, or it's threading that's misbehaving. I'll look into it. :)
Though one information would help. Does it crash each and every time, or randomly ( if randomly, then it's likelly to be threading issue )?
#58
VSIDO Discussions / Re: TRIOS linstaller questions
January 30, 2016, 04:16:13 PM
Found and fixed a bug present in testing branch ( I've missed a parentheses in one place, causing partition scaning to hang ).
So as usuall, clone testing --> rebuild the packages. :)

@PackRat:

For the basics, yes ( excluding pastebining, screenshot upload, and Detailed report ).
For a full monty, you need:

scrot fbcat python3-requests inxi xdotool

:)

EDIT:

And "pastebinit", I forgot it. :D Thanks VastOne for reminding. :)
#59
VSIDO Changes / Re: VSIDO new linstaller Discussion
January 30, 2016, 04:09:16 PM
Writing from live, while installing in the background ( with latest installer & custom_kernel_args )...

Now, a few nitpicks/suggestions/observations:

- It would be nice to have VBox Guest Additions preinstalled on ISO, since for me atleast, working in 640x480 and without shared clipboard/folders tends to be annoying.

- X issues you mentioned exist in (latest, 5.14) VBox, and I couldn't get rid of them even with a full restart of LightDM.
Everything is fine on metal.

- +1 on using SpaceFM. Awesome file manager with even more awesome features.
While at it, purely estetic and subjective, but I find it's coloration of a Root window quite ugly and somewhat distracting.
Though it can be disabled by unchecking "Show root user indicator color" in Preferences/Interface.

- Since, by using a Flux, you're aiming for light weight, I suggest you to take a look at SMTube.
It's a small YouTube browser which opens videos in a selected player ( SMPlayer by default ).
The gain here is in the fact that any player is many times faster and much less CPU intensive compared to watching online.
For example, I can watch 720p silky smooth with VLC on an ancient Athlon XP ( single core @2GHz, slow as hell ), while online it's basically a slide show.

- And to really nitpick, Apt seems to miss package lists in live, so in order to install something you need to get them first ( apt-get update ).

Besides that, great job! Blazing fast, good selection of apps, and +1 from me on using a dark theme. :)
Once I have enough time, I'll switch to VSIDO for a couple of days in order to take a proper look.

Rebooting now.... :)
#60
VSIDO Discussions / Re: TRIOS linstaller questions
January 30, 2016, 02:57:29 PM
Quote from: VastOne on January 29, 2016, 09:56:05 PM
^ Fantastic... Let me know when they are there and I can begin the testing.  Also keep in mind I am available at any time for any type of testing your team may need.  I do not know code as well as you all but I can track down issues and troubleshoot as well as anyone... though Miska is incredible and tough to beat!  :)

And by the way ...

a 2:50 install of a fully functional Linux Distro is incredible IMO



Should be good to go. :)
More details in commit message:
https://gitlab.com/trios-linux/trios-installer/commit/eed7c7a9f86cf1184e25e30cf0f0736da7f57660



@testing:
Tnx! :)
I'll let you know if/when help is needed.
Although right now, "trios-info" tool could use some wider testing, and besides that, you may find it usefull.
It's a system information tool, with CLI & GTK interfaces that can also generate nifty system reports ( hardware, repo's, install log etc ) which can be saved to file and/or uploaded to pastebin.
CLI variant can also take screenshots of itself and upload them to imgr, and also works in TTY ( very usefull when someone has X or VGA issues since it provides an easy way to upload system/hw info ).
https://gitlab.com/trios-linux/trios-info

@speed:
Mostly comes from the fact that squashfs is decompressed directly onto target partition, instead of mounting it separately and copying file by file ( like LMDE installer does, for example ). :)
Though there's nothing wrong with LMDE's approach, it's just slower ( on hdd's atleast ).

Quote from: VastOne on January 30, 2016, 02:28:42 AM
I have done a makeover on the Download Page that now reflects the VSIDO Test ISO Downloads

Please grab the latest version of the ISO's that is specifically for testing a new installer

If you find the tint2 all wacky when you first boot to a live-cd log out and back in using a password of live.  This brings you back in clean and tint2 is where it should be

This is due to some recent changes to X11 and should be corrected soon...

Downloading. :)

Btw, don't tell me that X11 issue comes from the fact that it's compiled with systemd support, which landed in Sid recently ( if I'm not mistaken )?  ???