Fatdog64-700 beta2 [Closed]
I have started to use FileZilla as FTP cliient. I have been using it as root. I know the standard practice is to run email clients and web browsers as spot rather than root for security reasons. Should the same be done for FTP clients? Thanks in advance for any help on this.
I decided to set it up to run as spot. I have also modified the spot script into a separate script to allow it to be run also as root. I can run either way and still use the same configuration file in spot. Normally, clicking on the menu entries for it will run using the spot script. If there is a need to run as root, one uses the other script.
I decided to set it up to run as spot. I have also modified the spot script into a separate script to allow it to be run also as root. I can run either way and still use the same configuration file in spot. Normally, clicking on the menu entries for it will run using the spot script. If there is a need to run as root, one uses the other script.
Last edited by JustGreg on Sat 15 Nov 2014, 00:01, edited 1 time in total.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
Bad news. I tried it on my rather non-standard nF3 board.Will do...
First problem: PS/2 mouse inactive. Stuck a USB mouse in.
Next problem: Had to use wifi connection. Appalling connection utility in control panel. Seen some bad ones in my time, but this one takes the biscuit. Eventually fathomed it, but refused to connect. Not a lot of point in pursuing machines without wired access.
Sorry - abandoning FD64 for the moment.
Hi kirk !
I think changing some views with Geoffrey about his way of compiling mvsas.ko module could help solving an issue in Fatdog ...
On my desktop mvsas.ko module does not work in Fatdog . My drive it's not seen at all . It happened also on my previous Gigabyte mobo and now on my actual Asus mobo.
Typing lsmod | grep mvsas in the Fatdog 700b2 terminal gave the result seen in the attached picture .
Now , in Carolina my OCZ Revodrive 3 is seen in Gparted and in Pmount as 2 drives .It's a bit strange that Pmount sees them as USB attached drives !!! Maybe it's the way the module get to them through a USB controller inside the motherboard , or is something in the module - I don't know , but it works!
Using mdadm and creating a fake raid and a small script in Startup folder gave me the possibility to use it in Carolina - no matter which kernel !!!
I got some infos from the terminal from battleshooter's Carolina with kernel 3.17 and compared them with the same infos taken in Fatdog 700b2 . I outlined the differences - the most important one seemed the last one , about vermagic: ...
Hopefully , maybe a hint from Geoffrey could help you to make the mvsas.ko module work in Fatdog , too .
I think changing some views with Geoffrey about his way of compiling mvsas.ko module could help solving an issue in Fatdog ...
On my desktop mvsas.ko module does not work in Fatdog . My drive it's not seen at all . It happened also on my previous Gigabyte mobo and now on my actual Asus mobo.
Typing lsmod | grep mvsas in the Fatdog 700b2 terminal gave the result seen in the attached picture .
Now , in Carolina my OCZ Revodrive 3 is seen in Gparted and in Pmount as 2 drives .It's a bit strange that Pmount sees them as USB attached drives !!! Maybe it's the way the module get to them through a USB controller inside the motherboard , or is something in the module - I don't know , but it works!
Using mdadm and creating a fake raid and a small script in Startup folder gave me the possibility to use it in Carolina - no matter which kernel !!!
I got some infos from the terminal from battleshooter's Carolina with kernel 3.17 and compared them with the same infos taken in Fatdog 700b2 . I outlined the differences - the most important one seemed the last one , about vermagic: ...
Hopefully , maybe a hint from Geoffrey could help you to make the mvsas.ko module work in Fatdog , too .
- Attachments
-
- No mvsas.jpg
- (83.11 KiB) Downloaded 854 times
-
- mvsas-info.tar
- (170 KiB) Downloaded 207 times
-
- drives in Carolina.tar
- (100 KiB) Downloaded 247 times
Skype on FatDog
Greetings,
I have successfully booted Fatdog64-700 beta2 (frugal) on my Dell Inspiron 15. I am searching for a Puppy that can run Skype easily and FatDog has two Skype 4.3.x SFS versions available. I have tried both SFS files but when I launch skype from the terminal I receive an error message(s): "No such file or directory"
I have verified that the files in question do, in fact, exist.
Trying to launch the files in question manually from the terminal also results in the same error message.
Any ideas?
Thanks very much
I have successfully booted Fatdog64-700 beta2 (frugal) on my Dell Inspiron 15. I am searching for a Puppy that can run Skype easily and FatDog has two Skype 4.3.x SFS versions available. I have tried both SFS files but when I launch skype from the terminal I receive an error message(s): "No such file or directory"
I have verified that the files in question do, in fact, exist.
Trying to launch the files in question manually from the terminal also results in the same error message.
Any ideas?
Thanks very much
Seagate Backup drive USB 3.0 worked in FD64 621 not in 700b2
Bug report?/Can't find solution in forums.. Any help appreciated.
I have FD64 621 installed on one HP GT7725 - drive works
I have a 2nd GT7725 I installed FD64 700b2 on. Seagate drive icon doesn't show on screen (not there to click on to mount) Not showing in Pmount.
I have a USB 3.0 thumbdrive that does show then plugged in to 700b2.
Below is what I see when I plug in the Seagate 1TB Mod:SRD0061
Sda1 is the 1GB onboard SSD
I have FD64 621 installed on one HP GT7725 - drive works
I have a 2nd GT7725 I installed FD64 700b2 on. Seagate drive icon doesn't show on screen (not there to click on to mount) Not showing in Pmount.
I have a USB 3.0 thumbdrive that does show then plugged in to 700b2.
Below is what I see when I plug in the Seagate 1TB Mod:SRD0061
Sda1 is the 1GB onboard SSD
Code: Select all
# dmesg|tail
[ 2777.919990] usb 1-3: new high-speed USB device number 9 using ehci-pci
[ 2778.048363] usb 1-3: New USB device found, idVendor=0bc2, idProduct=ab20
[ 2778.048378] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 2778.048385] usb 1-3: Product: BUP Slim BK
[ 2778.048392] usb 1-3: Manufacturer: Seagate
[ 2778.048397] usb 1-3: SerialNumber: NA76N37W
# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 04f2:0760 Chicony Electronics Co., Ltd Acer KU-0760 Keyboard
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 009: ID 0bc2:ab20 Seagate RSS LLC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
# fdisk -l
Disk /dev/sda: 977.5 MiB, 1024966656 bytes, 2001888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 63 1997855 998896+ 83 Linux
# lsub -v
Bus 001 Device 009: ID 0bc2:ab20 Seagate RSS LLC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bc2 Seagate RSS LLC
idProduct 0xab20
bcdDevice 1.00
iManufacturer 2 Seagate
iProduct 3 BUP Slim BK
iSerial 1 NA76N37W
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 85
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 98
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-in pipe (0x03)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Data-out pipe (0x04)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Status pipe (0x02)
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Command pipe (0x01)
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0000
(Bus Powered)
I added three stable release packages from Mozilla to the ibiblio.org fatdog64 contributor repository. They are FileZilla 3.9.0.6, Thunderbird 31.2.0 and Firefox 33.1.1 The applications are all configured to run as spot.
For the Firefox application, before installing it, one needs to remove the default Firefox package using Gslapt package manager. The new package can then be installed using Gslapt. Please excuse the description show in Gslapt. I am still learning how to correctly make a slack-desc file for packages.
I hope this helps.
I did not get the package name for FileZilla correct It does not show in Gslapt list of packages. You can find it here:http://distro.ibiblio.org/fatdog/contrib/packages/700/
I will get the package naming and slack-desc right one of these days.
For the Firefox application, before installing it, one needs to remove the default Firefox package using Gslapt package manager. The new package can then be installed using Gslapt. Please excuse the description show in Gslapt. I am still learning how to correctly make a slack-desc file for packages.
I hope this helps.
I did not get the package name for FileZilla correct It does not show in Gslapt list of packages. You can find it here:http://distro.ibiblio.org/fatdog/contrib/packages/700/
I will get the package naming and slack-desc right one of these days.
Last edited by JustGreg on Tue 18 Nov 2014, 18:19, edited 2 times in total.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
I have also seen that problem with mounting a Seagate Backup Plus 1 TB external USB 3.0 drive. But, I had not done as much to track it down. In my case both machines showing the problem had USB 3.0 cards added. I will need to bring up a machine with USB 3.0 on the mainboard to check if this also exhibits the problem. I'll also try some other brands of external USB drives.
- neerajkolte
- Posts: 516
- Joined: Mon 10 Feb 2014, 07:05
- Location: Pune, India.
I am also thinking to add usb 3.0 PCI card to my machine in a week or two. Hope it works well.
- Neeraj.
- Neeraj.
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
I have connected a small USB bluetooth device (SounsBot Model SB340). It is successfully detected and set up properly. I can connect to a bluetooth audio receiver (IBT-8), However, I can not transfer the audio from computer to the receiver and my stereo. I did a search on bluetooth audio, but had no luck. I also checked alsamixer to see if there was a control for bluetooth on it, no luck there. How does one get the computer audio to the bluetooth device?
After some searching of the Internet, I found out the Bluez protocol, which fatdog uses. I did try again and again with no audio. Here is what is reported: Any suggestions for the next step? Thanks in advance for any help.
20 Nov. edit:
After searching the Internet and trying different things, I think the bluetooth connection is fine and does not have the problem. It appears that control needs to be added to alsamixer for bluetooth. The sites with information say the change needs to be in /etc/asound.conf file. Fatdog64 has /etc/asound.state file. It is not clear to me if asound.state is the same as asound.conf. The control is needed for pcm bluetooth audio. I hope this helps.
After some searching of the Internet, I found out the Bluez protocol, which fatdog uses. I did try again and again with no audio. Here is what is reported:
Code: Select all
# bt-device -i IBT-08
[AB:12:67:11:1E:B7]
Name: IBT-08
Alias: IBT-08 [rw]
Address: AB:12:67:11:1E:B7
Icon: audio-card
Class: 0x240414
Paired: 1
Trusted: 1 [rw]
Blocked: 0 [rw]
Connected: 1
UUIDs: [Headset, AudioSink, AVRemoteControlTarget, AVRemoteControl, Handsfree, 0000112e-0000-1000-8000-00805f9b34fb, PnPInformation]
20 Nov. edit:
After searching the Internet and trying different things, I think the bluetooth connection is fine and does not have the problem. It appears that control needs to be added to alsamixer for bluetooth. The sites with information say the change needs to be in /etc/asound.conf file. Fatdog64 has /etc/asound.state file. It is not clear to me if asound.state is the same as asound.conf. The control is needed for pcm bluetooth audio. I hope this helps.
Last edited by JustGreg on Thu 20 Nov 2014, 21:23, edited 1 time in total.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
Kirk and James take care of yourself and your families. They come first and are more important. Thanks again for your efforts. For the fatdog problems, we will have to exercise some patience. After all, patience is a virtue that has to be practiced
Last edited by JustGreg on Thu 20 Nov 2014, 13:19, edited 1 time in total.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
-
- Posts: 52
- Joined: Tue 28 May 2013, 16:20
- neerajkolte
- Posts: 516
- Joined: Mon 10 Feb 2014, 07:05
- Location: Pune, India.
Kirk and James, take care brothers. Family should always come first. I wish them a fast recovery.
Thanks for all your work.
- Neeraj.
Thanks for all your work.
- Neeraj.
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
I used micko01 get_libreoffice script (version 0.29) to create a 64 bit English LibreOffice version 4.3.4 SFS. It does not show up in the SFS manager control panel application, probably due to a lack of knowledge on my part. It is available in the contributor repository here: http://distro.ibiblio.org/fatdog/contrib/sfs/700/
I hope this helps.
I hope this helps.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
- neerajkolte
- Posts: 516
- Joined: Mon 10 Feb 2014, 07:05
- Location: Pune, India.
CUPS 1.7.3 issue
Good evening to all...
I have set my wife up with Fatdog and she has been using it for several days. All was going well until she discovered a printing issue. It seems that this version of CUPS does not want to play with my printer. I have installed a PET file:
(http://shinobar.server-on.net/puppy/opt ... -1.4.0.pet)
which contains the drivers for my printer. Of course Fatdog converted the pet and I installed the converted package.
This pet has worked on Lucid 5.2.8.6, Slacko 5.3.3, Precise 5.6, and Precise 5.7 (all of which are running an earlier version of CUPS.
When printing the page will make it about halfway though the cycle and stops with the error "Stopped - filter failed"
I have tried using the built in NX2xx and NX3xx drivers but each has their own issues which will not allow successful printing.
I am tempted to install an earlier version of CUPS but wanted some feedback and other thoughts and ideas first....anyone have any insight?
Thanks in advance.
I have set my wife up with Fatdog and she has been using it for several days. All was going well until she discovered a printing issue. It seems that this version of CUPS does not want to play with my printer. I have installed a PET file:
(http://shinobar.server-on.net/puppy/opt ... -1.4.0.pet)
which contains the drivers for my printer. Of course Fatdog converted the pet and I installed the converted package.
This pet has worked on Lucid 5.2.8.6, Slacko 5.3.3, Precise 5.6, and Precise 5.7 (all of which are running an earlier version of CUPS.
When printing the page will make it about halfway though the cycle and stops with the error "Stopped - filter failed"
I have tried using the built in NX2xx and NX3xx drivers but each has their own issues which will not allow successful printing.
I am tempted to install an earlier version of CUPS but wanted some feedback and other thoughts and ideas first....anyone have any insight?
Thanks in advance.
Last edited by rek769 on Sun 23 Nov 2014, 04:20, edited 1 time in total.