Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 18 Nov 2019, 03:29
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
DebianDog - Wheezy
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 46 of 99 [1481 Posts]   Goto page: Previous 1, 2, 3, ..., 44, 45, 46, 47, 48, ..., 97, 98, 99 Next
Author Message
fredx181


Joined: 11 Dec 2013
Posts: 4159
Location: holland

PostPosted: Wed 25 Feb 2015, 05:28    Post subject:  

Hi Toni,
Quote:
To tell you the truth I like the old libsearch better. It gives simple packagename output and I can easy copy/paste it from terminal inside control file. This found and not-found output and path just makes things complicated for me. It is useful if you like to know what packages are not installed on the system at the moment but this is not what I use libsearch for.


Yes, I see what you mean, attached libsearch without the 'found' and 'not found' output but still gives complete list of dependencies.
Let me try to convince you that the new libsearch is much better: Smile
When I tried to use old libsearch for finding depends for the mpv binary it gave me a incomplete list, only what's installed,but even more important is to find the 'not installed' dependencies.

List of dependencies for mpv using old libsearch (=incomplete list):
Code:
libc6: /lib/i386-linux-gnu/libpthread.so.0
libdvdread4: /usr/lib/i386-linux-gnu/libdvdread.so.4
libxv1: /usr/lib/i386-linux-gnu/libXv.so.1
libxext6: /usr/lib/i386-linux-gnu/libXext.so.6
libxcb1: /usr/lib/i386-linux-gnu/libxcb.so.1
libx11-6: /usr/lib/i386-linux-gnu/libX11.so.6
libasound2: /usr/lib/i386-linux-gnu/libasound.so.2
liboss4-salsa-asound2: /usr/lib/i386-linux-gnu/libasound.so.2
libgcrypt11: /lib/i386-linux-gnu/libgcrypt.so.11
libmp3lame0: /usr/lib/i386-linux-gnu/libmp3lame.so.0
libgnutls26: /usr/lib/i386-linux-gnu/libgnutls.so.26
zlib1g: /lib/i386-linux-gnu/libz.so.1
libc6: /lib/i386-linux-gnu/librt.so.1
libc6: /lib/i386-linux-gnu/libm.so.6
libjpeg8: /usr/lib/i386-linux-gnu/libjpeg.so.8
libxinerama1: /usr/lib/i386-linux-gnu/libXinerama.so.1
libc6: /lib/i386-linux-gnu/libdl.so.2
libxrandr2: /usr/lib/i386-linux-gnu/libXrandr.so.2
libxss1: /usr/lib/i386-linux-gnu/libXss.so.1
liblua5.1-0: /usr/lib/i386-linux-gnu/liblua5.1.so.0
libgl1-mesa-glx: /usr/lib/i386-linux-gnu/libGL.so.1
libgl1-mesa-swx11: /usr/lib/i386-linux-gnu/libGL.so.1
libfontconfig1: /usr/lib/i386-linux-gnu/libfontconfig.so.1
libfribidi0: /usr/lib/i386-linux-gnu/libfribidi.so.0
libfreetype6: /usr/lib/i386-linux-gnu/libfreetype.so.6
libc6: /lib/i386-linux-gnu/libc.so.6

List of dependencies for mpv using new libsearch (=complete list):
Code:
libva-glx1: /usr/lib/i386-linux-gnu/libva-glx.so.1
libva1: /usr/lib/i386-linux-gnu/libva.so.1
libdvdnav4: /usr/lib/i386-linux-gnu/libdvdnav.so.4
libc6: /lib/i386-linux-gnu/libpthread.so.0
libguess1: /usr/lib/i386-linux-gnu/libguess.so.1
libdvdread4: /usr/lib/i386-linux-gnu/libdvdread.so.4
libv4l-0: /usr/lib/i386-linux-gnu/libv4l2.so.0
libpulse0: /usr/lib/i386-linux-gnu/libpulse.so.0
libroar-compat2: /usr/lib/roaraudio/complibs/libpulse.so.0
libbs2b0: /usr/lib/libbs2b.so.0
libxv1: /usr/lib/i386-linux-gnu/libXv.so.1
libxext6: /usr/lib/i386-linux-gnu/libXext.so.6
libxcb1: /usr/lib/i386-linux-gnu/libxcb.so.1
libx11-6: /usr/lib/i386-linux-gnu/libX11.so.6
libjack-jackd2-0: /usr/lib/i386-linux-gnu/libjack.so.0
libjack0: /usr/lib/i386-linux-gnu/libjack.so.0
libasound2: /usr/lib/i386-linux-gnu/libasound.so.2
liboss4-salsa-asound2: /usr/lib/i386-linux-gnu/libasound.so.2
libgcrypt11: /lib/i386-linux-gnu/libgcrypt.so.11
libx264-132: /usr/lib/i386-linux-gnu/libx264.so.132
libmp3lame0: /usr/lib/i386-linux-gnu/libmp3lame.so.0
libgnutls26: /usr/lib/i386-linux-gnu/libgnutls.so.26
zlib1g: /lib/i386-linux-gnu/libz.so.1
libc6: /lib/i386-linux-gnu/librt.so.1
libc6: /lib/i386-linux-gnu/libm.so.6
libenca0: /usr/lib/libenca.so.0
libcdio-paranoia1: /usr/lib/libcdio_paranoia.so.1
libcdio-cdda1: /usr/lib/libcdio_cdda.so.1
libcdio13: /usr/lib/libcdio.so.13
libmpg123-0: /usr/lib/i386-linux-gnu/libmpg123.so.0
liblircclient0: /usr/lib/liblirc_client.so.0
libva-x11-1: /usr/lib/i386-linux-gnu/libva-x11.so.1
libjpeg8: /usr/lib/i386-linux-gnu/libjpeg.so.8
libxinerama1: /usr/lib/i386-linux-gnu/libXinerama.so.1
libc6: /lib/i386-linux-gnu/libdl.so.2
libxrandr2: /usr/lib/i386-linux-gnu/libXrandr.so.2
libcaca0: /usr/lib/i386-linux-gnu/libcaca.so.0
libxss1: /usr/lib/i386-linux-gnu/libXss.so.1
libvdpau1: /usr/lib/i386-linux-gnu/libvdpau.so.1
liblua5.1-0: /usr/lib/i386-linux-gnu/liblua5.1.so.0
libgl1-mesa-glx: /usr/lib/i386-linux-gnu/libGL.so.1
libgl1-mesa-swx11: /usr/lib/i386-linux-gnu/libGL.so.1
libfontconfig1: /usr/lib/i386-linux-gnu/libfontconfig.so.1
libfribidi0: /usr/lib/i386-linux-gnu/libfribidi.so.0
libfreetype6: /usr/lib/i386-linux-gnu/libfreetype.so.6
libc6: /lib/i386-linux-gnu/libc.so.6


Quote:
What is the way to replace mpv player both versions? Do they conflict each other and can we add the debs in DD repository without changes?

The mpv_0.8.0dd_i386.deb is higher version, I think, so will replace the other (if installed).
Should work the same way as we have 2 versions of gsu.
I don't think they need any changes, there's no menu file in /usr/share/menu but that's not needed as it's not supposed to show in the Menu.

Quote:
I would try from DD-Jessie (always freshs - no persistent):
Code:
apt-get purge cryptsetup #we don't need it in initrd1.img
apt-get autoremove
apt-get purge live-boot live-boot-initramfs-tools live-tools

Then install:
https://packages.debian.org/squeeze/live-boot
https://packages.debian.org/squeeze/live-boot-initramfs-tools


Ok thanks, I need to refresh my memory about what I did back then.

Edit: I might be a bit stubborn Smile , attached also libsearch-mod with again the 'found' and 'not found' output but different displaying (and hopefully less confusing) as it was before.
For me the 'found' or 'not found' displaying could be helpful in some situations.
Looks like this now:
Code:
found:
libdvdread4: /usr/lib/i386-linux-gnu/libdvdread.so.4
---------------------------------
found:
libc6: /lib/i386-linux-gnu/libpthread.so.0
---------------------------------
not found:
libguess1: /usr/lib/i386-linux-gnu/libguess.so.1
---------------------------------


Edit2:Re-uploaded libsearch-mod, it's more advanced and creates sorted out list <binary>-deplist with -for example- this contents (from mpv binary):

Code:
Note; there may be conflicting packages with each other in below lists.
You may need to check mpv-liblist for duplicate libs, choose only one of them and remove the other from the below list.
For example, a double entry from <binary>-liblist:
found:
libgl1-mesa-glx: /usr/lib/i386-linux-gnu/libGL.so.1
libgl1-mesa-swx11: /usr/lib/i386-linux-gnu/libGL.so.1
---
Suppose you choose package 'libgl1-mesa-glx', then remove 'the other(s)', e.g. 'libgl1-mesa-swx11' from the below lists.
Not in all, but in most cases this should be the way.

For Depends: line in control file:
libasound2, libbs2b0, libc6, libcaca0, libcdio-cdda1, libcdio-paranoia1, libcdio13, libdvdnav4, libdvdread4, libenca0, libfontconfig1, libfreetype6, libfribidi0, libgcrypt11, libgl1-mesa-glx, libgl1-mesa-swx11, libgnutls26, libguess1, libjack-jackd2-0, libjack0, libjpeg8, liblircclient0, liblua5.1-0, libmp3lame0, libmpg123-0, liboss4-salsa-asound2, libpulse0, libroar-compat2, libv4l-0, libva-glx1, libva-x11-1, libva1, libvdpau1, libx11-6, libx264-132, libxcb1, libxext6, libxinerama1, libxrandr2, libxss1, libxv1, zlib1g,

For installing with apt-get (lists mostly NOT already installed packages):
libbs2b0 libcaca0 libcdio-cdda1 libcdio-paranoia1 libcdio13 libdvdnav4 libenca0 libguess1 libjack-jackd2-0 libjack0 liblircclient0 libmpg123-0 libpulse0 libroar-compat2 libv4l-0 libva-glx1 libva-x11-1 libva1 libvdpau1 libx264-132

For installing with apt-get (all dependencies):
libasound2 libbs2b0 libc6 libcaca0 libcdio-cdda1 libcdio-paranoia1 libcdio13 libdvdnav4 libdvdread4 libenca0 libfontconfig1 libfreetype6 libfribidi0 libgcrypt11 libgl1-mesa-glx libgl1-mesa-swx11 libgnutls26 libguess1 libjack-jackd2-0 libjack0 libjpeg8 liblircclient0 liblua5.1-0 libmp3lame0 libmpg123-0 liboss4-salsa-asound2 libpulse0 libroar-compat2 libv4l-0 libva-glx1 libva-x11-1 libva1 libvdpau1 libx11-6 libx264-132 libxcb1 libxext6 libxinerama1 libxrandr2 libxss1 libxv1 zlib1g


Fred
libsearch-mod.tar.gz
Description  libsearch with displaying 'found' and 'not found' output but in a different manner and creating sorted out list in <binaryname>-deplist
gz

 Download 
Filename  libsearch-mod.tar.gz 
Filesize  1.34 KB 
Downloaded  157 Time(s) 
libsearch.tar.gz
Description  New libsearch without 'found' and 'not found' output.
gz

 Download 
Filename  libsearch.tar.gz 
Filesize  788 Bytes 
Downloaded  158 Time(s) 

Last edited by fredx181 on Thu 26 Feb 2015, 13:53; edited 2 times in total
Back to top
View user's profile Send private message 
limelime

Joined: 18 Feb 2015
Posts: 16

PostPosted: Wed 25 Feb 2015, 14:48    Post subject: How persistence works?  

Hi guys,

How persistence works? When do changes are committed from RAM to the persistence partition?
I boot in DebianDog live-boot v3 in RAM live persistence of DebianDog-Wheezy-openbox_xfce.iso. I'm using 1Gb-persistence-or-live-rw.zip as described in this post.

thx!
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4159
Location: holland

PostPosted: Wed 25 Feb 2015, 15:16    Post subject:  

Hi limelime,
Quote:

How persistence works? When do changes are committed from RAM to the persistence partition?
I boot in DebianDog live-boot v3 in RAM live persistence of DebianDog-Wheezy-openbox_xfce.iso. I'm using 1Gb-persistence-or-live-rw.zip as described in this post.


You do have 'persistence' parameter on the kernel line?
You say 'persistence partition', is it a partition labeled 'persistence' or you have a save file named 'persistence'.
Please post some more information including the entry you use for grub, grub4dos or syslinux.

Edit: Sorry, looking at "DebianDog live-boot v3 in RAM live persistence" as you wrote above, I think you boot from cd.
Having a 'persistence' file on any partition (except for NTFS formatted) should work.

Fred
Back to top
View user's profile Send private message 
limelime

Joined: 18 Feb 2015
Posts: 16

PostPosted: Wed 25 Feb 2015, 15:53    Post subject:  

Hi Fred,

fredx181 wrote:


You do have 'persistence' parameter on the kernel line?
You say 'persistence partition', is it a partition labeled 'persistence' or you have a save file named 'persistence'.
Please post some more information including the entry you use for grub, grub4dos or syslinux.


The boot entry from isolinux/live.cfg is
Code:

label DebianDog live-boot v3 in RAM live persistence
kernel /live/vmlinuz1
append initrd=/live/initrd.img boot=live persistence config noeject quickreboot autologin toram=01-filesystem.squashfs


I have a partition(/dev/sda1) that contains a file called persistence(from 1Gb-persistence-or-live-rw.zip). If you mount that file, you will see persistence.conf and other files and directories. In persistence.conf, it contains
Code:
/ union
.

I made some changes in the /root and then reboot. The changes still there. Great! But how persistence works? When do changes are committed from RAM to the persistence file?

thx!
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4159
Location: holland

PostPosted: Wed 25 Feb 2015, 16:21    Post subject:  

Hi limelime,
Quote:
I made some changes in the /root and then reboot. The changes still there. Great! But how persistence works? When do changes are committed from RAM to the persistence file?


Ah, now I see what your real question is, I thought you couldn't make persistence to work.
Well.. I don't feel like I'm the one to explain this technical matter, maybe someone else can or probably a google search could give explanation.
I think that the changes are directly written to the savefile in case of live-boot v3 (but with porteus-boot there's an option to save changes on shutdown only. )

Edit: Maybe here's some useful info for you:
http://en.wikipedia.org/wiki/Copy-on-write

Fred
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Wed 25 Feb 2015, 17:15    Post subject: Re: How persistence works?  

Hi, limelime.

I find this information about Copy on Write easy understandable:
http://hackerboss.com/copy-on-write-101-part-1-what-is-it/
I agree with Fred copy of the changes is made inside the save file at the moment you make them. Instead / union you can save changes only in some folders by typing the folder paths inside persistence.conf More information is available here:
http://live-systems.org/manpages/stable/en/html/persistence.conf.5.html
If you like to save (or not to save) changes only on exit you need to use porteus-boot. Live-boot does not provide such option.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Wed 25 Feb 2015, 17:19    Post subject:  

fredx181 wrote:
Edit: I might be a bit stubborn Smile , attached also libsearch-mod with again the 'found' and 'not found' output but different displaying (and hopefully less confusing) as it was before.

Thanks, Fred!
I will rebuild the module with both new libsearch versions from your post in the next days.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Thu 26 Feb 2015, 05:34    Post subject:  

Hi, Fred.
Just for information new remaster scripts uploaded here till we have deb package:
http://smokey01.com/saintless/DebianDog/Packages/Fixes/
Repository updated with flashplayerchoice (moved in included) and mpv (in extra packages section).
09-apt-file-debdir-aptitude.squashfs rebuilded with updated apt-file database and new libsearch and libsearch-mod:
http://smokey01.com/saintless/DebianDog/System-modules/

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 4159
Location: holland

PostPosted: Thu 26 Feb 2015, 07:45    Post subject:  

Toni wrote:
Just for information new remaster scripts uploaded here till we have deb package:
http://smokey01.com/saintless/DebianDog/Packages/Fixes/
Repository updated with flashplayerchoice (moved in included) and mpv (in extra packages section).

Thanks!, Toni.

Quote:
09-apt-file-debdir-aptitude.squashfs rebuilded with updated apt-file database and new libsearch and libsearch-mod:

Aarg, to late!
I made much more advanced libsearch-mod, you may like it and it's 'not-advanced user' friendly now.
See my Edit2 here:
http://murga-linux.com/puppy/viewtopic.php?p=830458#830458

Edit: The "here" 'fixes' link gives error 404
http://smokey01.com/saintless/DebianDog/Packages/Fixes/Fixes-after-02.02.2015.txt
Probably should be this:
http://www.smokey01.com/saintless/DebianDog/Packages/Fixes/Fixes-after-02.02.2014.txt

Btw, is it an idea maybe to make notice of new added/upgraded packages (like mpv or gsu also maybe) on the "New packages, updated packages and fixes:" page?

Fred
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Thu 26 Feb 2015, 17:13    Post subject:  

Hi, Fred.

Quote:
I made much more advanced libsearch-mod, you may like it and it's 'not-advanced user' friendly now.
See my Edit2 here:
http://murga-linux.com/puppy/viewtopic.php?p=830458#830458

No problem, I will rebuild the module in the next days.

Quote:
Edit: The "here" 'fixes' link gives error 404
http://smokey01.com/saintless/DebianDog/Packages/Fixes/Fixes-after-02.02.2015.txt
Probably should be this:
http://www.smokey01.com/saintless/DebianDog/Packages/Fixes/Fixes-after-02.02.2014.txt

Thanks, It should be fixed now.

Quote:
Btw, is it an idea maybe to make notice of new added/upgraded packages (like mpv or gsu also maybe) on the "New packages, updated packages and fixes:" page?

I'm not sure how to do it best yet. For the moment we have links:
Quote:
DebianDog package repository - all packages here are available for installing/reinstalling with apt-get or Synaptic.
Extra packages for DebianDog (not included).
Packages not included in DebianDog repository - the reason not to include them in repository is these packages work fine for DebianDog but could create some problems in standard Debian.

Editing the post all the time for every new or updated package doesn't sound as a good idea to me. And most packages will need adding information like what is the difference for mpv versions. I started already similar post for DD packages here but it is difficult to keep it updated. One small mistake while editing and the tags get broken. Takes time to fix them again and again.
http://www.murga-linux.com/puppy/viewtopic.php?p=771573#771573
And I don't want the fixes post to be so long. If we start adding all not included packages from Extra section it will become very long in time.
Isn't it the link to extra packages enough?
Gsu updated deb is not important for Wheezy but for jessie as far as I understand. It will be upgraded anyway with apt-get dist-upgrade.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
limelime

Joined: 18 Feb 2015
Posts: 16

PostPosted: Thu 26 Feb 2015, 18:38    Post subject: RemasterDog doesn't preserve /etc/fstab  

Hi Fred,

RemasterDog application doesn't preserve changes in /etc/fstab. I think it should.
Back to top
View user's profile Send private message 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Fri 27 Feb 2015, 01:15    Post subject:  

Hi, limelime.
/etc/fstab is not excluded in RemasterDog. The changes should be there.
After remastering I have this in /etc/fstab and I clean it manually:
Code:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

In Wheezy /etc/fstab is generated on boot from the files inside /etc/fstab.d. It was different in older Debian.
In my opinion /etc/fstab should be empty after remastering and generated from the system. Otherswise on different hardware you will have not existing partitions and mount points from different HDD.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
saintless


Joined: 11 Jun 2011
Posts: 3882
Location: Bulgaria

PostPosted: Fri 27 Feb 2015, 05:14    Post subject:  

Hi, Fred.

09-apt-file-debdir-aptitude.squashfs reuploaded with libsearch, libsearch-mod and libsearch-mod-old in /usr/local/bin

About updated and new packages we can move updated in different section (Updated for example) and keep only links in fixes post to Updated and Extra packages.
Then inside control file we can add all the information about the deb as Description lines - what is changed from previous version, what is the difference for mpv versions... We save double work explaining this in separate post for each package.
We have Xfe installed in both DD versions. Then we can add information in fixes post to open the deb from Extra and Updated with xfp (x-file-pack). I think this is the default Right click View action for Xfe anyway.
Test deb view with xfp and tell me what you think or if you have different suggestion.

Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send private message MSN Messenger 
fredx181


Joined: 11 Dec 2013
Posts: 4159
Location: holland

PostPosted: Fri 27 Feb 2015, 15:26    Post subject:  

Hi Toni,

Quote:
09-apt-file-debdir-aptitude.squashfs reuploaded with libsearch, libsearch-mod and libsearch-mod-old in /usr/local/bin

Thanks again.

Quote:
About updated and new packages we can move updated in different section (Updated for example) and keep only links in fixes post to Updated and Extra packages.
Then inside control file we can add all the information about the deb as Description lines - what is changed from previous version, what is the difference for mpv versions... We save double work explaining this in separate post for each package.
We have Xfe installed in both DD versions. Then we can add information in fixes post to open the deb from Extra and Updated with xfp (x-file-pack). I think this is the default Right click View action for Xfe anyway.
Test deb view with xfp and tell me what you think or if you have different suggestion.


Yes, it's ok for me, 'left-click' on Openbox version also opens xfp info view so it should be clear then from the information in fixes post.
Btw, I tested more the mpv two versions and for me they are the same (however it's almost impossible to test all options). They are both compiled from the same source. Maybe it's better to keep the smaller one only in repository.

Fred
Back to top
View user's profile Send private message 
limelime

Joined: 18 Feb 2015
Posts: 16

PostPosted: Fri 27 Feb 2015, 15:48    Post subject:  

saintless wrote:
Hi, limelime.
/etc/fstab is not excluded in RemasterDog. The changes should be there.
After remastering I have this in /etc/fstab and I clean it manually:
Code:
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

In Wheezy /etc/fstab is generated on boot from the files inside /etc/fstab.d. It was different in older Debian.
In my opinion /etc/fstab should be empty after remastering and generated from the system. Otherswise on different hardware you will have not existing partitions and mount points from different HDD.

Toni


Hi Toni,
Changes in /etc/fstab are not preserved after running RemasterDog. I tried this multiple times. I was booting in "DebianDog live-boot v3 live (no save)" of "DebianDog-Wheezy-openbox_xfce.iso".

I made changes in /etc/fstab.d/live and they are preserved after running RemasterDog but /etc/fstab is still empty. Therefore, my mount entry is not executed.
Code:

cat /etc/fstab.d/live
aufs / aufs rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
shared /vbox/shared vboxsf defaults 0 0


I plan to use DebianDog as a full blown operating system running from memory. RAM are cheap nowadays. I don't plan to move DebianDog from 1 computer to another.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 46 of 99 [1481 Posts]   Goto page: Previous 1, 2, 3, ..., 44, 45, 46, 47, 48, ..., 97, 98, 99 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0917s ][ Queries: 12 (0.0172s) ][ GZIP on ]