Page 1 of 1

Small things to polish in Porteus 3.2

Posted: 15 Nov 2016, 14:51
by Falcony
Small things to polish in Porteus 3.2

Thanks for your work brokenman ! :friends: You are the best!

I just tried new release and found it rock stable but found several even not bugs but small issues - I will post it here.
May be in future - then have a time.

My env for Porteus 3.2

Code: Select all

uname -a

Linux fidoslax.local 4.8.7-porteus #1 SMP PREEMPT Fri Nov 11 20:41:54 Local time zone must be set-- i686 Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz GenuineIntel GNU/Linux

cat /proc/cmdline

quiet 3 vt.default_utf8=0 zram=5% login=root
1. Modules show as mount points /dev/loop* - previous version supress it.

df -h

Code: Select all

Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1,5G  1,4M  1,5G   1% /mnt/live
devtmpfs        1,5G  4,0K  1,5G   1% /dev
/dev/sda2       582G  244G  333G  43% /mnt/sda2
/dev/sdb1       3,8G  2,9G  860M  78% /mnt/sdb1
tmpfs           1,8G   14M  1,8G   1% /mnt/live/memory/changes
aufs            1,8G   14M  1,8G   1% /
/dev/loop0       43M   43M     0 100% /mnt/live/memory/images/000-kernel.xzm
/dev/loop1       66M   66M     0 100% /mnt/live/memory/images/001-core.xzm
/dev/loop2       15M   15M     0 100% /mnt/live/memory/images/001-zconsole.xzm
/dev/loop3       79M   79M     0 100% /mnt/live/memory/images/002-xorg.xzm
/dev/loop4      7,0M  7,0M     0 100% /mnt/live/memory/images/002-xzapp.xzm
/dev/loop6       45M   45M     0 100% /mnt/live/memory/images/003-xfce4.xzm
/dev/loop7      512K  512K     0 100% /mnt/live/memory/images/009-backuprecover.xzm
/dev/loop8       79M   79M     0 100% /mnt/live/memory/images/05-devel.xzm
/dev/loop9     256K  256K     0 100% /mnt/live/memory/images/xzm-utils--0.8--0.1.5.xzm
/dev/loop10     9,8M  9,8M     0 100% /mnt/live/memory/images/z5-russian-base--0.2--0.1.5.xzm
/dev/loop11     256K  256K     0 100% /mnt/live/memory/images/z7-russian-koi8-r--0.2--0.1.5.xzm
/dev/loop12     512K  512K     0 100% /mnt/live/memory/images/zz9-fidoslax--1.2--0.1.5.xzm
tmpfs           1,5G  112K  1,5G   1% /dev/shm
df output but little messy for users.

2. No manual page for ps, df and other ordinary unix command - previous version is
was.

Basically for newbie - when they have no access to internet - better to have it.
Although /usr/doc, /usr/local/doc - better in my opinion delete - as nobody read it.

3. Midnight commander - mc

It have some problem with virtual fs - tmp? Problem appears for ex. if you are using mc Midnight Commander and press ENTER on big ISO image.
Instead of list of contents it show nothing if ISO is around 1Gb. If it is more then 1,5 Gb it show errors - with red. Please try to open big enough iso to check.

And I think mc have to be more configured - to open different type of files. Current settings are for other disros - not for Porteus.
So if you press Enter or F3 or F4 on files it does not do or call for applications that is not in Porteus base.

That is all. For the first glance 3.2 is rock stable.

Thanks again you brokenman for good release.

Re: Small things to polish in Porteus 3.2

Posted: 15 Nov 2016, 19:26
by Bogomips
Falcony wrote: 2. No manual page for ps, df and other ordinary unix command - previous version is
was.

Basically for newbie - when they have no access to internet - better to have it.
Brought up this issue previously, and been discussed. Think a viable solution is to lift all man pages from Salackware 14.2 iso, and then make a module out of them. Been doing something like this regularly with the Slackware current iso from a while back by mounting the core.xzm equivalent. On my TODO list, but maybe if someone has time, disk space and ram to spare, could do it. :friends:

Re: Small things to polish in Porteus 3.2

Posted: 15 Nov 2016, 20:49
by brokenman
Think a viable solution is to lift all man pages from Salackware 14.2 iso, and then make a module out of them.
Ok. I can modify my build scripts to export ALL the man pages to a module. Good idea.

I (and the others) are working on the other issues Falcony. Thanks.

Re: Small things to polish in Porteus 3.2

Posted: 16 Nov 2016, 07:24
by Falcony
brokenman wrote:Think a viable solution is to lift all man pages from Salackware 14.2 iso, and then make a module out of them.
Ok. I can modify my build scripts to export ALL the man pages to a module. Good idea.

I (and the others) are working on the other issues Falcony. Thanks.
Thank to you! :) Manual pages as different module - who do not need it may delete - is cool.

Re: Small things to polish in Porteus 3.2

Posted: 19 Nov 2016, 12:57
by Bogomips
4.8.8 ISOs yet to appear on Mirrors. 8)

Re: Small things to polish in Porteus 3.2

Posted: 19 Nov 2016, 22:39
by brokenman
The plan is to wait for 4.9 LTS kernel and then push a .1 version. This is expected to be mid December.

I can put together an ISO wit 4.8.8 kernel if you wish.

Re: Small things to polish in Porteus 3.2

Posted: 19 Nov 2016, 23:20
by brokenman
4.8.9 kernel was released yesterday so I can push an ISO with this kernel if you like. It also includes a few bug fixes and should reflect the final version (4.9 kernel) fairly accurately.

Re: Small things to polish in Porteus 3.2

Posted: 19 Nov 2016, 23:43
by Bogomips
^ That would be great, as the 32 bit side is lagging behind. Crippled sources and devel would be appreciated for driver, so that KDE can run on my nvidia card.

Re: Small things to polish in Porteus 3.2

Posted: 21 Nov 2016, 05:30
by Falcony
brokenman wrote:4.8.9 kernel was released yesterday so I can push an ISO with this kernel if you like. It also includes a few bug fixes and should reflect the final version (4.9 kernel) fairly accurately.
Oh! Thats nice, thank you! :Yahoo!:

Re: Small things to polish in Porteus 3.2

Posted: 04 Dec 2016, 17:25
by Bogomips
KDE BOOT INTERRUPTION WHEN LOADING FROM ISO FILE
  • Booting

    Code: Select all

    quiet from=/dev/sda10/tmp/iso/3.2.1/i586/Porteus-KDE-v3.2.1-i586.iso copy2ram ramsize=25% noauto rootcopy=/dev/sda4/kd_rcp 3
    
  • Text Mode

    Code: Select all

    INIT: version 2.88 booting
    Triggering udev events:  /sbin/udevadm trigger --action=add
    INIT: Entering runlevel: 3
    ntfs-3g: Failed to access volume '/dev/isoloop': No such file or directory
    
    ntfs-3g 2016.2.22 integrated FUSE 27 - Third Generation NTFS Driver
                    Configuration type 1, XATTRS are on, POSIX ACLS are off
    
    Copyright (C) 2005-2007 Yura Pakhuchiy
    Copyright (C) 2006-2009 Szabolcs Szakacsits
    Copyright (C) 2007-2016 Jean-Pierre Andre
    Copyright (C) 2009 Erik Larsson
    
    Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>
    
    Options:  ro (read-only mount), windows_names, uid=, gid=,
              umask=, fmask=, dmask=, streams_interface=.
              Please see the details in the manual (type: man ntfs-3g).
    
    Example: ntfs-3g /dev/sda1 /mnt/windows
    
    News, support and information:  http://tuxera.com
    Retry? [Y/n]
    
  • Graphical Mode

    Code: Select all

    INIT: Entering runlevel: 4
    ntfs-3g: Failed to access volume '/dev/isoloop': No such file or directory
    
    ntfs-3g 2016.2.22 integrated FUSE 27 - Third Generation NTFS Driver
    ...
    News, support and information:  http://tuxera.com
    Retry? [Y/n]
    
Boot Sequence (Palemoon on black screen, followed many seconds later by wallpaper and taskbar) takes 2 minutes, and it gets boring if one forgets about having to press 'n', and goes off to do something else only to come back and find booting standing still on this question. :twisted: