ArchLinux packages manager for Porteus
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
ArchLinux packages manager for Porteus
Thanks Eerie for rclone link. In fact, during one such back up operation to an USB HDD, a Linux OS messed up while copying, (input-output error) and corrupted the file system. Now you can not delete that file as it is unreadable to Linux or Windows, and I have to live with that as formatting my back up files is not an option.
Many months back, I opened up initrd file of OS using systemd. The code had an option if 'systemd is not found in /etc or /usr, continue with init.d in /etc.
So I unsquash the file system file in /live, deleted systemd directories in /etc and /usr, made new squashfs and booted.
It stopped at systemd handing over, with with an error message directory not found'. why? I failed to understand.
I did not pursue further.
Most files I need are stored under windows. So unmounting or nohd cheatcode are not practical.
Many months back, I opened up initrd file of OS using systemd. The code had an option if 'systemd is not found in /etc or /usr, continue with init.d in /etc.
So I unsquash the file system file in /live, deleted systemd directories in /etc and /usr, made new squashfs and booted.
It stopped at systemd handing over, with with an error message directory not found'. why? I failed to understand.
I did not pursue further.
Most files I need are stored under windows. So unmounting or nohd cheatcode are not practical.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
ArchLinux packages manager for Porteus
@neko
Concerning the unmount problem, please have a look here --> https://www.reddit.com/r/debian/comment ... g/cse1uur/
Hopefully, you'll find something related.
EDIT:
These 2 links below can help too:
[Solved] Shutdown - systemd timing out attempting to unmount NFS
https://bbs.archlinux.org/viewtopic.php?id=195417
[SOLVED] Unmount pre-shutdown - FedoraForum.org
https://forums.fedoraforum.org/showthread.php?t=310888
Thanks
Concerning the unmount problem, please have a look here --> https://www.reddit.com/r/debian/comment ... g/cse1uur/
Hopefully, you'll find something related.
EDIT:
These 2 links below can help too:
[Solved] Shutdown - systemd timing out attempting to unmount NFS
https://bbs.archlinux.org/viewtopic.php?id=195417
[SOLVED] Unmount pre-shutdown - FedoraForum.org
https://forums.fedoraforum.org/showthread.php?t=310888
Thanks
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
-------------------------------------------------
@raja
This week, I am trying to fix the issue of APorteus reboot/shutdown process.
Next week, maybe I will have some result.
Thanks.
-------------------------------------------------
@M. Eerie
Thank you very much for your helpful advice.
Now I am studying the articles that were introduced by you.
Before reading these articles, I have analyzed the issue.
[Problem]
At systemd shutdown/reboot, "unmoun"s are done in fault.
[Cause]
The file systems that will be unmount are used by systemd running.
(umount: can't unmount ....: Resource busy)
[how to fix this issue]
====< In the case of original Porteus >====
There are two stages.
stage 1: /etc/rc.d/rc.6
the process is running in the ordinary space.
In this stage, basic modules 000-, 001-, 002-, 003- are not "unmount"ed.
At the end of stage 1, the control is transfered to the stage 2.
stage 2: /mnt/live/cleanup
At first step, running space is changed to the boot initrm space.
The boot space is not constructed with 000-,001-,002-,003- modules.
These modules can be "unmount"ed in stage 2.
Therefore they are "unmount"ed in stage 2 without fault.
====< In the case of APorteus >====
Now, APorteus has nothing to care this issue.
If the same approach as Porteus will be employed,
the following corresponding was tried.
stage 1: /usr/lib/systemd/systemd-shutdown
Note: an executable program under /usr/lib/systemd/system-shutdown/
will be executed by /usr/lib/systemd/systemd-shutdown.
But its PID is not 1.
stage 2: /mnt/live/cleanup
ISO@/porteus/base/001-z.core.xzm@/usr/lib/systemd/systemd-shutdown
ISO@/boot/syslinux/initrd.xz@/usr/share/systemd/cleanup
Thanks.
@raja
This week, I am trying to fix the issue of APorteus reboot/shutdown process.
Next week, maybe I will have some result.
Thanks.
-------------------------------------------------
@M. Eerie
Thank you very much for your helpful advice.
Now I am studying the articles that were introduced by you.
Before reading these articles, I have analyzed the issue.
[Problem]
At systemd shutdown/reboot, "unmoun"s are done in fault.
[Cause]
The file systems that will be unmount are used by systemd running.
(umount: can't unmount ....: Resource busy)
[how to fix this issue]
====< In the case of original Porteus >====
There are two stages.
stage 1: /etc/rc.d/rc.6
the process is running in the ordinary space.
In this stage, basic modules 000-, 001-, 002-, 003- are not "unmount"ed.
At the end of stage 1, the control is transfered to the stage 2.
stage 2: /mnt/live/cleanup
At first step, running space is changed to the boot initrm space.
The boot space is not constructed with 000-,001-,002-,003- modules.
These modules can be "unmount"ed in stage 2.
Therefore they are "unmount"ed in stage 2 without fault.
====< In the case of APorteus >====
Now, APorteus has nothing to care this issue.
If the same approach as Porteus will be employed,
the following corresponding was tried.
stage 1: /usr/lib/systemd/systemd-shutdown
Note: an executable program under /usr/lib/systemd/system-shutdown/
will be executed by /usr/lib/systemd/systemd-shutdown.
But its PID is not 1.
stage 2: /mnt/live/cleanup
ISO@/porteus/base/001-z.core.xzm@/usr/lib/systemd/systemd-shutdown
Code: Select all
#!/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
BLD=$(tput bold) # Bold
RED=${BLD}$(tput setaf 1) # Red
RST=$(tput sgr0) # Reset
redmsg()
{
echo -e $RED "$1" $RST
}
nfsd_stop()
{
killall rpc.mountd 2> /dev/null
killall nfsd 2> /dev/null
sleep 1
killall -9 nfsd 2> /dev/null # make sure :)
killall rpc.rquotad 2> /dev/null
exportfs -au 2> /dev/null
}
#=== save data size check ===#
if [ -a /mnt/live/memory/images/changes ]
then
SDspace=$(df -BM --output=size,used,avail,pcent /mnt/live/memory/images/changes | tail -n1)
read size used avail percent <<< $SDspace
if [ ${percent%\%} -gt 85 ]
then
echo
redmsg "Warning! save.dat file $percent full. Used: $used Free: $avail"
echo
else
echo
echo "save.dat file $percent full. Used: $used Free: $avail"
fi
fi
#=== Save random-seed to a file ===#
#dd if=/dev/urandom of=/etc/random-seed count=1 bs=$(expr `cat /proc/sys/kernel/random/poolsize` / 8) 2>/dev/null
#chmod 600 /etc/random-seed
#=== Write what's going to happen in wtmp ===#
if [ "$1" = "reboot" ]
then
command="reboot"
else
command="poweroff"
fi
$command -w
#=== Deactivate all porteus modules activated from /union (additional modules)===#
deactivate `grep ^devpts -A500 /proc/mounts | grep '.xzm ' | cut -d" " -f2` >/dev/null 2>&1
#=== Close magic-folders encrypted containers ===#
for x in `ls /dev/mapper/magic* 2>/dev/null`;
do
umount `grep -w /dev/mapper/$x /proc/mounts | cut -d " " -f2`
cryptsetup luksClose $x
done
#=== Detach loop devices used in /union ===#
losetup -a | grep /loop3 -A500 | grep -v '.xzm)' | cut -d: -f1 | xargs -n1 losetup -d 2>/dev/null
sync; echo
#=== Stop acpid/dbus/udev ===#
udevadm control --exit 2>/dev/null
killall acpid dbus-daemon udevd 2>/dev/null
#=== Stop nfsd ===#
#pidof nfsd >/dev/null && nfsd_stop
#=== Turn off swap ===#
swapoff -a
#=== Some filesystems needs to be unmounted later ===#
echo "Unmounting local file systems"
umount -at no,aufs,devtmpfs,proc,sysfs 2>/dev/null
#=== Sync what's left in buffers ===#
sync
#=== Deactivate LVM volume groups ===#
#if [ -e /mnt/live/tmp/lvm ];
#then
# echo "Deactivating LVM volume groups"
# vgchange -an --ignorelockingfailure
#fi
#=== Deactivate RAID arrays ===#
if [ -e /mnt/live/tmp/raid ];
then
echo "Deactivating RAID arrays"
mdadm -S /dev/md/* 2>/dev/null
fi
#=== Run the cleanup script ===#
cd /mnt/live/
exec ./cleanup $command <dev/console >dev/console 2>&1
#=== None return ===#
Code: Select all
#!/bin/sh
#
# Script will be called instead of final reboot/shutdown
# to safely switch back to initrd root and unmount everything possible.
# Mainly needed if you use changes= boot parameter in order to correctly
# unmount the changes device/file.
#
export PATH=.:/mnt/live/bin:/usr/sbin:/usr/bin:/sbin:/bin
#=== change root ===#
# This script needs to be re-executed to free up any shell
# from the union which may be used (eg. /union/bin/bash)
if [ ! "$RE_EXEC_CLEANUP" ];
then
export RE_EXEC_CLEANUP=1
/mnt/live/bin/pivot_root . union
exec /mnt/live/bin/chroot . /cleanup "$@" <dev/console >dev/console 2>&1
echo "Something was wrong because we should never be here!"
fi
#========================================================#
save_changes_EXIT()
{
# Save 'changes=EXIT:' session:
if [ ! -e /tmp/changes-exit ]
then
return 1
fi
echo -e "Your session will be saved in [1;33m3[0m seconds.\nPress space/enter to start doing it now or any other key to skip.";
x=3
while [ $x -gt 0 ];
do
if read -s -t1 -n1 ans
then
break
else
sleep 1;
fi
let x=x-1;
done
if [ "$ans" = "" ];
then
DEST=`cat /tmp/changes-exit`;
NAME=`basename $DEST`;
MNAME=/memory/images/changes;
FOLDERS=`grep '^/' /union/etc/changes-exit.conf | sed s/^.//g`
echo "saving changes to $NAME - do not power off the PC"
cd /memory/changes;
rm -rf var/lock/subsys/* var/run/laptop-mode-tools/* `grep '^!' /union/etc/changes-exit.conf | sed s/^..//g | tr "\n" " "`
for x in `find $FOLDERS -name ".wh.*" 2>/dev/null | sed s/.wh.//g | tr ' ' '@' `;
do
x=`echo $x | tr '@' ' ' `
if test -e $MNAME/"$x"
then
rm -rf $MNAME/"$x";
fi
done
for x in `find $MNAME -name ".wh.*" 2>/dev/null | tr ' ' '@' `;
do
x=`echo $x | tr '@' ' ' `
wh=`echo $x | sed -e s^$MNAME^^g -e s/.wh.//g `;
if test -e "$wh"
then
rm "$x";
fi
done
cp -af --parents $FOLDERS $MNAME 2>/dev/null
fi
return 0
}
#========================================================#
ejectCD()
{
# Determine if we booted from CD and copy 'eject' utility:
CD=`grep /dev/sr /proc/mounts | cut -d" " -f1 | uniq`
if [ ! -b "$CD" ]
then
return
fi
if [ -n "`egrep -o " noeject( |\$)" /proc/cmdline`" ]
then
return
fi
# Eject cdrom device:
echo "ejecting $CD...";
eject $CD 2>/dev/null;
x=6
while [ $x -gt 0 ];
do
echo -en "CD tray will be closed in [1;33m$x[0m seconds - hit enter to do it now.\r"
if read -s -t1
then
break
else
sleep 1
fi
let x=x-1
done
eject -t $CD 2>/dev/null
}
#========================================================#
OLDunmount_all()
{
#=== unmounting union ===#
echo "unmounting union"
sync
umount -nl `grep /union/ /proc/mounts | cut -d" " -f2 | tr "\n" " "` 2>/dev/null
umount -l /union 2>/dev/null
if [ $? -ne 0 ];
then
x=10;
free=no
while [ $x -gt 0 -a $free = no ];
do
usleep 200000;
sync;
let x=x-1
if umount -l /union 2>/dev/null
then
echo "union unmounted successfully";
free=yes;
fi
done
if [ $? -ne 0 ];
then
kill -9 `echo $PID` >/dev/null 2>&1;
umount -l /union 2>/dev/null;
fi
if [ $? -ne 0 ];
then
echo "remounting union as read-only"
echo -e "please use '[1;33mfsck[0m' cheatcode during next boot\nto make sure that all your filesystems are consistent..."
sleep 3;
umount -l -r /union 2>/dev/null
fi
fi
#=== unmounting everything else ===#
echo "unmounting everything else"
umount -a 2>/dev/null
if [ $? -ne 0 ];
then
# Close encrypted container:
if [ -b /dev/mapper/crypt ];
then
cryptsetup luksClose crypt
losetup -d /dev/loop2
fi
umount -arl 2>/dev/null
fi
}
#========================================================#
unmount_all()
{
for i in `ls -d /memory/images/*`;
do
umount -l $i
done
}
#========================================================#
debug()
{
#if ! egrep -qo " Pdebug( |\$)" /proc/cmdline
#then
# return
#fi
if [ $# -gt 0 ]
then
echo -e "\n=====<$1>====="
else
echo -e "\n=========="
fi
echo ": Debugging started. Here is the shell for you."
echo ": Type your desired commands, hit Ctrl+D to continue booting"
echo ": or press Ctrl+Alt+Del to reboot."
sh;
echo -e "\n\n";
}
#=== Send TERM signal to processes which can be killed ===#
SELF=$$
for i in `ps |sed 's/^ *//g'|grep -v '^PID'|cut -d' ' -f1`;
do
if [ $i = $SELF ]
then
continue
fi
kill -9 $i
done
#PID=`ps | sed -n '/PID/,/{cleanup}/p' | egrep -v '\[.*\]|PID|cleanup|ntfs-3g' | sed -r "s/^ *([0-9]+).*/\\1/" | tr "\n" " "`
#kill -15 `echo $PID` >/dev/null 2>&1
#debug "STOP processe ($1) PID=$$"
#=== Will need cryptsetup for closing encrypted container ===#
[ -b /dev/mapper/crypt ] && cp /memory/images/000-kernel.xzm/usr/bin/cryptsetup /bin
#=== Determine if we booted from CD and copy 'eject' utility ===#
#CD=`grep /dev/sr /proc/mounts | cut -d" " -f1 | uniq`
#[ -b "$CD" ] && cp -f /union/usr/bin/eject /bin
#=== Remove doubled ntfs mount entries from mtab ===#
sed -i "/ fuseblk /d" /etc/mtab
#=== Save 'changes=EXIT:' session ===#
if ! save_changes_EXIT
then
if grep -q ^memory /var/log/livedbg;
then
kill -9 `echo $PID` >/dev/null 2>&1
else
killall -9 klogd NetworkManager >/dev/null 2>&1
fi
fi
#=== unmounting all ===#
unmount_all
#debug umount
#=== Eject cdrom device ===#
ejectCD
#=== Launch debugging shell if requested ===#
#debug "START $1"
#=== $1 = action, eg. poweroff or reboot ===#
$1 -f
#debug "Something was wrong because we should never be here!"
return
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
-------------------------------------------------
@M. Eerie.
Thank you for your useful information.
I studied the articles that were intoduced by you.
1. "Concerning the unmount problem"
http://forum.porteus.org/go.php?https:/ ... g/cse1uur/
How to used mount command option "noauto" on systemd system.
I don't know the Systemd well. Then, this thema is a little difficult for me.
---> I need to study "Systemd and mount/unmount" more.
2. "Shutdown - systemd timing out attempting to unmount NFS"
http://forum.porteus.org/go.php?https:/ ... ?id=195417
By reading this article, I notice the missing packages.
APorteus doesn't include the "nfs-utils" package.
--->
(At next update,) the "nfs-utils" package (and "lvm2" package) will be included in APorteus.
3. "Unmount pre-shutdown - FedoraForum.org"
http://forum.porteus.org/go.php?https:/ ... p?t=310888
This article points out the problem how to use /usr/lib/systemd/system-shutdown/executable.
This approach is related concerning my report:
/usr/lib/systemd/system-shutdown/executable (PID not 1)
--->
/mnt/live/cleanup (PID not 1)
--->
(change to initrm space)
cleanup (PID not 1) cann't kill systemd (PID=1).
(systemd PID=1 is running and then) "umount live space" is NG.
Therefore, /usr/lib/systemd/systemd-shutdown (PID=1) is changed to "APorteus stage 1" one.
Thanks.
-------------------------------------------------
@raja
The APorteus example ISOs that were updated about reboot/shutdown process were uploaded.
APorteus-BUDGIE-v17.10.31-i486.iso (418 M)
http://www.mediafire.com/file/aks7d6e5s ... 1-i486.iso
md5sum: 4bce71a4d5dfe6dc125adc14eb4f73f9 APorteus-BUDGIE-v17.10.31-i486.iso
APorteus-BUDGIE-v17.10.31-x86_64.iso (427 M)
http://www.mediafire.com/file/bc2fb2lsk ... x86_64.iso
md5sum: 71c466f7e10e78bb246e6dae6a138a86 APorteus-BUDGIE-v17.10.31-x86_64.iso
Kernel version: 32Bit/64Bit 4.13.10
Packages version: the latest version at the time of creating ISO (2017.10.31).
Web browser:....slimjet 15.1.6.0 (66/76 M)
Thanks.
@M. Eerie.
Thank you for your useful information.
I studied the articles that were intoduced by you.
1. "Concerning the unmount problem"
http://forum.porteus.org/go.php?https:/ ... g/cse1uur/
How to used mount command option "noauto" on systemd system.
I don't know the Systemd well. Then, this thema is a little difficult for me.
---> I need to study "Systemd and mount/unmount" more.
2. "Shutdown - systemd timing out attempting to unmount NFS"
http://forum.porteus.org/go.php?https:/ ... ?id=195417
By reading this article, I notice the missing packages.
APorteus doesn't include the "nfs-utils" package.
--->
(At next update,) the "nfs-utils" package (and "lvm2" package) will be included in APorteus.
3. "Unmount pre-shutdown - FedoraForum.org"
http://forum.porteus.org/go.php?https:/ ... p?t=310888
This article points out the problem how to use /usr/lib/systemd/system-shutdown/executable.
This approach is related concerning my report:
(I tried)Note: an executable program under /usr/lib/systemd/system-shutdown/
will be executed by /usr/lib/systemd/systemd-shutdown.
But its PID is not 1.
/usr/lib/systemd/system-shutdown/executable (PID not 1)
--->
/mnt/live/cleanup (PID not 1)
--->
(change to initrm space)
cleanup (PID not 1) cann't kill systemd (PID=1).
(systemd PID=1 is running and then) "umount live space" is NG.
Therefore, /usr/lib/systemd/systemd-shutdown (PID=1) is changed to "APorteus stage 1" one.
Thanks.
-------------------------------------------------
@raja
The APorteus example ISOs that were updated about reboot/shutdown process were uploaded.
APorteus-BUDGIE-v17.10.31-i486.iso (418 M)
http://www.mediafire.com/file/aks7d6e5s ... 1-i486.iso
md5sum: 4bce71a4d5dfe6dc125adc14eb4f73f9 APorteus-BUDGIE-v17.10.31-i486.iso
APorteus-BUDGIE-v17.10.31-x86_64.iso (427 M)
http://www.mediafire.com/file/bc2fb2lsk ... x86_64.iso
md5sum: 71c466f7e10e78bb246e6dae6a138a86 APorteus-BUDGIE-v17.10.31-x86_64.iso
Kernel version: 32Bit/64Bit 4.13.10
Packages version: the latest version at the time of creating ISO (2017.10.31).
Web browser:....slimjet 15.1.6.0 (66/76 M)
Thanks.
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
ArchLinux packages manager for Porteus
Neko. only last Sunday, I tried Arch-Budgie(old one) with your new Kernel 4.13.9(8?). There was no wireless network and I found firmware for ath10k was missing. I copied that from another source and wlan0 was okay. I also found that webcam was listed under input as 'keyboard' and was not functioning with cheese( no driver installed by xorg). video0 was there under input. You may please check your new offering and rectify if necessary.
I shall download new ISO on confirmation.
Meanwhile, I thought why not experiment with Arch. I created a small 5GB partition and installed the basic Arch. I could now boot into root command prompt. No more progress could be made installing xorg,desktop and window manager, because I could not connect to my WiFi, which I used during installation with 'wifi-menu' command. Now.in the basic Arch installation dialog package is missing.
Arch wiki till now is not helpful. Interface 'wlan0' is not there. Driver and firmware for Mediatek are there in /usr/lib.
I use my smartphone as 'hotspot'. Any clue. Thanks in advance.
I shall download new ISO on confirmation.
Meanwhile, I thought why not experiment with Arch. I created a small 5GB partition and installed the basic Arch. I could now boot into root command prompt. No more progress could be made installing xorg,desktop and window manager, because I could not connect to my WiFi, which I used during installation with 'wifi-menu' command. Now.in the basic Arch installation dialog package is missing.
Arch wiki till now is not helpful. Interface 'wlan0' is not there. Driver and firmware for Mediatek are there in /usr/lib.
I use my smartphone as 'hotspot'. Any clue. Thanks in advance.
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
ArchLinux packages manager for Porteus
@neko
I have been trying your patches to systemd logout and, althought some systemd script is throwing errors, at the end your scripts got working and the drives are properly unmounted.
Also, I suggest you to make this change inside your initrd.xz scripts as pointed by abelM here -->
http://forum.porteus.org/viewtopic.php?p=59248#p59248
to ensure only updates are written to disk on exit.
Thanks very much!
I have been trying your patches to systemd logout and, althought some systemd script is throwing errors, at the end your scripts got working and the drives are properly unmounted.
Also, I suggest you to make this change inside your initrd.xz scripts as pointed by abelM here -->
http://forum.porteus.org/viewtopic.php?p=59248#p59248
to ensure only updates are written to disk on exit.
Thanks very much!
> Does not compute_
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
https://forum.porteus.org/viewtopic.php?p=94310#p94310
https://forum.porteus.org/viewtopic.php?p=84002#p84002
https://forum.porteus.org/viewtopic.php?p=77174#p77174
https://forum.porteus.org/viewtopic.php?f=39&t=8584
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
-------------------------------------------
@M. Eerie
Thank you very much for your check.
I will go to next step.
Next step is the implement of cheatcode "changes=EXIT:...".
Now APorteus neglects the "EXIT:" function, that is saving changed entities at reboot/shutdown.
Even if there is "changes=EXIT:.." in cheatcode, it will be converted to "changes=..".
[Next Step]
1. delete the line that masks the "changes EXIT" function
ISO@/boot/syslinux/initrd.xz@/usr/share/systemd/functions
line 562 - 569
OLD
NEW
2. open the file that is used for changed entities saving area.
The open process uses the commands for NTFS, CRYPT, etc,.
These commands, Everything is not included in "busybox".
Therefore this open process is performed in /usr/lib/systemd/systemd-shutdown.
3. copy changed entities to saving area.
It should be done in non-live space.
It is performed in ISO@/boot/syslinux/initrd.xz@/usr/share/systemd/cleanup.
The "busybox" of APorteus initrd.xz is one from Archlinux.
Its version is v1.25.1.
"cp" command "-u" option is able to use.
(@M. Eerie, thank you for your pointing out this.)
-------------------------------------------
@raja
Old issue: "closing files error at reboot/shutdown"
Now the old issue that was pointed out by you is under my working.
New issues: "wifi ath10k & cheese"
After the old ends, I will work on your new issues.
If already you have the module/iso that fixed these new issues,
it is very helpfull for me that you will upload the module/iso.
Thanks.
@M. Eerie
Thank you very much for your check.
I will go to next step.
Next step is the implement of cheatcode "changes=EXIT:...".
Now APorteus neglects the "EXIT:" function, that is saving changed entities at reboot/shutdown.
Even if there is "changes=EXIT:.." in cheatcode, it will be converted to "changes=..".
[Next Step]
1. delete the line that masks the "changes EXIT" function
ISO@/boot/syslinux/initrd.xz@/usr/share/systemd/functions
line 562 - 569
OLD
Code: Select all
CHNEXIT="" ###--- SKIP EXIT option ---###
if [ "$CHNEXIT" != EXIT ];
then
if [ $PCHANGES_RO -ne 0 ]
then
return
fi
fi
Code: Select all
# CHNEXIT="" ###--- SKIP EXIT option ---###
if [ "$CHNEXIT" != EXIT ];
then
if [ $PCHANGES_RO -ne 0 ]
then
return
fi
fi
2. open the file that is used for changed entities saving area.
The open process uses the commands for NTFS, CRYPT, etc,.
These commands, Everything is not included in "busybox".
Therefore this open process is performed in /usr/lib/systemd/systemd-shutdown.
3. copy changed entities to saving area.
It should be done in non-live space.
It is performed in ISO@/boot/syslinux/initrd.xz@/usr/share/systemd/cleanup.
The "busybox" of APorteus initrd.xz is one from Archlinux.
Its version is v1.25.1.
"cp" command "-u" option is able to use.
(@M. Eerie, thank you for your pointing out this.)
-------------------------------------------
@raja
Old issue: "closing files error at reboot/shutdown"
Now the old issue that was pointed out by you is under my working.
New issues: "wifi ath10k & cheese"
After the old ends, I will work on your new issues.
If already you have the module/iso that fixed these new issues,
it is very helpfull for me that you will upload the module/iso.
Thanks.
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
ArchLinux packages manager for Porteus
Neko, I shall test this week end, but 'web cam' error could be the result of some changes made in udev in kernel. Porteus too is behaving same way and camera is not available. I remember to have seen the camera working in original Porteus and your Aporteus-Budgie.
hanks
hanks
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
NEW example of ISOs that were created by "APorteus ISO builder" were uploaded.
====[64 BIT]====
Language: English (locale C)
kernel version: 64Bit 4.14-rc8
Packages version: the latest version at the time of creating ISO (2017.11.07).
10 kind desktop ISOs and 13 application modules are uploaded.
====[32 BIT]====
Language: English (locale C)
kernel version: 32Bit 4.13.12
Packages version: the latest version at the time of creating ISO (2017.11.09).
10 kind desktop ISOs and 13 application modules are uploaded.
Refer to ArchLinux packages manager for Porteus (Post by neko #49091)
Thanks.
-----------------------------------------
@raja
Thank you for your 'webcam' issue report.
These new example ISOs are updated to fix the file close issue at reboot/shutdown.
You can test the issue by using the uploaded small ISO.
Thanks.
====[64 BIT]====
Language: English (locale C)
kernel version: 64Bit 4.14-rc8
Packages version: the latest version at the time of creating ISO (2017.11.07).
10 kind desktop ISOs and 13 application modules are uploaded.
====[32 BIT]====
Language: English (locale C)
kernel version: 32Bit 4.13.12
Packages version: the latest version at the time of creating ISO (2017.11.09).
10 kind desktop ISOs and 13 application modules are uploaded.
Refer to ArchLinux packages manager for Porteus (Post by neko #49091)
Thanks.
-----------------------------------------
@raja
Thank you for your 'webcam' issue report.
These new example ISOs are updated to fix the file close issue at reboot/shutdown.
You can test the issue by using the uploaded small ISO.
Thanks.
Last edited by neko on 11 Nov 2017, 00:03, edited 3 times in total.
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
ArchLinux packages manager for Porteus
This is what I dread!
sda1 is the EFI partition for Windows 10.
info on web cam:
warning from Linux Kernel 4.13.52.011533] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
sda1 is the EFI partition for Windows 10.
info on web cam:
14.452] (II) event8 - (II) HD WebCam: HD WebCam: (II) is tagged by udev as: Keyboard
[ 14.452] (II) event8 - (II) HD WebCam: HD WebCam: (II) device is a keyboard
[ 14.452] (II) event8 - (II) HD WebCam: HD WebCam: (II) device removed
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
-
- Shogun
- Posts: 434
- Joined: 02 May 2017, 09:51
- Distribution: v3.2.2-32 and Porteus-Artix-64
- Location: Chennai,India
ArchLinux packages manager for Porteus
Failed unmounting 'live' system - errors remain. Saw 'don't kill messags for partitions.
Did you read ' Tomas Matejicek -Slax' s blog?
Did you read ' Tomas Matejicek -Slax' s blog?
Linux Kernel-4.4.272 -32 bit; Linux Kernel-5.4.185 - 64 bit
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
@raja
Now I am studying Slax.
So then, I suspend "Next Step" ("changes EXIT" function issue).
And I will fix your reported problems.
1. firmware for ath10k
You have already fixed this problem by yourself.
It is very good.
The reason is that Porteus has the restrict to include many firmwares in order to reduce ISO size.
In opposition to that "UBUNTU" includes many firmwares.
Therefor a few Porteus users need to add firmware by themself.
Would you tell me what ath10k firmware you used more exactly ?
2. cheese NG
Dependency packages are missing.
Please get following 6 packages by "Archlinux Simple Package Manager".
gnome-video-effects
gst-plugins-bad
gst-plugins-base
gst-plugins-base-libs
gst-plugins-good
gstreamer
At the next update, those dependency packages will be included.
Thanks.
Now I am studying Slax.
So then, I suspend "Next Step" ("changes EXIT" function issue).
And I will fix your reported problems.
1. firmware for ath10k
You have already fixed this problem by yourself.
It is very good.
The reason is that Porteus has the restrict to include many firmwares in order to reduce ISO size.
In opposition to that "UBUNTU" includes many firmwares.
Therefor a few Porteus users need to add firmware by themself.
Would you tell me what ath10k firmware you used more exactly ?
Code: Select all
lib/firmware/ath10k
lib/firmware/ath10k/QCA4019
lib/firmware/ath10k/QCA4019/hw1.0
lib/firmware/ath10k/QCA4019/hw1.0/board-2.bin
lib/firmware/ath10k/QCA4019/hw1.0/firmware-5.bin
lib/firmware/ath10k/QCA4019/hw1.0/notice_ath10k_firmware-5.txt
lib/firmware/ath10k/QCA6174
lib/firmware/ath10k/QCA6174/hw2.1
lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin
lib/firmware/ath10k/QCA6174/hw2.1/board.bin
lib/firmware/ath10k/QCA6174/hw2.1/firmware-5.bin
lib/firmware/ath10k/QCA6174/hw2.1/notice_ath10k_firmware-5.txt
lib/firmware/ath10k/QCA6174/hw3.0
lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin
lib/firmware/ath10k/QCA6174/hw3.0/board.bin
lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin
lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin
lib/firmware/ath10k/QCA6174/hw3.0/notice_ath10k_firmware-4.txt
lib/firmware/ath10k/QCA6174/hw3.0/notice_ath10k_firmware-6.txt
lib/firmware/ath10k/QCA9377
lib/firmware/ath10k/QCA9377/hw1.0
lib/firmware/ath10k/QCA9377/hw1.0/board-2.bin
lib/firmware/ath10k/QCA9377/hw1.0/board.bin
lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin
lib/firmware/ath10k/QCA9377/hw1.0/notice_ath10k_firmware-5.txt
lib/firmware/ath10k/QCA9887
lib/firmware/ath10k/QCA9887/hw1.0
lib/firmware/ath10k/QCA9887/hw1.0/board.bin
lib/firmware/ath10k/QCA9887/hw1.0/firmware-5.bin
lib/firmware/ath10k/QCA9887/hw1.0/notice_ath10k_firmware-5.txt
lib/firmware/ath10k/QCA9888
lib/firmware/ath10k/QCA9888/hw2.0
lib/firmware/ath10k/QCA9888/hw2.0/board-2.bin
lib/firmware/ath10k/QCA9888/hw2.0/firmware-5.bin
lib/firmware/ath10k/QCA9888/hw2.0/notice_ath10k_firmware-5.txt
lib/firmware/ath10k/QCA988X
lib/firmware/ath10k/QCA988X/hw2.0
lib/firmware/ath10k/QCA988X/hw2.0/board.bin
lib/firmware/ath10k/QCA988X/hw2.0/firmware-4.bin
lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin
lib/firmware/ath10k/QCA988X/hw2.0/notice_ath10k_firmware-4.txt
lib/firmware/ath10k/QCA988X/hw2.0/notice_ath10k_firmware-5.txt
lib/firmware/ath10k/QCA9984
lib/firmware/ath10k/QCA9984/hw1.0
lib/firmware/ath10k/QCA9984/hw1.0/board-2.bin
lib/firmware/ath10k/QCA9984/hw1.0/firmware-5.bin
lib/firmware/ath10k/QCA9984/hw1.0/notice_ath10k_firmware-5.txt
lib/firmware/ath10k/QCA99X0
lib/firmware/ath10k/QCA99X0/hw2.0
lib/firmware/ath10k/QCA99X0/hw2.0/board.bin
lib/firmware/ath10k/QCA99X0/hw2.0/firmware-5.bin
lib/firmware/ath10k/QCA99X0/hw2.0/notice_ath10k_firmware-5.txt
Dependency packages are missing.
Please get following 6 packages by "Archlinux Simple Package Manager".
gnome-video-effects
gst-plugins-bad
gst-plugins-base
gst-plugins-base-libs
gst-plugins-good
gstreamer
At the next update, those dependency packages will be included.
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
ArchLinux has stopped supporting 32 bit architecture.
Therefore 32 bit "APorteus ISO Builder" is the end of offering.
Thanks.
Therefore 32 bit "APorteus ISO Builder" is the end of offering.
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
ArchLinux has stopped offering 32 bit architecture.
But a sub-groupe of ArchLinux continues offering 32 bit packages.
a sub-groupe of ArchLinux: https://archlinux32.org/
APorteus will supports 32 bit architectur by using the sub-group's 32 bit repository.
32 bit repository: https://raw.githubusercontent.com/archl ... mirrorlist
-----------------------------
1. "Integrated Simple Package Management tool" was updated to 17.11.20
Please refer to ArchLinux packages manager for Porteus (Post by neko #36687)
"32 bit repository" was changed to one that is offered by ArchLinux sub-groupe.
2. "APorteus ISO Builder" was updated to v17.11.21.
Please refer to ArchLinux packages manager for Porteus (Post by neko #36689)
"32 bit repository" was changed to one that is offered by ArchLinux sub-groupe.
Thanks.
But a sub-groupe of ArchLinux continues offering 32 bit packages.
a sub-groupe of ArchLinux: https://archlinux32.org/
APorteus will supports 32 bit architectur by using the sub-group's 32 bit repository.
32 bit repository: https://raw.githubusercontent.com/archl ... mirrorlist
Code: Select all
##
## Arch Linux repository mirrorlist for i686
## Generated on 2017-11-15
##
## Canada
#Server = http://arch32.mirrors.simplysam.us/$arch/$repo
## France
#Server = https://archlinux32.mirror.roelf.org/$arch/$repo
## Germany
#Server = http://archlinux32.vollzornbrot.de/$arch/$repo
#Server = https://archlinux32.vollzornbrot.de/$arch/$repo
#Server = http://mirror.archlinux32.org/$arch/$repo
#Server = https://mirror.archlinux32.org/$arch/$repo
# note: you need to resolve via openNIC (or similar) to access the next mirror
#Server = http://mirror.archlinux32.oss/$arch/$repo
## India
#Server = https://ind.mirror.archlinux32.org/$arch/$repo
## Japan
#Server = https://jpn.mirror.archlinux32.org/$arch/$repo
## Mexico
#Server = https://mex.mirror.archlinux32.org/$arch/$repo
## Singapore
#Server = https://sgp.mirror.archlinux32.org/$arch/$repo
## United States
#Server = https://32.arlm.tyzoid.com/$arch/$repo
1. "Integrated Simple Package Management tool" was updated to 17.11.20
Please refer to ArchLinux packages manager for Porteus (Post by neko #36687)
"32 bit repository" was changed to one that is offered by ArchLinux sub-groupe.
2. "APorteus ISO Builder" was updated to v17.11.21.
Please refer to ArchLinux packages manager for Porteus (Post by neko #36689)
"32 bit repository" was changed to one that is offered by ArchLinux sub-groupe.
Thanks.
-
- DEV Team
- Posts: 2109
- Joined: 09 Feb 2013, 09:55
- Distribution: APorteus-FVWM-ja-x86_64.iso
- Location: japan
ArchLinux packages manager for Porteus
NEW example of ISOs that were created by "APorteus ISO builder" were uploaded.
====[64 BIT]====
Language: English (locale C)
kernel version: 64Bit 4.14.1
Packages version: the latest version at the time of creating ISO (2017.11.21).
10 kind desktop ISOs and 14 application modules are uploaded.
====[32 BIT]====
Language: English (locale C)
kernel version: 32Bit 4.13.15
Packages version: the latest version at the time of creating ISO (2017.11.20).
10 kind desktop ISOs and 13 application modules are uploaded.
Please refer to ArchLinux packages manager for Porteus (Post by neko #49091)
Thanks.
====[64 BIT]====
Language: English (locale C)
kernel version: 64Bit 4.14.1
Packages version: the latest version at the time of creating ISO (2017.11.21).
10 kind desktop ISOs and 14 application modules are uploaded.
====[32 BIT]====
Language: English (locale C)
kernel version: 32Bit 4.13.15
Packages version: the latest version at the time of creating ISO (2017.11.20).
10 kind desktop ISOs and 13 application modules are uploaded.
Please refer to ArchLinux packages manager for Porteus (Post by neko #49091)
Thanks.