Fatdog64-600b1

A home for all kinds of Puppy related projects
Post Reply
Message
Author
capicoso
Posts: 172
Joined: Fri 13 Jan 2012, 23:38
Location: Argentina

#121 Post by capicoso »

nooby wrote:Guys, hope you can bear with a naive noob.

All this trouble with 64Bit???

Would it be very demanding to make a 32-bit version
and then you would have plenty of time to get the 64 bit
version totally or absolutely compatible with all drivers
and such complications?

Having a multiuser Puppy that just works is a sensation.
So why add the complexity of 64-bit compatibility from Scratch?

I "vote for" to have both 32-bit and 64-bit and most being used to
32-bit do look for that and the enthusiasts have the patience to
wait for the 64-bit to come a bit later? Only my ignorant rant.

Edit
Here is one reason I don't like SeaMonkey. AutoUpdate
and it remember too much even when one tells it to delete history.

Read here
http://www.murga-linux.com/puppy/viewto ... 331#635331

Quote/
For some years now I've had Seamonkey set to delete browsing history when shutting down, as well as most other residues of online activity.

So I was dumbfounded when I happened to open the tab:

Tools/Data Manager

to see a list of domains that seems to include most, if not all, of the sites I've visited over the past several years!

At the bottom of the page I see a "remove" tab, but it's greyed out.

What use is clearing your history if every domain you've visited is shown and can't be removed?

Do other browsers have this same function?
/unquote
So you say they should start all over again with 32bits and then 64bits?
I'm switching to Fatdog because it's 64bits. There are already lots of puppy 32bits. You could use fatslacko...
And correct me if i'm wrong, but wouldn't be better if it's written from scratch from 64bits rather than make a 32bit version and then convert it to 64bits?
Btw, the project is already on beta1...

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#122 Post by nooby »

You could use fatslacko...
http://murga-linux.com/puppy/viewtopic.php?t=77951

Do you mean that that one are multi user too?
FatDog64 is a modern multi user Puppy and
therefor is a very unique Puppy that is why
that I am interested in it here now.

Would surprise me much if FATslacko is a multi user puppy.

Edit. I find it un-polite of us to talk about FATSlacko here
so let's only do that on their thread from now on okay! .


I did take a look and nowhere do they write it is anything other
than a fatter version of Slacko

Edit after being active in the other thread.
Mick confirmed that it is not a multi-user OS
I trust you read into my posts something I had not intention to say.
I am interested in a 32-bit version of FatDog because it is a multi-user
so a lot of people would be able to use Puppy on 32 bit machines
if one had two versions of a multi-user Puppy because now they
refuse to use a single user Puppy. Okay.
Last edited by nooby on Thu 21 Jun 2012, 07:38, edited 1 time in total.
I use Google Search on Puppy Forum
not an ideal solution though

Gobbi
Posts: 255
Joined: Fri 09 Mar 2012, 14:01

#123 Post by Gobbi »

Thamk's 'jamesbond' and thank's 'kirk' for your answers .
I'll try to change the kernel boot line and I hope it works . :)

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#124 Post by smokey01 »

rcrsn51 wrote:@smokey01: Did you get your Samsung ML-1660 working? Which of the two Samsung driver packages in the repo did you use?
rcrsn51 both the samsung_print_fd600 Ver 3.00.76 and Ver 4.00.35 work with my Samsung ML1660.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#125 Post by rcrsn51 »

Thanks.

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#126 Post by 01micko »

Edited my jwm_menu_create patch ... http://murga-linux.com/puppy/viewtopic. ... 581#634581

Cheers
Puppy Linux Blog - contact me for access

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#127 Post by jamesbond »

01micko wrote:Edited my jwm_menu_create patch ... http://murga-linux.com/puppy/viewtopic. ... 581#634581

Cheers
Mick, I did it quite differently. I added this after the main "while read LINE"
case $ICON in
*.*) ;; # extension provided, do nothing
*) ICON=${ICON}.png ;; # no extension, add PNG
esac
Still suffers from the same problem as before (if the path or the filename contains dot ... it won't work), but I suppose for 99% of the case there will be no dot there except for the file extension. The 1% case deserve to have their icons missing :)
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]

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#128 Post by 01micko »

jamesbond wrote:
case $ICON in
*.*) ;; # extension provided, do nothing
*) ICON=${ICON}.png ;; # no extension, add PNG
esac
Still suffers from the same problem as before (if the path or the filename contains dot ... it won't work), but I suppose for 99% of the case there will be no dot there except for the file extension. The 1% case deserve to have their icons missing :)
Hmm .. did work for me, latest of LibreOffice has a DOT in the filename, actually, has for awhile.. a bit stupid but who are we to tell them? :lol: They probably take their orders from Ubuntu, (funny how his initials are MS? [joke of course, not really bagging Ubuntu or Mark, he's done plenty for Linux :) ]).
Puppy Linux Blog - contact me for access

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#129 Post by jamesbond »

01micko wrote:Hmm .. did work for me, latest of LibreOffice has a DOT in the filename, actually, has for awhile.. a bit stupid but who are we to tell them? :lol: They probably take their orders from Ubuntu, (funny how his initials are MS? [joke of course, not really bagging Ubuntu or Mark, he's done plenty for Linux :) ]).
:lol:
I bow to libreoffice. Here's the updated code:

Code: Select all

case $ICON in
		*.xpm|*.jpg|*.png|*.svg) ;; # extension provided, do nothing
		*) ICON=${ICON}.png	;; # no extension, add PNG
esac
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]

Gobbi
Posts: 255
Joined: Fri 09 Mar 2012, 14:01

#130 Post by Gobbi »

kirk - the tip with adding the kernel boot line worked like a charm . I only switched the sound cards and unmute the channel from Alsa Mixer .After that i set up Seamonkey and loaded my own bookmarks into it , installed the wbar.pet , a few more cosmetics and remasterd the live CD.
Everything is working now - very nice job - thank's a lot to everybody for the work.
Nice thing the Evince Reader since it opens djvu's too.

Using Skype with both Fatdog 521 and Lighthouse 5.14 was always possible only with Analogue Audio because the system recognized only the external analogue microphone and not ( no matter what I tried ) the digital microphone which is inside the usb webcam .

Is there any tweak :idea: that could arrange that by the time the Skype pet arrives :?:

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#131 Post by smokey01 »

I like to put all of my files for any particular distribution in the same directory, for example:
/mnt/home/fd64. I would rather do something like /mnt/home/distro/fd64 to make things even tidier but most distributions, I believe, will only work one directory level deep.

When I create a savefile for fd64 it always places it in /mnt/home/ although the other two files are in /mnt/home/fd64/

I have tried a number of the savefile options without success. The only one that seems to work is savefile=no.

Wouldn't it be better if the savefile was always saved to where the other files were located unless otherwise specified.

What should the kernel line look like for my example above using legacy grub?

Thanks

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

#132 Post by Jim1911 »

smokey01 wrote:I like to put all of my files for any particular distribution in the same directory, for example:
/mnt/home/fd64. I would rather do something like /mnt/home/distro/fd64 to make things even tidier but most distributions, I believe, will only work one directory level deep.

When I create a savefile for fd64 it always places it in /mnt/home/ although the other two files are in /mnt/home/fd64/

I have tried a number of the savefile options without success. The only one that seems to work is savefile=no.

Wouldn't it be better if the savefile was always saved to where the other files were located unless otherwise specified.

What should the kernel line look like for my example above using legacy grub?

Thanks
This code works for me.

Code: Select all

kernel /fatdog64-600/vmlinuz  pmedia=atahd pdev1=sdb2 psubdir=fatdog64-600 savefile=direct:device:sdb2:fatdog64-600/fd64save.ext4

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#133 Post by 01micko »

I just moved my save to the subdir and tried this;

Code: Select all

kernel /fd64b2/vmlinuz savefile=direct:device:sda1:/fd64b2/fd64save.ext4
Worked fine. I think pdev1, psubdir, and pmedia are legacy puppy needs, may be wrong though.
Puppy Linux Blog - contact me for access

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#134 Post by jamesbond »

01micko wrote:I just moved my save to the subdir and tried this;

Code: Select all

kernel /fd64b2/vmlinuz savefile=direct:device:sda1:/fd64b2/fd64save.ext4
Worked fine. I think pdev1, psubdir, and pmedia are legacy puppy needs, may be wrong though.
You're right, I was just about to say the same. These legacy parameters have no effect but don't harm either.
In addition, one can directly make the savefile in a folder by specifying the path when asked for the savefile name. Perhaps I didn't make it clear enough in the dialog box, sorry :oops:

If you are running from flash device (or just want to play with it), the equivalent of "pmedia=ataflash" or "pmedia=usbflash" etc is to replace direct with ram. This way you will get a RAM layer on top of the savefile. You will see Puppy's usual big red save button on the desktop, and you can configure the RAMSAVEINTERVAL via the event manager as usual. If you set that to zero, none of your session will be saved.
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]

Jim1911
Posts: 2460
Joined: Mon 19 May 2008, 20:39
Location: Texas, USA

#135 Post by Jim1911 »

01micko wrote:I just moved my save to the subdir and tried this;

Code: Select all

kernel /fd64b2/vmlinuz savefile=direct:device:sda1:/fd64b2/fd64save.ext4
Worked fine. I think pdev1, psubdir, and pmedia are legacy puppy needs, may be wrong though.
I removed those parameters from my code and found that you are correct and all that's needed are the "savefile" parameters to find the save file although they do no harm.

However, when I just used the legacy parameters the save file could not be found. Grub can only find a save file located in /mnt/home.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

format floppy, probepart

#136 Post by shinobar »

jamesbond wrote:
jamesbond wrote:
Shinobar wrote:Note: Failed format floppy, tested on Fatdog64 alpha2 and beta1.
I only have one machine with floppy drive and I have not formatted a floppy for years ... :) I'm not even sure whether the
drive is still working :roll: Thank you for the report though, I think devtmpfs doesn't automatically create this "special" floppy device
nodes. The floppy formatter program needs to be upgraded to create them on the fly.
Shinobar, do you mind testing this? Rename the fake .gz to floppy-format.sh, chmod +x and put it to /usr/sbin (replacing the original file) and see if you can format a floppy with it?
Sorry for late response. It works :)

But the probepart shows /dev/fd0 twice:

Code: Select all

# probepart | grep fd
/dev/fd0|none|2880
/dev/fd0|none|2880
EDIT: The probepart in the most recent woof is fixed.

Code: Select all

#120602 kernel 3.2.18 major deviance from earlier kernels, /proc/partitions (and /sys/block) now shows /dev/sr0 when no disk.
#       new situation, getting duplicate /dev/sr0 so need 'sort -u'.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Kernel source

#137 Post by shinobar »

BTW, where is the 3.4.2 kernel source?
The fd64-devx_600.sfs has linux-3.3.4.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#138 Post by nooby »

Pardon my naive remark.
A noob would not know about this way to do a direct link to the savefile
in the menu.lst Even I who have read here each day since 2008
did not know about it. And I have at least tested frugal install of Puppy
almost daily following the developers suggestions on many different puppies.

savefile=direct:device:sda1:/fd64b2/fd64save.ext4

I changed it to savefile=direct:device:sda1:/fd64b2/fd64save.ext3
that worked too but needed some consistence at shut down that
maybe a noob will not be aware of.

I have a noob notion that ext3 is safer to use than ext4 due to ext4 less known? First time I used it in all those years of saving a save file :)

so I hope that the noob get instruction to do the savefile=direct:device:sda1:/fd64b2/fd64save.ext4 in an obvious way.
I had to read this thread to find out. Thanks for telling me.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#139 Post by smokey01 »

Guys here is my (legacy) Grub menu.lst

title FatDog 6.00b1
rootnoverify (hd0,2)
kernel /fd64b1/vmlinuz savefile=direct:device:sda3/fd64b1/fd64save.ext4
initrd /fd64b1/initrd

It will not load the savefile from this location.

If I put the savefile in /mnt/home with the below config it works fine.

title FatDog 6.00b1
rootnoverify (hd0,2)
kernel /fd64b1/vmlinuz
initrd /fd64b1/initrd

What am I doing wrong?

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Fatdog64-600b1

#140 Post by ETP »

smokey01 wrote:Guys here is my (legacy) Grub menu.lst

title FatDog 6.00b1
rootnoverify (hd0,2)
kernel /fd64b1/vmlinuz savefile=direct:device:sda3/fd64b1/fd64save.ext4
initrd /fd64b1/initrd

It will not load the savefile from this location.

If I put the savefile in /mnt/home with the below config it works fine.

title FatDog 6.00b1
rootnoverify (hd0,2)
kernel /fd64b1/vmlinuz
initrd /fd64b1/initrd

What am I doing wrong?
Possibly missing a colon after sda3 :)
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

Post Reply