Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 21 Apr 2014, 04:10
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Puppy 2.17alpha available
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 6 of 8 [108 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next
Author Message
Wolf Pup

Joined: 27 Apr 2006
Posts: 637

PostPosted: Thu 12 Jul 2007, 00:20    Post subject:  

BarryK wrote:
Perhaps there's some kind of weird interaction with the wifi driver. You could try:
# rmmod rt2570
then fix wvdial.conf,
then try pupdial.


dialup still doesn't work.

_________________

Visit The Repository - Helpful and hard-to-find treats for Puppy 3.
Click Here for Puppy Support Chat, + Helpful Links.
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Thu 12 Jul 2007, 00:23    Post subject:  

On the encryption:

Here's a fellow who got the same error in the 2.6.19 kernel when he compiled without turning on CONFIG_CRYPTO_CBC.

http://lkml.org/lkml/2006/11/29/302

Was that turned on with the new kernel we have in Puppy 2.17?
Back to top
View user's profile Send private message 
John Doe

Joined: 01 Aug 2005
Posts: 1689
Location: Michigan, US

PostPosted: Thu 12 Jul 2007, 00:45    Post subject:  

PaulBx1 wrote:
Was that turned on with the new kernel we have in Puppy 2.17?


looks like it was:

CONFIG_CRYPTO_CBC=m

http://puptrix.org/sources/kernel-2.6.21.5-pup217/DOTconfig-K2.6.21.5-23JUN07-9.20pm
Back to top
View user's profile Send private message 
John Doe

Joined: 01 Aug 2005
Posts: 1689
Location: Michigan, US

PostPosted: Thu 12 Jul 2007, 00:50    Post subject:  

does it need modprobed manually now?

perhaps a result of those "politics" discussed in that one thread long ago.

and this statement:

Quote:
> Shouldn't cryptoloop automatically select CONFIG_CRYPTO_CBC if it depends on it?


just a weird thought....
Back to top
View user's profile Send private message 
Lobster
Official Crustacean


Joined: 04 May 2005
Posts: 15117
Location: Paradox Realm

PostPosted: Thu 12 Jul 2007, 01:06    Post subject:  

The clock is displaying one hour earlier than it should. OK changed it from menu but it is one hour back again (after computer turn off - so could be a battery fault).

I vaguely remember this happening a long time ago but need confimation from other users before can label as bug . . . ah yes the trick was to set the time zone but Puppy has been doing this (from the keyboard choice I guess)
Might be to do with UK summertime? Was OK in 2.16.

Anyone else get this?

_________________
Puppy WIKI
Back to top
View user's profile Send private message Visit poster's website 
Wolf Pup

Joined: 27 Apr 2006
Posts: 637

PostPosted: Thu 12 Jul 2007, 02:40    Post subject:  

Does UK experience Daylight savings like the US?
_________________

Visit The Repository - Helpful and hard-to-find treats for Puppy 3.
Click Here for Puppy Support Chat, + Helpful Links.
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Thu 12 Jul 2007, 03:33    Post subject:  

jeffrey wrote:
By the way all keyboards that I've used in New Zealand are US format, so it would help if rc.country (I think that's the name of the script) could have the "x" changed to "us" for country 60 New Zealand.
Thanks. That's an impressive effort doing everything in a single selection.

Smile I'm reminded of Sir Humphrey Appleby in 'Yes Minister' telling the Minister that "that is a brave decision, Minister". It's very ambitious anyway, trying to put everything in one table, and there's going to be lots of tweaking required, plus some special cases.
Okay, I'll fix the keyboard for New Zealand.
Back to top
View user's profile Send private message Visit poster's website 
kirk

Joined: 11 Nov 2005
Posts: 1365
Location: florida

PostPosted: Thu 12 Jul 2007, 11:00    Post subject:  

Couple of problems with ext2/ext3:

I have these pup_save files from playing with 217a:

1) pup_save.2fs
2) pup_save.2fs-1.3fs
3) pup_save_crypta-217a.3fs

These are all on an ext3 partition. The #2 save file was named that way because the #1 save file already existed. Looking at rc.shutdown, I thought that saving on an ext3 partition would result in an ext3 pup_save file. When booting #1 and #2 above, fsck is ran on both.

The #3 encrypted save file is mounted as ext2 by init (line #754) and no fsck is done. Maybe it's remounted later as ext3?

I'd like to see us go back to all ext3, especially with the clean shutdown problem, But that's another story.

PS: Thanks for fixing the encryption problem! (see blog)
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Thu 12 Jul 2007, 11:50    Post subject:  

Wow, that file #2 was obviously named wrong. Bug in rc.shutdown!

<later> I took a look at rc.shutdown and at line 350 found this:
Code:
local BLA=1 #; local SFFIX=`echo "$SAVEFILE" | tail -c 5`


Problem is, the variable "SFFIX" is not used anywhere else.

That code about choosing the filename is, well, kinda tortured. Smile Seems like the way to do it is to break it into pieces - directory, name, extension. Then go through figuring what each piece should be, and finally at the bottom, reassemble the pieces into the full name, adding that "bla" thing between name and extension.

If you want my opinion, you should simply lay out what the two choices (2fs vs 3fs) are, what the reasoning is behind them, and then let the user choose. At the bottom say, "if you aren't sure, pick 2fs". Very Happy

I also noticed the variable "PCHOOSE" is never initialized to "no".

I have a couple more:

1) If xvesa is selected and I pick the default screen resolution (I think 640x480), then the windows, for example the browser with the welcome message, are too large for the screen. Maybe this is normal...

2) You replaced TkDiff with IIRC Xdiff. Bad move in my opinion. TkDiff is very intuitive, Xdiff such a mess that I finally gave up trying to get it to work. It may be that Xdiff actually is more capable, once you get to know it, but most people I think don't want to invest a lot of time in a program like that. They just want to find the differences in two files, right now. TkDiff was great for that; please don't dump it! Crying or Very sad

3) I went to create a lite encrypted pup_save when shutting down. In the final sanity check it says to hit ESC key if something is not right. I did that just to see what would happen, and it simply shut down without creating the pup_save. I thought it was going to go back and let me modify something.

4) Also I noticed there was no way to tell it what file type, 2fs or 3fs, you wanted for the pup_save. I think 2fs is the correct default but do we want to force people to use that? There is that utility kirk and I cooked up to change from one to the other, but that is an extra step that people have to know, and anyway it is not included in standard Puppy.

5) In the shutdown you use "x" to designate light encrypted files ("density") and "a" to designate heavy encrypted files. But in init you only look for "x" and assume anything else is heavy encrypted. There is a possibility that we may have loop-aes or dmcrypt in the future, which means more indicators. Right now, having no indicator after "crypt" is treated as heavy encryption. I'm not sure where I am going with this, but maybe there should be more documentation on this point; for example, in rc.shutdown just say that the indicator should be "a" or "x" and if the filename does not meet that specification it is not accepted. People should know what constraints there are in renaming pup_saves. I didn't know why the "a" appeared in the filename when I tried creating a new one.
Back to top
View user's profile Send private message 
Gschipps

Joined: 08 Jun 2007
Posts: 2

PostPosted: Thu 12 Jul 2007, 17:11    Post subject: Clock early one hour
Subject description: time wrong
 

I also have noticed that my normal HD install of 2.17RC1 on my laptop Dell CPX 450Mhz has the time resetting 1 hour too early upon every reboot. I like this OS. It makes this older equipment imminently more usable. i also have it on an 333Mhz w/128Mb RAM. I like it. Enough software to do what I do with a confuseser. Man- I wish I could fix that double-repeat problem, though! Good thing I am not a fast typist, any way. bettere stop rambling. thanks for the work on this, guys/gals.

Greg, in West Michigan
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Thu 12 Jul 2007, 20:30    Post subject:  

Oh, one other point. Is it true that encrypted pupsaves never get automatically fsck'ed? I know that doing it every time was awful slow, but doing it never might be going too far in the other direction.
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Thu 12 Jul 2007, 20:45    Post subject:  

PaulBx1 wrote:
Wow, that file #2 was obviously named wrong. Bug in rc.shutdown!

<later> I took a look at rc.shutdown and at line 350 found this:
Code:
local BLA=1 #; local SFFIX=`echo "$SAVEFILE" | tail -c 5`


Problem is, the variable "SFFIX" is not used anywhere else.

That code about choosing the filename is, well, kinda tortured. Smile Seems like the way to do it is to break it into pieces - directory, name, extension. Then go through figuring what each piece should be, and finally at the bottom, reassemble the pieces into the full name, adding that "bla" thing between name and extension.

If you want my opinion, you should simply lay out what the two choices (2fs vs 3fs) are, what the reasoning is behind them, and then let the user choose. At the bottom say, "if you aren't sure, pick 2fs". Very Happy

I also noticed the variable "PCHOOSE" is never initialized to "no".

I have a couple more:

1) If xvesa is selected and I pick the default screen resolution (I think 640x480), then the windows, for example the browser with the welcome message, are too large for the screen. Maybe this is normal...

2) You replaced TkDiff with IIRC Xdiff. Bad move in my opinion. TkDiff is very intuitive, Xdiff such a mess that I finally gave up trying to get it to work. It may be that Xdiff actually is more capable, once you get to know it, but most people I think don't want to invest a lot of time in a program like that. They just want to find the differences in two files, right now. TkDiff was great for that; please don't dump it! Crying or Very sad

3) I went to create a lite encrypted pup_save when shutting down. In the final sanity check it says to hit ESC key if something is not right. I did that just to see what would happen, and it simply shut down without creating the pup_save. I thought it was going to go back and let me modify something.

4) Also I noticed there was no way to tell it what file type, 2fs or 3fs, you wanted for the pup_save. I think 2fs is the correct default but do we want to force people to use that? There is that utility kirk and I cooked up to change from one to the other, but that is an extra step that people have to know, and anyway it is not included in standard Puppy.

5) In the shutdown you use "x" to designate light encrypted files ("density") and "a" to designate heavy encrypted files. But in init you only look for "x" and assume anything else is heavy encrypted. There is a possibility that we may have loop-aes or dmcrypt in the future, which means more indicators. Right now, having no indicator after "crypt" is treated as heavy encryption. I'm not sure where I am going with this, but maybe there should be more documentation on this point; for example, in rc.shutdown just say that the indicator should be "a" or "x" and if the filename does not meet that specification it is not accepted. People should know what constraints there are in renaming pup_saves. I didn't know why the "a" appeared in the filename when I tried creating a new one.

Quote:
2) pup_save.2fs-1.3fs

...I have never got naming like that!
2) It's Xfdiff, not Xdiff.
Back to top
View user's profile Send private message Visit poster's website 
kirk

Joined: 11 Nov 2005
Posts: 1365
Location: florida

PostPosted: Thu 12 Jul 2007, 21:21    Post subject:  

Quote:
Oh, one other point. Is it true that encrypted pupsaves never get automatically fsck'ed? I know that doing it every time was awful slow, but doing it never might be going too far in the other direction.


I havn't saw any speed difference between encrypted and non-encrypted. Fsck takes a while if you have a lot of files in your pup_save. If it's fairly empty then it's real fast. Rebuild all of the kernel modules or do somthing else that puts thousands of files in your pup_save and reboot, you'll see. You'll spend more time with fsck than the rest of the boot process. That's why journaling was invented Very Happy
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Fri 13 Jul 2007, 00:42    Post subject:  

In re-reading my comments, I realize they sounded a little overboard. Sorry about that, no excuse for it.
Back to top
View user's profile Send private message 
John Doe

Joined: 01 Aug 2005
Posts: 1689
Location: Michigan, US

PostPosted: Fri 13 Jul 2007, 01:17    Post subject:  

Lobster wrote:
The clock is displaying one hour earlier than it should....

Anyone else get this?


Yes. Me2. GMT -5 in DST (EST-Eastern Standard Time)

Do you have Daylight Saving Time also? or is it just all together off by 1 hour?
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 6 of 8 [108 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0984s ][ Queries: 13 (0.0179s) ][ GZIP on ]