Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)
You are welcome.gcmartin wrote:Thanks for the follow-up.
Fatdog's repo is limited, so this is unwise. What is wise to realise that foreign packages may cause problems and work towards solving them. If you are unsure you can always use Fatdog's sandbox. Or otherwise use a DVD+RW - if the foreign package doesn't work, just erase and start over again.Past post issues
I can only assume that the problem must be with using the Java PET and attempts with Chrome....which did work.
From this point on, I will stick with the Official Repo offerings to avoid troubles. Over the years, FATDOG has been very well behaved with little to no issues..
I'll leave that question to kirk.Question on a Google Voice PET
Iis this PET intended for the SeaMonkey browser?
That definitely is *not* the intent. The packages are still there, they have never been deleted. Even the packages for Fatdog64 600 are still there. Please check again.gcmartin wrote:Using 621, the PPM has changed.
The SAMBA management tools are GONE from the screen (used to be called SAMBA extras for the built-in version of SAMBA). It appears that the intent was to remove the old SAMBA version reference.
The cdrtools package in the repo is the same as the one included in Fatdog 620/621. That package is made available for those who decided to stay with older version of Fatdogs. I also noticed from your pet list - again, the "gpart" package has now been included in the base ISO, so you don't need to install it again. The information on these new and updated packages are included in the Release Notes (also forum announcement) for every release.gcmartin wrote:I have seen CDR-Tools in the PPM but, I also have noticed the versions of the tools that come with CDRecord as it is packaged in FATDOG..
Is CDR-Tools a separate package than whats included in FATDOG620/621? Or is there overlap?
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Thanks Jamesbond.jamesbond wrote:That definitely is *not* the intent. The packages are still there, they have never been deleted. Even the packages for Fatdog64 600 are still there. Please check again..gcmartin wrote:Using 621, the PPM has changed.
The SAMBA management tools are GONE from the screen (used to be called SAMBA extras for the built-in version of SAMBA). It appears that the intent was to remove the old SAMBA version reference.
SAMBA version that is in 621 is version 3.6.12. There are no Management tools, the Extras, which is separated from SAMBA available for V3.6.12 This is what's causing my confusion. The version of SAMBA that is enclosed is stable and the references to the version of SAMBA that shipped with FATDOG 520 is confusing what our steps should be so that we have a 621 with appropriate management tools.
Hope that clarifies why I ask. I did use the PPM an checked all of the REPOs starting with Ibiblio for a V3.6.12 PET to add management but find none.
QUESTION
Should the REPO's reference be updated to reflect that the entry is really for the currently installed SAMBA?
That's why I ask.
Thanks for your guidance. This is really a truly fast distro.
Delta file and bluray broken in 621
Here is a delta file between 620 to 621 wish I had this option.
also the 58byte difference isolinux.bin breaks bluray support on fully populated iso (22Gs)
well sorry cant post a 2Meg delta zip anymore
also the 58byte difference isolinux.bin breaks bluray support on fully populated iso (22Gs)
well sorry cant post a 2Meg delta zip anymore
Ted Dog,
If you need a spot to put your files there are a few of us that have servers/places
You are welcome to put files on puppylinux.ca if you wish..others will also offer space if you need large file access.
Welcome back Ted Dog...good to see you posting again.
On another note...has anyone seen Lobster of late?
Best,
Eric
To add: russoodle and smokey01 have servers running current...ask them as well as that's the point...access.
If you need a spot to put your files there are a few of us that have servers/places
You are welcome to put files on puppylinux.ca if you wish..others will also offer space if you need large file access.
Welcome back Ted Dog...good to see you posting again.
On another note...has anyone seen Lobster of late?
Best,
Eric
To add: russoodle and smokey01 have servers running current...ask them as well as that's the point...access.
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
Hi. I didn't know we had a Google Voice PET. I am using 620 with the Google supplied Debian package. Works good here. Install, refresh, make calls:gcmartin wrote: Question on a Google Voice PET
Iis this PET intended for the SeaMonkey browser?
google-talkplugin_current_amd64.deb
Hope that helps!
Cheers!
JFYI - using FD621 now from DVD-rw and all seems good. Really like the boot splash screen - very helpful for newer users.
Will play a little more and post a report shortly.
Many thanks for an outstanding puppy - very best regards - Ray
Will play a little more and post a report shortly.
Many thanks for an outstanding puppy - very best regards - Ray
[b]Asus[/b] 701SD. 2gig ram. 8gb SSD. [b]IBM A21m[/b] laptop. 192mb ram. PIII Coppermine proc. [b]X60[/b] T2400 1.8Ghz proc. 2gig ram. 80gb hdd. [b]T41[/b] Pentium M 1400Mhz. 512mb ram.
I installed FD620 on a newish Lenovo G585 laptop (1.3 GHz, 2 GB). Although I've installed a bunch of Puppies on different machines over the past five years, this is my first 64 bit Puppy and also my first run-in with UEFI and Windows 8.
After messing with the boot order in UEFI, I managed to boot the CD. And after a couple of false starts in choosing boot options, figuring out the key management business and such (RTFM!!), I was up and running. It surprised me to find this machine uses 7(!) partitions for Windows 8.
Resizing the HDD through Win8 and partitioning with GParted, I added sda8(fat32) and sda9(ext4).(This "refurbished" machine was crippled with a non-functioning right button, so following the instructions required some work-arounds). A couple missteps later, I had a working installed(dual -boot) FatDog ! It boots and runs faster and isn't annoying like Win8. And I could tame the out-of-control touchpad with flSynclient unlike in Win8.
I have to admit this installation was the most intimidating one in a long time, dealing with UEFI and worrying about Borking the Win8 install and making it unbootable.
Regrettably, I probably won't keep this install because this is not my machine and since Linux sees all the partitions, a beginner could "accidentally" corrupt the Win8 files in the 7 partitions and the Gods of M$ will be very angry!
Also, I was looking for something with Japanese language support for my client. As I understand it, FatDogs since 600 are not based on Woof. I think between this, and being 64 bit, the choice of available .pets are limited -- for now.
I was aiming for something like Puppy 4.3.1JP which while I can boot from CD, but only if I go into UEFI and enable Legacy boot. Ironically, the machine seems to know when there is a 64 bit system CD (FatDog) and a 32 bit system CD. When booting in UEFI mode, it only recognizes the existence of the CD/DVD drive when there.is a 64 bit CD in it.
If I leave things in Legacy mode, I can't fully boot the installed FatDog -- it always hangs somewhere past wpagui, goes to a blank screen with an unblinking cursor.
So, I think my question is, will there be better language support in FatDog's near future, or is there a simple way to boot an older 32 bit system with language support in the Win8/UEFI type machines?
Right now, for example using FatDog and browsers to look at email with Japanese characters just shows rectangles. Is there a simple solution?
Thanks, HJ
edit: For what it's worth flSynclient crashes X when in Live-CD, when trying to set the top/bottom/left/right parameters. I've seen this before in an early version of Saluki. FlSynclient just crashes itself when setting the parameters on the installed FatDog.
After messing with the boot order in UEFI, I managed to boot the CD. And after a couple of false starts in choosing boot options, figuring out the key management business and such (RTFM!!), I was up and running. It surprised me to find this machine uses 7(!) partitions for Windows 8.
Resizing the HDD through Win8 and partitioning with GParted, I added sda8(fat32) and sda9(ext4).(This "refurbished" machine was crippled with a non-functioning right button, so following the instructions required some work-arounds). A couple missteps later, I had a working installed(dual -boot) FatDog ! It boots and runs faster and isn't annoying like Win8. And I could tame the out-of-control touchpad with flSynclient unlike in Win8.
I have to admit this installation was the most intimidating one in a long time, dealing with UEFI and worrying about Borking the Win8 install and making it unbootable.
Regrettably, I probably won't keep this install because this is not my machine and since Linux sees all the partitions, a beginner could "accidentally" corrupt the Win8 files in the 7 partitions and the Gods of M$ will be very angry!
Also, I was looking for something with Japanese language support for my client. As I understand it, FatDogs since 600 are not based on Woof. I think between this, and being 64 bit, the choice of available .pets are limited -- for now.
I was aiming for something like Puppy 4.3.1JP which while I can boot from CD, but only if I go into UEFI and enable Legacy boot. Ironically, the machine seems to know when there is a 64 bit system CD (FatDog) and a 32 bit system CD. When booting in UEFI mode, it only recognizes the existence of the CD/DVD drive when there.is a 64 bit CD in it.
If I leave things in Legacy mode, I can't fully boot the installed FatDog -- it always hangs somewhere past wpagui, goes to a blank screen with an unblinking cursor.
So, I think my question is, will there be better language support in FatDog's near future, or is there a simple way to boot an older 32 bit system with language support in the Win8/UEFI type machines?
Right now, for example using FatDog and browsers to look at email with Japanese characters just shows rectangles. Is there a simple solution?
Thanks, HJ
edit: For what it's worth flSynclient crashes X when in Live-CD, when trying to set the top/bottom/left/right parameters. I've seen this before in an early version of Saluki. FlSynclient just crashes itself when setting the parameters on the installed FatDog.
FD64-621-final
# uname -a
Linux fatdog64 3.8.6 #1 SMP Fri Apr 5 17:01:02 EDT 2013 x86_64 GNU/Linux
# free
total used free shared buffers
Mem: 1784816 810936 973880 0 66272
-/+ buffers: 744664 1040152
Swap: 0 0 0
#
Mem: 812800K used, 972016K free, 0K shrd, 66476K buff, 550932K cached
CPU: 0.2% usr 0.2% sys 0.0% nic 99.4% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.00 0.03 0.05 2/131 7873
Booting from DVD-rw on an E732 laptop. i3 proc. 2Gb ram. External LCD monitor.
Running very well.
# uname -a
Linux fatdog64 3.8.6 #1 SMP Fri Apr 5 17:01:02 EDT 2013 x86_64 GNU/Linux
# free
total used free shared buffers
Mem: 1784816 810936 973880 0 66272
-/+ buffers: 744664 1040152
Swap: 0 0 0
#
Mem: 812800K used, 972016K free, 0K shrd, 66476K buff, 550932K cached
CPU: 0.2% usr 0.2% sys 0.0% nic 99.4% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.00 0.03 0.05 2/131 7873
Booting from DVD-rw on an E732 laptop. i3 proc. 2Gb ram. External LCD monitor.
Running very well.
- Attachments
-
- hardinfo_report.html.bz2
- (6.81 KiB) Downloaded 139 times
[b]Asus[/b] 701SD. 2gig ram. 8gb SSD. [b]IBM A21m[/b] laptop. 192mb ram. PIII Coppermine proc. [b]X60[/b] T2400 1.8Ghz proc. 2gig ram. 80gb hdd. [b]T41[/b] Pentium M 1400Mhz. 512mb ram.
Hi Ray MK.Ray MK wrote:FD64-621-final
# uname -a
Linux fatdog64 3.8.6 #1 SMP Fri Apr 5 17:01:02 EDT 2013 x86_64 GNU/Linux
...
Running very well.
I noticed in your earlier post you share that you're running 621. But, your uname shows an earlier release of FATDOG.
My Live media multi-session 621 is showing this
Code: Select all
# uname -a
Linux FD621-Laptop 3.8.7 #1 SMP Fri Apr 12 20:11:22 EDT 2013 x86_64 GNU/Linux
"Quit Wireless" on WGA-GUI icon on the taskbar
Running FATDOG 621 on Live media. Couple issues:
Issue #1
The GUI icon on the taskbar has a "Quit Wireless" selection.
If you have a wired connection AND a wireless connection on the same system (such as when using a laptop) and one clicks "Quit Wireless", the system will drop both the wired AND the wireless IP addresses from the active system. This causes any active LAN connections over the wired connection will be "hung".
Question
Is that its intended behavior? If so, should the selection be labeled something different?
Issue #2
After adding LVM PET to the system via PPM, the systems LVM, though see via pv/lv display, I cannot mount the LVM. Need guidance and a recommendation to have the LVM partition auto-started at boot time. Currently, I am booting the ...Multi... selection on the boot menu as it automatically accesses my save-session without need to type.
Thanks in advance for idea.
Issue #1
The GUI icon on the taskbar has a "Quit Wireless" selection.
If you have a wired connection AND a wireless connection on the same system (such as when using a laptop) and one clicks "Quit Wireless", the system will drop both the wired AND the wireless IP addresses from the active system. This causes any active LAN connections over the wired connection will be "hung".
Question
Is that its intended behavior? If so, should the selection be labeled something different?
Issue #2
After adding LVM PET to the system via PPM, the systems LVM, though see via pv/lv display, I cannot mount the LVM. Need guidance and a recommendation to have the LVM partition auto-started at boot time. Currently, I am booting the ...Multi... selection on the boot menu as it automatically accesses my save-session without need to type.
Thanks in advance for idea.
- Attachments
-
- Problem with WPA-GUI.png
- Problem with WPA-GUI
- (15.62 KiB) Downloaded 461 times
-
- Current Package List.png
- Packages added before last save-session reboot
- (96.89 KiB) Downloaded 462 times
FD64-621-final
# uname -a
Linux fatdog64-284 3.8.7 #1 SMP Fri Apr 12 20:11:22 EDT 2013 x86_64 GNU/Linux
# free
total used free shared buffers
Mem: 1784816 584216 1200600 0 54012
-/+ buffers: 530204 1254612
Swap: 0 0 0
#
# top
Mem: 614284K used, 1170532K free, 0K shrd, 57928K buff, 447872K cached
CPU: 0.0% usr 0.0% sys 0.0% nic 99.8% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.06 1.70 1.27 2/107 6196
Not sure what happened previously re: uname - got it right this time.
Luvly puppy - many thanks.
# uname -a
Linux fatdog64-284 3.8.7 #1 SMP Fri Apr 12 20:11:22 EDT 2013 x86_64 GNU/Linux
# free
total used free shared buffers
Mem: 1784816 584216 1200600 0 54012
-/+ buffers: 530204 1254612
Swap: 0 0 0
#
# top
Mem: 614284K used, 1170532K free, 0K shrd, 57928K buff, 447872K cached
CPU: 0.0% usr 0.0% sys 0.0% nic 99.8% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 0.06 1.70 1.27 2/107 6196
Not sure what happened previously re: uname - got it right this time.
Luvly puppy - many thanks.
[b]Asus[/b] 701SD. 2gig ram. 8gb SSD. [b]IBM A21m[/b] laptop. 192mb ram. PIII Coppermine proc. [b]X60[/b] T2400 1.8Ghz proc. 2gig ram. 80gb hdd. [b]T41[/b] Pentium M 1400Mhz. 512mb ram.
usb stick install no boot
Installed on a USB stick using the FD installer and the 621 iso. No boot I'm afraid.
extlinux.conf sayeth:
default fatdog
timeout 50
prompt 1
label fatdog
kernel vmlinuz
initrd initrd
append
Attempts to boot say missing operating system.
Any ideas on getting to takeoff with this? Sorry, in a rush, and haven't researched issue. Must be some more magic required to get stick to boot? A file called ldlinux,sys is on the stick. Should this be there - thought it may have resulted from various abortive efforts to install a Puppy.
extlinux.conf sayeth:
default fatdog
timeout 50
prompt 1
label fatdog
kernel vmlinuz
initrd initrd
append
Attempts to boot say missing operating system.
Any ideas on getting to takeoff with this? Sorry, in a rush, and haven't researched issue. Must be some more magic required to get stick to boot? A file called ldlinux,sys is on the stick. Should this be there - thought it may have resulted from various abortive efforts to install a Puppy.
Re: usb stick install no boot
That message usually means that a bootloader was not installed.gnomic wrote:Attempts to boot say missing operating system.
Go to Control Panel > Utilities and run Grub4Dos Bootloader Config.
Make sure that you select your flash drive and not your main hard drive.
1. Use an UTF-8 locale (en_US.UTF-8 would do, or any other UTF-8 English locale).heywoodj wrote:Also, I was looking for something with Japanese language support for my client
<<... snip...>>
Right now, for example using FatDog and browsers to look at email with Japanese characters just shows rectangles. Is there a simple solution?
2. For reading, get a CJK font, for example from here: http://wenq.org/en
3. For writing, install fcitx-anthy from the Package Manager - it should pull all the necessary components.
4. Note: Fatdog isn't localised/internationalised, so after you have done that, all the menus are still in English. If you don't like the English locales you can get additional locales from the Package Manager (glibc_locales package) but this will not change the fact - menus and messages will be always be in English.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]