Tiny Core Linux
dCore Import Debian Packages to Mountable SCE extensions => dCore X86 => Topic started by: Jason W on April 01, 2014, 07:33:22 PM
-
dCore v5.14.04.01 for x86 has been posted. No major theme this go around, just some fixes and enhancements.
Available at:
http://tinycorelinux.net/5.x/x86/release/
Full changelog viewable on our git page:
http://git.tinycorelinux.net/index.cgi?url=dCore-scripts.git/
dCore provides a suite of scripts to allow import of Debian packages. Currently amv7 and x86 are supported.
* Note: I am now using the same release announcement format as for armv7, one sticky topic, one post per release. Please raise bugs, questions, or issues in their own thread for better organization.
*** Found a bug and reposted on 9pm EST. If you downloaded before then, please re-download.
-
dCore and ub-dCore v5.14.05.26 for x86 has been posted. More bug fixes and enhancements.
Available at:
http://tinycorelinux.net/5.x/x86/release/
Full changelog viewable on our git page:
http://git.tinycorelinux.net/index.cgi?url=dCore-scripts.git/
dCore provides a suite of scripts to allow import of Debian packages. Currently amv7 and x86 are supported.
-
dCore and ub-dCore v5.14.06.13 for x86 has been posted. Fixed a bug in importsce as well as now using a rotating dash instead of echoing dependency names in the terminal as part of the dependency gathering routine. On my machine this results in up to a 40% performance increase in calculating dependencies when using a normal size xterm window.
Available at:
http://tinycorelinux.net/5.x/x86/release/
Full changelog viewable on our git page:
http://git.tinycorelinux.net/index.cgi?url=dCore-scripts.git/
dCore provides a suite of scripts to allow import of Debian packages. Currently amv7 and x86 are supported.
-
Uploaded a new cut to release candidates as there were some extensive file changes with udev.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
hi jason,
i experienced some problems with this cut and i guess the notification is outdated for the cut in june.
i cannot restore my backup-file properly and it's difficult for me to examine the causes for these problems:
my extensions cannot be installed, is there a problem with labeling devices in the boot-process?
is there are problem with bootlocal.sh or bootsync.sh?
thank you for your help.
ps: by the way, i have similar problems with dcore-jessie, so i cannot use my really extensive configurated backup :(
-
As the changes were to udev, there probably is an issue with devices. I will look into it.
-
I am booting the release candidates of dCore.gz and dCore-jessie.gz with no issues on 2 very different machines.
Are you using the tinycore.net location and not a mirror like ibiblio? Ibiblio right now has different dates of those files and I did have a bad cut of both of them fore a small time period.
-
Hi
I experience the same problem as netnomad. The extensions are not loaded.
I've used the tinycorelinux.net
-
Have you downloaded a new dCore.gz today? I will look into it.
-
hi jason,
tinycore.net offers me dCore-wheezy from 2014.09.01 and dCore-jessie from 2014.09.04.
-
Ok, I see, device naming varies across reboots. I had my sda hard drive and sdb usb drive switch naming a few times with the newest release candidate dCore.gz . A change in the one of the udev rules files which allowed the /dev/disk/by-* to be populated fully has also perhaps removed a more persistent naming of devices. I will look into it tonight.
-
Good news, I think I have found a solution via the 60-persistend-storage.rules from udev-extra.tcz in the 5.x repo.
Please try it out, it creates the needed files in /dev/disk and hopefully is better about consistency across reboots in device names versus the Debian/upstream udev files.
Posted new gzs:
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz.md5.txt
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie-5.14.09.03.iso
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie-5.14.09.03.iso.md5.txt
-
hi jason,
sorry, but i see no improvement for my setup.
it could be caused by the configurations of my backup?
thank you for your help.
-
Ok, what is your device setup? Usb drives, hard drive partitions, etc and how are they getting assigned device names. (HD is sda1, sda2, usb is sdb1, second usb is sdc1, etc). Are the device names attached to different ide or usb changing across reboots? (Normal for Linux, but for some reason prevented in previous dCore releases).
How is the backup not getting restored, not getting untarred, or do scripts in the backup not run, etc?
-
hi jason,
my boot-device is /dev/sdb1.
these are my boot-commands:
kernel /live/dcore-current/boot/vmlinuz waitusb=5:LABEL=tc protect restore=LABEL=tc tce=LABEL=tc/tce lst=sceboot.lst vga=795 psmouse.proto=imps settime tz=CET-1CEST,M3.5.0,M10.5.0/3 laptop kmap=de multivt lang=de_DE.UTF-8 mydata=dcore blacklist=snd_usb_audio intel_rng.no_fwh_detect=-1 printk.time=1 cron desktop=fluxbox log=3 acpi_sleep=s3_bios,s3_mode showapps
append initrd=/live/dcore-current/boot/dCore.gz
-
Ok, you have assigned a label to the device, that does help narrow it down. I can test that when I get in tonight.
How many devices do you have attached (hd, usb) and has that changed since dCore was last working as expected?
What is the output of the below command?
blkid -s LABEL /dev/sdb1
-
Hi
what's the difference between http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie.gz
and
http://tinycorelinux.net/5.x/x86/release_candidates/dCore-jessie/dCore-jessie-5.14.09.03.iso
?
-
Should only be that one is an ISO. I will be posting ISOs of releases/release candidates for all the dCore once things settle down.
-
JLS, are you having the same issue still? If so, please give me all the details you can so I can narrow it down.
-
I get the the extensions loaded at boot time changing :
waitusb=5:UUID=f184710d-4609-47c3-897e-4b8a0a6c02a2to
waitusb=5
-
jls@eeepc:~$ showbootcodes
BOOT_IMAGE=/boot/dCore/vmlinuz loglevel=3 noutc tz=CET-1CEST-2,M3.5.0,M10.5.0 lang=fr_FR.UTF-8 waitusb=5 tce=UUID=f184710d-4609-47c3-897e-4b8a0a6c02a2/dce user=jls host=eeepc vga=788 laptop multivt
-
jls@eeepc:~$ version
5.14.06.13
should be updated
-
Ok, you have assigned a label to the device, that does help narrow it down. I can test that when I get in tonight.
How many devices do you have attached (hd, usb) and has that changed since dCore was last working as expected?
What is the output of the below command?
blkid -s LABEL /dev/sdb1
tc@box:~$ blkid -s LABEL /dev/sdb1
/dev/sdb1: LABEL="MYSTICK"
tc@box:~$ blkid -s LABEL /dev/sdb2
/dev/sdb2: LABEL="tc"
my setup offers an internal harddisk sda and i use an usbstick with sdb1 fat32 and sdb2 ext4.
sdb1 boots with syslinux the different core-files and several other live-systems.
sdb2 labeled with tc contains my extensions and my chronological backups.
-
Netnomad, that is my exact same hardware setup so I can test label booting and hopefully find what is going on.
-
I will automate the updating of the version file, it is easy to overlook.
-
Netnomad, your boot options look like they are for core.gz and not dCore.
-
Ok, I think I have found a fix. I am booting with the LABEL= options, and it is working here, it did not before.
Please test.
-
Ok, I think I have found a fix. I am booting with the LABEL= options, and it is working here, it did not before.
hi jason,
you've got it!!! now it boots fine!
great work :)
Netnomad, your boot options look like they are for core.gz and not dCore.
sorry, i gave you the wrong bootcodes :(
i corrected them above and offer them here, too:
kernel /live/dcore-current/boot/vmlinuz waitusb=5:LABEL=tc protect restore=LABEL=tc tce=LABEL=tc/tce lst=sceboot.lst vga=795 psmouse.proto=imps settime tz=CET-1CEST,M3.5.0,M10.5.0/3 laptop kmap=de multivt lang=de_DE.UTF-8 mydata=dcore blacklist=snd_usb_audio intel_rng.no_fwh_detect=-1 printk.time=1 cron desktop=fluxbox log=3 acpi_sleep=s3_bios,s3_mode showapps
append initrd=/live/dcore-current/boot/dCore.gz
these options worked fine for so long.
i thought that the same kernel is loaded with similar tinycore-specific options.
are there options that make no sense?
thank you for your help and commitment :)
-
I copied the dCore.gz in release_candidates to release, updated the /usr/share/doc/tc/release.txt, actually automated it so it should always reflect the day it was packed.
Please report any issues.
-
...works flawless, smooth and fine for me :)
-
Updated to deal better with groups the user needs to belong to and that would require a re-login to effect upon adding the user to group. Please download and test.
In the release area as I am confident there will be no breakage.
http://tinycorelinux.net/5.x/x86/release/dCore.gz
http://tinycorelinux.net/5.x/x86/release/dCore.gz.md5.txt
-
Updated with the fix mentioned in the dCore-jessie update post.
http://tinycorelinux.net/5.x/x86/release/dCore.gz
http://tinycorelinux.net/5.x/x86/release/dCore.gz.md5.txt
-
Ok, I have made a testing dCore.gz in release_candidates. 6 files were changed, so it is major enough to go through a testing phase. If you create a .dep file for a package in the sce directory, or there is an existing .dep file, it's contents will be used as deps when the package is imported or re-imported whether the -d option is used or not, as with the existence of a .dep file it is assumed you wish to keep it. Delete any .dep file if you wish to make a different new one, or to import without one. Also, if you re-import a mounted SCE, it will be created in the /etc/sysconfig/tcedir/sce/update directory, and the contents of that directory will be moved to /etc/sysconfig/tcedir/sce during reboot. The size calculation of importsce has been adjusted for this. Please download and test. If all is well, then these changes will be applied to the other dCore ports.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
the list of the deb(s) there will be included is not shown; tried it with a present dep file and leaving the 5 seconds passing without pressing any key
-
reimported currently mounted pidgin (-f): correctly placed in the update dir and then moved.
Thanks Jason.
-
Oh, I meant to say that the echoing of all the package names, which can be hudreds, are now echoed to a file that can be read by pressing "y" when asked. Do nothing, and in 5 seconds that option dissapears. Less screen clutter, knowing all the package names that will be included in an SCE is sort of debugging info IMO. But the option to see which packages will be included is available.
This information is stored in a file that can be read once the SCE is loaded, it also stores the md5sums of those individual Debian or prebuilt packages:
/usr/local/sce/PKGNAME/PKGNAME.md5sum
-
if I want to see the debs (tar.gz) included I have pay attention of the end of the deps generation, cause then I only have 5 secs. it's stressing me.
-
Ok, I will make it a simple yes/no that comes unless the non-interactive option is used. I was mainly thinking of not creating yet another yes/no that one has to answer, but that can be avoided with the non-interactive switch.
-
Updated to release_candidates removing the 5 second timeout to where it waits indefinitely for input, unless non-interactive mode is chosen.
Also, have created a yes/no for when there is not enough free ram or hard drive space. This is invoked even with non-interactive mode since there is no reason to keep going when failure will result.
-
hi jason,
i'm looking forward testing these new features in jessie :)
keep on hacking, thank you for your excellent work!
-
Thanks netnomad, I will put this all now in Jessie to widen the testing base and Jessie is release candidate status at this point.
Updated dcore.gz in release_candidates. Added the ability to call unloaded ondemand apps from a root terminal if root use is desired like in gparted. Also fixed the issue of ondemand not obeying command arguements.
I added an exit code of 1 in debExtract where tar and ar are used in the case of their failure. Deb2sce was supposed to exit on a fail of debExtract, but the tar and ar commands failing were not causing the debExtract script to exit with a 1. Hopefully it is more robust now, the md5sums of the debian packages and prebuilt were already being checked whether being redownloaded or using what is already in the sce dir, my hunch is normally an out of disk space issue if there is failure.
Please download and test.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
Hi
dCore iso in the release candidate area is not the latest
-
Ok, should be good now.
-
Updated to change the "importsce -f" option to the more logically named "importsce -l". Also, a /etc/sysconfig/tcedir/sce/pkgname.sce.lst file is created out of that specified file list. That .lst list will be used on future import sessions of that package name whether a Debian one or one of the user's choosing. Using the "importsce -l" option on future imports of that package name with an expanded package list will create a new sce with those packages and also overwrite the previous .lst list file. Still in release candidate area, if this and the last changes are stable, will move to the release area.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
Hi
I'm importing advancecomp I get this:
cat: can't open '/tmp/.targetfile': No such file or directory
-
Ok, I see what is causing it. A very simple fix, will get it when I get home tonight.
-
Fixed, new cut uploaded to release_candidates and new iso.
-
Updated to release_candidates with a fix for non-interactive mode on package selection.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
Updated to remove pathname from command line when present during importsce.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
Updated to make import sessoins more time efficient and to create the tool updatesce.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
Updated with bugfixes and enhancements.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
Uploaded with bugfixes releted to updatesce.
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz
http://tinycorelinux.net/5.x/x86/release_candidates/dCore.gz.md5.txt
-
Updated with latest fixes. Available in the release_candidates directory below. Note, the releases and release candidates under the tinycorelinux/5.x/x86/ directory will no longer be supported once a stable release is make in tinycorelinux/dCore/x86/. Users are advised to download the latest release at that time.
http://tinycorelinux.net/dCore/x86/release_candidates/dCore-wheezy/
-
A smalll update with more streamlined md5sum and dependency searching during import.
http://tinycorelinux.net/dCore/x86/release_candidates/dCore-wheezy/
-
Bugfix in extra repo md5sum function.
http://tinycorelinux.net/dCore/x86/release_candidates/dCore-wheezy/
-
Bugfix.
http://tinycorelinux.net/dCore/x86/release_candidates/dCore-wheezy/
-
Updated. Import creates an md5.txt file for created SCE's, and loadsce checks for it's existence and it's md5 if it exists. This won't break existing SCE directories, it will simply add an md5.txt file for future imported SCE's.
http://tinycorelinux.net/dCore/x86/release_candidates/dCore-wheezy/
-
Hi
ondemand uses xmessage which is in the x11-utils package which is not in base dCore
-
A check is made for a running X session, otherwise xmessage is not used and instead terminal output is given. X11-utils is a dependency of Xorg, so a running X session should always have xmessage.
-
Hi
In my setup there no x11-utils, I use xorg-trident
-
Ok, I have adjusted the dependencies and x11-utils should now be part of any xorg setup.
-
Updated, please test.
Import and load the "sed" package for better performance during import.
http://tinycorelinux.net/dCore/x86/release_candidates/dCore-wheezy/
-
Merging hicolor-icon-theme
Connecting to ftp.fr.debian.org (212.27.32.66:80)
liblzma5_5.1.1alpha+ 100% |*******************************| 202k 0:00:00 ETA
Merging liblzma5
Connecting to ftp.fr.debian.org (212.27.32.66:80)
libxml2_2.8.0+dfsg1- 100% |*******************************| 871k 0:00:00 ETA
Merging libxml2
cat: /opt/debextra/ep: No such file or directory
wget: not an http or ftp url: /pool/main/s/shared-mime-info/shared-mime-info_1.3-1~bpo70+1_i386.deb
failed on download of pool/main/s/shared-mime-info/shared-mime-info_1.3-1~bpo70+1_i386.deb
wget: not an http or ftp url: /pool/main/s/shared-mime-info
ar: can't open '/etc/sysconfig/tcedir/import/debs/shared-mime-info_1.3-1~bpo70+1_i386.deb': No such file or directory
ar: can't open '/etc/sysconfig/tcedir/import/debs/shared-mime-info_1.3-1~bpo70+1_i386.deb': No such file or directory
/usr/bin/debExtract: line 41: can't create /tmp/: Is a directory
Failure to extract shared-mime-info_1.3-1~bpo70+1_i386.deb, exiting..
-
Ok, there is something with the /opt/debextra routine, I will aim to fix it.
Could you post the names of your /opt/debextra entries and their contents, as well as what package you are trying to import?
-
unfortunately my mydata.tgz got corrupted here in the main biblioteque of marsleille france, mydata corruption happen quite frequently due to (d)core philosofy, so I've lost my debextras
-
hi jls_legalize,
your last statement is very easy misunderstood...
kind regards.
-
JlS - please open a new thread with more information for the mydata.tgz corruption. I have not seen any curruption myself, and the backup function is the same as Core.
-
Updated, reverting to using grep for the md5 and dependency routines, sed no longer used. Turns out I went around my elbow to get to my ear on that one, though grep itself can't search until next new line, a simple grep trick can.
http://tinycorelinux.net/dCore/x86/release_candidates/dCore-wheezy/
-
Hi
so "grep" should be imported for better performances?
-
Yeah, importing grep will greatly improve performance during dependency and md5sum gathering.
-
Excuse me, but "grep" is not part of the core?, if it is, why is interesting to import it? or, is because it's into busybox?
-
Busybox grep in the dependency gathering routine will read between 1 and 2 packages per second. GNU grep will give you about 10 or 15 dependencies a second, almost 10 times faster. I believe GNU grep caches the file it is reading in RAM so it does not need to pull it from the disk on subsequent reads. Busybox grep will be used unless grep is imported which then by default GNU grep will be called on. The md5sum functions in deb2sce and debGetSize also show the same performance increase with an imported grep, so it is quite a time difference overall.
Below is an actual comparison of the two greps, each ran twice to eliminate cache factor.
root@box:/home/tc# time /bb/grep "Package: file$" /etc/sysconfig/tcedir/debian_jessie_main_i386_Packages
Package: file
real 0m 0.38s
user 0m 0.37s
sys 0m 0.00s
root@box:/home/tc# time /bb/grep "Package: file$" /etc/sysconfig/tcedir/debian_jessie_main_i386_Packages
Package: file
real 0m 0.38s
user 0m 0.37s
sys 0m 0.00s
root@box:/home/tc# time grep "Package: file$" /etc/sysconfig/tcedir/debian_jessie_main_i386_Packages
Package: file
real 0m 0.01s
user 0m 0.00s
sys 0m 0.00s
root@box:/home/tc# time grep "Package: file$" /etc/sysconfig/tcedir/debian_jessie_main_i386_Packages
Package: file
real 0m 0.01s
user 0m 0.00s
sys 0m 0.00s
-
Good, so clearly explained.
Thanks
-
Actually, using the time command in deb2sce on the debGetDeps function, I clocked 22 dependencies per second so the performance increase is substantial indeed.
-
This thread will now close in favor of the Release and Release candidate sections above. Please direct any posts there.