Code: Select all
# git --version
git version 1.8.4
You need to uninstall the version you have and delete the profile, then install the devx (sfs file) which will have git included, as well as all the other goodies needed for compiling .. (re)
Code: Select all
# git --version
git version 1.8.4
Yes they are.keyboard wrote: This are some bizzare problems I am running into. is it a OS problem ? maybe storage drive ?
this is the version I am having in devx sfs:01micko wrote:That's from slacko which is quite a bit older than tahr.Code: Select all
# git --version git version 1.8.4
You need to uninstall the version you have and delete the profile, then install the devx (sfs file) which will have git included, as well as all the other goodies needed for compiling ..
Code: Select all
root# git --version
git version 1.9.1
These are not symlinks:mavrothal wrote: I just repeated your commands and show no issues.
What is the filesystem that your local woof-CE folder resides on?
BTW are these 2 affected files showing as symlinks in your repo?
Code: Select all
root# ls
howl woof-CE
root# cd woof-CE
root# ls -la woof-code/rootfs-skeleton/etc/wvdial_options/APN-VirginBroadband
-rwxr-xr-x 1 root root 5 Apr 20 15:44 woof-code/rootfs-skeleton/etc/wvdial_options/APN-VirginBroadband
root# ls -la woof-code/rootfs-skeleton/usr/local/lib/X11/mini-icons/mini-Desktop.xpm
-rwxr-xr-x 1 root root 637 Apr 20 15:44 woof-code/rootfs-skeleton/usr/local/lib/X11/mini-icons/mini-Desktop.xpm
vfat does not support symlinks (and many other things).keyboard wrote: I have vfat file system formatted with puppy linux installer (from CD).
mavrothal wrote: vfat does not support symlinks (and many other things).
Actually I'm surprised that you have only these problems (or maybe you have more ).
Clone the repos in an ext2,3,4 file system or your savefile if it is big enough and see how this goes.
Code: Select all
root# cd my-applications
root# ls
bin lib test test2
root# git clone https://github.com/keyboard-k/howl.git
Cloning into 'howl'...
remote: Counting objects: 20140, done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 20140 (delta 7), reused 0 (delta 0), pack-reused 20117
Receiving objects: 100% (20140/20140), 25.92 MiB | 772.00 KiB/s, done.
Resolving deltas: 100% (11237/11237), done.
Checking connectivity... done.
Checking out files: 100% (5833/5833), done.
root# ls
bin howl lib test test2
root# cd howl
root# git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Code: Select all
root# cd git
root# git clone https://github.com/keyboard-k/howl.git
Cloning into 'howl'...
remote: Counting objects: 20140, done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 20140 (delta 7), reused 0 (delta 0), pack-reused 20117
Receiving objects: 100% (20140/20140), 25.92 MiB | 374.00 KiB/s, done.
Resolving deltas: 100% (11237/11237), done.
Checking connectivity... done.
Checking out files: 100% (5833/5833), done.
root# ls
howl
root# cd howl
root# git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working directory)
modified: woof-code/rootfs-skeleton/etc/wvdial_options/APN-VirginBroadband
modified: woof-code/rootfs-skeleton/usr/local/lib/X11/mini-icons/mini-Desktop.xpm
no changes added to commit (use "git add" and/or "git commit -a")
my savefile is not so big , while running script for patches it gets full.Will this work instead of a save file ??mavrothal wrote: Clone the repos in an ext2,3,4 file system or your savefile if it is big enough and see how this goes.
Code: Select all
root# pwd
/mnt/home/git
root# ls
pixie-online
root# dd if=../../../../dev/zero of=howling.4fs bs=1M count=50
50+0 records in
50+0 records out
52428800 bytes (52 MB) copied, 0.256032 s, 205 MB/s
Code: Select all
root# mkfs -t ext4 howling.4fs
mke2fs 1.42.9 (4-Feb-2014)
howling.4fs is not a block special device.
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
12824 inodes, 51200 blocks
2560 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=52428800
7 block groups
8192 blocks per group, 8192 fragments per group
1832 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Under the "Utility" menu there is a "Resize personal storage file" appkeyboard wrote: my savefile is not so big , while running script for patches it gets full.Will this work instead of a save file ??
mavrothal wrote: Under the "Utility" menu there is a "Resize personal storage file" app
Yes, My save file is already too big... So I was making different partition for all the docs/reposmavrothal wrote: Resizing your savefile would be simpler though. Just keep in mind that VFAT can support up to 4GB (save)files
Thanks for the advice , I will do it.mavrothal wrote: You file generation looks OK.
To mount ii make a folder somewhere, in /mnt for example and just mount it.
If you want to auto load it, either add a line in your /etc/fstab file or in /etc/rc.d/rc.local or make a little script and place it in /root/Startup.
If you really want to work on linux I would recommend a linux partition on a hard drive. If not and have a USB-3 machine, get an 8-32GB USB-3 stick, reformat it with ext4 without journal running "mkfs.ext4 -O ^has_journal" (do not repartition it) and the use a "savefolder" that has no size limitations. You can do that with USB-2 but is considerably slower.keyboard wrote:My save file is already too big... So I was making different partition for all the docs/repos
mavrothal wrote:Under the "Utility" menu there is a "Resize personal storage file" appkeyboard wrote: my savefile is not so big , while running script for patches it gets full.Will this work instead of a save file ??
You file generation looks OK.
To mount ii make a folder somewhere, in /mnt for example and just mount it.
If you want to auto load it, either add a line in your /etc/fstab file or in /etc/rc.d/rc.local or make a little script and place it in /root/Startup.
Resizing your savefile would be simpler though. Just keep in mind that VFAT can support up to 4GB (save)files
keyboard wrote:mavrothal wrote: Under the "Utility" menu there is a "Resize personal storage file" appYes, My save file is already too big... So I was making different partition for all the docs/reposmavrothal wrote: Resizing your savefile would be simpler though. Just keep in mind that VFAT can support up to 4GB (save)files
Thanks for the advice , I will do it.mavrothal wrote: You file generation looks OK.
To mount ii make a folder somewhere, in /mnt for example and just mount it.
If you want to auto load it, either add a line in your /etc/fstab file or in /etc/rc.d/rc.local or make a little script and place it in /root/Startup.
I might do that, you see, on one hand my save file is not so big to accomodate all the docs and repos, on the other hand it is really big nearly close to 4GB which is it's limitation. I have a empty harddisk with a old ntfs partition, but, my system has overheating problems, I have changed the thermal paste, and also cut off it's DWM wire so the fan runs at full speed. Even then it is overheating , (around 90 deg c). I know that puppy linux is always great rescue when stuck in these kind situations when you want to make some old harware work again. So I am using puppy linux on this system. I might reformat the hardisk on ext partition, but it really depends. whether it will crash from overheating while reformat or not (currently it stores some of my files). Also I have tested some formats/installation of puppy linux on very old desktops and bios it doesn't works on all (tried chameleon and FDD format as well) so I have to check into all those before I move all my developements to linux (puppy linux)mavrothal wrote:If you really want to work on linux I would recommend a linux partition on a hard drive. If not and have a USB-3 machine, get an 8-32GB USB-3 stick, reformat it with ext4 without journal running "mkfs.ext4 -O ^has_journal" (do not repartition it) and the use a "savefolder" that has no size limitations. You can do that with USB-2 but is considerably slower.keyboard wrote:My save file is already too big... So I was making different partition for all the docs/repos
I think that a) you change the specs file to the pet version that you want to use and b) put it in your local pets folder.peebee wrote:If I want to have a local directory with some updated pets which I want Woof-CE to use instead of the pets in the online repositories ..... how do I configure Woof-CE to do this?
Hi mavrothalmavrothal wrote:I think that a) you change the specs file to the pet version that you want to use and b) put it in your local pets folder.peebee wrote:If I want to have a local directory with some updated pets which I want Woof-CE to use instead of the pets in the online repositories ..... how do I configure Woof-CE to do this?
Right. So you change the version of the pet there.peebee wrote: The specs file (DISTRO_PKGS_SPECS) only contains the generic name of the package - the pet file that then provides the package is found dynamically by various searches in the Packages-puppy-*-official database files.
toseamonkey-2.19-i486-precise|seamonkey|2.19-i486-precise||Internet;browser|75244K||seamonkey-2.19-i486-precise.pet|...
(or whatever the specs file in the pet says)seamonkey-2.21-i486-precise|seamonkey|2.21-i486-precise||Internet;browser|75244K||seamonkey-2.21-i486-precise.pet|...