kernel compiling in woof-ce
@peebee
Thanks for the feedback.
Please note: aufs-utils not included in that.
However last night I adjusted the script and recompiled pae, nopae and 64 bit kernels all with aufs-utils included.
I will upload then post Huge packages and sources and modified sukk. Although i am going to rewrite sukk-universal to include fdrv/kernel-kit improvements and a few ideas of my own.
Thanks for the feedback.
Please note: aufs-utils not included in that.
However last night I adjusted the script and recompiled pae, nopae and 64 bit kernels all with aufs-utils included.
I will upload then post Huge packages and sources and modified sukk. Although i am going to rewrite sukk-universal to include fdrv/kernel-kit improvements and a few ideas of my own.
4.1.2-pae-i686
http://tinyurl.com/pfxm6k9
kernel-sources
http://tinyurl.com/osxuntr
4.1.2-nopae-i486
http://tinyurl.com/nc89pg4
kernel sources
http://tinyurl.com/nq3m33h
4.1.2-64-x86_64
http://tinyurl.com/q6d2ye3
kernel sources
http://tinyurl.com/ocwzra6
SUKK-5
http://tinyurl.com/p4d6n5l
http://tinyurl.com/pfxm6k9
kernel-sources
http://tinyurl.com/osxuntr
4.1.2-nopae-i486
http://tinyurl.com/nc89pg4
kernel sources
http://tinyurl.com/nq3m33h
4.1.2-64-x86_64
http://tinyurl.com/q6d2ye3
kernel sources
http://tinyurl.com/ocwzra6
SUKK-5
http://tinyurl.com/p4d6n5l
hi stemsee,
the SUKK-5 link is broken
Error: TinyURL redirects to a TinyURL.
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
build separately pae, nopae, 64. Same build log:
In ram:
Specifically:
then it stops, hanging at the blinking cursor. Source, modules, headers and kernel all built but no mksquashfs. No packages. The "No such file or directory" warnings are in error, to say the least.
Might it be something I messed up in the latest JL64-603? I've been making packages for days, so I don't think it's me. But maybe I've missed something else?
df
Code: Select all
fatal: Not a git repository (or any parent up to mount point /initrd/mnt/dev_save)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Code: Select all
fatal: Not a git repository (or any parent up to mount point /initrd/mnt/dev_ro2)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Code: Select all
...
WARNING: This will delete aufs, kernel folder but wont touch configs or dist.
Please wait...
Cleaning complete
Kernel Sources already there!
Creating the Aufs sources tarball
Extracting the kernel sources
Adding Aufs to the kernel sources
Resetting the minor version number
Reducing the verbosity level
Applying ../patches/commoncap-symbol.patch
Cleaning the kernel sources
./ubuild.sh: line 719: cd: linux-4.1.2: No such file or directory
For unattended config of new kernels do nothing here!
For old kernel versions or other customisations enter 2 ...
1. make olddefconfig
2. make menuconfig
3. make oldconfig
8 seconds
...
...
...
Creating the kernel package
Huge kernel 4.1.2-JL is ready in dist
Cleaning the kernel sources
Now to build the aufs-utils for userspace
Failed to get aufs-util from git, do it manually. Kernel is compiled OK :)
./ubuild.sh: line 819: cd: aufs-util: No such file or directory
fatal: Not a git repository (or any parent up to mount point /initrd/mnt/dev_ro2)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Failed to get aufs-util from git, do it manually. Kernel is compiled OK :)
Patching aufs-util sources
cp: cannot stat 'Makefile': No such file or directory
sed: can't read Makefile: No such file or directory
./ubuild.sh: line 838: ../dist/sources/patches/aufs-util-dynamic.patch: No such file or directory
rm: cannot remove '*.orig': No such file or directory
Might it be something I messed up in the latest JL64-603? I've been making packages for days, so I don't think it's me. But maybe I've missed something else?
df
Hi, just returned from camping trip!
@DryFalls
Which version of sukk are you using? 5? I had similar troubles before. 666philb indicated that the servers were experiencing difficulties!
I will do a run for 4.1.3 lat.er today to check if the script has bugs. But I did compile 4.1.2 kernels flawlessly, however sometimes the script from the wrong partition gets uploaded!!!
EDIT:
@DryFalls
Which version of sukk are you using? 5? I had similar troubles before. 666philb indicated that the servers were experiencing difficulties!
I will do a run for 4.1.3 lat.er today to check if the script has bugs. But I did compile 4.1.2 kernels flawlessly, however sometimes the script from the wrong partition gets uploaded!!!
EDIT:
- Attachments
-
- capture30847.jpg
- This is how it appears for sukk-5 . so I think @Dry Falls you are using an older version.
- (18.26 KiB) Downloaded 566 times
how to make dialog accept multiple-selections?
This pure bash code does one selection at a time!
Finally this code does it exactly right.[/code]
Code: Select all
files=$(dialog --stdout --title "Choose a file" --fselect $HOME/ 14 48)
This pure bash code does one selection at a time!
Code: Select all
#!/bin/bash
# customize with your own.
options=("AAA" "BBB" "CCC" "DDD")
menu() {
echo "Avaliable options:"
for i in ${!options[@]}; do
printf "%3d%s) %s\n" $((i+1)) "${choices[i]:- }" "${options[i]}"
done
[[ "$msg" ]] && echo "$msg"; :
}
prompt="Check an option (again to uncheck, ENTER when done): "
while menu && read -rp "$prompt" num && [[ "$num" ]]; do
[[ "$num" != *[![:digit:]]* ]] &&
(( num > 0 && num <= ${#options[@]} )) ||
{ msg="Invalid option: $num"; continue; }
((num--)); msg="${options[num]} was ${choices[num]:+un}checked"
[[ "${choices[num]}" ]] && choices[num]="" || choices[num]="+"
done
printf "You selected"; msg=" nothing"
for i in ${!options[@]}; do
[[ "${choices[i]}" ]] && { printf " %s" "${options[i]}"; msg=""; }
done
echo "$msg"
Finally this code does it exactly right.
Code: Select all
#!/bin/bash
cmd=(dialog --separate-output --checklist "Select options:" 22 76 16)
options=(1 "Option 1" off # any option can be set to default to "on"
2 "Option 2" off
3 "Option 3" off
4 "Option 4" off)
choices=$("${cmd[@]}" "${options[@]}" 2>&1 >/dev/tty)
clear
for choice in $choices
do
case $choice in
1)
echo "First Option"
;;
2)
echo "Second Option"
;;
3)
echo "Third Option"
;;
4)
echo "Fourth Option"
;;
esac
done
Here are Kernels 4.1.3
64
http://tinyurl.com/ohwfw72
sources
http://tinyurl.com/oz7p25g
32pae-i686
http://tinyurl.com/ovl6z4p
sources
http://tinyurl.com/ovsrmxt
32nopae-i486
http://tinyurl.com/p4nbpy8
sources
http://tinyurl.com/oz2yahp[/url]
64
http://tinyurl.com/ohwfw72
sources
http://tinyurl.com/oz7p25g
32pae-i686
http://tinyurl.com/ovl6z4p
sources
http://tinyurl.com/ovsrmxt
32nopae-i486
http://tinyurl.com/p4nbpy8
sources
http://tinyurl.com/oz2yahp[/url]
Last edited by stemsee on Mon 27 Jul 2015, 11:14, edited 1 time in total.
SUKK-Universal includes woof-ce > fdrv > kernel kit > build.sh
and configs and build.conf, there is no conflict with sukk/ubuild.sh and confs, which now use configs_extra_user. The only caveat is that if dist has packages from ubuild.sh build and if you then run build.sh it will delete dist with everything inside. However if you select the mega upload option then the work is backed up on the cloud. Or just rename dist to dis or something!
http://tinyurl.com/qavafjz
and configs and build.conf, there is no conflict with sukk/ubuild.sh and confs, which now use configs_extra_user. The only caveat is that if dist has packages from ubuild.sh build and if you then run build.sh it will delete dist with everything inside. However if you select the mega upload option then the work is backed up on the cloud. Or just rename dist to dis or something!
http://tinyurl.com/qavafjz
- Attachments
-
- capture26112.jpg
- (30.94 KiB) Downloaded 513 times
-
- capture27762.jpg
- (17.7 KiB) Downloaded 507 times
-
- capture29405.jpg
- (21.4 KiB) Downloaded 498 times
-
- capture2166.jpg
- (23.39 KiB) Downloaded 503 times
It was v5 downloaded from the prior post (oops) attachment. Here is the aufs from build64:stemsee wrote:Hi, just returned from camping trip!
@DryFalls
Which version of sukk are you using? 5? I had similar troubles before. 666philb indicated that the servers were experiencing difficulties!
Code: Select all
kernel_version="4.1.2"
# below is a list of kernel mirrors
# uncomment the closest one to you
# make sure only one is uncommented!
# you can search for more mirrors and use them
numer=`echo $kernel_version | cut -f1 -d '.'`
kernel_mirror="http://www.kernel.org/pub/linux/kernel/v4.x/"
#kernel_mirror="http://mirror.aarnet.edu.au/pub/ftp.kernel.org/linux/kernel/v3.0/"
# new vars
# if sourceforge seems unstable use the sfjro url
#aufs_git=git://github.com/sfjro/aufs4-linux.git
aufs_git=git://github.com/sfjro/aufs4-standalone.git
# This is only for new kernels, leave blank if not using bleeding edge RC
aufsv=4.1
#aufs3=3.x-rcN
#SPECIAL NOTE. LTS 3.10X kernels past 3.10.25 need this set with 'aufs3=3.10.x'
df
@Chilli Dog
You can see that write is enabled in the pae config. Have you checked your fstab? I plugged a usb ntfs partition in and created a directory no problem, with my 4.1.3 kernel. Did you use a custom config?
Try booting your system without a savefile and see if the problem is still there! Are the kernel modules named and loaded correctly?
There are a few variables involved you give little useful information.
You can see that write is enabled in the pae config. Have you checked your fstab? I plugged a usb ntfs partition in and created a directory no problem, with my 4.1.3 kernel. Did you use a custom config?
Try booting your system without a savefile and see if the problem is still there! Are the kernel modules named and loaded correctly?
There are a few variables involved you give little useful information.
- Attachments
-
- capture10376.jpg
- (53.75 KiB) Downloaded 397 times
Yes I did use a custom config, but the section you posted looks the same.
I booted without a save file.
I wonder what it could be?
Code: Select all
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
I wonder what it could be?
Out of topic, sorry, but I think it is important to know:
http://sourceforge.net/p/aufs/mailman/message/34289816/
Many people wouldn't know what aufs is and what good it is for - but since this is a kernel-compiling thread, I am sure you all know what it is used for (in case you don't, I wrote an explanation here: http://www.murga-linux.com/puppy/viewto ... 140#506140).
If you think Puppy is nice, and you have donated to Barry, I would urge you to donate to him as well. If not because of the kindness of your heart or because of your gratitude of having enjoyed Puppy (and indirectly, aufs); at least donate for the selfish reason to ensure the longevity of aufs (and thus that of Puppy and many other distros like it e.g. Slax, etc as well). If you have already donated - then please ignore this plea
http://sourceforge.net/p/aufs/mailman/message/34289816/
J.R. Okajima is the original author and the sole maintainer of aufs since its inception in 2006.J.R. Okajima wrote:Today is Monday. I usually release aufs on every Monday and it is
expected to be release aufs4.x-rcN for linux-4.2-rc[12] today.
But fortunately/unfortunately I am very busy now and have to suspend my
aufs development for a while, at least for this month. In other words, I
will not release aufs4.x-rcN for almost all linux-4.2-rcN series.
If everything goes well, I will come back in next month and will release
aufs4.2.
Many people wouldn't know what aufs is and what good it is for - but since this is a kernel-compiling thread, I am sure you all know what it is used for (in case you don't, I wrote an explanation here: http://www.murga-linux.com/puppy/viewto ... 140#506140).
If you think Puppy is nice, and you have donated to Barry, I would urge you to donate to him as well. If not because of the kindness of your heart or because of your gratitude of having enjoyed Puppy (and indirectly, aufs); at least donate for the selfish reason to ensure the longevity of aufs (and thus that of Puppy and many other distros like it e.g. Slax, etc as well). If you have already donated - then please ignore this plea
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]