BionicDog (updated: 2018-06-04)
@wiak, @fredx181,
I'm sorry, but this was just a stupid fault by myself.
I happen to have a GIMP .sfs (renamed to .squashfs) loaded at remaster. That GIMP .sfs included a symbolic link /usr/lib/i386-linux-gnu which points to /usr/lib (this is in all Puppies, so I created my PaDS to move everything from /usr/lib/i386-linux-gnu to /usr/lib, remove /usr/lib/i386-linux-gnu and make it a symbolic link to /usr/lib).
It just sat on top at remaster, so everything from /usr/lib/i386-linux-gnu didn't make it into the remastered .squashfs.
Thanks.
I'm sorry, but this was just a stupid fault by myself.
I happen to have a GIMP .sfs (renamed to .squashfs) loaded at remaster. That GIMP .sfs included a symbolic link /usr/lib/i386-linux-gnu which points to /usr/lib (this is in all Puppies, so I created my PaDS to move everything from /usr/lib/i386-linux-gnu to /usr/lib, remove /usr/lib/i386-linux-gnu and make it a symbolic link to /usr/lib).
It just sat on top at remaster, so everything from /usr/lib/i386-linux-gnu didn't make it into the remastered .squashfs.
Thanks.
Ah, thanks, that's a relief Yes, watch out with adding SFS's made for Puppy, better use apt2sfs or repo2sfs to create a module (which then includes the packages made for Bionic, so gives more chance to work and avoid problems).ITSMERSH wrote:@wiak, @fredx181,
I'm sorry, but this was just a stupid fault by myself.
I happen to have a GIMP .sfs (renamed to .squashfs) loaded at remaster. That GIMP .sfs included a symbolic link /usr/lib/i386-linux-gnu which points to /usr/lib (this is in all Puppies, so I created my PaDS to move everything from /usr/lib/i386-linux-gnu to /usr/lib, remove /usr/lib/i386-linux-gnu and make it a symbolic link to /usr/lib).
It just sat on top at remaster, so everything from /usr/lib/i386-linux-gnu didn't make it into the remastered .squashfs.
Thanks.
@stemsee
I tried Wifi-TrayNet, sorry to say, but it didn't work for me, no connection could be made for wlan0.
But maybe it's me, I found some things very confusing and complicated, also the timeout dialogs gave me sort of a stress.
Here's output from terminal (I did several things after creating the profile, e.g. reconnect etc..):
Code: Select all
root@live:~# '/usr/sbin/Wifi-TrayNet'
cat: /root/.wifi-connect/geometry/: No such file or directory
Warning: Missing charsets in String to FontSet conversion
no eth1
no usb0
cat: /tmp/Wifi-TrayNet/exip: No such file or directory
cat: /root/.wifi-connect/geometry/Try-Profiles: No such file or directory
xwininfo: error: No window with name "External-Ip-Address" exists!
xwininfo: error: No window with name "External-Ip-Address" exists!
cat: /tmp/Wifi-TrayNet/netsel: No such file or directory
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 14 100 14 0 0 44 0 --:--:-- --:--:-- --:--:-- 44
curl: no process found
xwininfo: error: No window with name "Try-Profiles" exists!
xwininfo: error: No window with name "Try-Profiles" exists!
sed: -e expression #1, char 3: extra characters after command
cat: '/root/.wifi-connect/static/"UPC44685"': No such file or directory
environment: line 35: xvkbd: command not found
cat: '/root/.wifi-connect/geometry/Configuration-&-Connection': No such file or directory
(yad:6498): Gtk-WARNING **: 15:20:17.618: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
(yad:6498): Gtk-WARNING **: 15:20:17.619: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &
xvkbd: no process found
Successfully initialized wpa_supplicant
Line 7: Invalid BSSID '"UPC44685"'.
Line 7: failed to parse bssid '"UPC44685"'.
Line 15: failed to parse network block.
Failed to read or parse configuration '/tmp/Wifi-TrayNet/netsel'.
Successfully initialized wpa_supplicant
Line 7: Invalid BSSID '"UPC44685"'.
Line 7: failed to parse bssid '"UPC44685"'.
Line 15: failed to parse network block.
Failed to read or parse configuration '/tmp/Wifi-TrayNet/netsel'.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: icanhazip.com
curl: no process found
Successfully initialized wpa_supplicant
Line 7: Invalid BSSID '"UPC44685"'.
Line 7: failed to parse bssid '"UPC44685"'.
Line 15: failed to parse network block.
Failed to read or parse configuration '/tmp/Wifi-TrayNet/netsel'.
cat: /root/.wifi-connect/geometry/External-Ip-Address: No such file or directory
xwininfo: error: No window with name "External-Ip-Address" exists!
xwininfo: error: No window with name "External-Ip-Address" exists!
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: icanhazip.com
curl: no process found
sed: -e expression #1, char 3: extra characters after command
cat: '/root/.wifi-connect/static/"UPC44685"': No such file or directory
environment: line 35: xvkbd: command not found
Hi.
Is there a counterpart to:
- /etc/profile
- /etc/rc.d/rc.local
- /etc/Puppybackgroundpicture
from Puppy in BionicDog
or in other words:
- how can I pack/unpack the initrd1.xz
- where can I "jump in" to modify stuff at boot up
- where is the settings for a new defined wallpaper stored
???
Be aware, I will come up with some more of these questions...
Is there a counterpart to:
- /etc/profile
- /etc/rc.d/rc.local
- /etc/Puppybackgroundpicture
from Puppy in BionicDog
or in other words:
- how can I pack/unpack the initrd1.xz
- where can I "jump in" to modify stuff at boot up
- where is the settings for a new defined wallpaper stored
???
Be aware, I will come up with some more of these questions...
Hi RSH,
/etc/rc.d/rc.local = /etc/rc.local
/etc/Puppybackgroundpicture = I don't know
- Copy the initrd1.xz inside it
- Then from terminal inside bionic32
To unpack:
To pack again to parent folder of bionic32 (but remove old ./initrd1.xz first):
~/Startup
/etc/rc.local
/etc/init.d/ (boot scripts)
openbox (with tint2) = ~/.config/nitrogen/bg-saved.cfg
openbox with rox-pinboard = ~/.config/rox.sourceforge.net/ROX-Filer/pinbd-OB
pcmanfm providing the Desktop = ~/.config/pcmanfm/default/desktop-items-0.conf [EDITED] previously was wrong
Fred
/etc/profile = the sameIs there a counterpart to:
- /etc/profile
- /etc/rc.d/rc.local
- /etc/Puppybackgroundpicture
/etc/rc.d/rc.local = /etc/rc.local
/etc/Puppybackgroundpicture = I don't know
- Create folder, for example: bionic32how can I pack/unpack the initrd1.xz
- Copy the initrd1.xz inside it
- Then from terminal inside bionic32
To unpack:
Code: Select all
xz -dc initrd1.xz | cpio -i
Code: Select all
find . -print | cpio -o -H newc 2>/dev/null | xz -f --extreme --check=crc32 > ../initrd1.xz
In:where can I "jump in" to modify stuff at boot up
~/Startup
/etc/rc.local
/etc/init.d/ (boot scripts)
That depends on which Desktop mode, e.g plain openbox (with tint2) or openbox with rox-pinboard, or pcmanfm providing the Desktop (with "Desktop Manager" you can switch these).where is the settings for a new defined wallpaper stored
openbox (with tint2) = ~/.config/nitrogen/bg-saved.cfg
openbox with rox-pinboard = ~/.config/rox.sourceforge.net/ROX-Filer/pinbd-OB
pcmanfm providing the Desktop = ~/.config/pcmanfm/default/desktop-items-0.conf [EDITED] previously was wrong
Fred
Last edited by fredx181 on Thu 14 Jun 2018, 21:48, edited 1 time in total.
Hi fredx181,
I found /etc/profile (first I searched for it in casper's changes directory )
Directory /etc/rc.d only includes rc.network, So when I'm creating /etc/rc.d/rc.local its content will be executed at boot?
I'm using the Openbox/Tint2 desktop combination and searched the places/files you mentioned. My wallpaper is /opt/docs/pictures/development.jpg and the changes on the wallpaper is stored, so it's visible after a reboot.
Found the wallpaper in /root/.config/nitrogen/bg-saved.cfg after reboot. Before reboot after changing the wallpaper it wasn't there, so I was a little confused. I'm saving only on exit/reboot, which could be a reason for confusing.
Pcmanfm doesn't provide the wallpaper - even after reboot.
Thanks
I found /etc/profile (first I searched for it in casper's changes directory )
Directory /etc/rc.d only includes rc.network, So when I'm creating /etc/rc.d/rc.local its content will be executed at boot?
I'm using the Openbox/Tint2 desktop combination and searched the places/files you mentioned. My wallpaper is /opt/docs/pictures/development.jpg and the changes on the wallpaper is stored, so it's visible after a reboot.
Found the wallpaper in /root/.config/nitrogen/bg-saved.cfg after reboot. Before reboot after changing the wallpaper it wasn't there, so I was a little confused. I'm saving only on exit/reboot, which could be a reason for confusing.
Pcmanfm doesn't provide the wallpaper - even after reboot.
Code: Select all
[config]
bm_open_method=0
[volume]
mount_on_startup=1
mount_removable=1
autorun=1
[ui]
always_show_tabs=0
max_tab_chars=32
win_width=810
win_height=464
splitter_pos=150
media_in_new_tab=0
desktop_folder_new_win=0
change_tab_on_drop=1
close_on_unmount=1
focus_previous=0
side_pane_mode=places
view_mode=compact
show_hidden=1
sort=name;ascending;
toolbar=newtab;navigation;home;
show_statusbar=1
pathbar_mode_buttons=0
No, /etc/rc.local is the one. The rc.network script is called from /etc/init.d/rc.network-start (is for peasywifi)ITSMERSH wrote:Directory /etc/rc.d only includes rc.network, So when I'm creating /etc/rc.d/rc.local its content will be executed at boot?
I was wrong earlier, sorry, It's set in ~/.config/pcmanfm/default/desktop-items-0.confPcmanfm doesn't provide the wallpaper - even after reboot.
Fred
Thanks, meanwhile I'd stumbled upon it.fredx181 wrote:No, /etc/rc.local is the one. The rc.network script is called from /etc/init.d/rc.network-start (is for peasywifi)ITSMERSH wrote:Directory /etc/rc.d only includes rc.network, So when I'm creating /etc/rc.d/rc.local its content will be executed at boot?
No, this doesn't have the wallpaper either.fredx181 wrote:I was wrong earlier, sorry, It's set in ~/.config/pcmanfm/default/desktop-items-0.confPcmanfm doesn't provide the wallpaper - even after reboot.
Fred
Code: Select all
[*]
wallpaper_mode=screen
wallpaper_common=1
wallpaper=/opt/docs/pictures/uk_glacial_lake_wales_gwynedd_county_snowdonia_region_100866_1920x1080.jpg
desktop_bg=#000000
desktop_fg=#ffffff
desktop_shadow=#000000
desktop_font=Sans 10
show_wm_menu=0
sort=mtime;ascending;
show_documents=0
show_trash=1
show_mounts=0
[abiword.desktop]
x=204
y=102
[DogRadio.desktop]
x=105
y=100
[gnome-mplayer.desktop]
x=103
y=179
[pcmanfm.desktop]
x=207
y=3
[firefox.desktop]
x=103
y=7
[PicDrop.desktop]
x=304
y=3
Code: Select all
[:0.0]
file=/opt/docs/pictures/08.jpg
mode=4
bgcolor=#000000
[xin_-1]
file=/opt/docs/pictures/development.jpg
mode=0
bgcolor=#000000
Since nitrogens config stores it correctly and it is displayed correctly the file /root/.config/pcmanfm/default/desktop-items-0.conf doesn't seem to affect it.
I'm almost sure to recall that /opt/docs/pictures/uk_glacial_lake_wales_gwynedd_county_snowdonia_region_100866_1920x1080.jpg is the default wallpaper after a fresh install / at first boot.
Ok, two questions. Is there a boot option to boot without
- additional squashfs modules loaded
- to have the changes in 'casper/changes' loaded
??
It's definetely not you! It's the gremlins ... AGAIN! The only error you see in term that I could not explain is the yad, suggesting ampersands be escaped with '&' which made no difference!fredx181 wrote: @stemsee
I tried Wifi-TrayNet, sorry to say, but it didn't work for me, no connection could be made for wlan0.
But maybe it's me, I found some things very confusing and complicated, also the timeout dialogs gave me sort of a stress.
Here's output from terminal (I did several things after creating the profile, e.g. reconnect etc..):
Fred
Please see previous post 'EDIT'! Thanks for your patience!
There's small misunderstanding, pcmanfm has it's own wallpaper chooser, when selected Desktop mode is "pcmanfm + lxpanel" (through "Desktop Manager") and right-click on the Desktop "Desktop preferences" (separate from nitrogen).ITSMERSH wrote:No, this doesn't have the wallpaper either.fredx181 wrote:I was wrong earlier, sorry, It's set in ~/.config/pcmanfm/default/desktop-items-0.confPcmanfm doesn't provide the wallpaper - even after reboot.
Fred
Never mind.
Since nitrogens config stores it correctly and it is displayed correctly the file /root/.config/pcmanfm/default/desktop-items-0.conf doesn't seem to affect it.
I'm almost sure to recall that /opt/docs/pictures/uk_glacial_lake_wales_gwynedd_county_snowdonia_region_100866_1920x1080.jpg is the default wallpaper after a fresh install / at first boot.
Then the chosen wallpaper will be in /root/.config/pcmanfm/default/desktop-items-0.conf
Yes, sort of, see here:Ok, two questions. Is there a boot option to boot without
- additional squashfs modules loaded
http://www.porteus.org/tutorials/26-gen ... -them.html
Put them in the optional folder and only specified modules will be loaded
cheatcodes wrote:load=module
load=module[1];module[n]
... Load optional modules from /optional/ directory on the booting
media. Additional modules can be listed, separated
by semicolons, without spaces.
Exampe: 'load=gimp;inkscape' would search for and load any
modules in the /porteus/optional folder that contain the strings
'gimp' or 'inkscape'.
Just remove "changes=....." from kernel commandline for to boot without changes.- to have the changes in 'casper/changes' loaded
@stemsee, I'll test Wifi-TrayNet later and reply in your Wifi-TrayNet thread
Fred
I notice that neither /etc/xdg/Startup and /root/Startup are in path, nor referenced in rc.local, so how are the scripts in /root/Startup triggered?
can they be added safely with
EDIT: found /usr/local/bin/start-up
would this be ok for xdg and backwards compatibility with puppy
can they be added safely with
Code: Select all
sed -i 's|:/usr/games"|:/usr/games:/etc/xdg/Startup:/root/Startup"|' /etc/profile
would this be ok for xdg and backwards compatibility with puppy
Code: Select all
#!/bin/bash
# items are listed numbers first then alphabetical order
sleep 4
ls $HOME/Startup/* | while read J
do
"$J" &
done
[[ -d /etc/xdg/Startup ]] && ls /etc/xdg/Startup/* | while read k
do
"$k" &
done
[[ -d $HOME/my-applications/bin ]] && ls $HOME/my-applications/bin/* | while read l
do
"$l" &
done
Startup from /etc/xdg/autostart (I assume you mean that, /etc/xdg/Startup does not exist ) only works with .desktop launchers, not for scripts or binaries.stemsee wrote:would this be ok for xdg and backwards compatibility with puppy
Code:
#!/bin/bash
# items are listed numbers first then alphabetical order
sleep 4
ls $HOME/Startup/* | while read J
do
"$J" &
done
[[ -d /etc/xdg/Startup ]] && ls /etc/xdg/Startup/* | while read k
do
"$k" &
done
[[ -d $HOME/my-applications/bin ]] && ls $HOME/my-applications/bin/* | while read l
do
"$l" &
done
Adding $HOME/my-applications/bin is good idea for backwards compatibility with puppy but just to be added to PATH, not to auto-start from IMO.
Fred
Hi.
There seems to be an issue at reboot/shutdown in BionicDog after booting with 'changes' activated. The boot drive isn't cleanly unmounted. Need to do a e2fsck in a Puppy since I can't unmount the boot drive in BionicDog to do a e2fsck.
If I don't do a e2fsck (e.g. by overseen it before next boot), I get results similar to this:
There seems to be an issue at reboot/shutdown in BionicDog after booting with 'changes' activated. The boot drive isn't cleanly unmounted. Need to do a e2fsck in a Puppy since I can't unmount the boot drive in BionicDog to do a e2fsck.
If I don't do a e2fsck (e.g. by overseen it before next boot), I get results similar to this:
Code: Select all
sh-4.3# e2fsck -y /dev/sda1
e2fsck 1.42.9 (4-Feb-2014)
Intern_1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 6291475 has zero dtime. Fix? yes
Deleted inode 6291481 has zero dtime. Fix? yes
Deleted inode 6291568 has zero dtime. Fix? yes
Deleted inode 6291613 has zero dtime. Fix? yes
Deleted inode 6291733 has zero dtime. Fix? yes
Deleted inode 6291734 has zero dtime. Fix? yes
Deleted inode 6291987 has zero dtime. Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(2832--2847) -(2912--2943) -(4416--4435) -(7456--7519) -(10112--10239) -(20176--20191) -(20240--20255) -(20320--20351) -(20768--20831) -(20864--20991) -(1999490--1999745) -(2017280--2018303) -(2018816--2019327) -(2282896--2282911) -(2282976--2283007) -(2283040--2283103) -(2283392--2283763) -(2284544--2285567) -(2285940--2286195) -(2288128--2288639) -(2289664--2289907) -(2359810--2359811) -(2359936--2359937) -(2360841--2360856) -(2492603--2492858) -(2493440--2494463) -(2497024--2497535) -(2697216--2703359) -(2721792--2745668) -(3015216--3015263) -(3015296--3015359) -(3015680--3016191) -(3022208--3022335) -(3022464--3022719) -(3022848--3023871) -(3024896--3047423) -(3049472--3080191) -(3082240--3112959) -(3125248--3126579) -(25167452--25167455) -(25176080--25176082) -(25186833--25186848) -(25255988--25255999) -25256449 -(25256544--25256564) -25258496 -(25259008--25259022) -(25259520--25259522) -(25262592--25262607) -25265231 -(25265272--25265279) -(25265288--25265295) -(25265792--25265800) -25265811 -(25265816--25265823) -(25265913--25265916) -(25265922--25265937) -25266013 -(25266168--25266171) -25266211 -(25266330--25266332) -(25266398--25266399) -25266408 -25266410 -(25266420--25266427) -(25266461--25266463) -(25266472--25266476) -25266488 -(25266566--25266567) -(25281025--25281040)
Fix? yes
Free blocks count wrong for group #0 (10844, counted=11360).
Fix? yes
Free blocks count wrong for group #61 (3581, counted=5373).
Fix? yes
Free blocks count wrong for group #69 (7906, counted=10426).
Fix? yes
Free blocks count wrong for group #72 (10441, counted=10461).
Fix? yes
Free blocks count wrong for group #76 (6015, counted=7807).
Fix? yes
Free blocks count wrong for group #82 (25961, counted=32105).
Fix? yes
Free blocks count wrong for group #83 (8377, counted=32254).
Fix? yes
Free blocks count wrong for group #92 (7694, counted=32254).
Fix? yes
Free blocks count wrong for group #93 (1534, counted=32254).
Fix? yes
Free blocks count wrong for group #94 (1534, counted=32254).
Fix? yes
Free blocks count wrong for group #95 (8108, counted=9440).
Fix? yes
Free blocks count wrong for group #768 (27147, counted=27170).
Fix? yes
Free blocks count wrong for group #770 (32099, counted=32168).
Fix? yes
Free blocks count wrong for group #771 (30800, counted=30903).
Fix? yes
Free blocks count wrong (14925749, counted=15049937).
Fix? yes
Inode bitmap differences: -6291475 -6291481 -6291568 -6291613 -(6291733--6291734) -6291987
Fix? yes
Free inodes count wrong for group #768 (6617, counted=6624).
Fix? yes
Free inodes count wrong (9484941, counted=9484948).
Fix? yes
Intern_1: ***** FILE SYSTEM WAS MODIFIED *****
Intern_1: 132460/9617408 files (2.1% non-contiguous), 23413551/38463488 blocks
sh-4.3#
sh-4.3#
Yes, as I said: when I'm NOT doing (just overseen) a e2fsck immediately at next boot I get those results similar. If I do it immediately there's no problem, though the drive still remains not cleanly unmounted. So booting and rebooting from a drive not cleanly unmounted causes those errors.
But the main cause is: the drive isn't cleanly unmounted with changes used. If the drive were cleanly unmounted there would be no need to do a e2fsck and then there were no errors after doing reboots from that drive.
But the main cause is: the drive isn't cleanly unmounted with changes used. If the drive were cleanly unmounted there would be no need to do a e2fsck and then there were no errors after doing reboots from that drive.
Hi Fred,
Just noticed you've included IUPLua programming capability in the iso. That's great; I will have to move from XenialDog to BionicDog now and get back to IUPLua programming soonish. It is supposed to be easy calling C routines from Lua; if so, now that I've brushed up on my C again, I might be able to offer some nice tricks later.
As things stand, there are actually additional bolt-on module/batteries available for IUPLua which I have compiled but not yet packaged, which will be a nice addition for the repo - allow drawing graphs and much more.
But the core IUPLua stuff is enough for most simple gui building. Main thing will be to write some more exemplars on how to interface with underlying utilities (including shell). You may well find it proves more useful than YAD or gtkdialog/gtkwialog eventually; certainly more powerful and nice to encourage users to learn another programming language other than just bash.
I'm busy on gtkwialog still - but fixing up the <input> side of things to allow bash -c is alot of work and involves many source files; been trying various alternative means. I have to keep at it though or the C code required will evaporate from my head leaving too much rust again.
wiak
Just noticed you've included IUPLua programming capability in the iso. That's great; I will have to move from XenialDog to BionicDog now and get back to IUPLua programming soonish. It is supposed to be easy calling C routines from Lua; if so, now that I've brushed up on my C again, I might be able to offer some nice tricks later.
As things stand, there are actually additional bolt-on module/batteries available for IUPLua which I have compiled but not yet packaged, which will be a nice addition for the repo - allow drawing graphs and much more.
But the core IUPLua stuff is enough for most simple gui building. Main thing will be to write some more exemplars on how to interface with underlying utilities (including shell). You may well find it proves more useful than YAD or gtkdialog/gtkwialog eventually; certainly more powerful and nice to encourage users to learn another programming language other than just bash.
I'm busy on gtkwialog still - but fixing up the <input> side of things to allow bash -c is alot of work and involves many source files; been trying various alternative means. I have to keep at it though or the C code required will evaporate from my head leaving too much rust again.
wiak