@Rich wrote FetchExt.sh - see here: http://forum.tinycorelinux.net/index.php/topic,23034.msg164745.html
The repo contains files *dep and *tree with the deps and recursive deps respectively.
-enable-kvm enable KVM full virtualization support
qemu-system-x86_64 --cdrom CorePure64-current.iso -enable-kvm
Thank you for making a video and explaining tiny core.
I see in the video, you using qemu in linux environment.
Have you tried add the "-enable-kvm" to the command line to make qemu faster.Code: (bash) [Select]-enable-kvm enable KVM full virtualization support
Code: (bash) [Select]qemu-system-x86_64 --cdrom CorePure64-current.iso -enable-kvm
You have to enable virtualization support in the bios.
sudo fdisk -u /dev/sda
sudo resize2fs /dev/sda1
Now you are ready to use the bigger partition.Thanks you also, by the way:
I have also test another way of doing what you doing, you can follow this article to make some images that you can burn to some usb thumb drives or to some ssd or to some spinning disks using qemu :)
https://fabianstumpf.de/articles/tinycore_images.htm
Don't forget then burning the image to the usb thumb drive or to ssd or to disk, you have to expand the partition to correct size after you booting the system natively.
You need to do the following:
Thanks to @bmarkus at this forum for the original text:
1) Start fdisk partitioning tool as root:
Code: (bash) [Select]sudo fdisk -u /dev/sda
Now list partitions with 'p' command and write down the starting and
ending sectors of partition.
2) Delete partition with 'd' than recreate it with 'n' command.
Use the same starting sector as deleted had and provide end
sector or size greater than deleted had having enough free space
for Mounted Mode. When finished, exit fdisk with 'w' command. Now
partition size increased but file system size is not yet changed.
3) Reboot. It is necessary to make Kernel aware of changes.
4) After reboot expand file system to the new partition boundaries with
typing the following command as root:Code: (bash) [Select]sudo resize2fs /dev/sda1
Now you are ready to use the bigger partition.
wifi.tcz
firmware-atheros.tcz
firmware-ipw2100.tcz
firmware-ipw2200.tcz
firmware-iwimax.tcz
firmware-iwl8000.tcz
firmware-iwl9000.tcz
firmware-iwlwifi.tcz
firmware-marvel.tcz
firmware-myri10ge.tcz
firmware-netxen.tcz
firmware-openfwwf.tcz
firmware-ralinkwifi.tcz
firmware-rtlwifi.tcz
firmware-ti-connectivity.tcz
firmware-ueagle-atm.tcz
firmware-vxge.tcz
firmware-zd1211.tcz
Xvesa is 32bit only, so if you don’t want to use Xorg-7.7, you need to use Xfbdev.
If you run the first line of .xsession from the console prompt you might get more info on why Xfbdev doesn’t start.
There is a file called mirrors.tcz
The contents of that file is:
cat /usr/local/share/mirrors
http://repo.tinycorelinux.net/
http://distro.ibiblio.org/tinycorelinux/
http://ftp.nluug.nl/os/Linux/distr/pub/linux/distributions/tinycorelinux/
http://ftp.vim.org/os/Linux/distr/pub/linux/distributions/tinycorelinux/
http://sunsite.icm.edu.pl/pub/Linux/sunsite.unc.edu/distributions/tinycorelinux/
http://sunsite2.icm.edu.pl/pub/Linux/sunsite.unc.edu/distributions/tinycorelinux/
http://ftp.cc.uoc.gr/mirrors/linux/tinycorelinux/
http://kambing.ui.ac.id/tinycorelinux/
http://mirror.cedia.org.ec/tinycorelinux/
http://mirror.epn.edu.ec/tinycorelinux/
http://mirrors.dotsrc.org/tinycorelinux/
http://mirror.cpsc.ucalgary.ca/mirror/tinycorelinux/
http://mirrors.163.com/tinycorelinux/
ftp://distro.ibiblio.org/tinycorelinux/
ftp://ftp.gtlib.gatech.edu/pub/tinycore/
ftp://ftp.nluug.nl:21/pub/ibiblio/distributions/tinycorelinux/
ftp://ftp.vim.org:21/pub/ibiblio/distributions/tinycorelinux/
ftp://sunsite.icm.edu.pl/pub/Linux/sunsite.unc.edu/distributions/tinycorelinux/
ftp://sunsite2.icm.edu.pl/pub/Linux/sunsite.unc.edu/distributions/tinycorelinux/
ftp://ftp.cc.uoc.gr/mirrors/linux/tinycorelinux
ftp://mirror.cedia.org.ec/tinycorelinux/
ftp://mirrors.dotsrc.org/tinycorelinux/
Glad you like TinyCore, but my daily driver is Arch, but when it comes to Raspberry Pi it's picore :)I would've considered Arch if only not system.d, well and because of Xorg of course. I love using X frame buffer on Tiny core - it's such a cool concept. If I didn't need to produce programming videos on YouTube I would've dropped GUI completely. For instance my minimalist setup is just a core + wifi firmware + python/pip and that's it.
wifi.tcz
firmware-atheros.tcz
firmware-ipw2100.tcz
firmware-ipw2200.tcz
firmware-iwimax.tcz
firmware-iwl8000.tcz
firmware-iwl9000.tcz
firmware-iwlwifi.tcz
firmware-marvel.tcz
firmware-myri10ge.tcz
firmware-netxen.tcz
firmware-openfwwf.tcz
firmware-ralinkwifi.tcz
firmware-rtlwifi.tcz
firmware-ti-connectivity.tcz
firmware-ueagle-atm.tcz
firmware-vxge.tcz
firmware-zd1211.tcz
aterm.tcz
bzip2-lib.tcz
fltk-1.3.tcz
flwm_topside.tcz
freetype.tcz
glib2.tcz
graphite.tcz
harfbuzz.tcz
imlib2-bin.tcz
imlib2.tcz
libffi.tcz
libfontenc.tcz
libICE.tcz
libjpeg-turbo.tcz
libpng.tcz
libSM.tcz
libX11.tcz
libXau.tcz
libxcb.tcz
libXdmcp.tcz
libXext.tcz
libXfont.tcz
libXmu.tcz
libXt.tcz
pcre.tcz
wbar.tcz
Xorg-7.7.tcz
Xlibs.tcz
Xprogs.tcz
firefox_getLatest.tcz
guvcview.tcz
alsa.tcz
alsa-config.tcz
pulseaudio.tcz
mplayer-cli.tcz
recordmydesktop.tcz
waitusb=5 tce=sdb home=sdb opt=sdb (and a few more)
which has resulted in having a distro allowing me recording programming videos for youtube:[code][ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
[ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
Hi cmk
Please use Code Tags when posting commands and responses seen in a terminal. To use Code Tags click on the # icon
above the reply box and paste your text between the Code Tags as shown in this example:Quote[code][ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517[/code]
It will appear like this in your post:Code: [Select][ 36.176529] pcm512x 1-004d: Failed to get supply 'AVDD': -517
[ 36.176536] pcm512x 1-004d: Failed to get supplies: -517
[ 36.191753] pcm512x 1-004d: Failed to get supply 'AVDD': -517
Code Tags serve as visual markers between what you are trying to say and the information you are posting. They also preserve
spacing so column aligned data displays properly. Code tags also automatically add horizontal and or vertical scrollbars
to accommodate long lines and listings.