Page 8 of 8

Re: Porteus Desktop Edition 3.0 rc2 bugs/feedback thread

Posted: 06 Mar 2014, 07:45
by dustbunnies
syslinux
porteus.cfg

(user can manually edit boot line but)

it might be helpful to expand the menu text, to clarify:
-- changes will persist if the "Graphical mode" entry is used
-- the "Copy to RAM" entry does not persist changes

Re: Porteus Desktop Edition 3.0 rc2 bugs/feedback thread

Posted: 06 Mar 2014, 10:01
by donald
@brokenman, fanthom

root@porteus:~# chmod 4755 /usr/bin/eject

guest@porteus:~$ eject /dev/sr0
umount: only root can unmount /dev/sr0 from /mnt/sr0
eject: unmount of `/mnt/sr0' failed

root@porteus:~# eject /dev/sr0 ..CD goes out/in
------------------------------------------------------
rebooted (always fresh)

root@porteus:~# for a in `pgrep -f udevd`; do kill $a ;done
-su: kill: (2035) - No such process
root@porteus:~# eject -T /dev/cdrom
ioctl: Input/output error
root@porteus:~# eject /dev/cdrom -> CD came out and tray stay open
root@porteus:~# exit
logout
guest@porteus:~$ eject -t /dev/cdrom
guest@porteus:~$ eject /dev/cdrom -> CD came out and tray stay open
guest@porteus:~$

Re: Porteus Desktop Edition 3.0 rc2 bugs/feedback thread

Posted: 06 Mar 2014, 16:09
by brokenman
Thanks Donald. udev seems to be the culprit. May need to increase the polling time of the device.

Re: Porteus Desktop Edition 3.0 rc2 bugs/feedback thread

Posted: 06 Mar 2014, 18:12
by Kriss
BTW... ifenslave? http://forum.porteus.org/viewtopic.php?f=53&t=1621
When I tested bonding I used this one http://pkgs.org/ubuntu-13.10/ubuntu-mai ... 4.deb.html
But recently I've discovered that topic and I think this package is small enough (20Kb) to be included.
And I didn't know there are methods besides editing rc.M, so excuse me please... =)

Re: Porteus Desktop Edition 3.0 rc2 bugs/feedback thread

Posted: 08 Mar 2014, 12:38
by fanthom
@donald
if this is really an udev fault then we can't do much as i would worry to upgrade this package myself to not break anything. i would wait till Pat does it in Slackware.
maybe there is a rule to control polling for optical media?

@Slaxmax
good to know - thanks.

@dustbunnies
persistence depends on 'changes=' cheatcode so i would avoid hardcoding it in the porteus.cfg description.
GUI mode can work without persistence and copy2ram can be persistent so if user modify default cheatcodes for these modes then the description would be misleading (yes - i know that user could also modify desc, but as i know life it would rarely happen)

@Kriss
added ifenslave package but i did not add a check to rc.M.
please use sysvinit script for this.

Re: Porteus Desktop Edition 3.0 rc2 bugs/feedback thread

Posted: 08 Mar 2014, 21:09
by donald
@fanthom
..... :cry: .....
btw
it's the same in rc1 + rc2...it only works in INIT 1

Re: Porteus Desktop Edition 3.0 rc2 bugs/feedback thread

Posted: 09 Mar 2014, 15:42
by budchekov
Well...after a shaky start here, just want to say I'm using the KDE version and its Absolutely Fabulous, nothing amiss so far, THANKS ! :)