Feedback for Porteus version 2.0 RC2

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
att
Contributor
Contributor
Posts: 131
Joined: 28 Dec 2010, 17:09

Re: Feedback for Porteus version 2.0 RC2

Post#136 by att » 18 Feb 2013, 10:56

Oh, shiiiiit....

I can now see why Porteus makes unmount problems!

Code: Select all

# Recognized devices:
/dev/sda1: LABEL="WIN_XP" UUID="08007CC1007CB6F2" TYPE="ntfs" 
/dev/sda2: LABEL="DRIVE_D" UUID="36A8A323A8A2E11B" TYPE="ntfs" 
/dev/sda3: LABEL="DRIVE_E" UUID="069CB4FB9CB4E679" TYPE="ntfs" 
/dev/sda4: LABEL="WIN_7" UUID="4A367BD8367BC38B" TYPE="ntfs" 
/dev/sdb1: LABEL="ATT_PL0011" UUID="E8007D21007CF7C0" TYPE="ntfs" 
/dev/sdc1: LABEL="ATT_PL0012" UUID="648483AE848380F2" TYPE="ntfs" 
/dev/sdd1: LABEL="ATT_PL0015" UUID="1CE42E69E42E44FC" TYPE="ntfs" 
/dev/sde1: LABEL="ATT_1500_IN" UUID="1EDCF208DCF1D9CB" TYPE="ntfs" 
/dev/sdf1: LABEL="INTENSO" UUID="401E-7F10" TYPE="vfat" 
/dev/sdg1: LABEL="ATT_PL0014" UUID="AE586F32586EF90B" TYPE="ntfs" 
/dev/sdh1: LABEL="ATT_PL0016" UUID="26C08844C0881C65" TYPE="ntfs" 

# Booting device:
/mnt/sdf1

# Porteus data found in:
/mnt/sdf1/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/memory/copy2ram/000-kernel.xzm
/memory/copy2ram/001-core.xzm
/memory/copy2ram/002-xorg.xzm
/memory/copy2ram/003-lxde.xzm
/memory/copy2ram/004-kde.xzm
/memory/copy2ram/005-devel.xzm
/memory/copy2ram/006-firefox.xzm
/memory/copy2ram/Jdownloader-0.9-2013-01-02-incl_updates.xzm
/memory/copy2ram/SABnzbd-0.7.11_64bit.xzm
/memory/copy2ram/abuse-0.8-x86_64-3ponce.xzm
/memory/copy2ram/arp-scan-1.8.1-x86_64-1cf.xzm
/memory/copy2ram/binbot.xzm
/memory/copy2ram/cabextract-1.2-i486.xzm
/memory/copy2ram/cairomm-1.9.8-x86_64-1sl.xzm
/memory/copy2ram/chntpw-0.99.6-x86_64.xzm
/memory/copy2ram/chttpd-1.3-x86_64.xzm
/memory/copy2ram/cksfv.xzm
/memory/copy2ram/cli-ftp-pack.xzm
/memory/copy2ram/compat32-libraries-1.1.02_13.37-x86_64-2ftm.xzm
/memory/copy2ram/ctorrent-1.3.4.xzm
/memory/copy2ram/ctunnel-0.6-x86_64-3cf.xzm
/memory/copy2ram/curl-7.19.4.xzm
/memory/copy2ram/db44-4.4.20-2.xzm
/memory/copy2ram/etherape-0.9.7-i686-1.xzm
/memory/copy2ram/etherdump-2.11-x86_64-1cf.xzm
/memory/copy2ram/ethtool--3.1--0.1.4.xzm
/memory/copy2ram/ettercap-0.7.5-x86_64-1cf.xzm
/memory/copy2ram/expat-2.0.1-x86_64-2.xzm
/memory/copy2ram/filezilla-3.6.0.2-x86_64-1cf.xzm
/memory/copy2ram/fping-2.4b2_to-i486-1sl.xzm
/memory/copy2ram/glib-1.2.10-x86_64-3.xzm
/memory/copy2ram/glibmm-2.32.1-x86_64-2sl.xzm
/memory/copy2ram/gmime-2.4.15-x86_64-1.xzm
/memory/copy2ram/gnutls-3.0.23-x86_64-1.xzm
/memory/copy2ram/gst-plugins-base-0.10.36-x86_64-2.xzm
/memory/copy2ram/gstreamer-0.10.36-x86_64-1.xzm
/mnt/sdf1/porteus/modules/gtk+3-3.4.4-x86_64-1.xzm                              ; -----------> this must be the culprit ! .... but.... why......????
/memory/copy2ram/gtkspell-2.0.16-x86_64-1.xzm
/memory/copy2ram/hping2.xzm
/memory/copy2ram/irssi-0.8.15-x86_64-6.xzm
/memory/copy2ram/json-c-0.10-x86_64-2gv.xzm
/memory/copy2ram/kismet-2008-05-r1-i686.xzm
/memory/copy2ram/klibido-0.2.5-i486-1bj.xzm
/memory/copy2ram/kmess-2.0.6.1-x86_64-1hamza.xzm
/memory/copy2ram/kvirc-4.0.2-x86_64.xzm
/memory/copy2ram/kvpnc-0.9.6.xzm
/memory/copy2ram/libevent-2.0.11-x86_64-1hamza.xzm
/memory/copy2ram/libiconv--1.13.1--0.1.3.xzm
/memory/copy2ram/libmspack-0.3alpha-x86_64-1hamza.xzm
/memory/copy2ram/libnet-1.1.6-x86_64-1cf.xzm
/memory/copy2ram/libnl-1.1-x86_64-1.xzm
/memory/copy2ram/libpcap-1.3.0-x86_64-1.xzm
/memory/copy2ram/libpng-1.4.5-x86_64-1.xzm
/memory/copy2ram/libtasn1-2.12-x86_64-1.xzm
/memory/copy2ram/libtheora-1.1.1-x86_64-1.xzm
/memory/copy2ram/libvisual-0.4.0-x86_64-3.xzm
/memory/copy2ram/lua-5.1.3.xzm
/memory/copy2ram/lynx-cur-2.8.8dev.1-1.xzm
/memory/copy2ram/mysql-5.0.67-1.xzm
/memory/copy2ram/nano-2.0.7-i486-1.xzm
/memory/copy2ram/nasm-2.07.xzm
/memory/copy2ram/nc-1.10.xzm
/memory/copy2ram/nettle-2.5-x86_64-1.xzm
/memory/copy2ram/netwatch-1.3.0-x86_64-2.xzm
/memory/copy2ram/newsbeuter-2.5-x86_64-1gv.xzm
/memory/copy2ram/newspost.xzm
/memory/copy2ram/nmap-6.01-x86_64-2.xzm
/memory/copy2ram/ntfs_progs-x86_64.xzm
/memory/copy2ram/ntp-4.2.4p0-i486-1.xzm
/memory/copy2ram/nzb-0.1.9.xzm
/memory/copy2ram/nzbget-0.7.0-x86_64-1hamza.xzm
/memory/copy2ram/nzbperl_64bit_porteus_addon.xzm
/memory/copy2ram/nzbperl_SSL.xzm
/memory/copy2ram/openjre-7u9_b30-x86_64-2alien.xzm
/memory/copy2ram/openldap-client-2.4.31-x86_64-2.xzm
/memory/copy2ram/opera-12.12-x86_64-1ro.xzm
/memory/copy2ram/ostinato-0.5.1-x86_64-1cf.xzm
/memory/copy2ram/p11-kit-0.13-x86_64-1fg.xzm
/memory/copy2ram/p7zip-9.04-x86_64.xzm
/memory/copy2ram/pan-0.139-x86_64-1.xzm
/memory/copy2ram/pidgin-2.7.11-x86_64-1.xzm
/memory/copy2ram/portmap-5-0.xzm
/memory/copy2ram/protobuf-2.4.1-x86_64-2cf.xzm
/memory/copy2ram/python-2.6.6-x86_64-1.xzm
/memory/copy2ram/rar_unrar_64bit_att.xzm
/memory/copy2ram/requiredbuilder-0.16.5-x86_64-1hamza.xzm
/memory/copy2ram/seamonkey-solibs-2.12.1-x86_64-1.xzm
/memory/copy2ram/sniffit_0_3_5.xzm
/memory/copy2ram/sqlite-3.5.8.xzm
/memory/copy2ram/squid-3.1.4-x86_64.xzm
/memory/copy2ram/sshd-activate.xzm
/memory/copy2ram/stfl-0.22-x86_64-1gv.xzm
/memory/copy2ram/strace-4.5.20-x86_64-1.xzm
/memory/copy2ram/stunnel-4.53-x86_64-1.xzm
/memory/copy2ram/tcc-0.9.25.xzm
/memory/copy2ram/tcl8.4.19.xzm
/memory/copy2ram/tcpdump-4.3.0-x86_64-1.xzm
/memory/copy2ram/teamviewer-7.0.9377-x86_64-1_SBo.xzm
/memory/copy2ram/telnet-1.5.xzm
/memory/copy2ram/thttpd.xzm
/memory/copy2ram/tigervnc-1.1.0-x86_64-2alien.xzm
/memory/copy2ram/tinyproxy.xzm
/memory/copy2ram/upx-3.03.xzm
/memory/copy2ram/uudeview-0.5.20-i486-1as.xzm
/memory/copy2ram/vmware-view-open-client-4.0.1-235010.xzm
/memory/copy2ram/vpnc-0.5.3.xzm
/memory/copy2ram/wifi-radar-1.9.9-1.1.xzm
/memory/copy2ram/wine-1.5.10-i486-1sl.xzm
/memory/copy2ram/winetricks--20110429--0.1.4.xzm
/memory/copy2ram/wireless-tools-29-1.1.xzm
/memory/copy2ram/wlassistant-0-5-7.xzm
/memory/copy2ram/wxPython-2.8.12.0-x86_64-1hamza.xzm
/memory/copy2ram/wxWidgets-2.8.12-x86_64-1hamza.xzm
/memory/copy2ram/wxWidgets-2.9.4-x86_64-1sl.xzm
/memory/copy2ram/xchat-2.8.8-x86_64.xzm
/memory/copy2ram/yasm-1.1.xzm
/memory/copy2ram/youtube-dl-2010.12.09-x86_64.xzm



User avatar
Hamza
Warlord
Warlord
Posts: 1847
Joined: 28 Dec 2010, 07:41
Distribution: Porteus
Location: France

Re: Feedback for Porteus version 2.0 RC2

Post#137 by Hamza » 18 Feb 2013, 11:04

@att, Just by curiosity. Why doesn't Porteus load the modules with "+" sign into memory?
NjVFQzY2Rg==

User avatar
fanthom
Site Admin
Site Admin
Posts: 4613
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Feedback for Porteus version 2.0 RC2

Post#138 by fanthom » 18 Feb 2013, 11:46

@Rava
i have set gnome-mplayer to 'stereo' as it's still more common that surround (especially for PC where usually you have speakers only).
each Desktop maintainer can override this setting in his DE module (Ahau could do it in 0090-xfce.xzm if not happy with my defaults).

i wouldn't go with automatic detection as it would bring additional troubles.
changing one setting in player preferences is not that hard.
On my Toshiba Satellite Laptop the sound via HDMI is not working
i have similar setup and all what i need to do is to change to 'gnome-mpleyer -> Preferences -> Player -> Audio Output -> HDA Intel MID (HDMI 0) (alsa)' and sound gets redirected to my TV without other tweaks.
Are details like this (about more programs) somewhere documented so we folks know whom best to address?
in porteus 2.1 i'll be maintaining 000+001+002 + kde4 + devel
brokenman: razorqt +browsers + office
Ahau: Xfce + Lxde + print pack
things may change till we reach first rc of 2.1

@gnomic
thanks for confirming that 3G mobile network is working with usb_modeswith.
regarding root -> guest issues.
i think mobile broadband is user specific (user A can have modem A, user B can have user B) so it must be set for each user separately.
just a wild guess...

@att
looks like modules with '+' in name are not copied to RAM.
glad that you have found it as i should be able to fix this for final.

Cheers
Please add [Solved] to your thread title if the solution was found.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Feedback for Porteus version 2.0 RC2

Post#139 by Ahau » 18 Feb 2013, 16:14

Thanks Rava -- I'm not quite clear from your post -- did unload/reloading the driver eventually change your device order?

Maybe we can adjust your system with asound.conf. I think I didn't use this for my script because it was a bit harder to manipulate the needed information, but now that we've had two reports of users with multiple pci devices with the same driver, I think it needs some attention.

Have you tried this config?:

Code: Select all

pcm.!default {
   type hw
   card NVidia
}

ctl.!default {
   type hw           
   card NVidia
}
then run 'etc/rc.d/rc.alsa restart'. That should switch your NVidia to be the default card, but I'm not sure if that will activate the HDMI subdevice.

I'm starting to think we might need to build a pulseaudio module with an equalizer, etc. The sound stuff I have included in the default iso will probably never be sufficient for audiophiles.
Please take a look at our online documentation, here. Suggestions are welcome!

inspector
White ninja
White ninja
Posts: 11
Joined: 08 Feb 2013, 22:14
Distribution: Porteus XFCE 3.0
Location: Canada

Re: Feedback for Porteus version 2.0 RC2

Post#140 by inspector » 19 Feb 2013, 01:17

Porteus XFCE 2.0 RC2 64-bit

Bug: Not sure if this has been reported yet, but I'm having trouble setting up magic folders from the Porteus Settings Centre. When I try to select a target as a .dat file, the target file box is still disabled, and the result is one line in folders.cfg that begins with a space followed by the source directory. Works fine if the target is a directory on a linux filesystem.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Feedback for Porteus version 2.0 RC2

Post#141 by Ahau » 19 Feb 2013, 19:33

nassausky wrote:Would it take alot of work to add to the final version of 2.0 changing the color scheme (maybe a dark red border) to thunar when it's running in Super User Mode? When I have multiple thunar windows open, sometimes I forget which one is in Super User Mode.

Thanks :)
Hi nassausky,

It wouldn't be a lot of work, however, the banner to which you are referring is removed by me on purpose. Some Porteus users only run as root, and having this banner across the top is distracting and ugly, so I've patched it out. The banner is controlled by the source code, which I have patched so the banner doesn't show up. In order to create a new package with the banner present, download this file:

http://porteus-xfce.googlecode.com/file ... ild.tar.gz

unpack it anywhere you like (tar -xvf thunar-slackbuild.tar.gz). You'll also need to install the package "linuxdoc-tools" to avoid a compile error (standard package from slackware works). Then go into the 'thunar' directory, open thunar.SlackBuild, and comment out this line:

Code: Select all

#disable warning about being root
patch -p1 < $CWD/thunar-norootwarning.patch
Save the change, then run the slackbuild:

Code: Select all

./thunar.Slackbuild
this will create a slackware package inside /tmp, which you can convert to an xzm module with txz2xzm:

Code: Select all

txz2xzm thunar-1.6.2-x86_64-1Ahau.txz thunar-1.6.2-x86_64-1Ahau-withrootwarning.xzm
Place that module in /porteus/modules on your flashdrive and, when you boot up this unpatched version of thunar will be used in place of my patched version.
Please take a look at our online documentation, here. Suggestions are welcome!

chyang0527
White ninja
White ninja
Posts: 10
Joined: 21 Sep 2012, 09:37
Location: Taiwan

Re: Feedback for Porteus version 2.0 RC2

Post#142 by chyang0527 » 21 Feb 2013, 02:25

@fanthom
I had post a question of the hard disk drive did not be auto mount in vm machine while boot time in Porteus 2.0 RC2.
I have tested with Porteus 2.0 release, now the hard disk in vm machine could be automatically mounted at boot time.
Just share this information to you and thanks for your effort.

btw, i am also curious about the settings relative in this case. Does this change relative with the kernel config "CONFIG_FUSION_SAS=y"?

Thank you.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4613
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Feedback for Porteus version 2.0 RC2

Post#143 by fanthom » 21 Feb 2013, 09:50

Does this change relative with the kernel config "CONFIG_FUSION_SAS=y"?
yes - that's what i changed.
Please add [Solved] to your thread title if the solution was found.

chyang0527
White ninja
White ninja
Posts: 10
Joined: 21 Sep 2012, 09:37
Location: Taiwan

Re: Feedback for Porteus version 2.0 RC2

Post#144 by chyang0527 » 22 Feb 2013, 03:02

@fanthom
Thank you for quick responding my post. :)

Post Reply