Re: [indiana-discuss] Keyboard mapping with different language
Hi Jasse, If /etc/X11/xorg.conf exists in you system; you can simply modify it by changing the following: Option XkbLayout se with the following: Option XkbLayout us If /etc/X11/xorg.conf does not exist; you can add the following line at the end of the file: /etc/default/kbd LAYOUT=US-English Regards, Jasse Jansson wrote: When I installed oso2008.11 I had to choose Swedish to get the right keyboard mapping, and that's fine. But I want English language for everything else. With Solaris 10 I got different choices for keyboard and language and I miss that opportunity. Now I have to change that every time I log in, but I want i set permanently, but I can't find anywhere to change it and I don't know where to start search for the answer. Pinters in the right direction are appreciated. Kaiser Jasse -- Authorized Stealth Oracle The axioms of wisdom: 1. Go the SPARC way of life 2. You can't conquer the universe without the knowledge of FORTRAN 3. In the Unix realm, 10% of work fixes 90% of the problems ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss -- Javier Acosta ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Keyboard mapping with different language
Thanks, but that will change the keyboard mapping, right. I want to use the Swedish keyboard but English language in the login screen and menues and such. On Jan 26, 2009, at 11:36 AM, Javier Acosta wrote: Hi Jasse, If /etc/X11/xorg.conf exists in you system; you can simply modify it by changing the following: Option XkbLayout se with the following: Option XkbLayout us If /etc/X11/xorg.conf does not exist; you can add the following line at the end of the file: /etc/default/kbd LAYOUT=US-English Jasse Jansson wrote: When I installed oso2008.11 I had to choose Swedish to get the right keyboard mapping, and that's fine. But I want English language for everything else. With Solaris 10 I got different choices for keyboard and language and I miss that opportunity. Now I have to change that every time I log in, but I want i set permanently, but I can't find anywhere to change it and I don't know where to start search for the answer. Pointers in the right direction are appreciated. Kaiser Jasse -- Authorized Stealth Oracle The axioms of wisdom: 1. Go the SPARC way of life 2. You can't conquer the universe without the knowledge of FORTRAN 3. In the Unix realm, 10% of work fixes 90% of the problems ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Cannot activate BE
Hi Sebastien, I've outlined steps below to help you recovery from the label problem. Make sure you can boot from the primary disk, c4t0d0s0, before you begin. I've reproduced these steps correctly on my Nevada, build 104 system because my OpenSolaris system doesn't have two disks. An easier recovery might be to just relabel the disk while it is still part of the root pool. I'm not sure how ZFS will react if the disk label is changing while the disk is still part of the pool. That's a test for another day... :-) Cindy 1. Make sure the system is currently bootable from c4t0d0s0. 2. Detach the second disk, c4t1d0s2, like this: # zpool detach rpool c4t1d0s2 3. Convert the existing EFI label on the disk to VTOC (SMI). # format -e c4t1d0s2 format label [0] SMI Label [1] EFI Label Specify Label type[1]: 0 Auto configuration via format.dat[no]? Auto configuration via generic SCSI-2[no]? format q Make sure all the disk space is in s2 or recreate it in s0. The relabeling process might go back to the default sizing so check to see that all the disk space is where you want it. (Write me offline if you need help with this step.) 4. Reattach the disk, c4t1d0s2, like this: # zpool attach rpool c4t0d0s0 c4t1d0s2 5. Wait for the newly attached disk to resilver completely by using zpool status to watch the progress. 6. Install the bootblock on the newly attached disk. # installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c4t1d0s2 7. Confirm that you can boot from c4t1d0s2. Sébastien Stormacq wrote: Hello, I tried that already format shows only a Solaris partition. I did label the disk too but r...@yajug:~# zpool attach rpool mirror c4t1d0 cannot label 'c4t1d0': EFI labeled devices are not supported on root pools. Seb --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:42, Evan Layton wrote: Try running format, choose that disk, run fdisk and remove the EFI fdisk partition and create a Solaris partition. Then in format label the disk. -evan Sébastien Stormacq wrote: OK will try this Any suggestion to repartition ? I can't remind the exact errors but it seems that fdisk is not happy at all with the EFI partition :-( thanks --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:26, Evan Layton wrote: On Jan 23, 2009, at 3:15 PM, Sébastien Stormacq sebastien.storm...@sun.com wrote: Evan, Using BE_PRINT_ERR=true (instead of 1 ;-) gives one more line that point to the error s...@yajug:~# beadm activate opensolaris-1 be_do_installgrub: installgrub failed for device c4t1d0s2. c4t1d0s2 is a mirror in my zpool s...@yajug:~# zpool status pool: rpool state: ONLINE scrub: resilver completed after 0h4m with 0 errors on Wed Jan 21 13:57:10 2009 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c4t0d0s0 ONLINE 0 0 0 23.9M resilvered c4t1d0s2 ONLINE 0 0 0 4.16G resilvered errors: No known data errors I did not install grub (yet) on the second disk Actually, I had a whole bunch of issues to include that disk in the mirror because it is EFI partitioned Any suggestion ? EFI labeled disks are not supported for root pools. The only thing I can suggest is to remove that device from the pool and remove the EFI labeled partition, create a solaris fdisk partition (vtoc) and re-attach the device. -evan Thanks for your help --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:11, Evan Layton wrote: Sébastien Stormacq wrote: Hello, I installed OpenSolaris 2008.11 on a Sun v40z machine. Unfortunately the build I use, although being 101b was not the latest one, i.e. it was a couple of hours before GA : Sun Microsystems Inc. SunOS 5.11 snv_101b November 2008 I tried to update to GA with image-update r...@yajug:~# pkg list -u NAME (AUTHORITY) VERSION STATE UFIX entire0.5.11-0.101 installed u--- r...@yajug:~# pkg image-update PHASEACTIONS Update Phase 1/1 PHASE ITEMS Reading Existing Index 9/9 Indexing Packages1/1 pkg: unable to activate opensolaris-1 r...@yajug:~# beadm activate opensolaris-1 Unable to activate opensolaris-1. Unknown external error. How can I further diagnose / solve this ?? Can you set export BE_PRINT_ERR=true before running beadm activate and send the debug output? That should help narrow down where the problem is. Thanks, -evan I followed the same procedure with the same image on a couple of VMs and it was always
Re: [indiana-discuss] OpenSolaris 2008.11 hangs in hald daemon
Sriram, Since you mention that everything was going fine and then problems started to occur, is it possible that you have some hardware issues ? Is there anything in /var/adm/messages that could provide a clue ? Can you run zpool status and zpool scrub to see if everything is fine ? -Sanjay On 01/24/09 16:15, Sriram Natarajan wrote: Hi I even tried image updating to build 105 and tried to boot normally. Still , I get a same error where in all services are keep getting killed. the last service I see is svc.startd[7]: system/hal:default failed fatally: transition to maintenance and before this all other services like ogl-select, pkg/update, ssh etc are all failed due to signal KILL I wonder why system does not enter system maintenance mode and provide me with a shell . keep seeing messages like requesting system maintenance mode and even asks for user name and password. but I never get a login shell Any help in how to get this system back online will be much much appreciated. I feel handicapped without my primary desktop working successfully. Note: when I tried to boot in single user mode and try to look at service logs for service like hal etc , there is nothing useful that I can find to tell me what the problem is. - sriram Sriram Natarajan wrote: Phi Tran wrote: Sriram Natarajan wrote: Phi Tran wrote: Hi, Where exactly does the system hang? When you try to login to gnome? BTW, hald will not run in single user mode because it depends on dbus and dbus is not running. In normal boot mode, the system hangs way before then - does not even start X server. in fact, system goes into a infinite loop where in all services are continuously killed (I get some message like timeout , killed contract etc..) In single user mode, I started enabling various services including milestone/multi-user-server and then also enabled dbus service before proceeding to enable hal. svcs -xv did not report error that some dependent service is not running but only reported that service did not start successfully and what it seems to me that the service timed out (600) seconds . It's hard to tell what state you put the system in and I don't know if it's correct for single user mode. What are the services you started in single user mode? I kept adding services until all its dependents are resolved. From your paragraph about services being killed, do the logs show you anything? nothing useful except that they are killed (timeout) - almost every service (even service like http:apache22) is getting killed in normal startup mode.. - Sriram Phi - Sriram Phi Sriram Natarajan wrote: Hi I was successfully working with OpenSolaris 2008.11 (upgraded from 2008.05) on my Ultra-40 workstation for quite some time now. Not sure, what caused it - but my system is unable to boot successfully since last week end. Long story short - I got the system in single user mode and found that the system does not come up because of system/hal daemon. So, when I tried to start this daemon (as given below) from a single user mode (af course - after starting all its dependent services ..) /usr/lib/hal/hald --daemon=no --verbose=yes I see this is where the daemon is hanging.. /usr/lib/hal/hald-probe-storage exited hald_dbus.c:4278: unregistered.. Any ideas on how to resolve this further will be much appreciated.. - Sriram ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] OpenSolaris 2008.11 hangs in hald daemon
Sanjay Nadkarni wrote: Sriram, Since you mention that everything was going fine and then problems started to occur, is it possible that you have some hardware issues ? Is there anything in /var/adm/messages that could provide a clue ? Can you run zpool status and zpool scrub to see if everything is fine ? I just checked /var/adm/messages and I find that hald failed with exit status 95. I have already checked out zpool scrub and zpool status. no errors are reported. The hardware seems to be running fine. I am able to get opensolaris booted with a livecd again. but unable to start from the installed hard disk. I very much hate to go through the process of (re) installation. well, what is more frustrating is that the system fails to startup successfully, it is unable to give me a console session so that I can look into when the problem is happening. any further ideas on how to proceed will be much appreciated - sriram On 01/24/09 16:15, Sriram Natarajan wrote: Hi I even tried image updating to build 105 and tried to boot normally. Still , I get a same error where in all services are keep getting killed. the last service I see is svc.startd[7]: system/hal:default failed fatally: transition to maintenance and before this all other services like ogl-select, pkg/update, ssh etc are all failed due to signal KILL I wonder why system does not enter system maintenance mode and provide me with a shell . keep seeing messages like requesting system maintenance mode and even asks for user name and password. but I never get a login shell Any help in how to get this system back online will be much much appreciated. I feel handicapped without my primary desktop working successfully. Note: when I tried to boot in single user mode and try to look at service logs for service like hal etc , there is nothing useful that I can find to tell me what the problem is. - sriram Sriram Natarajan wrote: Phi Tran wrote: Sriram Natarajan wrote: Phi Tran wrote: Hi, Where exactly does the system hang? When you try to login to gnome? BTW, hald will not run in single user mode because it depends on dbus and dbus is not running. In normal boot mode, the system hangs way before then - does not even start X server. in fact, system goes into a infinite loop where in all services are continuously killed (I get some message like timeout , killed contract etc..) In single user mode, I started enabling various services including milestone/multi-user-server and then also enabled dbus service before proceeding to enable hal. svcs -xv did not report error that some dependent service is not running but only reported that service did not start successfully and what it seems to me that the service timed out (600) seconds . It's hard to tell what state you put the system in and I don't know if it's correct for single user mode. What are the services you started in single user mode? I kept adding services until all its dependents are resolved. From your paragraph about services being killed, do the logs show you anything? nothing useful except that they are killed (timeout) - almost every service (even service like http:apache22) is getting killed in normal startup mode.. - Sriram Phi - Sriram Phi Sriram Natarajan wrote: Hi I was successfully working with OpenSolaris 2008.11 (upgraded from 2008.05) on my Ultra-40 workstation for quite some time now. Not sure, what caused it - but my system is unable to boot successfully since last week end. Long story short - I got the system in single user mode and found that the system does not come up because of system/hal daemon. So, when I tried to start this daemon (as given below) from a single user mode (af course - after starting all its dependent services ..) /usr/lib/hal/hald --daemon=no --verbose=yes I see this is where the daemon is hanging.. /usr/lib/hal/hald-probe-storage exited hald_dbus.c:4278: unregistered.. Any ideas on how to resolve this further will be much appreciated.. - Sriram ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list
Re: [indiana-discuss] OpenSolaris 2008.11 hangs in hald daemon
On 01/26/09 13:10, Sriram Natarajan wrote: Sanjay Nadkarni wrote: Sriram, Since you mention that everything was going fine and then problems started to occur, is it possible that you have some hardware issues ? Is there anything in /var/adm/messages that could provide a clue ? Can you run zpool status and zpool scrub to see if everything is fine ? I just checked /var/adm/messages and I find that hald failed with exit status 95. I have already checked out zpool scrub and zpool status. no errors are reported. The hardware seems to be running fine. I am able to get opensolaris booted with a livecd again. but unable to start from the installed hard disk. I very much hate to go through the process of (re) installation. well, what is more frustrating is that the system fails to startup successfully, it is unable to give me a console session so that I can look into when the problem is happening. You shouldn't have to reinstall. If you upgraded with beadm then the previous versions should be available via the grub menu. If you have deleted those, you can still use liveCD to boot into a usable environment and then rollback to a snapshot that was taken at install. -Sanjay any further ideas on how to proceed will be much appreciated - sriram On 01/24/09 16:15, Sriram Natarajan wrote: Hi I even tried image updating to build 105 and tried to boot normally. Still , I get a same error where in all services are keep getting killed. the last service I see is svc.startd[7]: system/hal:default failed fatally: transition to maintenance and before this all other services like ogl-select, pkg/update, ssh etc are all failed due to signal KILL I wonder why system does not enter system maintenance mode and provide me with a shell . keep seeing messages like requesting system maintenance mode and even asks for user name and password. but I never get a login shell Any help in how to get this system back online will be much much appreciated. I feel handicapped without my primary desktop working successfully. Note: when I tried to boot in single user mode and try to look at service logs for service like hal etc , there is nothing useful that I can find to tell me what the problem is. - sriram Sriram Natarajan wrote: Phi Tran wrote: Sriram Natarajan wrote: Phi Tran wrote: Hi, Where exactly does the system hang? When you try to login to gnome? BTW, hald will not run in single user mode because it depends on dbus and dbus is not running. In normal boot mode, the system hangs way before then - does not even start X server. in fact, system goes into a infinite loop where in all services are continuously killed (I get some message like timeout , killed contract etc..) In single user mode, I started enabling various services including milestone/multi-user-server and then also enabled dbus service before proceeding to enable hal. svcs -xv did not report error that some dependent service is not running but only reported that service did not start successfully and what it seems to me that the service timed out (600) seconds . It's hard to tell what state you put the system in and I don't know if it's correct for single user mode. What are the services you started in single user mode? I kept adding services until all its dependents are resolved. From your paragraph about services being killed, do the logs show you anything? nothing useful except that they are killed (timeout) - almost every service (even service like http:apache22) is getting killed in normal startup mode.. - Sriram Phi - Sriram Phi Sriram Natarajan wrote: Hi I was successfully working with OpenSolaris 2008.11 (upgraded from 2008.05) on my Ultra-40 workstation for quite some time now. Not sure, what caused it - but my system is unable to boot successfully since last week end. Long story short - I got the system in single user mode and found that the system does not come up because of system/hal daemon. So, when I tried to start this daemon (as given below) from a single user mode (af course - after starting all its dependent services ..) /usr/lib/hal/hald --daemon=no --verbose=yes I see this is where the daemon is hanging.. /usr/lib/hal/hald-probe-storage exited hald_dbus.c:4278: unregistered.. Any ideas on how to resolve this further will be much appreciated.. - Sriram ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___
Re: [indiana-discuss] OpenSolaris 2008.11 hangs in hald daemon
Sanjay The only other thing that I did last week was to connect my Palm Treo to my desktop (through USB) mostly for charging it . I wasn't planning to do any synchronization. Not sure, how this could cause my solaris system to not boot up... Sanjay Nadkarni wrote: On 01/26/09 13:10, Sriram Natarajan wrote: Sanjay Nadkarni wrote: Sriram, Since you mention that everything was going fine and then problems started to occur, is it possible that you have some hardware issues ? Is there anything in /var/adm/messages that could provide a clue ? Can you run zpool status and zpool scrub to see if everything is fine ? I just checked /var/adm/messages and I find that hald failed with exit status 95. I have already checked out zpool scrub and zpool status. no errors are reported. The hardware seems to be running fine. I am able to get opensolaris booted with a livecd again. but unable to start from the installed hard disk. I very much hate to go through the process of (re) installation. well, what is more frustrating is that the system fails to startup successfully, it is unable to give me a console session so that I can look into when the problem is happening. You shouldn't have to reinstall. If you upgraded with beadm then the previous versions well, some time back (after successfully upgrading to build 101), I ran zpool upgrade and not sure, if that is any reason - but I am unable to boot from my older image (say build 96 as well ). Still, I am able to boot from my live CD though. should be available via the grub menu. If you have deleted those, you can still use liveCD to boot into a usable environment and then rollback to a snapshot that was taken at install. I did zpool import -f rpool and ran zpool list but could not find any snapshot. I never took one (my mistake). Also, I upgraded to 101 through pkg image-update. - Sriram -Sanjay any further ideas on how to proceed will be much appreciated - sriram On 01/24/09 16:15, Sriram Natarajan wrote: Hi I even tried image updating to build 105 and tried to boot normally. Still , I get a same error where in all services are keep getting killed. the last service I see is svc.startd[7]: system/hal:default failed fatally: transition to maintenance and before this all other services like ogl-select, pkg/update, ssh etc are all failed due to signal KILL I wonder why system does not enter system maintenance mode and provide me with a shell . keep seeing messages like requesting system maintenance mode and even asks for user name and password. but I never get a login shell Any help in how to get this system back online will be much much appreciated. I feel handicapped without my primary desktop working successfully. Note: when I tried to boot in single user mode and try to look at service logs for service like hal etc , there is nothing useful that I can find to tell me what the problem is. - sriram Sriram Natarajan wrote: Phi Tran wrote: Sriram Natarajan wrote: Phi Tran wrote: Hi, Where exactly does the system hang? When you try to login to gnome? BTW, hald will not run in single user mode because it depends on dbus and dbus is not running. In normal boot mode, the system hangs way before then - does not even start X server. in fact, system goes into a infinite loop where in all services are continuously killed (I get some message like timeout , killed contract etc..) In single user mode, I started enabling various services including milestone/multi-user-server and then also enabled dbus service before proceeding to enable hal. svcs -xv did not report error that some dependent service is not running but only reported that service did not start successfully and what it seems to me that the service timed out (600) seconds . It's hard to tell what state you put the system in and I don't know if it's correct for single user mode. What are the services you started in single user mode? I kept adding services until all its dependents are resolved. From your paragraph about services being killed, do the logs show you anything? nothing useful except that they are killed (timeout) - almost every service (even service like http:apache22) is getting killed in normal startup mode.. - Sriram Phi - Sriram Phi Sriram Natarajan wrote: Hi I was successfully working with OpenSolaris 2008.11 (upgraded from 2008.05) on my Ultra-40 workstation for quite some time now. Not sure, what caused it - but my system is unable to boot successfully since last
Re: [indiana-discuss] OpenSolaris 2008.11 hangs in hald daemon
Sriram Natarajan wrote: Sanjay The only other thing that I did last week was to connect my Palm Treo to my desktop (through USB) mostly for charging it . I wasn't planning to do any synchronization. Not sure, how this could cause my solaris system to not boot up... Sanjay Nadkarni wrote: On 01/26/09 13:10, Sriram Natarajan wrote: Sanjay Nadkarni wrote: Sriram, Since you mention that everything was going fine and then problems started to occur, is it possible that you have some hardware issues ? Is there anything in /var/adm/messages that could provide a clue ? Can you run zpool status and zpool scrub to see if everything is fine ? I just checked /var/adm/messages and I find that hald failed with exit status 95. I have already checked out zpool scrub and zpool status. no errors are reported. The hardware seems to be running fine. I am able to get opensolaris booted with a livecd again. but unable to start from the installed hard disk. I very much hate to go through the process of (re) installation. well, what is more frustrating is that the system fails to startup successfully, it is unable to give me a console session so that I can look into when the problem is happening. You shouldn't have to reinstall. If you upgraded with beadm then the previous versions well, some time back (after successfully upgrading to build 101), I ran zpool upgrade and not sure, if that is any reason - but I am unable to boot from my older image (say build 96 as well ). Still, I am able to boot from my live CD though. Yup that would be the reason. should be available via the grub menu. If you have deleted those, you can still use liveCD to boot into a usable environment and then rollback to a snapshot that was taken at install. I did zpool import -f rpool and ran zpool list but could not find any snapshot. I never took one (my mistake). Also, I upgraded to 101 through pkg image-update. Really ? you ran zfs list -t snapshot and did not see snapshots ? -Sanjay - Sriram -Sanjay any further ideas on how to proceed will be much appreciated - sriram On 01/24/09 16:15, Sriram Natarajan wrote: Hi I even tried image updating to build 105 and tried to boot normally. Still , I get a same error where in all services are keep getting killed. the last service I see is svc.startd[7]: system/hal:default failed fatally: transition to maintenance and before this all other services like ogl-select, pkg/update, ssh etc are all failed due to signal KILL I wonder why system does not enter system maintenance mode and provide me with a shell . keep seeing messages like requesting system maintenance mode and even asks for user name and password. but I never get a login shell Any help in how to get this system back online will be much much appreciated. I feel handicapped without my primary desktop working successfully. Note: when I tried to boot in single user mode and try to look at service logs for service like hal etc , there is nothing useful that I can find to tell me what the problem is. - sriram Sriram Natarajan wrote: Phi Tran wrote: Sriram Natarajan wrote: Phi Tran wrote: Hi, Where exactly does the system hang? When you try to login to gnome? BTW, hald will not run in single user mode because it depends on dbus and dbus is not running. In normal boot mode, the system hangs way before then - does not even start X server. in fact, system goes into a infinite loop where in all services are continuously killed (I get some message like timeout , killed contract etc..) In single user mode, I started enabling various services including milestone/multi-user-server and then also enabled dbus service before proceeding to enable hal. svcs -xv did not report error that some dependent service is not running but only reported that service did not start successfully and what it seems to me that the service timed out (600) seconds . It's hard to tell what state you put the system in and I don't know if it's correct for single user mode. What are the services you started in single user mode? I kept adding services until all its dependents are resolved. From your paragraph about services being killed, do the logs show you anything? nothing useful except that they are killed (timeout) - almost every service (even service like http:apache22) is getting killed in normal startup mode.. - Sriram Phi - Sriram Phi Sriram Natarajan wrote: Hi I was successfully working with OpenSolaris 2008.11 (upgraded from 2008.05) on my Ultra-40 workstation for quite some time
Re: [indiana-discuss] Keyboard mapping with different language
Now I have to change that every time I log in, Could you explain what you change every time? I'm wondering if it would work fine for you to simply log in with any English locale such as en_US.UTF-8 and make it default in the dialog pupped up when you change login locale. Thanks, Fuyuki Jasse Jansson wrote: Thanks, but that will change the keyboard mapping, right. I want to use the Swedish keyboard but English language in the login screen and menues and such. On Jan 26, 2009, at 11:36 AM, Javier Acosta wrote: Hi Jasse, If /etc/X11/xorg.conf exists in you system; you can simply modify it by changing the following: Option XkbLayout se with the following: Option XkbLayout us If /etc/X11/xorg.conf does not exist; you can add the following line at the end of the file: /etc/default/kbd LAYOUT=US-English Jasse Jansson wrote: When I installed oso2008.11 I had to choose Swedish to get the right keyboard mapping, and that's fine. But I want English language for everything else. With Solaris 10 I got different choices for keyboard and language and I miss that opportunity. Now I have to change that every time I log in, but I want i set permanently, but I can't find anywhere to change it and I don't know where to start search for the answer. Pointers in the right direction are appreciated. Kaiser Jasse -- Authorized Stealth Oracle The axioms of wisdom: 1. Go the SPARC way of life 2. You can't conquer the universe without the knowledge of FORTRAN 3. In the Unix realm, 10% of work fixes 90% of the problems ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
