From Fedora Project Wiki

(ed)
 
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:Documentation]]
=Integrate Proxy Settings and Network Connections(Locations)=
[[Category:User Guide]]


This section of the Fedora User Guide explains how to identify yourself - or, how to ''login'' - to your system.  During the post-installation process, you created an identity with a user name and a password, called an ''account''.  If you have forgotten any of your user account details, you may read the section [[User_Guide-Logging_into_the_Desktop#I Cannot Login: HELP!| I Cannot Login: HELP!]].  For additional information about the login process, refer to the section [[User_Guide-Logging_into_the_Desktop#Logging In: A Technical Explanation | Logging In : A Technical Explanation]].
{{:GSOC_2012/Student_Application_muditha}}


== Login ==
=== Proposal Description ===


When you restart or turn on your computer, it goes through a process called ''booting''.  During the boot process, your computer hardware powers on and performs a series of self-tests.  Immediately after the computer has finished booting, the login screen appears. The login screen displays one or more user names, depending on the number of user accounts present.


Here is how to log in to your account.


To start, enter your user name. To do this, do one of the following:
====An overview of your proposal====
# Type your user name and then press the '''[Enter] ''' key.   The user name is ''case sensitive'' (capitalization matters; "A" is not the same as "a").
* According to the project description, the summarized idea is to create a network connection stably and less involving the user. For the wireless system this is like roaming when user cross the networks, detect the new network and using the database automatically connect to the new network without involving the user. I think Python or C the best languages to implement this.When Wi-Fi adapter detects another network, network manger should check whether it is defined in the database or not. Then it should calculate the signal strength of both signals. If and only if the strength of new signal is greater than the current signal should change the network profile of the current network to the new network. A very high-level view I designed the following diagram which depicts about the solution.For wired connections as describe in the project idea it is enough to get the domain name of the network. After detecting the network connection, using the domain name can be selected the appreciate network profile and connect to the network using its proxy settings.  
# Click on your user name in the list of choices.


{{Admon/note | Using Non-default Desktop Environments | If you wish to use [[User Guide - The Fedora Desktops | desktops besides the default choice]], use the ''Desktop'' combo box on the bottom of the screen to select the desktop you wish to load ''before'' you enter your password.  The default is usually GNOME.}}
====The need you believe it fulfills====
* To achieve my target I want to improve my Python and C knowledge. Especially about the package python-take-bilinear-pairing.
====Any relevant experience you have====
* As an undergraduate I have some good experiences about network programming using Java, C and Python. I have developed some client-server protocols such as Go-Back-N, Selective repeat etc. Also I have the basic knowledge of configuring routers, configuring switches, MySQL, Shell scripting and IPv6.  


Next, enter your password in the text box and press the '''[Enter] ''' key. The password is also case sensitive.
====How do you intend to implement your proposal====
* Because these are some special features of NetworkManager and it can be used as a separate application, I hope to implement these features using its source files.


{{Admon/important | Keep Your Password Secret! | To keep your password secret, the password field displays a dot for every character entered. As with any password, keep your account password private. Do not share it with anyone or write it down in plain view.}}
====Final deliverable of the proposal at the end of the period====
* Modified NetworkManager according to the requirements.
* Documentation.
* Video demo about “how to use new features”.
* Tutorial for those who are interested to learn how we modified NetworkManager.


Now the ''desktop environment'' loads.  In some desktop environments, a small box containing a logo and some icons, called a ''splash screen'', may temporarily appear.  When your splash screen (if you have one) disappears, your desktop is ready for use.  You can now launch applications to access the Internet, manage files, and play media.  These tasks are described in the following chapters.
====A rough timeline for your progress====
* 23th April - 20rd May :-
Finalizing the technologies to be used with mentor and the community,Finalizing the deliverables  with community,Report - 01 to Fedora GSoC blog.


<!-- I think it's nice to have this somewhat more advanced explanation below.  I've changed the title to "Techincal" so hopefully it's clear that this is a deeper discussion than what is needed to use Fedora.  If we decide that this section needs a home somewhere else, though, that's okay as well. --~~~~  -->
* 21rd May - 28th May:-
== Logging In: A Technical Explanation ==
Creating the database,Finishing UIs (might need to add some more later),Report - 02


Fedora is a multi-user operating system. Multiple users, each with different access privileges, can be logged into the computer at the same time.
* 29th May –  1st July:-
Developing the required implementation for the Wi-Fi connections,Discuss the implementation,Report - 03


During installation, you provided a password for the system administrator account, sometimes called the ''superuser''.  The user name for this account is ''root''.
* 2nd July - 8th July:-
Testing and finalizing the Wi-Fi task,Report -04


After installation, Fedora asked you to set up a normal user account.  Use that account, or any other such normal account, for daily use of the system, and the root account for administrative and maintenance tasks.
* 9th July - 13th July:-
Preparing for mid evaluation,Get the feedback from community,Submit work for mid evaluation,Report - 05
This design has many benefits:


* Limited privileges reduce the possibility of doing significant damage to the entire system.
* 14th July – 4th July:-
* Each user account has individual settings.
Developing the required implementation for the wired connection,Report - 06
* Each user account maintains its data separate and private from others.
* A problem in one user account does not put the entire system at risk.


{{Admon/warning | Do not login as root! | Do not use the root account for routine purposes. A normal user account can run all the desktop applications, and greatly increases your security and safety. Applications that require root privileges prompt you for the root password when they start, so you need not login as root to use them.}}
* 5th July – 12th August:-
Testing and finalizing the wired connection task,Discuss the implementation,Testing the entire implementation of NetworkManager,Report -07


== I Cannot Login: HELP! ==
* 13th August – 24th August:-
Code clean up,Documentation,Other deliverables, discussed at the very beginning,Submit the work for final evaluation,Report - 06


A common mistake during login is accidentally having the '''[CapsLock]''' key turned on. This situation can cause the login process to fail because usernames and passwords are case sensitive. If problems persist, re-enter your username and password a few times to ensure that you have typed them correctly.


Recovering the password for a user account is not a difficult process, but it is beyond the scope of this guide. You may wish to ask for help on user forums or chat rooms for further assistance. For an explanation and details on how to do this, please refer to the [[Docs/Drafts/AGBeta#User_Accounts|  User Accounts ]] section of the Fedora Administration Guide.
====Any other details you feel we should consider====
No


----


{|
=== Have you communicated with a potential mentor?  If so, who? ===
|-
* Yes, he is [[User:Danw]]
|[[User Guide - The Fedora Desktops| Previous Page - The Fedora Desktops]] ||[[User Guide| Table of Contents]] ||[[User Guide - Tour of the GNOME Desktop| Next Page - Tour of the GNOME Desktop]]
|}

Latest revision as of 04:30, 1 April 2012

Integrate Proxy Settings and Network Connections(Locations)

Contact Information


Why do you want to work with the Fedora Project?

Fedora is a powerful operating system based on the Linux kernel. Under the Fedora Project include very successful open-source software releases such as NetworkManager, Policy Kit, FreeIPA, SELinux, HAL, D-bus, PulseAudio etc. As I hope to become a network engineer in my career in the shortest time I can with the real experiences, I believe Fedora Project is the best place for it. Because I can see a clear path to achieve my targets especially under the NetworkManager. Even though I won’t be able to do the GSoC 2012 I want to contribute with Fedora to improve the technical and communication skills.


Do you have any past involvement with the Fedora project or with any another open source project as a contributor (if possible please add some references as well)?

  • No

Did you participate with the past GSoC programs, if so which years, which organizations?

  • No

Will you continue contributing/ supporting the Fedora project after the GSoC 2012 program, if yes, which team(s)/area(s), you are interested with?

  • Yes,

BZR Python-Fedora Package(bzrpython-fedora)

Why should we choose you over the other applicants?

  • Because I’m so much interesting about networking and to be a good network engineer is my only dream. I have some experience in network programming using Java, Python, C and I successfully followed CCNA in 2011 December. Also I’m a very friendly person.

Proposal Description

An overview of your proposal

  • According to the project description, the summarized idea is to create a network connection stably and less involving the user. For the wireless system this is like roaming when user cross the networks, detect the new network and using the database automatically connect to the new network without involving the user. I think Python or C the best languages to implement this.When Wi-Fi adapter detects another network, network manger should check whether it is defined in the database or not. Then it should calculate the signal strength of both signals. If and only if the strength of new signal is greater than the current signal should change the network profile of the current network to the new network. A very high-level view I designed the following diagram which depicts about the solution.For wired connections as describe in the project idea it is enough to get the domain name of the network. After detecting the network connection, using the domain name can be selected the appreciate network profile and connect to the network using its proxy settings.

The need you believe it fulfills

  • To achieve my target I want to improve my Python and C knowledge. Especially about the package python-take-bilinear-pairing.

Any relevant experience you have

  • As an undergraduate I have some good experiences about network programming using Java, C and Python. I have developed some client-server protocols such as Go-Back-N, Selective repeat etc. Also I have the basic knowledge of configuring routers, configuring switches, MySQL, Shell scripting and IPv6.

How do you intend to implement your proposal

  • Because these are some special features of NetworkManager and it can be used as a separate application, I hope to implement these features using its source files.

Final deliverable of the proposal at the end of the period

  • Modified NetworkManager according to the requirements.
  • Documentation.
  • Video demo about “how to use new features”.
  • Tutorial for those who are interested to learn how we modified NetworkManager.

A rough timeline for your progress

  • 23th April - 20rd May :-

Finalizing the technologies to be used with mentor and the community,Finalizing the deliverables  with community,Report - 01 to Fedora GSoC blog.

  • 21rd May - 28th May:-

Creating the database,Finishing UIs (might need to add some more later),Report - 02

  • 29th May – 1st July:-

Developing the required implementation for the Wi-Fi connections,Discuss the implementation,Report - 03

  • 2nd July - 8th July:-

Testing and finalizing the Wi-Fi task,Report -04

  • 9th July - 13th July:-

Preparing for mid evaluation,Get the feedback from community,Submit work for mid evaluation,Report - 05

  • 14th July – 4th July:-

Developing the required implementation for the wired connection,Report - 06

  • 5th July – 12th August:-

Testing and finalizing the wired connection task,Discuss the implementation,Testing the entire implementation of NetworkManager,Report -07

  • 13th August – 24th August:-

Code clean up,Documentation,Other deliverables, discussed at the very beginning,Submit the work for final evaluation,Report - 06


Any other details you feel we should consider

No


Have you communicated with a potential mentor? If so, who?