Firstrun-2.2 (Country Settings and more)
firstrun-1.9.5
I am not sure whether this firstrun still needs to survive when the Barry's Quicksetup is already out. But i made an update focusing speed up in lauching dialogue.
Test release: firstrun-1.9.5.pet. See the top post.
Note:
Older versions did not show all languages but only the ones the current font can display.
This new version shows all language codes which puppy potentially supports. But some language names are not readable beacuase of the font is not available.
You need to install those font before you select such a langage.
Test release: firstrun-1.9.5.pet. See the top post.
Note:
Older versions did not show all languages but only the ones the current font can display.
This new version shows all language codes which puppy potentially supports. But some language names are not readable beacuase of the font is not available.
You need to install those font before you select such a langage.
Last edited by shinobar on Tue 29 Nov 2011, 21:52, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Hello shinobar
Seems to work nicely
I have a custom pinstall.sh that I use with firstrun-1.9 and previous that fixes the symlinks when installing firstrun from "woof" build system previous to November 2011.
However, since Barry has added "quicksetup" as a part of "woof" all the DOTdesktop files have changed. What I can do is modify the pinstall.sh to remove or patch all the "quicksetup" stuff and then firstrun get's priority. Of course woof users, you must modify the /usr/sbin/delayedrun script to call this firstrun. I fear that "quicksetup" is well entrenched in things like "video-wizard" so I will need to make patches for all apps that "quicksetup" affects and restore "firstrun".
When I have it working well I will publish the custom pinstall.sh here for developers.
Cheers
Seems to work nicely
I have a custom pinstall.sh that I use with firstrun-1.9 and previous that fixes the symlinks when installing firstrun from "woof" build system previous to November 2011.
However, since Barry has added "quicksetup" as a part of "woof" all the DOTdesktop files have changed. What I can do is modify the pinstall.sh to remove or patch all the "quicksetup" stuff and then firstrun get's priority. Of course woof users, you must modify the /usr/sbin/delayedrun script to call this firstrun. I fear that "quicksetup" is well entrenched in things like "video-wizard" so I will need to make patches for all apps that "quicksetup" affects and restore "firstrun".
When I have it working well I will publish the custom pinstall.sh here for developers.
Cheers
Puppy Linux Blog - contact me for access
Re: firstrun-1.9.5
Yes please do make it 'survive'.. I always use Firtsrun, which is better (IMHO) and more mature, supporting a wider variety of puppies... Also you might need or want to port some upgrades from Barrys QuickSetup in the future... or vice vera...shinobar wrote:I am not sure whether this firstrun still needs to survive when the Barry's Quicksetup is already out. But i made an update focusing speed up in launching dialogue.
Will try it out soonTest release: firstrun-1.9.5.pet. See the top post.
Actually, I am using Firstrun 1.8.2 in 'Akita Linux' and can still see some language names in the list (such as japanese, chinese, others) seem not to be supported by the default system font in Akita (Ubuntu-Light)... But Arabic, Russian and others display OK - it is mainly the Asian fonts that do not display correctly.Older versions did not show all languages but only the ones the current font can display. This new version shows all language codes which puppy potentially supports. But some language names are not readable becuase of the font is not available.
I prefer to have all languages listed (like I do now), so i would like to know:
...where can I get japanese, thai, chinese, fonts from? Ideally with a small filesize?You need to install those font before you select such a langage.
- Attachments
-
- lang-list.png
- (26.8 KiB) Downloaded 1214 times
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Re: firstrun-1.9.5
Hi Shinobar.shinobar wrote:I am not sure whether this firstrun still needs to survive when the Barry's Quicksetup is already out. But i made an update focusing speed up in launching dialogue.
I had sent you a PM on this in the past. This product of yours needs to survive. It currently is the only single screen utility that we have. As Puppy matures into the LAN arena as it has over the past 18 months, this single screen approach for localization is a mainstay.
It also provide a single point where users can easily (via Menu>Settings) come back to in order to update or change those localization settings. this is important if you travel to other areas of the world. Its also very important should anyone need to change the station's name when necessary. It a single place that provide an excellent at a glance UI.
Barry has a good tool, but its approach is different and the components are broken apart. Your tool keeps all of the components along with its information in eye's view.
This has become an important tool for, not just distro developers, but most of all for the USERS!
Your work and the contributions of others has created a very stable tools that has addressed all of its aspects for localization. its easy to understand and its very easy to use.
Please do not abandon us on this. It currently is the best tool for startup and easy understand for simple users, as well. We need this tool.
Ok, here is the pinstall.sh for woof
Note that in a non-woof install (even with the current script in 1.9.5) the chooselocale symlink to Barry's quicksetup is not removed so quicksetup is still called.
Note that in a non-woof install (even with the current script in 1.9.5) the chooselocale symlink to Barry's quicksetup is not removed so quicksetup is still called.
Code: Select all
#!/bin/sh
#firsrun pinstall.sh
#=================== check if running from woof =========================
if [ ! "`pwd`" = "/" ];then
echo "Configuring first start wizard"
QSPROG="countrywizard.qs"
#[ -s $QSPROG ] || exit
#rm -f ./tmp/firstrun 2>/dev/null
for P in ./usr/sbin/countrywizard ./usr/sbin/xrandrshell ./usr/sbin/timezone-set ./usr/sbin/quicksetup; do
[ -s $P -a ! -L $P ] && cp -f $P $P.org
rm -f $P
ln -sf $QSPROG $P
done
#remove Barry's QuickSetup
[ -f ./usr/share/applications/QuickSetup.desktop ] && rm -f ./usr/share/applications/QuickSetup.desktop
#================== end woof ==========================================
else
#================= v 1.9.5 ==========================================
QSPROG=/usr/sbin/countrywizard.qs
[ -s .$QSPROG ] || exit
rm -f ./tmp/firstrun
for P in /usr/sbin/countrywizard /usr/sbin/xrandrshell; do
[ -s .$P -a ! -L .$P ] && cp -f .$P .$P.org
rm -f .$P
ln -sf $QSPROG .$P
done
# some old version (Puppy-4.2x etc) corrupts by the comment line
if grep -q '#.*LANG=' ./etc/profile; then
sed -e 's/#.*LANG=/#LANG:/g' ./etc/profile > /tmp/profile
[ -s /tmp/profile ] && mv -f /tmp/profile ./etc/profile
fi
# LupQ has extralang conflicts with firstrun # v1.9 removed extralang
#[ -x ./root/Startup/extralang -a -x ./root/Startup/fullstart ] && chmod -x ./root/Startup/extralang
# v1.9: remove old /root/Startup/fullstart, now renamed root/Startup/firstrun
OLDFILE=/root/Startup/fullstart
rm -f ."$OLDFILE"
#================= end 1.9.5===========================================
fi
[quote][/quote]
Puppy Linux Blog - contact me for access
Re: pinstall.sh
Tnx micko. Will merge at next update.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
unifont
You can find them in the lang_pack_all.sc0ttman wrote:...where can I get japanese, thai, chinese, fonts from? Ideally with a small filesize?
http://www.murga-linux.com/puppy/viewtopic.php?t=51702
- M+1P+IPAG.ttf 1.9M ... Japanese only
- wqy-microhey.ttf 5M ... Chinese, Japanese and Korean, no thai
- unifont.ttf 16M ... univasal including CJK and thai
Well, need some files are needed to support ko_KR and zh_CN locale.
That is /usr/share/i18n/locales/transit_cjk_variant_compat and iso14651_t1_pinyn you can find in the lang_pack_all.
i am not sure on thai but may need libthai components in /usr/lib and /usr/share/libthai for input.
These components are not essencial if you only want to read them.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Hi Shinobar
Please make it obvious that you are offering a single Page "FirstRUN" and a double_page FirstRUN here. Right now you are showing a double page version which is not the version that distro owners are offering for user to see at boot.
Personally, I'm still in favor of the very simple approach of a single-page FirstRUN.
Hope this helps all.
Please make it obvious that you are offering a single Page "FirstRUN" and a double_page FirstRUN here. Right now you are showing a double page version which is not the version that distro owners are offering for user to see at boot.
Personally, I'm still in favor of the very simple approach of a single-page FirstRUN.
Hope this helps all.
- Attachments
-
- 1.png
- (78.53 KiB) Downloaded 997 times
Last edited by gcmartin on Wed 21 Dec 2011, 01:44, edited 1 time in total.
UPDETE: v1.9.6
v1.9.6: UTF-8 on main dialog(tnx to zigbert)
Refreshed pinstall.sh but 01micko reports it has still problem with recent woof install. The distributer need to correct them by hand.
Refreshed pinstall.sh but 01micko reports it has still problem with recent woof install. The distributer need to correct them by hand.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
hostname
Hi Shinobar
Since your introduction with your FirstRUN it has become a startup "statue" to single screen localization as many have taken advantage of your design.
As a result, some, many, most new Pups from Puppyland have tended to adopt or attempt duplication of FirstRUN, alias "Personalize Settings".
Because of this all 64bit and several 32bit PUPs will boot from CD all the way to desktop to complete localization versus stopping at text mode screens before getting to desktop.
One of the great benefits to your effort has been for users to set the local PC's name (hostname).
Here's an issue that I think FirstRUN can make consistent in its implementation for all in Puppyland. And, I'll begin by stating the issue and sharing who has addressed it, individually and perhaps differently.
Issue: Setting of the hostname properly in ALL system fields for system/subsystem application use. There are actually 5 system parms/fields that reflect the hostname. I see these by executing the following commands
# hostname
Slacko-LaptopP3
# echo $HOSTNAME
Slacko-LaptopP3
# cat /etc/hosts
127.0.0.1 localhost Slacko-LaptopP3
192.168.1.1 pc2
192.168.1.2 pc3
192.168.1.3 pc4
# cat /etc/hostname
Slacko-LaptopP3
I had found that is the cases where FirstRUN is being used, it was important to exit the desktop and issue a logout before restarting the desktop via xwin.
This is evidence that shows what FirstRUN provides during its operation after initial system start.
But, here's the problem. The above shows ALL fields to be set properly, resulting from it being changed in FirstRUN, But, there is some in-memory remnants of the original hostname that remain for system use UNTIL A LOGOUT OCCURS! When a logout occurs, then all in-memory as well as these above parms are properly set for any system/subsystem/application use as it carries out operations on behalf of the user.
So, my question is as following
Can/should/would FirstRUN address the hostname issue by a "logout and xwin restart" whenever a hostname change is entered in the hostname field of FirstRUN.
If this is done, the total community benefits because there will be a consistent fashion for handling of desktop startup for all distro builders and users, alike.
Please weigh a practical solution for this in FirstRUN. And, please keep in mind that a logout seems be a key ingredient of proper settings for all hostname fields.
Also, remember that 01Micko, Playdayz, and TaZoC have addressed this...but in different ways. A common approach would remove the need for specific, independent designs to address this issue.
In summary, i feel that should any user use FirstRun to set/reset the PC's name (hostname), some utility (FirstRUN) should schedule an immediate Logout and restart of the desktop when the OK button is clicked in FirstRUN.
Thanks in advance.
Since your introduction with your FirstRUN it has become a startup "statue" to single screen localization as many have taken advantage of your design.
As a result, some, many, most new Pups from Puppyland have tended to adopt or attempt duplication of FirstRUN, alias "Personalize Settings".
Because of this all 64bit and several 32bit PUPs will boot from CD all the way to desktop to complete localization versus stopping at text mode screens before getting to desktop.
One of the great benefits to your effort has been for users to set the local PC's name (hostname).
Here's an issue that I think FirstRUN can make consistent in its implementation for all in Puppyland. And, I'll begin by stating the issue and sharing who has addressed it, individually and perhaps differently.
Issue: Setting of the hostname properly in ALL system fields for system/subsystem application use. There are actually 5 system parms/fields that reflect the hostname. I see these by executing the following commands
# hostname
Slacko-LaptopP3
# echo $HOSTNAME
Slacko-LaptopP3
# cat /etc/hosts
127.0.0.1 localhost Slacko-LaptopP3
192.168.1.1 pc2
192.168.1.2 pc3
192.168.1.3 pc4
# cat /etc/hostname
Slacko-LaptopP3
I had found that is the cases where FirstRUN is being used, it was important to exit the desktop and issue a logout before restarting the desktop via xwin.
This is evidence that shows what FirstRUN provides during its operation after initial system start.
But, here's the problem. The above shows ALL fields to be set properly, resulting from it being changed in FirstRUN, But, there is some in-memory remnants of the original hostname that remain for system use UNTIL A LOGOUT OCCURS! When a logout occurs, then all in-memory as well as these above parms are properly set for any system/subsystem/application use as it carries out operations on behalf of the user.
- TaZoC solved it one way
- Playdayz solved it a different way
- 01Micko solved it in a different way
So, my question is as following
Can/should/would FirstRUN address the hostname issue by a "logout and xwin restart" whenever a hostname change is entered in the hostname field of FirstRUN.
If this is done, the total community benefits because there will be a consistent fashion for handling of desktop startup for all distro builders and users, alike.
Please weigh a practical solution for this in FirstRUN. And, please keep in mind that a logout seems be a key ingredient of proper settings for all hostname fields.
Also, remember that 01Micko, Playdayz, and TaZoC have addressed this...but in different ways. A common approach would remove the need for specific, independent designs to address this issue.
In summary, i feel that should any user use FirstRun to set/reset the PC's name (hostname), some utility (FirstRUN) should schedule an immediate Logout and restart of the desktop when the OK button is clicked in FirstRUN.
Thanks in advance.
-
- Posts: 130
- Joined: Fri 23 Dec 2011, 09:21
- Location: The Little Red Dot
Downloaded the firstrun-1.9.6.pet which is actually a .gz file, i.e firstrun-1.9.6.gz(not tar.gz).
XArchive in Slacko 531 couldn't recognize or didn't support the format and therefore unable to extract the file.
Tried using the older Xarchiver (xarchiver-0.5.2-i386-v4.pet), also to no avail.
Please advise. Thank you
XArchive in Slacko 531 couldn't recognize or didn't support the format and therefore unable to extract the file.
Tried using the older Xarchiver (xarchiver-0.5.2-i386-v4.pet), also to no avail.
Please advise. Thank you
Re: hostname
I think it need not.gcmartin wrote:In summary, i feel that should any user use FirstRun to set/reset the PC's name (hostname), some utility (FirstRUN) should schedule an immediate Logout and restart of the desktop when the OK button is clicked in FirstRUN.
See my post:
http://www.murga-linux.com/puppy/viewto ... 667#604667
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
xinerama, dual screens
I have a problem once I have enabled 2 screens through the "Nvidia Settings" program...
See screenshot.. List of resolutions not working.
Current resolution is apparently 'Choices'!
EDIT: I see some duplicate info in my xorg.conf, the 'driver'....
Here is my xorg.conf (old style, version 7.3)
See screenshot.. List of resolutions not working.
Current resolution is apparently 'Choices'!
EDIT: I see some duplicate info in my xorg.conf, the 'driver'....
Here is my xorg.conf (old style, version 7.3)
Code: Select all
......stuff
....
...
Section "Monitor"
#DisplaySize 300 230 # mm
### Comment all HorizSync and VertRefresh values to use DDC:
#UseModes "Modes0" #monitor0usemodes
Identifier "Monitor0"
VendorName "Unknown"
ModelName "LG L1520B"
HorizSync 30.0 - 63.0
VertRefresh 56.0 - 75.0
Option "DPMS"
Option "PreferredMode" "1024x768"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 30.0 - 63.0
VertRefresh 56.0 - 75.0
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "HWcursor" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "ShadowFB" # [<bool>]
#Option "UseFBDev" # [<bool>]
#Option "Rotate" # [<str>]
#Option "VideoKey" # <i>
#Option "FlatPanel" # [<bool>]
#Option "FPDither" # [<bool>]
#Option "CrtcNumber" # <i>
#Option "FPScale" # [<bool>]
#Option "FPTweak" # <i>
#Option "DualHead" # [<bool>]
Driver "vesa" #card0driver
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV34 [GeForce FX 5200]"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX 5200"
BusID "PCI:2:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce FX 5200"
BusID "PCI:2:0:0"
Screen 1
EndSection
Section "Screen"
# Removed Option "TwinView" "1"
# Removed Option "metamodes" "CRT: 1024x768 +0+0, TV: nvidia-auto-select +1024+0"
Identifier "Screen0"
Device "Videocard1"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT: 1024x768 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Videocard0"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "TV: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
- Attachments
-
- screeny1.png
- (35.4 KiB) Downloaded 768 times
Last edited by sc0ttman on Mon 12 Mar 2012, 17:44, edited 2 times in total.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]
Note to Shinobar
I did an experiment to switch the "OpenWith' folder
from an English version to a German version
automaticlly.
I used Lazy since it has a lot of right click menu items and is mainly German.
http://murga-linux.com/puppy/viewtopic. ... a83#610425
Note that your recent version of Firstrun 1.9.6 isn't totally
compatible but I'm sure that a little work will it compatible.
_____________________________________________________-
I did an experiment to switch the "OpenWith' folder
from an English version to a German version
automaticlly.
I used Lazy since it has a lot of right click menu items and is mainly German.
http://murga-linux.com/puppy/viewtopic. ... a83#610425
Note that your recent version of Firstrun 1.9.6 isn't totally
compatible but I'm sure that a little work will it compatible.
_____________________________________________________-
Firstrun-1.9.9
http://shino.pos.to/linux/puppy/
Firstrun-1.9.9 is intended to be compatible with recent woof, but recommended to work with next setup tools:
Firstrun-1.9.9 is intended to be compatible with recent woof, but recommended to work with next setup tools:
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
rc.country
The rc.country is removed from the firstrun-1.9.9 because it is updated in woof hard to follow up. As for old puppies, I am not sure but maybe no significant problem occurs even with old rc,country.pemasu wrote:I believe above is the reason that /etc/rc.d/rc.country has been left out which was included in 1.9.6 ?Firstrun-1.9.9 is intended to be compatible with recent woof, but recommended to work with next setup tools:
The sfs_load needs to load the language packages if they are provided as a sfs. The sfs_load works better with pupsaveconfig for the RAM modes.
Getflash is preferable to avoid the delayedrun offers to download flashplayer when the first setup GUI is running. But you are better to modify the delayedrun itself.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
firstrun and the console font
Additional note on the firstrun-1.9.9.
The firstrun(countrywizard.qs) does not handle the console fonts (same as the old versions of the firstrun). I have tested Racy-5.2.2.8 and I am not sure the console fonts works with no problem on Puppy.
The firstrun(countrywizard.qs) does not handle the console fonts (same as the old versions of the firstrun). I have tested Racy-5.2.2.8 and I am not sure the console fonts works with no problem on Puppy.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Shino,
Seems you uploaded just the firstrun-2.0 directory, not the pet.
Also, concerning the pinstall.sh, what happens if this is installed in the woof build system the pinstall may act on the running host system, best to add a test to see how we are installing.
Seems you uploaded just the firstrun-2.0 directory, not the pet.
Also, concerning the pinstall.sh, what happens if this is installed in the woof build system the pinstall may act on the running host system, best to add a test to see how we are installing.
Code: Select all
if [ "$(pwd)" = "/" ];then
(the pinstall code goes here)
fi
Puppy Linux Blog - contact me for access