Porteus Nemesis v3.5 BUG REPORTS

Arch based Porteus community project
User avatar
francois
Contributor
Contributor
Posts: 5070
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#151 by francois » 25 Jan 2016, 22:42

Followup:
2.0 chromium misses a dependency:
-installed chromium and started it under guest. Error message:

The solution would be to upgrade
Voltaire: Le mieux est l'ennemi du bien.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5558
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#152 by brokenman » 26 Jan 2016, 00:47

What is systemdless equivalent to `journalctl -b -N` for boot -N logs?
What does that extract exactly? I ran Nemesis with systemd for a couple of weeks, but I haven't yet memorized all the journalctl switches.
BTW where do you guys put your rc.local for its content to be run upon boot? /etc/rc.d/ didn't work.
/etc/rc.local
chmod +x /etc/rc.local <--- make it executable
How do i become super user?
Wear your underpants on the outside and put on a cape.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#153 by aus9 » 26 Jan 2016, 01:43

re /etc/rc.local.....with openrc....I am not sure that is correct.

AFAIK our default has the local which is good

Code: Select all

rc-status
Runlevel: default
 dbus                                                                                                                        [  started  ]
 NetworkManager                                                                                                              [  started  ]
 netmount                                                                                                                    [  started  ]
 syslog-ng                                                                                                                   [  started  ]
 ntpd                                                                                                                        [  started  ]
 acpid                                                                                                                       [  started  ]
 boot-network                                                                                                                [  started  ]
 cgmanager                                                                                                                   [  started  ]
 consolekit                                                                                                                  [  started  ]
 local                                                                                                                       [  started  ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
Dynamic Runlevel: manual
but I wonder if the location of /etc/rc.local is correct and its syntax appears wrong

IMHO local scripts belong /etc/local.d

and might be called myscript.start.....I will have to test this and report back ......done see next post

###########################
probable bug detected
##############

etc/local.d/preshutdown.stop

contents snip
[ -x /etc/rc.d/rc.local_shutdown ] && /etc/rc.d/rc.local_shutdown
AFAIK /etc/rc.d/rc.local_shutdown no such beast

Code: Select all

ls /etc/rc.d/rc.local_shutdown 
ls: cannot access /etc/rc.d/rc.local_shutdown: No such file or directory
also maybe its could be called shutdown.stop and be placed in /etc/local.d? and then amend the preshutdown?

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#154 by aus9 » 26 Jan 2016, 01:57

regarding rc.local

Ok I think I may be right....will make a mini tutorial unless someone thinks I am wrong?

step one
default already has local running...just mentioning it to be anal

step 2
create a file with root powers and save it with some filename.start
I called mine myscript.start with (test contents)
#!/bin/bash
umount /mnt/sda1
full reboot to test that

Code: Select all

ls /mnt/sda1
shows nothing....this can't be your Nemesis partition....its my Ubuntu

You can have multiple commands in there but IMHO we should not try to use a filename like rc.local.start but a more meaningful name
and/or multiple files to do one thing?

waiting for others to confirm.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5558
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#155 by brokenman » 26 Jan 2016, 02:44

IMHO we should not try to use a filename like rc.local.start but a more meaningful name
Are you talking about 3.5? I think the file is already named /etc/local.d/preshutdown.stop
At least that is what is in my tree.

I will fix the path there for /etc/rc.d

Thanks
How do i become super user?
Wear your underpants on the outside and put on a cape.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#156 by aus9 » 26 Jan 2016, 04:03

Are you talking about 3.5? I think the file is already named /etc/local.d/preshutdown.stop
if this file has any effect good or bad etc it only works for stopping or for shutdown. IMHO it must have .start to be a startup script.
:beer:

donald
Full of knowledge
Full of knowledge
Posts: 1217
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#157 by donald » 26 Jan 2016, 07:10

More feedback than a bug report
nemesis 3.5 32 bit

PCmanFM
If you start a file search in the root (file system) it get stuck at a very high cpu usage
with the revolving icon -- it never ends.

Testing tool
qv4l2: error while loading shared libraries: libQtOpenGL.so.4: cannot open shared object file: No such file or directory

temp module(s) missing k8temp for example
modprobe = module not found

firewall??

minor:
a lot of settings not set (root)

good:
(CD tray open/close issue) - still working solution:
sysctl -w dev.cdrom.autoclose=0

system boot with nouveau driver -- it didn't in slack 3.1

nm-applet is visible/working

shutdown and reboot = OK

anything special to test?
because the LXDE-DE is not my cup of tea..
btw
It would be nice to have md5sums with the ISOs

User avatar
brokenman
Site Admin
Site Admin
Posts: 5558
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#158 by brokenman » 26 Jan 2016, 12:26

if this file has any effect good or bad etc it only works for stopping or for shutdown. IMHO it must have .start to be a startup script
Not at home right now but I believe that IS a shutdown script. It is responsible for kicking off the shutdown procedure, killing openrc and handing back to initrd.

Thanks Donald. I`ll check out some of those issues. There is not a lot more to test in LXDE. I consider it still very much a beta considering the feedback. Next release will tidy up some of the existing bugs and perhaps introduce another desktop. Any preferences?
How do i become super user?
Wear your underpants on the outside and put on a cape.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#159 by aus9 » 26 Jan 2016, 13:28

@brokenman

why not put a blank startup script into /etc/local.d maybe named z.start?
I could then do a mini tutorial on it as it contents will be just
#!/bin/bash and I could then mention its a replacement for /etc/rc.local

I chose z.start as its the last letter of the alphabet and your readme says scripts there
All files are processed in lexical order.
and I would need my script to process after your umount.start

cheers

PS It would help if you modify the contents of /etc/rc.local to say where to look for its replacement.

User avatar
brokenman
Site Admin
Site Admin
Posts: 5558
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#160 by brokenman » 26 Jan 2016, 19:56

Sure. I can put a hello world script there. What about naming it something more meaningful like zz-start-commands.start? This way people poking around without reading your tutorial may stumble across something slightly more comprehensible.

I will check out whether it is better to include the script at /etc/rc.local for compatibility. I think arch used this path before systemd and systemd also has backwards compat.
How do i become super user?
Wear your underpants on the outside and put on a cape.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#161 by aus9 » 26 Jan 2016, 22:54

well I already know that I can't use an executable /etc/rc.local sorry if I did not make that obvious and I assume you are keeping openrc which differs from systemd.
zz-start-commands.start
sounds mighty fine

I have taken the liberty of second guessing your answer and already bodgeed up a mini tutorial
https://forum.porteus.org/viewtopic.php?f=137&t=5450

cheers

roadie
Full of knowledge
Full of knowledge
Posts: 205
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 3.5...with a twist
Location: In a hayfield

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#162 by roadie » 26 Jan 2016, 23:31

brokenman wrote:Sure. I can put a hello world script there. What about naming it something more meaningful like zz-start-commands.start? This way people poking around without reading your tutorial may stumble across something slightly more comprehensible.

I will check out whether it is better to include the script at /etc/rc.local for compatibility. I think arch used this path before systemd and systemd also has backwards compat.

Thats the thing....using Nemesis openrc, I only knew about /etc/local.d/preshutdown.stop because I was poking around. And I was a bit surprised to see it....rc.local seems a better, more traditional file to be used for these things.

Actually, shouldn't startup commands come from /etc/init.d?

My 2 pennies.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#163 by aus9 » 26 Jan 2016, 23:50

@roadie
I guess we are talking different things.
Actually, shouldn't startup commands come from /etc/init.d?

Sure but they are system wide and not user created scripts, and you may see that is where local is

strictly speaking all scripts in /etc/local.d are local or user supplied but I don't have a problem with brokenman doing his thing in there....which is exactly what he did with /usr/local/bin stuff......easy to find.....Nemesis specific binaries and for /etc/local.d .....easy to find Nemesis specific start up or shutting down scripts.

Is that clearer?

User avatar
brokenman
Site Admin
Site Admin
Posts: 5558
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#164 by brokenman » 26 Jan 2016, 23:58

Actually, shouldn't startup commands come from /etc/init.d?
Startup scripts in this path will be passed the 'start' argument during boot. Startup scripts in /etc/local.d aren't. I think there is advice in the example file in /etc/local.d explaining the pros and cons of using it.
How do i become super user?
Wear your underpants on the outside and put on a cape.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#165 by aus9 » 27 Jan 2016, 00:03

I had mislead roadie by using the word "system" in my tutorial me thinks. I have corrected that now. With luck

Post Reply