Puppy 4 Beta 2

[Leon]

I must enter an IP of a DNS for the initial configuration (you know the details).

It works for me. At DNS prompt I just pressed Enter.

It is important to test it in Puppy started with pfix=ram, to unpack rp_pppoe_cli-3.8-patched2.tar.gz tarball and to copy the files to their destinations to overwrite all existing rp-pppoe files that are already installed with Puppy.

[oli]

Leon, you are right. Althoug pppoe-setup says you have to enter "server" you must leave it blank. If I enter nothing and press return only everything is fine. So I would suggest that Barry changes the description of pppoe-setup.

One interesting thing with your connectwizard: If I use it with Puppy 2.14 it looks like your screenshot. If I use it with Puppy 4.0 beta it looks like the attached pic (pppoe is already configured and I'm online).

[Leon]

One interesting thing with your connectwizard: If I use it with Puppy 2.14 it looks like your screenshot. If I use it with Puppy 4.0 beta it looks like the attached pic (pppoe is already configured and I'm online).

I uploaded a new version and the installation instructions.

http://www.murga-linux.com/puppy/viewto ... 403#193403

[BarryK]

There may be a problem if you type just the ENTER key instead of "server". It may setup PPPoE not to obtain the nameservers from the ISP.

It still works because I have written the free nameserver to /etc/resolv.conf. But, that's not really the right thing.

Could you check that, start with nothing in /etc/resolv.conf, press just the ENTER key instead of typing "server", and see if it gets the nameservers from the isp.

[Leon]

Could you check that, start with nothing in /etc/resolv.conf, press just the ENTER key instead of typing "server", and see if it gets the nameservers from the isp.

Works fine for me.

Checked with fresh install. At DNS prompt just pressed ENTER.

This is the contents of my /etc/resolv.conf file created after starting internet connection for the first time:

nameserver 193.189.160.13
nameserver 193.189.160.23

This are the nameservers from my ISP.

[Sage]

Please excuse this interjection, Leon, but I need advice about getting CDLinux, the new compact Chinese distro, on line. It won't permit me to save a nameserver (or save anything!) into /etc/resolv.conf and only has PPPoE as an alternative manual setup - we are all PPPoA in the UK. I can enter the IP and GW via the CLI SuperUser, but not the DNS. They don't have a Forum. Appreciate if you or one of the troops could help, please, then I'll delete this item.

[dogone]

So far as I can determine, this problem was first reported in v3.01*. It has persisted through all v4 betas.

Desktop "launchers" created by dragging from Rox-Filer automatically receive the system icon assigned to that MIME type. Users can then edit the launcher and change the icon. These custom icons almost always revert to the MIME default within a couple of reboots. The link to custom icon appears to get lost.

* http://www.murga-linux.com/puppy/viewto ... 378#144954

[oli]

BarryK wrote:
Could you check that, start with nothing in /etc/resolv.conf, press just the ENTER key instead of typing "server", and see if it gets the nameservers from the isp.

To press just ENTER works fine for me. /etc/resolv.conf than gets automatically the nameservers from my ISP.

[rerwin]

Reviewing my notes on minor problems, I will list a few that probably are easy fixes for the final.

1. net-setup.sh has two tests for driver prism2_usb, identifying it as wireless. But prism2_pci is also wireless but not checked for. Should prism2_pci be added to the tests for prism2_usb?

2. Wireless wizard: a title is misspelled as "Wizrd".

3. Wireless wizard: when creating a new profile, selecting "ad-hoc" is ignored if you toggle between "advanced" and "basic. (Fix probably should be deferred)

4. Universal Installer: several mentions (in sanity check) of pup_save.3fs, which should now be pup_save.2fs. Right?
Richard

[Tui]

I have d/l-ed and did a fresh full h/d install. This version looks
good and is being used to post this thread.

The problem I have is that with using a 800x600 res. and a number of
the h/d partitions show up just above the bottom taskbar and after a move
to clear the bar at a position I like. After a re-boot they return to the bottom
position again !

Moving into ROX Filer and "option" cycling thro' to pinboard with setting
the desktop icons to clear the bottom, sides and top by a variable number, sides and top save ok! I think. So its the bottom I want, say set bottom at '40' save as I thought., backed out to close down machine and go into
re-boot mode with the hope that this value would give the clearance
I had hoped. - Not so!

So what am I doing that this value has not been saved ?

Help here please.

Tui

[HairyWill]

There is a bug in init for puppy 3.01, I don't think this has been fixed in dingo. They don't always set PUPMODE=13 for ideflash type installs. There is a fix here:
http://www.murga-linux.com/puppy/viewto ... 681#193681

[Lobster]

Last chance coding . . .

release candidate planned for Friday 2 May

Sunday 4 May
Puppy 4 Final . . .

check Barrys Blog - oh I guess you do

ok and the wiki
http://puppylinux.org/wikka/Puppy4

[John Doe]

oh my, I hope this makes the deadline.

I went nuts with the connection wizard and added (hopefully) usb modem and cellphone support as well as MS VPN support.

still have to fix the 'configure' tab a bit, but it should all work ok. There are a few files under /usr/sbin and the config files for vpn are under /etc/ppp. The vpn wizard overwrites 4 files in there. Two of them have there own names but the other two are ip-up and chap-secrets. Most people don't have anything in those files anyway, but if you do back them up. Very soon, I'll add logic to only edit one section of the files. Rather than overwrite them.

I'd recommend testing this in Beta2 with a pfix=ram boot. Install the pet and then click the connect icon on the desktop.

Also added "ping and traceroute" to the options under the "tools" tab and moved the firewall wizard over there. In addition to adding functionality, I was shooting at making it fit nicely at 640x480.

[FuturePerfect]

Barry:

Have I missed any recent references to a barebones Dingo?

Back in October in your developer blog, you talked about having an official barebones Dingo.

I think this might reduce the size of the Puppy folks need and be of great use to those non-technical people like me who are nervous about trying Unleashed to get a Puppy with less stuff.

Thanks for your consideration of a barebones Dingo now or in an upcoming Dingo release.

[barriew]

This doesn't work in 4.0Beta2 - I think because there is no symlink to smbspool in /usr/lib/cups/backend.

At least this gives the 'Windows Printer via Samba' option in the set up. I still have a problem getting the print to work, but at least this gives the connection option!

Barrie

I now have CUPS printing to my XP printer, despite the error message

Tree Connect failed (NT_STATUS_ACCESS_DENIED)

I think my earlier problems were to do with wireless networking. I have this working, but only by hard coding for my home network. The problem appears to relate to DHCPCD - still investigating.

Barrie

[rerwin]

John Doe,
I applaud your accomplishment in dealing with ACM0 and USB0 USB modems that Puppy does not already detect. However, it is such a major addition to insert into the final puppy 4.00 release that it could compromise the perception of Puppy's straightforward and reliable behavior. It is also risky because there has been no beta testing of it and apparently no integration with the overall modem management function.

It is obvious to me that you and I need to coordinate our efforts. I have just (3.98+) updated the automatic detection of modems at initialization time, so understand the mechanism involved. As I watched the postings about the USB modems, I concluded that we need to add them to the set of modems already detected. But I did/do not have the full information necessary to implement that, yet. Would you consider working with me to get that done.

In response to your request for testers, I tested with my USB modem, a SmartLink USB modem that Puppy already supports at bootup. Your dialog boxes do not take that possibility into account, leaving a confused user. So we have the situation where some USB modems are detected automatically, like PCI modems, and are not represented in your ttyS... options, while others are not detected but let you start them from the desktop. To a user, this appears convoluted and inconsistent.

With that said, I propose that, for all USB modems, we provide both auto-detection when the modem is already plugged in at bootup, as well as the ability to start any of the USB modems after plugging them in as Puppy is running. This could simplify how the user starts a modem, because the auto-detection logic could also be used in usbmodemwizard.

Although I could not get to the "manage" and "link" dialogs (assuming they exist) I do see in the script something implying that the USB modem can be started even though a PCI modem is already detected and announced in pupdial. I think Puppy currently assumes only one modem in use at a time. So allowing a second to somehow pre-empt the PCI modem could be dangerous. I think we need to discuss the ramifications of that and whether it is necessary. We need more development time.

For me to start automating detection of the modems you address, I need to get their vendor and device IDs and the driver names they use. From that we can put the driver modules in the zdrv /lib/(modem) directories for automatic loading, and create modem scripts that do anything specific to the modem type and set the softlink in /dev/modem -- or not, if we implement a safe way of pre-emption. The script may need to run whenever the wizard activates a modem (definitely, for SmartLinks).

Let's see what we can work out for 4.01 or a service pack.
Richard

[djringjr]

Right now I am worried that my 1st hard drive hda1 hasn't been blown up by pmount. It is not showing on the desktop.

I downloaded beta2 and did a md5sum check - and am running as liveCD. The beta2 was useless because of Seamonkey crashing all the time. So I added the new Seamonkey 1.1.9 and did a remaster CD. Seamonkey is now working very very well but some of the other problems remain.


ALSA wizard doesn't complete if you "choose" not to save. Since I didn't save the settings (ALSA wasn't working for me in 3.01), I don't know if it correctly detected my soundblaster card as being preferred to the built-in audio on the motherboard, or even if the config is saved with 4.00 beta2.

Sometimes the desktop disappears, but restarting X seems to fix that. I find that when I click on the icons for the drives that the screen goes black also (desktop disappears).

Many things such as pmount and
other programs make the desktop go black. Seamonkey was very buggy until I replaced it with the latest version of Seamonkey - which works very very well.

Usually icons work the second time they are pressed. The first time they are pressed, the screen comes up for a split second then closes. Also under the command line, the xorg wizard will sometimes work, sometimes not. Seems like the same "Try it twice" that seems to be happening here.

The memory leak that plagued 3.00 and 3.01 seems to be gone. I can open multiple windows of Seamonkey 1.1.9 for hours and the system doesn't crash.

I had used beta1 and it was terrible. This is much better - but if you'd ask me neither of these is beta material - more like alpha material.

Best to all,

djringjr

[djringjr]

My hda1 drive reappeared after I "restart x" but when I return to X, when I resize Seamonkey screen or do anything, the desktop goes to black. Once it is black, the system is stable.

This beta is much better than beta1 which wouldn't even stay running for me. This will run for a long time and with the latest Seamonkey doesn't crash.

Best

[josh.viklef]

I can find on PETget package manager (Official Puppy2 repository) Openoffice 1.1.4 cutdown version. Could you give it to the list, please?

[tempestuous]

EDIT: b43-firmware attachment removed.
Puppy4-2.6.25 already contains this firmware.