Welcome, Guest. Please login or register.
April 18, 2014, 20:34:12 PM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

  Show Posts
Pages: 1 [2] 3
16  General / Tips and tricks / Re: Basic commands for PiSi on: November 23, 2007, 12:30:31 PM
I'm sometimes looking for a package without knowing the right name. Wildcards don't help, say I'm looking for Yakuake: "pisi info yak*"  is not going to provide the package name unfortunately. My workaround is to search all available package and list the ones I'm after with grep. In the Yakuake example above:

pisi la | grep -i yak


yakuake         - Yet Another Kuake aka YaKuake (Quake like konsole)
tilda           - A drop down Terminal like Yakuake
yakuake-split   - Drop down terminal

This is a bit of a last resort: listing all available packages takes a while so it's slow. If you see the package you're after you can press <CTRL> C to abort the process of course. The -i option used with grep means "ignore case" and probably isn't necessary; omitting it in the example would have left "tilda" out.
17  General / Tips and tricks / Re: Removing Pardus name from menu and modifying launch feedback on: November 23, 2007, 12:12:42 PM
Good one, thx!
18  General / Wish list / Re: some whishes on: November 21, 2007, 02:13:26 AM
@Caesar Tjalbo:

My friend took my computer for 3 min. and he did crash MBR sector in that minute. He accidently select wrong (recover windoz) menu item from grup list. That's how things began.
Well, who needs enemies with friends like that, eh?  Wink I hope you had your system back up and running fast and easy.
19  General / Wish list / Re: some whishes on: November 17, 2007, 00:16:02 AM
One generally expects that the distro you install also provide for the recovery and its not too much to expect, just a recovery shell.

I stand corrected. I must admit: I didn't bother with the Pardus LiveCD (or other LiveCDs) so I've no idea what it's (not) capable of but shell access would seem handy. Still don't know if that would fix the problem of highenergy. The only time when I messed up my MBR was when I tried my first Linux installation and went for a dual boot system without having RTFM, "just install GRUB" wasn't going to help me there. Grin
The existence of recovery distros made me assume it's not a normal thing for an ordinary distro.

I remember when I used the install CD there was an option to not write a GRUB entry, so I guess the opposite could be possible too.
20  General / Wish list / Re: some whishes on: November 16, 2007, 12:50:14 PM
2- There should be "restore grub" or "Just install Grub" menu item in the livecd or install cd of pardus. Sometimes I crash MBR and there should be an easy way to restore damaged MBR sector by installing grub easily. I shouldn't have to reinstall all system again.
How do you crash the MBR? Do you do something to corrupt it or does it crash by itself? It seems strange to me, perhaps you experiment a lot and then things can go awry but it shouldn't just crash without a reason I think.
I don't know what's wrong but to me it doesn't seem a situation that needs to be catered for in the Pardus installation; there are special recovery distros to fix a system when something's broken.
21  Assistance / Pardus for beginners / Re: Logitech Web Cam on: November 10, 2007, 18:26:39 PM
Hey Holmes, you can post it as you wish.
And no, neither of your languages are normal.

I stated time's over that its old. Wouldn't think its wireless?

To power something, perhaps turn it on? an application to turn it on.
Oh wait is this the elecrtric wiring forum.

Smartass  Tongue
How about you try Google. Perhaps searching on "webcam kde".  Roll Eyes
Does the name Kopete ring a bell?
You know what happened when I hooked up a webcam and typed dmesg on the prompt? It told me:
usb 4-1: new full speed USB device using uhci_hcd and address 2
usb 4-1: new device found, idVendor=046d, idProduct=08b2
usb 4-1: new device strings: Mfr=0, Product=0, SerialNumber=0
usb 4-1: configuration #1 chosen from 1 choice
Linux video capture interface: v2.00
pwc: Philips webcam module version 10.0.13 loaded.
pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
pwc: Trace options: 0x0001
pwc: Logitech QuickCam 4000 Pro USB webcam detected.
pwc: Registered as /dev/video0.
usbcore: registered new driver Philips webcam
usbcore: registered new driver snd-usb-audio

Oh wow, I have a Logitech QuickCam 4000 Pro USB webcam and the driver is loaded automagically. Let's try Kopete, "Testbed" sounds about right for what I'm after. Hmmm, maybe I have to try Settings, Configure. Devices sounds right again.....

No shit! It's my webcam recording the output of my webcam!  Shocked (with a lovely Droste effect as bonus)
And that took all of 1 minute, a bit of help from Google, about 10 mouseclicks and no additional installs whatsoever (the 4000 Pro is probably a bit newer than your Express).
22  Assistance / Pardus for beginners / Re: Logitech Web Cam on: November 10, 2007, 03:07:03 AM
something to power it.
What does that mean?
Is it a USB cam? If you plug it in, what does lsusb or dmesg tell you? Does the device show up in an audiomixer? Tried kdetv?

Oops, I was going to post it just like that, but that's not normal language. See the Multimedia menu first and try 'kdetv' or 'kmix'. Perhaps you see output or something indicating the device is recognized.
Else try lsusb or dmesg on the commandline: lsusb = list usb ports/devices, dmesg = list kernel messages. If you'd compare lsusb or the last lines of dmesg just before and immediately after you plug in a USB device, you (hopefully) see some change.
23  Assistance / News & Announcements / Re: New Beta!!!! on: November 10, 2007, 02:37:36 AM
Python 2.5.1 perhaps?
24  Assistance / Pardus for beginners / Re: DNS Server on: November 06, 2007, 21:26:11 PM
I don't have enough knowledge and experience, I'm sure you can google yourself but perhaps this link (+ links in the text) comes in handy (it's old, be sure to read the comments too):
(or check lifehacker, search on "geek dns server")
25  Assistance / Pardus for beginners / Re: DNS Server on: November 04, 2007, 15:00:31 PM
The DNS server package thats located in the pardus repository;

Is it a dns server software to better connect and translate addresses  like
Domain names,ip numbers,static ip numbers, local ip numbers, and .com names?

That's it. It translates a IP address to a domain name. See if you can access your second pc over the internet, via the IP address of that pc. Then worry whether you want your own DNS server or a 3rd party service, the company that sold you your domain may offer DNS or there's something like DynDNS. A good resource for information are the forums on DNSStuff.com.
26  Assistance / Pardus for beginners / Re: Locate & updatedb on: November 04, 2007, 14:38:52 PM
Hey Caesar, So you're saying updatedb is a utility that allows us to update internal files like named.ca and named.conf in our bind folders.

No, it has nothing to do with Bind, it's much more trivial. The command 'locate' is used to find a file on a filesystem, your harddisk for example. Locate doesn't actually read the filesystem but reads a database where it finds filenames and locations to those files. Initially that database is empty so before you can use locate you have to fill the database with the 'updatedb' command. Additionally, when something changes on your filesystem, you rename, create or delete a file for example, you need to run updatedb to make sure the locate database contains the actual situation. Typically, updatedb is set as a cron-job to run daily.

So then, what's the relevance?

Say you're looking for a file on your harddisk. You know (part of) the name of the file but not where it's stored. Some examples:
- you've installed an application and you want to edit the config file but you don't know what the directory of the application is and hence not where to find that file,
- you've got a tune in your head, you don't know the artistname or the album, only that the song has a specific word in the title (and you don't have a player like Amarok installed which allows you to search for songs in its database),

Now, in the Pardus menu there's an entry called "Find Files/Folders", alternatively you can use Konqueror or Dolphin's find function. But being 1337 Linux hackers, we've got a console open anyway so we might aswell use it and type the commandos.  Wink

The most straight forward way is to use 'find'. Find walks through the filesystem, starting at the directory you provide and looks for filenames which fit the expression provided (see the manpage for find). Find looks at _every_ file and directory and returns filenames that matches the search expression. The time this takes depends how fast your harddisks are and on how many files there are in the path to search: a standard system consists easily of several thousands of files and dozens of directories, even without an extensive mp3 or pornicture collection.
Meaning that if you're looking for an mp3 and all your mp3s are in the directory /home/user/Music, then you can limit the search considerably but if you've no idea where to look then the starting point needs to be the system root directory /. From the example in my previous post, I gather that it takes over 2 minutes to do a full search, and that's with hardly music and images present but my disks are slow.
The following command searches everything for everything but instead of displaying all the filenames, it counts how many lines are outputted. Normally, every line is a file but many files get 2 lines: "/home/<user>/<file>" is equal to "/mnt/<harddisk>/<user/<file>" but both are displayed. Anyway, even with the number divided by 2 it's a large amount of files.
# find / -name * | wc -l
of which are 'mine':
# find /home -name * | wc -l

From what I've seen, 'find' takes a long time the first time it's run but is near instantaneous on subsequent runs. That is comparable with 'locate': 'updatedb' takes a few minutes to populate the database and locate is then near instantaneous. The difference is that I can run updatedb when it's convenient and it also uses a smart mechanism to update only those database entries that have changed; I think it's faster if there aren't many changes to the filesystem. I'm a bit surprised with the way find works in subsequent searches but I imagine locate is faster than find since it can have an index on the database.

Hence I'd like to hear from the Pardus package maintainer for GNU-findutils; I don't know enough about the background. I can look at the sourcecode for findutils but I'm afraid that's just it: look at it, I think it's so complicated that I won't understand what I'm looking at. It's probably not written in Python Grin or very accessible C, I guess it's highly optimized and specialized code, and will go way over my head.

Edit: for those interested, Linux Format December 2007 has an article about searching with many practical examples of how to use find.
27  General / General topics / Re: Show off your Desktop on: November 03, 2007, 14:59:43 PM

A screenshot at 50%. Image made with Inkscape: the logo is scanned from a bitmap, the lettering drawn new to get it 'crisp'. The rest is just the taskbar with icons, time & systray.
I can up the SVG if anyone wants it, so you can use it for your own artwork (change color/resolution etc.) but it's pretty easy to make with Inkscape. Google on "pardus logo" and you'll find the original immediately.
28  Assistance / Pardus for beginners / Re: Locate & updatedb on: November 03, 2007, 14:36:30 PM
As root:
# time find / -iname locate

real    2m1.746s
user    0m0.800s
sys     0m2.402s
# time find / -iname slocate

real    0m4.454s
user    0m0.535s
sys     0m0.740s
What this tells me is: 1. I don't have (s)locate, 2. 'find' uses some sort of caching so subsequent searches are a lot faster (but you see why a database approach is useful).

I might write my own 'locate' for fun and exercise but I'm still curious why it's not included with the default install. Can a Pardus engineer perhaps enlighten me? It's not really an issue, merely curiosity, but I'll explain why I'm so surprised:
# pisi la | grep findutils
findutils       - GNU utilities to find files
(it's green in the console, indicating it's installed)

According to http://www.gnu.org/software/findutils/:
find - search for files in a directory hierarchy
locate - list files in databases that match a pattern
updatedb - update a file name database
xargs - build and execute command lines from standard input
find and xargs are present (try "find / -name find" if in doubt  Cheesy), locate and updatedb are not (not even in the man pages). Why, oh why? Huh? Grin

(locate or slocate? I found slocate is "secure" locate; when updatedb is run as root, the filenames/locations of the entire filesystem are stored in a database. Running locate as non-root would then display files in directories where the non-root user doesn't have read-permission on. slocate prevents those entries to be seen. It's probably a distro-specific thing how locate behaves or what it's called.)
29  General / Wish list / GNOME-games on: October 30, 2007, 13:43:39 PM
I prefer KDE as windowmanager and KDE applications work best in KDE. For simple games however, I like the GNOME-games set. Everyone's taste is different but for me counts:
- GNOME-sudoku works better than KSudoku.
- GNOME-MahJongg looks *much* better than KMahjongg. I know this will change with KDE 4 but that's still equal to GNOME MahJongg and not better. I know I can (and do) change the tile-set and background, even download other images but with the GNOME version I'm happy to play with the default graphics.
- I like Robots Smiley
30  General / General topics / Re: Few good things from arch world on: October 28, 2007, 22:58:27 PM
I'm very interested in Arch Linux. I've started using GNU/ Linux distros a little more than a year ago. My aim was a dual boot system with Windows XP but I screwed up and via a zero boot system I was full on free software in a bang. No internet or sound but otherwise uneventful; I'd anticipated something more difficult. I found installing a distro (Fedora, *buntu, Centos but even Slackware) so easy that I'm completely clueless when something does go wrong. Arch seemed a nice small step into deeper waters, a challenge.

Before installation I tried to be as prepared as possible, I compiled an A4 full of notes of everything I thought I was going to need. Then boot, install, reboot: kernel panic. I was prepared so I knew how to boot the recovery kernel as normal kernel. Prompt, log in as root: X borked. Or I should say my monitor borked since it refused to display anything more. X restart, some magic, back to prompt, repeat. But eventually there I was: a root user in Arch... .... .... ...and now what?

I'll try Arch again some time, when I have an idea what's needed and I'll be a little more prepared. Gave Pardus a try and I'm back into "Linux is child's play land". One minor error during installation (bug filed) but further smooth sailing. Even MP3s & Flash enabled, I've spent all the time saved in making KDE just right.  Grin
Pages: 1 [2] 3

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!