awesome, gonna try this when I get in!Geoffrey wrote:The game Enemy territory is in the sfs downloads and it appears the id serverlist hasn't been accessible since January.
If you have downloaded the game then if you add the code below to the end of /etc/hosts then the game servers will show.Code: Select all
91.220.53.73 etmaster.idsoftware.com
Saluki
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Works for me thanks alot.Geoffrey wrote:The game Enemy territory is in the sfs downloads and it appears the id serverlist hasn't been accessible since January.
If you have downloaded the game then if you add the code below to the end of /etc/hosts then the game servers will show.Code: Select all
91.220.53.73 etmaster.idsoftware.com
I have added it to the repo.Tman wrote:The Firefox-11.0.pet from http://www.smokey01.com/Tman/apps/firefox/ is running well for me in Saluki for me so far. (works in Exprimo too, Pemasu..but I know you like to add your own version). This version feels a bit faster than previous Firefox versions
DaveS, thanks for the fontfix pet. It makes fonts in firefox much nicer.
-
I've split the Python3 packages and added it to the repo:jemimah wrote:Thanks. I'll check this out when I get back home tomorrow.antiloquax wrote:@Jemimah
Re-built pet that installs to /usr
Python 3.1.4
Regarding Scratch:
I've just booted into Saluki14 with pfix=ram.
It might be okay to ignore the libpulse message - I changed the plugins entry to ALSA in the shell-script.
I've remade the pet with the original name and it now uninstalls correctly.
It does seem to be working (cat meows when asked to!)
I'll try to get the libv4 thing working as soon as I can
Code: Select all
Python3-3.1.4-i486|Python3|3.1.4-i486||BuildingBlock|35640K||Python3-3.1.4-i486.pet||no description provided|puppy|wary5||
Python3_DEV-3.1.4-i486|Python3_DEV|3.1.4-i486||BuildingBlock|6148K||Python3_DEV-3.1.4-i486.pet||no description provided|puppy|wary5||
Python3-tk-3.1.4|Python3-tk|3.1.4||BuildingBlock|1752K||Python3-tk-3.1.4.pet|+Python3,+tk|no description provided|puppy|wary5||
pygame3-1.9.1|pygame3|1.9.1||BuildingBlock|5944K||pygame3-1.9.1.pet|+Python3,+SDL,+SDL_mixer,+SDL_sound,+SDL_ttf,+SDL_image|no description provided|puppy|wary5||
I've added these to the repo.pemasu wrote:Some things to play and have fun....
Composite editor which seems to be quite clear. Yeah...I know there is already one composite editor inbuild already.
It installs under System.
Couple of themes to test...
Url to the site where these stuff are from:
http://keithhedger.hostingsiteforfree.com/
Geoffrey.
Your new dmesg log shows that the firmware loading fails.
Okay. I did this in Saluki-014. I downloaded needed b43-firmware-cutter, compiled it, then I downloaded the correct source of firmwares and installed them. I created the pet of the result.
These 117 firmwares are basically the same as the included but they are prepared in Saluki-014.
I dont know if they make any difference, but we need a candidate to test.
This pet basically overwrites the existing firmwares in /lib/firmware/b43. You can first manually delete them to be sure.
Your new dmesg log shows that the firmware loading fails.
Okay. I did this in Saluki-014. I downloaded needed b43-firmware-cutter, compiled it, then I downloaded the correct source of firmwares and installed them. I created the pet of the result.
These 117 firmwares are basically the same as the included but they are prepared in Saluki-014.
I dont know if they make any difference, but we need a candidate to test.
This pet basically overwrites the existing firmwares in /lib/firmware/b43. You can first manually delete them to be sure.
Saluki 014 had an experimental udev. I think that is the source of the problem. I'm going to roll it back for 15. Hopefully that will solve it.pemasu wrote:Geoffrey.
Your new dmesg log shows that the firmware loading fails.
Okay. I did this in Saluki-014. I downloaded needed b43-firmware-cutter, compiled it, then I downloaded the correct source of firmwares and installed them. I created the pet of the result.
These 117 firmwares are basically the same as the included but they are prepared in Saluki-014.
I dont know if they make any difference, but we need a candidate to test.
This pet basically overwrites the existing firmwares in /lib/firmware/b43. You can first manually delete them to be sure.
I did as before, updated from 0.13, this time the wireless worked on the first boot, that was the last I saw of it, a reboot showed nothing, I installed the b43 drivers but it made no difference same as before I have to load the driver manually but it don't find the hardware.pemasu wrote:Geoffrey.
Your new dmesg log shows that the firmware loading fails.
Okay. I did this in Saluki-014. I downloaded needed b43-firmware-cutter, compiled it, then I downloaded the correct source of firmwares and installed them. I created the pet of the result.
These 117 firmwares are basically the same as the included but they are prepared in Saluki-014.
I dont know if they make any difference, but we need a candidate to test.
This pet basically overwrites the existing firmwares in /lib/firmware/b43. You can first manually delete them to be sure.
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
That's great!jemimah wrote:
I've split the Python3 packages and added it to the repo:
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
UPnP,DLNA,DAAP,RSP,MPD
Jemimah wrote:
Avahi now works, however one has to still adduser avahi then reboot for it to auto start. If you are yet finish up on saluki 15, i would suggest that from your curent setup you do .
four files are modified in the /etc folder these are 'group' 'gshadow' 'passwd' and 'shadow' you could place the modified files in woof so that saluki always has the user avahi. Then all it takes is for one to install avahi and the start up scripts handle the rest. Works for me i remastered saluki with those four files and all works.
Code: Select all
Also I fixed avahi to run as root and added the startup scripts. I'm still not sure it is working so let me know.
Code: Select all
adduser avahi
four files are modified in the /etc folder these are 'group' 'gshadow' 'passwd' and 'shadow' you could place the modified files in woof so that saluki always has the user avahi. Then all it takes is for one to install avahi and the start up scripts handle the rest. Works for me i remastered saluki with those four files and all works.
new version of pfind
Zigbert has a new version of pfind that cures some bugs with Saluki
http://murga-linux.com/puppy/viewtopic. ... &start=420
_______________________________________________________________
http://murga-linux.com/puppy/viewtopic. ... &start=420
_______________________________________________________________
Re: reality
Well last week was commvault training, and it looks like I'll be interviewing for a bladelogic gig sometime this week. That's good news - it's not fun to be on the bench for this long.Volhout wrote:Jemimah,
How is the new job ?