Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 544 online users. » 0 Member(s) | 542 Guest(s) Bing, Google
|
Latest Threads |
How to install Archboot i...
Forum: Network Problems
Last Post: Meup
2025-05-13, 01:41 PM
» Replies: 0
» Views: 448
|
clear logs in smoothwall
Forum: Security and Firewalls
Last Post: amanda63
2024-03-10, 03:27 PM
» Replies: 8
» Views: 88,108
|
I cannot install RedHat 8...
Forum: Redhat
Last Post: hybrid
2023-11-11, 01:01 PM
» Replies: 1
» Views: 41,755
|
How things are done, usin...
Forum: Xorg Problems
Last Post: ross
2023-09-04, 09:03 AM
» Replies: 0
» Views: 1,892
|
Im back.....
Forum: Hello
Last Post: anyweb
2021-01-17, 11:36 AM
» Replies: 1
» Views: 5,374
|
add mp3 plugin to xmms in...
Forum: Fedora
Last Post: anyweb
2021-01-17, 11:30 AM
» Replies: 11
» Views: 41,441
|
Configuring VSFTPd Server
Forum: FTP Server
Last Post: Johnbaca
2020-10-14, 10:25 AM
» Replies: 32
» Views: 117,685
|
Wolf won't play sound!
Forum: Game Problems
Last Post: Guest
2020-10-03, 05:51 PM
» Replies: 1
» Views: 55,547
|
Using git + python
Forum: How Do I?
Last Post: Clueless puppy
2020-08-21, 04:37 PM
» Replies: 0
» Views: 45,562
|
what does your nick mean ...
Forum: Hello
Last Post: volt
2020-08-06, 03:25 PM
» Replies: 28
» Views: 42,036
|
|
|
sound problems |
Posted by: Shibz - 2005-04-10, 10:20 PM - Forum: Audio and Video
- Replies (2)
|
 |
Can someone please explain to me how the sound works? I am having major problems. I want to be able to have multiple things playing sound at the same time, I want be able to play a game, listen to mp3's and talk on teamspeak (voice chat program) at the same time, but I can't get more than one to play sound at a time. Please help. Thanks.
|
|
|
Screensaver Logout |
Posted by: Shibz - 2005-04-09, 03:57 AM - Forum: How Do I?
- Replies (3)
|
 |
Is it possible to set up the screensaver password so that it puts you back at the login screen when you come out of the screensaver. I am using KDE right now in Fedora Core 3 and when the screensaver comes up, it locks the computer so that you need that users password to get out. If someone else wants to use my computer, they need to press the restart button on my case. I just want some way that other people can log in after the screensaver comes on, without having to remove the password protection on the screensaver.
|
|
|
udevilicious |
Posted by: znx - 2005-04-07, 07:02 PM - Forum: Kernel Related
- Replies (1)
|
 |
!--=[ udevilicios
!--=[ by znx
Original the /dev directory was full to the gills of every possible
combination, this made for a huge amount of wasted space. Lots of devices
that you would never need nor require and the possibility that the device
doesn't exist at all. Now due to the fact that ever increasing amounts of
hardware were getting supported (yes Linux is growing ;)) the /dev
directory was growing to near ridiculous levels.
Enter devfs. This was the first attempt at a solution to the problem,
created by Richard Gooch, devfs allowed the device entries to be made on
the fly. Connecting a device would then create the device node inside the
/dev directory, disconnecting would then remove the entry. This mean that
the huge difficultly with over population of the directory. So you think
why udev? Well unfortunately devfs had some problems along the way (nothing
that I ever encountered) but bugs that couldn't get solved meant that
another solution was required. So this is where udev steps in, written by
Greg Kroah-Hartman, it was a user space solution removing the need for more
code inside the kernel (hence user dev!).
One of the great features of udev is something called persistent naming.
Normally devices are named in the order that they are connected in. If you
use any USB device you'll already know this, the first time you find you
camera as /dev/sda the next as /dev/sdb. This makes it a difficult to
handle these devices via /etc/fstab. Udev solves all this by allowing the
user to specify a device name. This means you can name your camera
/dev/camera, no more hunting.
All of the rules that we will create will be made in the file
/etc/udev/rules.d/10-udev.rules. All the default rules are in
/etc/udev/rules.d/50-udev.rules, don't add any here, they'll get
overwritten.
OK so lets find our device. I'm going to use my 256Mb USB stick in this
example. So stick the drive into the port and lets look throw the output of
dmesg.
Code: # dmesg
...
usb 1-1: new full speed USB device using uhci_hcd and address 2
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Vendor: USB Model: Flash Drive Rev: 1.12
Type: Direct-Access ANSI SCSI revision: 00
usb-storage: device scan complete
SCSI device sda: 507901 512-byte hdwr sectors (260 MB)
sda: Write Protect is off
sda: Mode Sense: 37 00 00 00
sda: assuming drive cache: write through
SCSI device sda: 507901 512-byte hdwr sectors (260 MB)
sda: Write Protect is off
sda: Mode Sense: 37 00 00 00
sda: assuming drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: unknown partition table
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
#
I can see that it has mounted this device under /dev/sda. You can also see
that the drive hasn't had any partitions detected (else we would have sda1,
sda2 etc). So now we need to discover where the information is stored
inside the /sys directory. After that we can read through the information
inside the /sys directory.
Code: # udevinfo -q path -n /dev/sda
/block/sda
# udevinfo -a -p /block/sda | less
device '/sys/block/sda' has major:minor 8:0
looking at class device '/sys/block/sda':
SYSFS{dev}="8:0"
SYSFS{range}="16"
SYSFS{removable}="1"
SYSFS{size}="507901"
...
There is a lot of data in there and what we need to do now is pick the
correct keys to identify our device uniquely. So on with the rule (remember
put this into /etc/udev/rules.d/10-udev.rules):
Code: BUS="usb",KERNEL="sd[a-z]",SYSFS[product]="USB Flash Drive",NAME="%k",SYMLINK="flash"
Let's walk through this:
Code: BUS="usb" - Connecting on the USB bus
KERNEL="sd[a-z]" - How the kernel sees your device
SYSFS[product]="USB Flash Drive" - From the output of of udevinfo
NAME="%k" - Continue to create the default device name
SYMLINK="flash" - Link to /dev/flash
You can add lots of other SYSFS entries if you need to tighten up the
description of the device. Using "USB Flash Device" or something equally as
generic can lead to more than device matching the rule. Instead look for
information on the particular manufacture and model.
Now when the device is connected the symlink will magically appear. And
then you can use it. The entry can be made in /etc/fstab allowing quick and
easy access to your device. A really nice rule to show you the power of
udev is this:
Code: KERNEL="eth*",SYSFS[address]="00:d0:b7:c5:48:30",NAME="inet"
KERNEL="eth*",SYSFS[address]="00:d0:b7:c5:48:31",NAME="lan"
When the interface is configured you will get /dev/lan and /dev/inet. Just
think of your firewall rules:
Code: iptables -A input -i lan -p tcp -j accept
iptables -A input -i inet -p tcp -j drop
This is far easier to understand which interface you are configuring.
Well thats it.. have fun!
|
|
|
Thursday Fun =) |
Posted by: lia - 2005-04-07, 01:20 PM - Forum: Jokes
- No Replies
|
 |
Breeding Bulls
A man took his wife to the rodeo and one of the first exhibits they stopped at was the breeding bulls.
They went up to the first pen and there was a sign attached that said, "This bull mated 50 times last year." The wife playfully nudged her husband in the ribs and said, "He mated 50 times last year."
They walked to the second pen which had a sign attached that said, "This bull mated 120 times last year. " The wife gave her husband a healthy jab and said, "That's more than twice a week! You could learn a lot from him."
They walked to the third pen and it had a sign attached that said, in capital letters, "This bull mated 365 times last year." The wife, so excited that her elbow nearly broke her husband's ribs, said, "That's once a day. You could REALLY learn something from this one."
The husband looked at her and said, "Go over and ask him if it was with the same cow."
NOTE: The husband's condition has been upgraded from critical to stable.
|
|
|
glib config missing |
Posted by: Shibz - 2005-04-07, 01:09 AM - Forum: How Do I?
- Replies (4)
|
 |
I keep getting messages saying crap about my glib not being set up right when I try to ./configure xmms (and a few other things).
checking for glib-config... no
checking for GLIB - version >= 1.2.2... no
*** The glib-config script installed by GLIB could not be found
*** If GLIB was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GLIB_CONFIG environment variable to the
*** full path to glib-config.
configure: error: *** GLIB >= 1.2.2 not installed - please install first ***
It said to set the path to where ever glib-config is stored. I did a full search for that file and couldnt find it. I think that I have glib installed, I did rpm -lq glib and I got this:
[root@localhost glib-2.6.4]# rpm -lq glib
/usr/lib/libglib-1.2.so.0
/usr/lib/libglib-1.2.so.0.0.10
/usr/lib/libgmodule-1.2.so.0
/usr/lib/libgmodule-1.2.so.0.0.10
/usr/lib/libgthread-1.2.so.0
/usr/lib/libgthread-1.2.so.0.0.10
/usr/share/doc/glib-1.2.10
/usr/share/doc/glib-1.2.10/AUTHORS
/usr/share/doc/glib-1.2.10/COPYING
/usr/share/doc/glib-1.2.10/ChangeLog
/usr/share/doc/glib-1.2.10/NEWS
/usr/share/doc/glib-1.2.10/README
So does that mean its installed? I don't see any config files in there, how would I fix it? Thanks in advance.
--Shibz
|
|
|
How would you put together a new install |
Posted by: AsProductions - 2005-04-06, 02:12 PM - Forum: Fedora
- Replies (9)
|
 |
I've just completed the server install of FC3 text mode. No GUI for me. Maybe in the future but not yet. I would like to configure this server as a mail server (either SendMail or PostFix, I've never used postfix however), DNS, Samba, SFTP, DHCP for starters. I'm hoping someone could offer some advice as to what to start with first. I just completed the install and am now at the command prompt but I'm not sure where to begin or if there is any recommended "tweaking" to be done. How do you approach a fresh new system configuration process?
Thanks and Salute! :)
A
|
|
|
atitvout |
Posted by: kZo - 2005-04-06, 02:06 AM - Forum: ATI Problems
- No Replies
|
 |
This was pretty easy to setup. Just follow these basic commands, and you should be good to go.
Just a side note: You will not be able to run the LCD and TV output at the same time. I've tinkered with it for hours, and wasn't able to get it to work. It's one or the other. o_O
Code: apt-get install atitvout
This will install the application to run the TV out.
This should display something like "Forcing Rage Mobility/Rage 3D Pro LT mode." Simply put, this is running in the "LCD/TV" mode. The L = LCD and T = TV.
Next force the card to display on the TV.
Of course you must have the svideo cable attached, but this will force your card to display through Svideo to your TV.
Remember, since your card cannot display both, it would be wise to be able to kill the command and force back to the LCD using:
Typically I force it to LCD before I force it to the TV. In case something goes wrong with the display on the TV, I can always hit the "UP Arrow" twice to force it back to the LCD.
Just a little suggestion.
Anyway, I hope this helps anyone utilizing the atitvout command. o_O
|
|
|
Jokes |
Posted by: kZo - 2005-04-06, 01:50 AM - Forum: Jokes
- No Replies
|
 |
What did one casket say to the other?
Give up?
"Is that you coffin"
Badda Bing! Bang Boo..
[img]<___base_url___>/uploads/emoticons/default_dry.png[/img]
|
|
|
|