You can now use the program to share internet.

To get the program, use svn command:
$svn co http://svn.pardus.org.tr/uludag/trunk/gsoc/net-sharing/

Then change the working directory to:
$cd net-sharing/openvpn/model2/

Then get the content of model.xml to /etc/comar/model.xml,
and copy tr.org.pardus.comar.net.share.policy file to /usr/share/PolicyKit/policy/ directory.
After that you have to register Net.Share 's share application with the command:
$sudo hav register share Net.Share link.py

Now you are ready to use it, change the directory to:
$cd ../network-manager/
and run it:
$./network-manager.py

The other work is on NM's GUI.
In the GUI push the "Share Connection" toolbar, and set enabled the checkbox, then select the profile name that goes to the internet(it is recommended that this profile's state should be up), then select the profile name that will share the internet to the internal hosts(recommended to be Ethernet based network). Then push the apply button. Now if any failure occures, it will be informed to your screen, if succeeds, an information box meaning that it is ok to share will be shown. Ok it and now enjoy the sharing of your internet with your clients.
To help you, one moment of this progress is:

24 July 2008 @ 03:59 PM

Emrah Özesen is an interesting photographer who started his journey when he was in high school and used photography to dive into journalism during his college years, which were quite tempered politically. Later on, Özesen became a national athlet in Kayaking, where he documented numerous rivers in and out of Turkey both with wild landscapes and seeing the challange of man versus nature through his objective...

It is not so easy to live as an artist (or even as an athlete as long as you are not a member of national football team) in Turkey, so most of the photograph artists are also working as commercial photographers or take different professions and spare time for their passion. This situation makes any conceptual project quite valuable, sometimes even luxury for artists...

Özesen, politely donated 8 different pictures of his latest work which he made with jugglers. Following our motto, ...for freedom, Özesen chose Creative Commons 3.0 BY-NC-ND license to publish these great pictures. I would like to thank him personally by this note, where I also owe him an apology for writing this so late, approx. 1 month later than the release... Anyway... Thanks buddy, keep going so we can see much more...

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

17 July 2008 @ 10:56 AM

Configuration tool of the notification manager is ready! The tool lets the user change the PNM config file in a user friendly environment, and saves the XML file back. The tool also validates XML files using an XSD and hence does not permit a 'wrong' configuration to be saved. This program uses the lxml library instead of the default pyxml, as the latter does not offer any XSD validation support.

Now the only remaining task is to have the PNM read the XML config file and behave accordingly. Then, we're all done :)

Cheers,

ozan

28 June 2008 @ 04:32 PM

From the Pardus web site:

One more step for freedom: Pardus 2008

New version of the Pardus project, Pardus 2008, improved by the latest technologies and up-to-date applications, has been released. As always, Pardus 2008, is being freely distributed under the terms of GNU General Public License (GPL). In compliance with the main goals of the Pardus project, Pardus 2008 has lots of new features for ease of installation and use, both at the infrastructure and interface level. In addition Pardus 2008 provides enhanced hardware support, stable and reliable Linux infrastructure and numeruous applications on a single CD. You will go through a brand new experience of freedom, using Pardus 2008

We wish you days in freedom, using Pardus 2008...

27 June 2008 @ 01:23 PM

To share internet connection, i will use bridging. In order to do that, i implement some methods that add/delete bridge interface and add/remove interfaces to the bridge interface. These methods are:
*addBridge(br_name)
*delBridge(br_name)
*addInterface(br_name,if_name)
*delInterface(br_name,if_name)

and also i add a new interface to comar's model.xml file, named "Net.Share" and the above methods are added to these comar interface.

23 June 2008 @ 01:43 PM

 

Notification senders can now add buttons to the window that shows their notification. When this interactive mode is selected, the SendNotification() procedure of the PNM becomes a blocking procedure which waits until the user presses one of the supplied buttons or the notification times out. For applications involving a main event loop, the notification sender can make the SendNotification() call non-blocking by providing two callbacks to it. When the user presses one of the supplied buttons or a timeout happens, these callbacks are called. Both GLib and Qt main loops are supported. A screenshot is given above.

19 June 2008 @ 11:38 PM

Nowadays i am trying to add openvpn client connection feature to Tasma 's network-manager and soon it will finish. OpenVPN is an application that provides secure connection. To setup an openvpn connection, you have to enter the parameters:
-device type: tun/tap
-domain name or ip of the openvpn server
-port number - occasionally 1194
-protocol number UDP/TCP
-CA certificate
-client certificates: .crt and .key files
-Chipher type: no chipher, BF-CBC, AS-128-CBC, DES-EDE3-CBC

These parameters can be written to a configuration file (assume "client.conf") and the connection can be done easily with the command "#openvpn --config client.conf" if all the parameters are rigth and complete.

You can see codes by clikcing here

17 June 2008 @ 01:28 PM

Today i went to TUBITAK UEKAE and meet Pardus project developers. The team was very nice and they were working hard to complete the new release of Pardus 2008. While they were doing these, i was studying on my project part that is about DHCP Server Configuration.

09 June 2008 @ 09:26 AM

Or Display Configuration Manager.. Hhmm.. name sucks, doesn’t it? =) (But it will stay like that until you suggest something cool =))

Anyway, we have released Pardus 2008 Beta this week. It comes with a new manager (I and Fatih - “the Xorg guy” =) were together in this) which enables you to configure Xorg server (drivers, monitors, dual screens etc.)

You can reach DM via Tasma -> System -> Display Manager or simply by typing display-manager command from the line. Please do not hesitate to share your opinions and bug reports via Bugzilla.

There’re some screenshots here:

(more…)

---

copyleft ~ pinguar for ..the mythical woman month.., 2008. | Permalink | No comment

06 June 2008 @ 05:01 AM

I made major changes in the GUI code structure: The GUI is now skinnable and the default GUI is not hardcoded. The program loads the ui file dynamically when the program first starts. There are still some restrictions though: The ui file needs to have some compulsory elements for the mechanism to work (e.g. an exit button). I will write some documentation on how to create a compatible ui file sooner or later :)

Cheers,

ozan

01 June 2008 @ 11:52 AM

Hello everyone,
I have been selected as Google Student Participant this year and my project is Internet Connection Share Module which will be established to Pardus Operating System.
By following this blog, I think you will have enjoyable time and learn what i will have done during the project.

For project proposal, click here
For my personal web page, click here

31 May 2008 @ 06:50 AM

 

PNM now has a completely redesigned GUI. It allows multiple notifications to be displayed on the screen. Each notification can be closed independently and positioning of the notification windows are automatic. The GUI has some animation too: When a notification window is closed, the notification windows on top of it slide down :)

 I tried to write the GUI as configurable as possible. I will try to get the program read its configuration from a file in the near future.

30 May 2008 @ 09:05 PM

PNM now has gettext support. I also uploaded the first translation [of course it is to Turkish ] of PNM as well. For now, PNM fetches the translation information from ./i18n instead of the system default path. I did this for easy testing.

28 May 2008 @ 12:45 AM

 

It turns out that learning Qt4 is much easier than I anticipated. So here it comes: I just finished coding a skeletal GUI module and it is working :) I tested the program with a simple command line client (notification generator) and it seems to be working fine. Soon I'll upload the sources to SVN and you'll get to see the thing.

26 May 2008 @ 10:56 PM

Edited: Gokmen just informed me that a documentation of GLib (GObject in particular) python bindings is available, so we are back to GLib for the listener program. So the dbus-listener will be completely free of any Qt dependency. All of the stuff that I have written before does not apply now.

Cheers,

ozan

26 May 2008 @ 09:38 AM

Edited: I made some minor changes to the overall architecture after consulting Gokmen.

I have written a quick and dirty (~140 lines) notification manager that listens the session bus, gets the notifications and adds them to its queue. It right now doesn't do anything else and does not have any GUI to display its results. I am gonna need to learn some QT4 to add display capabilities to it. Unfortunately finals will begin in one week so this may take some time.

Simply stated, I organized the software into four main classes:

1. Notification class: This class contains the data related to notifications. Right now it only contains the "message" property :) When one wants to send a notification, he/she will create an instance of this class and fill in its properties.
2. Notifier class: This encapsulates the whole IPC-dbus related stuff in it. The good thing about it is the following: When someone writes a program that needs a notification to be displayed, he/she won't even need to know anything about dbus. Just create an instance of Notifier, give it the Notification instance that contains your message, and kaboom! Your notification is sent to the notification manager.
3. NotificationManager class: There is only one instance of this class: the actual notification manager. This instance runs in a GLib Main loop and maintains a notification queue. Whenever a notification arrives, it gets added to the aforementioned queue and a QT4 based small GUI application is spawned to handle the notification.
4. NotXFace class: This class has only one instance as well. This instance is the actual dbus object that gets exported on the session bus. Instances of Notifier call methods on this instance, which then relays relevant information to the NotificationManager instance.

Note that users of the notification manager software does not even see the third and the fourth classes. They only use Notifier instances and Notification instances. Another important design decision was to separate the GUI part and the dbus-listener part completely. I initially thought of integrating both, but after talking to Gokmen I realized having a completely independent (and replacable) GUI (a seperate python module to be loaded) was a better design.

I implemented everything mentioned above except for the GUI spawned by the NotificationManager.

After getting over with finals, I plan to learn some PyQT and continue developing the thing.

Cheers,

ozan

25 May 2008 @ 05:06 PM

Blogging attempt #2. 

Update #1: One thing I noticed is that the blogging software doesn't activate any configuration changes unless you update at least one blogging entry (or enter a new one). Is it a bug? Probably yes.

Update #2: Still trying some functionalities.

25 May 2008 @ 12:32 AM

here we go.

25 May 2008 @ 12:18 AM

When I came back to home from the office, Eren gave me great news that made my day! =)

As we heard (in #pardus-devel (@freenode)) from Jonathan Riddell and Martin Böhm, they were in Ubuntu Developer Summit (@ Prague) and were discussing to adopt our configuration tools into Kubuntu. I really got excited, because we have a lot of beautiful tools for end-users to make Linux easier for them, but we lack of presenting these tools to open source community.. =(

When Pardus 2008 (and it’s very soon) got released, we will start to port all of our configuration tools (as well as other applications such as Kaptan and TASMA) to KDE 4 immediately.. And as being the maintainer of TASMA, I’ll really be happy to see them being used on Kubuntu..Yay! =)

---

copyleft ~ pinguar for ..the mythical woman month.., 2008. | Permalink | No comment

22 May 2008 @ 05:18 PM

I should have been written this post months and months earlier, but I was waiting for our superb designer, Gokhan’s designs for layouts. He did an excellent job, both for Kaptan and Yali (you should have seen last screenshots of Yali in OzgurlukIcin.com magazine, if you haven’t yet, have a look at here).

Well, as some of you may know, Kaptan was written in C++. But as all of our tools (except TASMA) are being written in Python, we decided to port Kaptan into Python, too. Actually, it only works on Pardus (network and package manager stuff) but I’ve been thinking to write a generic welcome wizard for KDE- but wait until we port ourselves to KDE4 =)

Okay, okaay.. here’re the screenshots =)

*i am putting a more tag here, and installed a wp plugin for truncating long posts. hope it works =)*

(more…)

---

copyleft ~ pinguar for ..the mythical woman month.., 2008. | Permalink | 22 comments

19 May 2008 @ 11:51 PM

From S. Çağlar Onur's blog:

The Pardus Project is pleased to announce that Google has agreed to sponsor five student slots. Congratulations, and welcome to the Pardus community! We are looking forward to the successful completion of the following interesting projects:

• A System Restore Project for Pardus
  by Mehmet Ozan Kabak, mentored by Gökmen GÖKSEL
• Pardus CD/DVD/USB Distribution Wizard
  by Türker Sezer, mentored by S.Çağlar Onur
• Internet Connection Share Module
  by Cihangir Beşiktaş, mentored by Pınar Yanardağ
• 802.1x support for network manager
  by İşbaran Akçayır, mentored by Gökçen Eraslan
• PISI - Package Signing Mechanism
  by Serdar DALGIC, mentored by Faik Yalçın Uygur

Student projects will be worked on roughly full time (~40 hours/week) between May 26th and August 18th.

24 April 2008 @ 10:23 PM

The Pardus Project is pleased to announce that Google has agreed to sponsor five student slots .

Congratulations, and welcome to the Pardus community! We are looking forward to the successful completion of the following interesting projects:

• A System Restore Project for Pardus
  by Mehmet Ozan Kabak, mentored by Gökmen GÖKSEL
• Pardus CD/DVD/USB Distribution Wizard
  by Türker Sezer, mentored by S.Çağlar Onur
• Internet Connection Share Module
  by Cihangir Beşiktaş, mentored by Pınar Yanardağ
• 802.1x support for network manager
  by İşbaran Akçayır, mentored by Gökçen Eraslan
• PISI - Package Signing Mechanism
  by Serdar DALGIC, mentored by Faik Yalçın Uygur

Student projects will be worked on roughly full time (~40 hours/week) between May 26th and August 18th.

Right now you should spend some time talking to your mentor(s), so you can both get to know each other better. Here's a rough idea of some of the things you should be trying to work on with your mentor over the next several weeks:

• Get a copy of your related projects source code and become familiar enough with it that you can make changes and commit them.
• Start dicussing with your mentor your timeline and goals.
• Discuss your personal schedule(s) with your mentor(s)/student(s).
• Subscribe to gsoc and pardus-devel mailing lists and introduce yourself.
• Read Pardus Developer Guide and apply for a SVN account.

We realize you are still taking classes, and have project deadlines, homework and exams to still worry about. But now that you are accepted into GSoC its also time to start setting aside a few hours a week to plan out your summer, so you can make the most of this opportunity.

We are excited to have you join us, and are really looking forward to these projects!

22 April 2008 @ 11:18 AM

We're proud to announce that Pardus Project has been selected as a mentoring organization for Google's 2008 Summer of Code program. Thanks to Google for considering us worthy to be a part of this organization among other mainstream distributions like Debian, The Fedora Project, Gentoo and openSUSE. This is a giant step towards to our dream about being one of the best Linux distributions, and we made that in less than 2 years :).

So if you are interested in writing open source code, contributing Pardus Project, getting paid for your work and being a part of this wonderful organization over the summer, apply now!...

We already have outlined some project ideas on our SumerOfCode2008Ideas page. Give us a shout if you have any questions about the info there. We're also curious to hear alternative ideas about how you'd like to contribute to Pardus.

Good luck to all mentoring organizations and applicants, we look forward to working with you!...

20 March 2008 @ 09:20 AM

As the new Pardus 2008 repo matures, it became hard to update Pardus 2008 - RootFS 0.1 to current packages by hand. So we’ve created a new rootFS with current packages for the developers. This new RootFS includes :

• COMAR 2.0 alpha1, mudur 2.0 alpha2, PiSi 2.0 alpha3
• ConsoleKit 0.2.10, PolicyKit 0.7, dbus 1.1.20 integration
• hal 0.5.10
• GCC 4.3.0
• kernel 2.6.24.3 with bootsplash support
• New service / init infrastructure, up-to-date system.base & system.devel

Pardus 2008-RootFS 0.1 can be dowloaded from here, all PiSi packages included in this rootfs and a bit more (like kernel-source) are here. You can use the setup procedure described here to use this rootFS.

Happy Hacking…

18 March 2008 @ 01:27 PM

On the way to Pardus 2008, there has been a huge update on core components - so it became very hard to work on devel and the new 2008 repo for developers. So we’ve released a custom rootFS including the new system.base and system.devel components, kernel 2.6.24.2, vi and subversion packages…

This rootfs is intended to be used for a base system during package cleanup and adaptation process during the Pardus 2008 Phase. As we move on with other components, we’ll be releasing weekly developer install CDs as usual.

Developers will have to install and boot into this rootfs to work - it’s not possible to chroot to Pardus 2008 toolchain from Pardus 2007 platforms (unless you use a 2.6.24 kernel of course). It will be convenient to use a virtualization solution such as Virtualbox, as it is ready in 2007 repo and very easy to prepare a working Pardus 2008 setup. Below are the brief instructions for installing rootFS under Virtualbox - similar steps are required for a real disc partition install, but the device names and GRUB configurations should be adjusted accordingly..

Pardus 2008-RootFS 0.1 can be dowloaded from here, all PiSi packages included in this rootfs and a bit more (kernel-debug, kernel-source) are here.

Installing Pardus 2008-RootFS 0.1 :

• Prepare the required disc : For Virtualbox, add a new virtual disc to the virtual machine you’ll be using.
• Boot the virtual machine with a Pardus CD, fire up a console and login as root.
• Prepare a partition and format it :

  # fdisk /dev/hda
  # mkfs.ext3 /dev/hda1 -m 1 -L PARDUS_2008
  

  You should create a primary partition occupying full disc in the first step. If you’re using a real system and disc partition, adjust device names accordingly.

• Mount the partition:

  # mkdir target
  # mount /dev/hda1 target
  

• Transfer rootFS Image (you’ll have to configure your network beforehand) :

  # wget [ftp/sftp/....]
  

• Extract the image:

  # cd target
  # tar -jxf ../pardus2008-rootfs01.tar.bz2
  

• Upon completion of the extraction, you may reboot your system now.
• Boot your system with the Pardus CD once again - at the boot menu, choose desired language and proceed to next menu. On first option (normal boot), press “e” and edit the boot parameters as :

  root (hd0,0)
  kernel (hd0,0)/boot/kernel-2.6.24.2-87 root=LABEL=PARDUS_2008 vga=0x317 mudur=language:tr
  initrd (hd0,0)/boot/initramfs-2.6.24.2-87
  

  Pressing “b” will boot ssytem to your new rootFS.

• root password is “pardus” - login to your ssytem as root and finalize the installation by installing grub :

  # grub-install /dev/sda --recheck
  

  If you’re using a real system and disc partition, edit /boot/grub/grub.conf to suit your system or add the new rootFS to your existing boot loader.

• Reboot your system to check boot loader configuration, if all gone well, you have a working Pardus 2008 base system now - Happy hacking..

  # reboot
  

28 February 2008 @ 08:38 AM

I’ve been asking this question to myself in last days, and decided to customize my desktop by removing any extra “thing” as possible as I can. Both KDE and applications (e.g. Firefox) come with neat interfaces. But cleaning up unnecessary menus and panels will really help to expand your workplace.

I’m going to give you some hints, but first have a look at my desktop (yes there’s only wallpaper :)):

There’s no taskbar or panel except this little panel which displays on mouse hover.

I love to think all components of an interface as windows. Like all windows have a close button on top right, my desktop (panel) has a close button, too.

.

On the left of the close button, there’s lock session button which lets you to lock your desktop quickly.

Show desktop and system tray sine qua non things on our little panel.

.
You may have think if it’s hard to:

- work without seeing a task bar, but I think alt + tab do it very well.
- and starting an application without clicking an app icon on panel, menu, swh else. katapult rocks at it, just an alt + space and type F brings you Firefox:

Customization about desktop ends here In fact, the most important one is Firefox, one of the most frequently usable app. Here’s a screenshot of my firefox:

Have a look at the details:

Normally Firefox comes a toolbar & menu like that:

With the customization, area for toolbar & menu eg. reduces by half! That means nearly you’ll save %12 area of your workspace! I made this customization with three different actions.

Note that, with this customization; back, stop and forward buttons only appears when there’s something to stop, or a page to back or fwd. Plus, active tab is wider than others.

(more…)

---

copyleft ~ pinguar for ..the mythical woman month.., 2008. | Permalink | One comment

21 January 2008 @ 12:51 AM

07 January 2008 @ 09:47 PM

Pardus 2008 comes with lots of new features, each feature deserves to be blogged seperately, this one is about our configuration manager COMAR...

(R)evolutions in FreeDesktop world effected Pardus, like many other distributions. Among all Pardus projects, COMAR was most effected one, probably. The RPC protocol used for service, process and client communication in 1.* releases replaced with DBus, and access control job transferred to PolicyKit.

D-Bus is a message bus system, a simple way for applications to talk to one another. In addition to interprocess communication, D-Bus helps coordinate process lifecycle; it makes it simple and reliable to code a "single instance" application or daemon, and to launch applications and daemons on demand when their services are needed.

PolicyKit is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes: It is a framework for centralizing the decision making process with respect to granting access to privileged operations for unprivileged applications. PolicyKit is specifically targeting applications in rich desktop environments on multi-user UNIX-like operating systems. It does not imply or rely on any exotic kernel features.

You can see User-Manager (which uses DBus to communicate COMAR) using PolicyKit to obtain authorization through authentication.

04 January 2008 @ 12:01 PM

For Qt4 based Yalı, I made a mockup and then started to work on it; while porting the Qt3 based codes I used lots of Qt4 CSS (or QSS) support, for example;

In mockup (which is here) I made shiny navigation buttons (we used similar ones in old Yalı, but it’s based on images brrr):

I could use images again but where is my imagination; I used CSS like;

QPushButton {
background-color: #FF7308;
border-style: outset;
border-width: 2px;
border-radius: 8px;
border-color: beige;
font: 12px;
min-width: 5em;
padding:6px;
color:#FFF;
}

It was for the all buttons in Yalı, also for Nav buttons (which objects name are buttonNext and buttonBack);

#buttonNext {
border-top-left-radius:none;
border-bottom-left-radius:none;
border-left-width: 1px;
min-width: 3em;
}

#buttonBack {
border-top-right-radius:none;
border-bottom-right-radius:none;
border-right-width: 1px;
min-width: 3em;
}

And the result;

Good eh :)

ps. If you interest codes are in our svn ;)

19 December 2007 @ 12:51 PM

As I mentioned at the start, Pardus is not based on Slackware, Debian, Red Hat, or anything else and in this day and age that's a real rarity. It's nice to see someone trying to do something different and not imitate. I think this distro is really one to watch in the future; it's come so far in two years, where could it be in another two years time? Who knows? I, for one, can't wait to find out. It's already a nicely polished Linux distro and I was able to get a fully working desktop up very easily, it's also a very nice looking OS. So if you want to sample something a little different my advice is give Pardus a spin.

yazının tümü burada // the article is here

18 December 2007 @ 09:59 AM

Overall, Pardus lives up to the goals and statements made by its developers. It is indeed easy to install and even easier to use. Pardus is an accommodating and customizable desktop system suitable for new and experienced users alike.

yazının tümü burada // the article is here

13 December 2007 @ 08:44 PM

Inspired by Max Spevack’s blog post, here are some statistics for the Pardus repositories.

Pardus 2007 statistics, gathered on 2007-12-13.
(generated by packagerStats script)

Total source pisi packages in Pardus 2007 repositories (both stable and contrib) is 2433.

1337 (55%) are maintained by non-TUBITAK developers.
1096 (45%) are maintained by TUBITAK developers.

The total number of non-TUBITAK maintainers is 45.
The total number of TUBITAK maintainers is 10.

1337 / 45 = 29.7 packages per non-TUBITAK maintainer.
1096 / 10 = 109.6 packages per TUBITAK maintainer.

Here are the top three non-TUBITAK maintainers by package count:

Eren Türkay - 259
Ali Erdinç Köroğlu - 165
Murat Şenel - 155

Here are the top three TUBITAK maintainers by package count:

İsmail Dönmez - 329
S.Çağlar Onur - 327
Onur Küçük - 235

If we distribute all the packages equally among the current developers, we would get:

2433 / 55 = 44.2 packages per maintainer.

Pardus is growing fast. Although the numbers are mind-numbing, currently Pardus developers manage to keep all the packages up to date. And thanks to our security ninja for keeping us safe.

New developers are always welcome. Come join us and help us make Pardus one of the best Linux distributions.

13 December 2007 @ 12:34 PM

The beta version of the last update release of Pardus 2007 is ready... We dedicate 2007.3 Beta to Gürer Özen who was one 

of the oldest developer working in Tubitak since last month. Gürer-San decided to kick-off his plans to conqueror the world 

and he's so busy with the invasion plans. 

"Pardus 2007.3 beta" and "Pardus 2007.3 live beta" versions present 

a massive update and package additions to the version 

2007.2 Caracal caracal version released on July, 11. In order to 

download live or installable versions incorporating many 

features including KDE 3.5.8, OpenOffice, k3b, Xorg, please click on 

the following links:

Check out ftp servers for ISO's   

ftp://ftp.pardus.org.tr/pub/pardus/kurulan/2007.3-Beta/

ftp://ftp.pardus.org.tr/pub/pardus/calisan/2007.3-Beta/

Please remember that this is a beta version which may be buggy or 

unstable. So please inform us if you see any problems... 

You can mail us or use bugzilla @ http://bugs.pardus.org.tr

11 November 2007 @ 12:40 PM

"If you can read this, I should have succesfully installed a version of Pivot." =) Well, most of the blog template stuff starts with these silly words, however I would like to thank Pivot Open-Source Blog Tool, which made my job easier to get acquainted with that blogging event. I hope my experience with it will improve day by day..

While coding within the GSoC timeline, I would like to share my experiments and the things I find interesting in this blog. Surely, you can also track the development process of my GSoC project through this blog..

So let the journey begin.. Follow the white rabbit, alice ;)

03 September 2007 @ 05:01 PM

makes people eager to code for fun :)

03 September 2007 @ 05:00 PM

I shall soon be going on holiday on this Monday. I am taking my girlfriend away to Rome for three nights to celebrate our two year anniversary (not wedding).I shall soon be going on holiday on this Monday. I am taking my girlfriend away to Rome for three nights to celebrate our two year anniversary (not wedding).

Our anniversary is not until august, but she is away during august and I have work, so we could not go for the proper date of our anniversary :(

I am actually quite looking forward to it. I really want to see the Colosseum and the Spanish Steps. Hopefully I will be able to get some nice photos or videos whilst I am away and upload them to my photo gallery. All I know is it is going to be hot and I do not really like the heat so I am probably going to fry whilst I am there.

All the best,

Tuxedup

visit my Pardus Linux website

21 July 2007 @ 02:35 AM

Well I guess I can finally say my website has properly launched. I have a new look for the site and have finally added some real content to the website. At present I have added a guide to installing Crossover Office and some wallpapers. More content is soon to follow.

Please check out the website;

http://www.tuxedup.com

Tuxedup.Well I guess I can finally say my website has properly launched. I have a new looks for the site and have finally added some real content to the website. At present I have added a guide to installing Crossover Office and some wallpapers. More content is soon to follow.

Please check out the website;

http://www.tuxedup.com

Tuxedup.

20 July 2007 @ 03:15 PM

Planet is full of with Guadec posts & reviews - everybody is having a fine time in Birmingham I see. I should have been in Birmingham at 14th as Adam wrote and was going to give my little poor lightning talk at Wednesday. But because of my mother got an accident at the day I was going to fly (thanx God), now I’m only counting my fingers & coding my SoC project

But I recently got a news that Guadec 2008 will be in Istanbul! Wow, if that’s true, I’ll really be happy to see all of you in my country.

Let’s see where you’re going to come via this cool video

---

copyleft ~ pinguar for ..the mythical woman month.., 2007. | Permalink | No comment

17 July 2007 @ 10:22 PM

My career prospects are certainly looking up now. I have been offered the job I went to the interview for on Monday.My career prospects are certainly looking up now. I have been offered the job I went to the interview for on Monday.

So in September I shall be starting my new job in Liverpool University as a web developer mainting the university's Web Based Personal Planner. So this will involve some Java work, XML, (X)HTML, ASP.NET, SQL with Oracle and some occasional graphics work.

I will be working there for around 10-11 months and getting paid for it also. So this will provide me with valuable experience for the future.

Michael

visit my website: http://www.tuxedup.com

20 June 2007 @ 01:55 PM

The release date is coming, so release notes translation is necessary.
And that's mean: Portuguese Brazilian support is a bit outdated... At least the release notes is OK.

If you are a Portuguese speaker, you should check the following release notes of the upcoming Pardus =D
For other languages, just access: http://svn.pardus.org.tr/uludag/trunk/CD-image/CD-image-version-2007.2/

Notas do release Pardus 2007.2

1. Bem-vindo ao Pardus 2007.2

Bem-vindo ao Pardus versão 2007.2, um release de manutenção para o Pardus 2007
depois do Pardus 2007.1, contendo um sistema operacional fácil de instalar e
utilizar, provendo um desenvolvimento muito útil, compatível e seguro sobre o
K Desktop Environment (KDE). Este documento contém as diferenças básicas entre
o Pardus 2007.1 e o 2007.2.

Nós gentilmente convidamos você a visitar www.pardus.org.tr/eng para mais
informações (em inglês).

1.1 Feedback

Você pode usar bugs.pardus.org.tr, também conhecido como sitema de rastreamento
de bugs do Pardus, para enviar um bug, uma correção de bug ou qualquer sugestão
relacionada ao Pardus. Nós gostaríamos de agradecer nossos usuários e desenvolvedores
com seus relatórios de bugs, correções relacionadas, novas sugestões de pacotes
e funcionalidades para este release.






Você pode também utilizar a aplicação de feedback através do menu
para enviar suas idéias sobre o Pardus pela Internet.

2. Funcionalidades básicas

Esta seção descreve as funcionalidades que o Pardus 2007.2 introduz. Pardus
2007.2 é principalmente um release de correção de bugs, atualização de traduções
e pequenas extensões ao Pardus 2007.1.

2.1 Atualização do KDE (3.5.7)

Pardus 2007.1 agora introduz o KDE 3.5.7 para uma melhor estabilidade, traduções
e efeitos visuais para os usuários do Pardus. Este pacote também é disponível
para usuários do Pardus 2007 e Pardus 2007.1 através do gerenciador de pacotes
do Pardus.

2.2 Suporte PEAP-MSCHAPv2 para o Gerenciador de Redes

A aplicação de gerenciamento de redes agora vem com suporte PEAP-MSCHAPv2
embutido. Agora clientes Pardus podem se autenticar com dispositivos sem fio
usando este protocolo, beneficiando de possibilidades de forte encriptamento.

2.3 Sistema de gerenciamento de pacotes melhorado

Alguns usuário reclamaram do desempenho do facilitador de busca no
gerenciador de pacotes. Agora o pisi se beneficia de um novo método de busca
por nomes e descrição de pacotes. Como um resultado, buscas de pacotes são
mais rápidas e confiáveis.

2.4 Atualizações de pacotes

O repositório do Pardus 2007.2 tem um número de softwares sempre crescente,
contendo 1728 pacotes testados e estáveis neste releas. Ainda, usuários Pardus
podem aproveitar e baixar mais de 650 pacotes através da adição do repositório
contrib ao Gerenciador de Pacotes.

2.5 Gerenciador de inicialização

Pardus 2007.2 introduz um novo gerenciador de inicialização que pode ser
utilizado para adicionar, modificar ou deletar entradas do GRUB vistas durante o
processo de inicialização.

2.6 Suporte a autologin no YALI

Muitos usuários nos questionavam sobre uma maneira de rapidamente iniciar a
área de trabalho do Pardus e nós a implementamos. YALI (Yet Another Linux
Installer) agora inclui suporte a autologin durante a instalação. Ou seja, você
pode escolher um usuário que poderá logar-se automaticamente na área de trabalho
do KDE assim que o sistema inicializar.

2.7 Atualizações e correções

Suporte ao Jmicron foi adicionado ao Pardus 2007.2. Aqueles que possuem
controladores Jmicron são agora capazes de instalar o Pardus 2007.2 se nenhum
problema.

3. Requisitos de instalação

Você pode rodar o Pardus 2007.2 num hardware médio. Nós o sugerimos 512MB de RAM
ao menos e um processador de 1200MHz para conseguir uma performance efetiva.
Requisitos mínimos e de hardware recomendados para o Pardus 2007.2 são
mencionados abaixo:

• Memória de 256MB RAM (512MB recomendados)


• Processador Intel ou AMD de 800MHz (1200MHz recomendados)


• Ao menos 4GB de espaço livre no disco rígido (10GB recomenados)

4. Contato

Por favor, visite a página do Pardus (www.pardus.org.tr/eng) para mais
informações.

19 June 2007 @ 09:58 PM