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 Tue 16 Oct 2018, 03:45
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Pet pinstall.sh script runs in frugal but not full install
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 3 [39 Posts]   Goto page: Previous 1, 2, 3 Next
Author Message
perdido


Joined: 09 Dec 2013
Posts: 986
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Tue 28 Aug 2018, 11:43    Post subject: Re: Adding my 2 Cents  

mikeslr wrote:
Hi All,

Like musher0, I only run frugal installs. Musher0, however, asked "Why do a full install of a distro that was designed for a frugal install?" I thought the only exception to the general recommendation to use Frugal installs to be if you had a RAM-challenged computer, e.g. 256 Mbs or less. But recently someone --perdido perhaps-- suggested that Full installs present a better environment for compiling. Knowing nothing about compiling I have no reason to doubt that. But I don't see how that relates to the current problem of Full installs not ever executing pinstall.sh.

I discovered the lack of documentation/explanations regarding pinstall.sh under another circumstance when they cease to function. If you convert a pet to an SFS, a pinstall.sh of the pet will be copied to the into the SFS but, as far I know, isn't executed when the SFS is loaded or ever.

When I discovered that, I thought perhaps it would be necessary to write some type of "run-once" script to be placed in /root/Startup: check to see if the commands in the script had already be executed, and if not execute them. Way beyond my scripting skills. Fortunately, I don't recall any converted-SFS that failed to function as expected. Which left me wondering under what circumstances are pinstall.shs actually necessary.

mikesLr


Hi mikeslr,

You present an interesting potential workaround using the /root/startup/ directory.
I have borrowed a script from shinobar that did something similar when installing the nvidia driver,
the script resides in /root/startup/ after the pet installs and runs on reboot. Here is the start of the script, the whole script is attached as nvidia.tar.gz so unzip to view.
Code:
#!/bin/sh
# watch and make the nvidia graphic driver ready
# 22jun2012 shinobar
# 23jun2012: fatdog64
# 25jun2012: lhp64
#10oct2012: vdpau
#3may2013: try to avoid the depmod bug found in Puppy 4.3.1
# 23may2012: fix disablenouveau (thanks to peebee)
# 24may2012: improve disablenouveau keeping compatibility with Barry's xorgwizard-cli, welcome message
# 25may2013: can be called from rc.nvidia
# 26may2013: never use nvidia-xconfig
# 4sep2013: [Meeki] Must check xconfig file with nvidia-xconfig -t (see line(s) 255-258 & 296-304)
# 6sep2013: [Meeki] added LH64 to the skip of msg to run xorg after reboot (see line 286)
# 6sep2013: [Meeki] -a changed to -o meeki (see line 280)
# 6sep2013: [Meeki] tons of edits (see line 284 to 290)

# avoid multiple run
PSRESULT=$(ps)
N=$(echo "$PSRESULT"| grep -w "$0"| grep -w 'sh'| wc -l)
if [ $N -gt 1 ] ; then
  echo "$0 seems already running."
  exit 0
fi




.
nvidia.tar.gz
Description  This is an auto run script that resides in /root/startup/ after installing an nvidia pet from shinobar,
it runs automatically when the system is rebooted after the pet is installed and then removes itself
gz

 Download 
Filename  nvidia.tar.gz 
Filesize  4.61 KB 
Downloaded  13 Time(s) 

Last edited by perdido on Tue 28 Aug 2018, 12:09; edited 2 times in total
Back to top
View user's profile Send private message 
rockedge


Joined: 11 Apr 2012
Posts: 829
Location: Connecticut, United States

PostPosted: Tue 28 Aug 2018, 11:47    Post subject:  

I have not tried it on a full install.....which I will soon.
pinstall.sh
Code:
#!/bin/sh
DATABASE_PASS="admin"
chown -R webuser /var/run/mysqld
chown -R webuser /var/cache/zoneminder
/usr/bin/mysql_install_db
sleep 7
mysqld &
sleep 7
mysqladmin -u root password "$DATABASE_PASS"
mysql -u root -p"$DATABASE_PASS" -e "UPDATE mysql.user SET Password=PASSWORD('$DATABASE_PASS') WHERE User='root'"
mysql -u root -p"$DATABASE_PASS" -e "DELETE FROM mysql.user WHERE User='root' AND Host NOT IN ('localhost', '127.0.0.1', '::1')"
mysql -u root -p"$DATABASE_PASS" -e "DELETE FROM mysql.user WHERE User=''"
mysql -u root -p"$DATABASE_PASS" -e "DELETE FROM mysql.db WHERE Db='test' OR Db='test\_%'"
mysql -u root -p"$DATABASE_PASS" -e "FLUSH PRIVILEGES"

mysql -u root -p"$DATABASE_PASS" -e "CREATE USER 'pma'@'localhost' IDENTIFIED BY 'admin';"
mysql -u root -p"$DATABASE_PASS" -e "GRANT ALL PRIVILEGES ON * . * TO 'pma'@'localhost'"

mysql -u root -p"$DATABASE_PASS" -e "CREATE USER 'zmuser'@'localhost' IDENTIFIED BY 'zmpass';"
mysql -u root -p"$DATABASE_PASS" -e "GRANT ALL PRIVILEGES ON * . * TO 'zmuser'@'localhost'"

mysql -u root -p"$DATABASE_PASS" < /usr/share/phpmyadmin/sql/create_tables.sql
sleep 2
mysql -u root -p"$DATABASE_PASS" < /usr/share/zoneminder/db/zm_create.sql
ln -s /etc/init.d/zoneminder /root/my-applications/bin
hiawatha
zoneminder start
Back to top
View user's profile Send private message Visit poster's website 
bigpup


Joined: 11 Oct 2009
Posts: 11124
Location: Charleston S.C. USA

PostPosted: Tue 28 Aug 2018, 21:36    Post subject:  

perdido wrote:
bigpup wrote:
Maybe the question should be what exactly is in the pinstall.sh?

Post the contents.
Could be something in it that is trying to do something wrong for a full install Puppy.


Sure, here is one version per instructions from BK
Code:
#!/bin/sh
mv ./usr/share/applications/icon_switcher.desktop ./usr/share/applications/icon_switcher.desktop.bak
mv ./usr/share/applications/icon_switcher.desktop.new ./usr/share/applications/icon_switcher.desktop
mv ./usr/share/applications/Desktop-drive-icons.desktop ./usr/share/applications/Desktop-drive-icons.desktop.bak
mv ./usr/share/applications/Desktop-drive-icons.desktop.new ./usr/share/applications/Desktop-drive-icons.desktop
mv ./usr/share/applications/pdesktop.desktop ./usr/share/applications/pdesktop.desktop.bak
mv ./usr/share/applications/ptheme.desktop ./usr/share/applications/ptheme.desktop.bak


The pet installs a couple desktop files with the extension "new"
The script changes the existing similarily named desktop files to the extension ".bak" and
replaces them with the desktop files with the "new" extension by removing the .new using "mv" to change the names.

I wonder if trying to replace core Puppy program .desktop files could be the problem. Idea
icon_switcher.desktop
Desktop-drive-icons.desktop
Both of these are used by several other Puppy programs.
Why are you replacing them?

These two are not in example: Puppy Xenialpup 7.5
ptheme.desktop
pdesktop.desktop
Are you adding them with the pet install?

This is what works to change the name:
mv /usr/share/applications/icon_switcher.desktop /usr/share/applications/icon_switcher.desktop.bak

There is no ./usr/share/applications/ directory.

So that second set of commands for the pinstall.sh should work. Version without "the dot" in front of the absolute paths.

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
bigpup


Joined: 11 Oct 2009
Posts: 11124
Location: Charleston S.C. USA

PostPosted: Tue 28 Aug 2018, 21:51    Post subject:  

Another idea.

Is the pinstall.sh a shell script, so it is exec for permissions Idea

_________________
I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected Shocked
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 986
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Tue 28 Aug 2018, 22:28    Post subject:  

bigpup wrote:
Another idea.

Is the pinstall.sh a shell script, so it is exec for permissions Idea


Yes and it runs and installs in a frugal just fine.

On a full install it does not automagically execute but will run if I mouse click it and finish like it is supposed to.

I think petget is broken, maybe I should full install a bunch of pups and see if any of them will run a pinstall.sh

.
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Tue 28 Aug 2018, 23:09    Post subject:  

Hi Perdido.

Going back to your screen cap on page 1, and please correct me if I'm
wrong, I notice that you are trying to create an sfs archive from a pinstall.sh
script in a fully installed Puppy.

Yoo-hoo!!!
Conceptually, that's an extreme sport of sorts for a Puppy distro !!! Laughing
Let me explain:

One thing is certain: using sfs's in a full install is iffy. -- If you have a full
install, you go all the way, you install the apps whether through a pet or a
deb or rpm archive and that is it. You try not to use sfs's.

Here's why:
sfs's are meant to be used in frugal installs. IIRC, fully installed Pups do NOT
have the "au" layer-unifying whachamacallit utility, whereas frugally
installed Pups depend on it, it's vital for frugal installs.

Sorry for the "mouse" imagery Wink, but the "au" layer-unifying
whachamacallit utility manages the "gruyere cheese holes" the sfs's fit into.

In a full install, there are no "gruyere cheese holes to fit sfs's into" and no
layers; all programs and libs, etc., are on the same level. So the "au" layer-
unifying whachamacallit utility either is not there or has no" gruyere cheese
layers" to manage.

Look at the PUPSTATE # for a full install and look at BarryK's diagram for it,
it's pretty clear, I think.

~~~~~

2nd point, IMO -- and as I said, I have never done a full install of Puppy.
You may be asking too much of the Puppy system: install a BBIIGG pet
archive AND then immediately afterwards start a squashfs compression?

If you run htop or a similar diagnostics app, and then start the mksquashfs
compression app, you'll see that mksquashfs grabs almost all the computer's
resources for the job it's doing.

I'm not sure if you and rockedge are talking about the same pet file, but if
that pet file is 252 Mg, as rockedge mentions, I would suggest you do one
operation and give the Pup a "bone break" Smile (You can have coffee or tea or
a pop or a beer!) And then, when the Pup is rested, ask it to do the
squashing operation.

But again, AFAIK, sfs's do not play well in full installs. So in the context of
a full install, maybe creating an sfs is not the way to go. Why not provide
another pet, simply?

My 2 ¢, but IHTH.

_________________
musher0
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 986
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Tue 28 Aug 2018, 23:17    Post subject:  

bigpup wrote:

I wonder if trying to replace core Puppy program .desktop files could be the problem. Idea
icon_switcher.desktop
Desktop-drive-icons.desktop
Both of these are used by several other Puppy programs.
Why are you replacing them?

They are exact copies of the desktop files they are replacing except they
have NoDisplay-True so they don't get put in the menu.
-------------
Quote:
These two are not in example: Puppy Xenialpup 7.5
ptheme.desktop
pdesktop.desktop
Are you adding them with the pet install?

They are programs in puppy that are called by the new "Puppy Desktop" GUI that radky has been working on, this is in bionic.
I disable the new "Puppy Desktop" from the menu using NoDisplay=True, then add the desktop files to put those two programs
in the jwm mwnu where they used to reside in earlier pups.
--------------
Quote:
This is what works to change the name:
mv /usr/share/applications/icon_switcher.desktop /usr/share/applications/icon_switcher.desktop.bak

Yes, that works in a script file. It also works in the pinstall.sh that runs ok in a frugal install. That is not the proper format for a pinstall.sh, however.
---------------
Quote:
There is no ./usr/share/applications/ directory.

That dot before the path is explicit in the instructions for pinstall.sh, for reference see this post earlier in the thread.
http://www.murga-linux.com/puppy/viewtopic.php?p=1003152&sid=11df74ca0f6f3c145ffb5ffe44fec8dd#1003152
Code:
It is important to know what the "current directory" is when execution enters the script. In the Unleashed environment,
directory "rootfs-complete" has the just-created complete Puppy filesystem, and rootfs-complete/ is the current directory when the script
 is entered.
However, when the package is downloaded and installed with PETget, the current directory is the top of the running Puppy filesystem, that is, "/".
That is why the script has a dot on front of "/usr/local/bin", so that it will work in both cases.

That "dot in front" is the only special thing that you need to remember when creating a "pinstall.sh" script.

----------------
Quote:
So that second set of commands for the pinstall.sh should work. Version without "the dot" in front of the absolute paths.

BK explains the reasoning for the .dot before the path in the paragraph above. It makes no difference in my pinstall.sh

I believe petget is to blame because it is handling the pet differently between a frugal install and a full install.

.
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 986
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Tue 28 Aug 2018, 23:27    Post subject:  

musher0 wrote:
Hi Perdido.

Going back to your screen cap on page 1, and please correct me if I'm
wrong, I notice that you are trying to create an sfs archive from a pinstall.sh
script in a fully installed Puppy.

Its just a miserly little 188k pet file, petget / ppm are doing all that extra sfs stuff you see. Thanks for looking at that!

rockedge is having the same problem with the pet he made.

We are having similar issues with different pets. The pinstall.sh runs and completes in a frugal install but not a full install.

I believe petget is at fault.

.
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Wed 29 Aug 2018, 02:04    Post subject:  

Well, perdido, believe what you will! Go ahead then, study bash and edit
petget until the cows come home! Wink

I brought to your attention 2 technical reasons why I think that you are
having this problem. Three actually, if one considers that Puppy is designed
for frugal, and that the full install of PuppyLinux was sort of an afterthought.
I also suggested three work-arounds.

What else can I say? Use another distro that offers only full install?

What's the obsession with "full install" anyway?

Best regards.

_________________
musher0
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 986
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Wed 29 Aug 2018, 03:23    Post subject:  

musher0 wrote:
Well, perdido, believe what you will! Go ahead then, study bash and edit
petget until the cows come home! Wink

I brought to your attention 2 technical reasons why I think that you are
having this problem. Three actually, if one considers that Puppy is designed
for frugal, and that the full install of PuppyLinux was sort of an afterthought.
I also suggested three work-arounds.

What else can I say? Use another distro that offers only full install?

What's the obsession with "full install" anyway?

Best regards.


The whole point of the post was to find out if there is a way to get the pinstall.sh working in a full install.
I'm not the only person thats noticed this problem. It being a problem because the pinstall.sh is supposed to run in a full install and it does not.

As it stands, the issue is no closer to being resolved than it was on day one of the topic.

Thanks for participating in this discussion.

I believe petget is broken regarding pinstall.sh in a full install.

.
Back to top
View user's profile Send private message 
musher0

Joined: 04 Jan 2009
Posts: 12792
Location: Gatineau (Qc), Canada

PostPosted: Wed 29 Aug 2018, 05:19    Post subject:  

Ditto.

Edit, 10 minutes later.
I just checked and pinstall.sh is not called by petget; you can check for
yourself by opening a console in /usr/local/petget and typing:
Code:
grep pinstall.sh petget
Easy enough, but nothing shows up.

It is called by script installpkg.sh in the same directory. You do a similar
grep call from console and this is what you get:
Code:
[/usr/local/petget]>grep pinstall.sh installpkg.sh
# 20aug10 shinobar: excute [sic] pinstall.sh under original LANG environment
 rm -f /pet.specs /pinstall.sh /puninstall.sh /install/doinst.sh
          #rm -f $DIRECTSAVEPATH/pet.specs $DIRECTSAVEPATH/pinstall.sh $DIRECTSAVEPATH/puninstall.sh $DIRECTSAVEPATH/install/doinst.sh
for i in pinstall.sh install/doinst.sh DEBIAN/postinst
 #120926 if a langpack installed, it will have /usr/share/applications.in (see /usr/sbin/momanager, /usr/share/doc/langpack-template/pinstall.sh).
As you can see, it is further modulated by the "langpack" and the original
LANGuage environment; also pinstall.sh is removed at some point.

So this raises a couple of questions that may give us a lead -- or not:
-- in what language environment have you been working?

-- if you tried installing your pet more than once, perhaps the pinstall.sh
file was erased, and the 2nd time, it could not be found? Can you recall if
this is a possibility? On the other hand, the original pinstall.sh is in the pet
archive, so it should be available every time.

Finally, on line 70 of installpkg.sh, there is a mention of PUPMODE
Code:
[ "$PUPMODE" = "2" ] && [ ! -d /audit ] && mkdir -p /audit
I could not find BarryK's original article, but according to this page by
shinobar, PUPMODE 2 is the full install mode. (It's in Japanese, but the
essentials are in English.) So your instinct may be partially right about
something being different for full install.

I wish I could help more, perdido, but I am not familiar enough with
shinobar's style of coding. Also, I tried to find where his
"$DIRECTSAVEPATH/" variable pointed to and couldn't. Finally, touching up
shinobar's code is sort of taboo in PuppyLand (IMO), because he is such an
excellent coder. I'll leave this in more capable hands, when they show up...

Sorry.

_________________
musher0
~~~~~~~~~~
Fidèle elle commença, ainsi elle restera. (Prov. canadien) /
Faithful she began, so will she stay. (Canadian prov.)
Back to top
View user's profile Send private message 
MochiMoppel


Joined: 26 Jan 2011
Posts: 1661
Location: Japan

PostPosted: Wed 29 Aug 2018, 08:37    Post subject:  

perdido wrote:
bigpup wrote:
Another idea.
Is the pinstall.sh a shell script, so it is exec for permissions Idea

Yes and it runs and installs in a frugal just fine.
On a full install it does not automagically execute but will run if I mouse click it and finish like it is supposed to.
.
I like "automagically". Laughing
What do you mean by "click it"? It shouldn't exist anymore. It is to be removed immediately after execution by installpks.sh.
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 986
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Wed 29 Aug 2018, 09:34    Post subject:  

MochiMoppel wrote:
perdido wrote:
bigpup wrote:
Another idea.
Is the pinstall.sh a shell script, so it is exec for permissions Idea

Yes and it runs and installs in a frugal just fine.
On a full install it does not automagically execute but will run if I mouse click it and finish like it is supposed to.
.
I like "automagically". Laughing
What do you mean by "click it"? It shouldn't exist anymore. It is to be removed immediately after execution by installpks.sh.


Hi MochiMoppel,

When using a pinstall.sh in a .pet
It executes and fully runs in a frugal install, there are no relics to click.
However in a full install puppy the pinstall.sh does not run and gets left in the puppy root / along with the puninstall.sh and pet.specs file

The discussion has been about why can't rockedge and I get our pinstall.sh to run in a fully installed puppy when it runs and works in a frugal installed puppy?

.
Back to top
View user's profile Send private message 
perdido


Joined: 09 Dec 2013
Posts: 986
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Wed 29 Aug 2018, 09:59    Post subject:  

musher0 wrote:
Ditto.

Edit, 10 minutes later.
I just checked and pinstall.sh is not called by petget; you can check for
yourself by opening a console in /usr/local/petget and typing:
Code:
grep pinstall.sh petget
Easy enough, but nothing shows up.

It is called by script installpkg.sh in the same directory. You do a similar
grep call from console and this is what you get:
Code:
[/usr/local/petget]>grep pinstall.sh installpkg.sh
# 20aug10 shinobar: excute [sic] pinstall.sh under original LANG environment
 rm -f /pet.specs /pinstall.sh /puninstall.sh /install/doinst.sh
          #rm -f $DIRECTSAVEPATH/pet.specs $DIRECTSAVEPATH/pinstall.sh $DIRECTSAVEPATH/puninstall.sh $DIRECTSAVEPATH/install/doinst.sh
for i in pinstall.sh install/doinst.sh DEBIAN/postinst
 #120926 if a langpack installed, it will have /usr/share/applications.in (see /usr/sbin/momanager, /usr/share/doc/langpack-template/pinstall.sh).
As you can see, it is further modulated by the "langpack" and the original
LANGuage environment; also pinstall.sh is removed at some point.

So this raises a couple of questions that may give us a lead -- or not:
-- in what language environment have you been working?

Been using english only, I am no longer fluent in anything else. Embarassed
40 years ago the usarmy qualified me as a linguist. Shocked
---------------------------
Quote:

-- if you tried installing your pet more than once, perhaps the pinstall.sh
file was erased, and the 2nd time, it could not be found? Can you recall if
this is a possibility? On the other hand, the original pinstall.sh is in the pet
archive, so it should be available every time.

I may have run it like that a few times just thinking the outcome may be different(definition of crazy comes to mind) Laughing But I have reinstalled
the full installed test vehicles more times than I can remember and started fresh with each variation of the pinstall.sh, with no different outcome.
-----------------------------
Quote:
Finally, on line 70 of installpkg.sh, there is a mention of PUPMODE
Code:
[ "$PUPMODE" = "2" ] && [ ! -d /audit ] && mkdir -p /audit
I could not find BarryK's original article, but according to this page by
shinobar, PUPMODE 2 is the full install mode. (It's in Japanese, but the
essentials are in English.) So your instinct may be partially right about
something being different for full install.

Barry's original article here via archive.org https://web.archive.org/web/20100519032633/http://www.puppylinux.com:80/development/howpuppyworks.html
I'm not sure it goes into enough detail to be helpful?
--------------------------------------

Quote:
I wish I could help more, perdido, but I am not familiar enough with
shinobar's style of coding. Also, I tried to find where his
"$DIRECTSAVEPATH/" variable pointed to and couldn't. Finally, touching up
shinobar's code is sort of taboo in PuppyLand (IMO), because he is such an
excellent coder. I'll leave this in more capable hands, when they show up...

Sorry.


Thanks for digging around and confirming the problem actually exists.
Perhaps it worked at one time and something was changed
and never got tried on the fully installed puppy since that is not as common as frugal installs.

.
Back to top
View user's profile Send private message 
MochiMoppel


Joined: 26 Jan 2011
Posts: 1661
Location: Japan

PostPosted: Wed 29 Aug 2018, 10:30    Post subject:  

perdido wrote:
The discussion has been about why can't rockedge and I get our pinstall.sh to run in a fully installed puppy when it runs and works in a frugal installed puppy?

Mystifies me also. I don't run any of the distros you mentioned and my environment is different, so I have no way to see the effect. Obviously installpkg.sh runs fine as it extracted the file to / and there is little in the way that could prevent it from executing the script. A short test on my system with a simulated full install showed no problems. My pinstall.sh worked fine.

If you like you can send me a PM. I'll try to walk you through the debugging process.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 3 [39 Posts]   Goto page: Previous 1, 2, 3 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
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.1311s ][ Queries: 12 (0.0381s) ][ GZIP on ]