udev core 5


 
Thread Tools Search this Thread
Operating Systems Linux udev core 5
# 1  
Old 04-05-2006
udev core 5

installed fedora core 5 on a pc with USB and some usual things. in boot up it is stopped at "Starting udev:". Its harddisk light is busy. is it reconfiguring the kernel?. what do to solve this problem?.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Fdisk and grep command not working in udev trigger

Hi Guys, Can someone take a look at my scripts what missing, plugin usb drive the script is running can log all my echo but cannot execute command. Is there any configuration in linux or to my scripts need to add?. What i want to achieve is every time I plugin the usbdisk automatic mount to... (21 Replies)
Discussion started by: lxdorney
21 Replies

2. UNIX for Dummies Questions & Answers

Question about udev Rules File?

Hello All, I found this site here: AndDiSa Android Blog: Nexus 7 MTP automount on OpenSuse 11.4 That sites explains how to mount an Android device that can only connect to a computer using MTP or PTP instead of what it used to get treated as, which was a Mass Storage Device. In my Rules... (0 Replies)
Discussion started by: mrm5102
0 Replies

3. Shell Programming and Scripting

udev rules for mounting CDROM

Hi All, I need a simple udev rules in my server Centos 5.4. This rules needs to get trigger my script whenever the cdrom is attached to the server. Could you please provide your suggestion on it. Thanks, Kalai (0 Replies)
Discussion started by: kalpeer
0 Replies

4. Red Hat

set device mode permanently with udev rule

On a test server running CentOS 6, I try to permanently set the owner, group and mode of disk devices for use with a DB2 database. For this I created an udev rule file /etc/udev/rules.d/99-db2.rules: KERNEL=="sdb*", OWNER="db2usrl1", GROUP="db2adml1", MODE="0600" After a reboot, the owner and... (4 Replies)
Discussion started by: hergp
4 Replies

5. Linux

Error: Retrigger failed udev events in Fedora 14!

Hi everybody! I installed Fedora 14 from dvd iso file (3.3 GB). But after that, when i enter command init 3 or init 5 an error occurs: "retrigger failed udev events". Who has experienced pls give me some suggestions. Tks so much! Ok now I can use graphic mode. The first time, I use 256MB for... (0 Replies)
Discussion started by: nguyendu0102
0 Replies

6. UNIX for Advanced & Expert Users

Problems with udev & mounting fat32 usb storage

I have been trying to get USB storage devices to auto-mount themselves under "/media/usb/<dev>" but have been running into some problems with udev (on FC7, btw... running udevd v.106) Every time I put in a FAT (not 32) USB stick, udev identifies it as "USB storage", identifies the partition and... (3 Replies)
Discussion started by: jjinno
3 Replies

7. Shell Programming and Scripting

Pass params with Udev

Hello! I'm sorry if this is the false Forum, didn't really knew where to put it... My question: I have serveral USB-Sticks and wrote several Udev-Rules for theme, each Sticks needs to do something else, but all are using the same script (they have common tasks to do) and only some parts are... (2 Replies)
Discussion started by: al0x
2 Replies

8. UNIX for Dummies Questions & Answers

difference between Dual-core & Core-to-duo

Can anybody tell What is the exact difference between a Dual-core processor and a Core-to-duo processor ?Advance thanks to all my friends. (1 Reply)
Discussion started by: Ajith kumar.G
1 Replies
Login or Register to Ask a Question
CRASHINFO(8)						    BSD System Manager's Manual 					      CRASHINFO(8)

NAME
crashinfo -- analyze a core dump of the operating system SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core] DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX. By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel file can also be explicitly provided via the kernel argument. Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8), ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8). The options are as follows: -d crashdir Specify an alternate core dump directory. The default crash dump directory is /var/crash. -n dumpnr Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory. -k kernel Specify an explicit kernel file. SEE ALSO
textdump(4), savecore(8) HISTORY
The crashinfo utility appeared in FreeBSD 6.4. BSD
June 28, 2008 BSD