dmesg Mandrake10.2

Просмотр 15 сообщений - с 1 по 15 (из 22 всего)
  • Автор
    Сообщения
  • #1941132
    Demiurg
    Участник

    есть проблема в Линухе по неизвестным мне причинам не перестал пахать dmesg, если кто знаком с решением проблемы просьба подсказать. Команда dmesg возвращает сотню строк видаdevfs_mk_dev: could not append to parent for 7…devfs_mk_dev: could not append to parent for 127SyncLink serial driver $Revision: 4.28 $, tty major#253SyncLink MultiPort driver $Revision: 4.29 $devfs_mk_dev: could not append to parent for 0…devfs_mk_dev: could not append to parent for 127SyncLink MultiPort driver $Revision: 4.29 $, tty major#252Supermount version 2.0.4 for kernel 2.6loop: loaded (max 8 devices)hdc: ATAPI 52X CD-ROM drive, 128kB Cache, DMAUniform CD-ROM driver Revision: 3.20PCI: Found IRQ 10 for device 0000:00:0a.03c59x: Donald Becker and others. http://www.scyld.com/network/vortex.html0000:00:0a.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.19ip_conntrack version 2.1 (2047 buckets, 16376 max) – 248 bytes per conntrackip_tables: (C) 2000-2002 Netfilter core teamFloppy drive(s): fd0 is 1.44MFDC 0 is a post-1991 82077NET: Registered protocol family 17PCI: Found IRQ 10 for device 0000:00:0a.0eth0: Setting promiscuous mode.device eth0 entered promiscuous modeNET: Registered protocol family 10Disabled Privacy Extensions on device c03b26e0(lo)eth0: Setting promiscuous mode.eth0: Setting promiscuous mode.IPv6 over IPv4 tunneling driverDisabled Privacy Extensions on device cec47c00(sit0)ip_tables: (C) 2000-2002 Netfilter core teambootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 0 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 1 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 2 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 3 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 4 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 5 changed to oneth0: no IPv6 routers presentlease broken – owner pid = 16727lease broken – owner pid = 16635

    #1941138
    Brain
    Участник

    И что? В чем проблема? Может пива много, но на вид стандарный вывод dmesg.В тебе видно тоже. [smile :)))]. Судя по поставленому вопросу.

    #1941141
    Brain
    Участник

    man dmesgDMESG(8)NAMEdmesg – print or control the kernel ring bufferSYNOPSISdmesg [ -c ] [ -n level ] [ -s bufsize ]DESCRIPTIONdmesg is used to examine or control the kernel ring buffer.The program helps users to print out their bootup messages. Instead of copying the mes-sages by hand, the user need only:dmesg > boot.messagesand mail the boot.messages file to whoever can debug their problem.OPTIONS-c Clear the ring buffer contents after printing.-sbufsizeUse a buffer of size bufsize to query the kernel ring buffer. This is 16392 bydefault. (The default kernel syslog buffer size was 4096 at first, 8192 since1.3.54, 16384 since 2.1.113.) If you have set the kernel buffer to be larger thanthe default then this option can be used to view the entire buffer.-nlevelSet the level at which logging of messages is done to the console. For example, -n1 prevents all messages, expect panic messages, from appearing on the console. Alllevels of messages are still written to /proc/kmsg, so syslogd(8) can still be usedto control exactly where kernel messages appear. When the -n option is used, dmesgwill not print or clear the kernel ring buffer.When both options are used, only the last option on the command line will have aneffect.SEE ALSOsyslogd(8)AUTHORTheodore Ts?o (tytso@athena.mit.edu)DMESG(8)~

    #1941172
    Demiurg
    Участник

    ладно, если непонятно вывожу полный лог, это НЕ нормальная реакция dmesgappend to parent for 6devfs_mk_dev: could not append to parent for 7devfs_mk_dev: could not append to parent for 8devfs_mk_dev: could not append to parent for 9devfs_mk_dev: could not append to parent for 10devfs_mk_dev: could not append to parent for 11devfs_mk_dev: could not append to parent for 12devfs_mk_dev: could not append to parent for 13devfs_mk_dev: could not append to parent for 14devfs_mk_dev: could not append to parent for 15devfs_mk_dev: could not append to parent for 16devfs_mk_dev: could not append to parent for 17devfs_mk_dev: could not append to parent for 18devfs_mk_dev: could not append to parent for 19devfs_mk_dev: could not append to parent for 20devfs_mk_dev: could not append to parent for 21devfs_mk_dev: could not append to parent for 22devfs_mk_dev: could not append to parent for 23devfs_mk_dev: could not append to parent for 24devfs_mk_dev: could not append to parent for 25devfs_mk_dev: could not append to parent for 26devfs_mk_dev: could not append to parent for 27devfs_mk_dev: could not append to parent for 28devfs_mk_dev: could not append to parent for 29devfs_mk_dev: could not append to parent for 30devfs_mk_dev: could not append to parent for 31devfs_mk_dev: could not append to parent for 32devfs_mk_dev: could not append to parent for 33devfs_mk_dev: could not append to parent for 34devfs_mk_dev: could not append to parent for 35devfs_mk_dev: could not append to parent for 36devfs_mk_dev: could not append to parent for 37devfs_mk_dev: could not append to parent for 38devfs_mk_dev: could not append to parent for 39devfs_mk_dev: could not append to parent for 40devfs_mk_dev: could not append to parent for 41devfs_mk_dev: could not append to parent for 42devfs_mk_dev: could not append to parent for 43devfs_mk_dev: could not append to parent for 44devfs_mk_dev: could not append to parent for 45devfs_mk_dev: could not append to parent for 46devfs_mk_dev: could not append to parent for 47devfs_mk_dev: could not append to parent for 48devfs_mk_dev: could not append to parent for 49devfs_mk_dev: could not append to parent for 50devfs_mk_dev: could not append to parent for 51devfs_mk_dev: could not append to parent for 52devfs_mk_dev: could not append to parent for 53devfs_mk_dev: could not append to parent for 54devfs_mk_dev: could not append to parent for 55devfs_mk_dev: could not append to parent for 56devfs_mk_dev: could not append to parent for 57devfs_mk_dev: could not append to parent for 58devfs_mk_dev: could not append to parent for 59devfs_mk_dev: could not append to parent for 60devfs_mk_dev: could not append to parent for 61devfs_mk_dev: could not append to parent for 62devfs_mk_dev: could not append to parent for 63devfs_mk_dev: could not append to parent for 64devfs_mk_dev: could not append to parent for 65devfs_mk_dev: could not append to parent for 66devfs_mk_dev: could not append to parent for 67devfs_mk_dev: could not append to parent for 68devfs_mk_dev: could not append to parent for 69devfs_mk_dev: could not append to parent for 70devfs_mk_dev: could not append to parent for 71devfs_mk_dev: could not append to parent for 72devfs_mk_dev: could not append to parent for 73devfs_mk_dev: could not append to parent for 74devfs_mk_dev: could not append to parent for 75devfs_mk_dev: could not append to parent for 76devfs_mk_dev: could not append to parent for 77devfs_mk_dev: could not append to parent for 78devfs_mk_dev: could not append to parent for 79devfs_mk_dev: could not append to parent for 80devfs_mk_dev: could not append to parent for 81devfs_mk_dev: could not append to parent for 82devfs_mk_dev: could not append to parent for 83devfs_mk_dev: could not append to parent for 84devfs_mk_dev: could not append to parent for 85devfs_mk_dev: could not append to parent for 86devfs_mk_dev: could not append to parent for 87devfs_mk_dev: could not append to parent for 88devfs_mk_dev: could not append to parent for 89devfs_mk_dev: could not append to parent for 90devfs_mk_dev: could not append to parent for 91devfs_mk_dev: could not append to parent for 92devfs_mk_dev: could not append to parent for 93devfs_mk_dev: could not append to parent for 94devfs_mk_dev: could not append to parent for 95devfs_mk_dev: could not append to parent for 96devfs_mk_dev: could not append to parent for 97devfs_mk_dev: could not append to parent for 98devfs_mk_dev: could not append to parent for 99devfs_mk_dev: could not append to parent for 100devfs_mk_dev: could not append to parent for 101devfs_mk_dev: could not append to parent for 102devfs_mk_dev: could not append to parent for 103devfs_mk_dev: could not append to parent for 104devfs_mk_dev: could not append to parent for 105devfs_mk_dev: could not append to parent for 106devfs_mk_dev: could not append to parent for 107devfs_mk_dev: could not append to parent for 108devfs_mk_dev: could not append to parent for 109devfs_mk_dev: could not append to parent for 110devfs_mk_dev: could not append to parent for 111devfs_mk_dev: could not append to parent for 112devfs_mk_dev: could not append to parent for 113devfs_mk_dev: could not append to parent for 114devfs_mk_dev: could not append to parent for 115devfs_mk_dev: could not append to parent for 116devfs_mk_dev: could not append to parent for 117devfs_mk_dev: could not append to parent for 118devfs_mk_dev: could not append to parent for 119devfs_mk_dev: could not append to parent for 120devfs_mk_dev: could not append to parent for 121devfs_mk_dev: could not append to parent for 122devfs_mk_dev: could not append to parent for 123devfs_mk_dev: could not append to parent for 124devfs_mk_dev: could not append to parent for 125devfs_mk_dev: could not append to parent for 126devfs_mk_dev: could not append to parent for 127SyncLink serial driver $Revision: 4.28 $, tty major#253SyncLink MultiPort driver $Revision: 4.29 $devfs_mk_dev: could not append to parent for 0devfs_mk_dev: could not append to parent for 1devfs_mk_dev: could not append to parent for 2devfs_mk_dev: could not append to parent for 3devfs_mk_dev: could not append to parent for 4devfs_mk_dev: could not append to parent for 5devfs_mk_dev: could not append to parent for 6devfs_mk_dev: could not append to parent for 7devfs_mk_dev: could not append to parent for 8devfs_mk_dev: could not append to parent for 9devfs_mk_dev: could not append to parent for 10devfs_mk_dev: could not append to parent for 11devfs_mk_dev: could not append to parent for 12devfs_mk_dev: could not append to parent for 13devfs_mk_dev: could not append to parent for 14devfs_mk_dev: could not append to parent for 15devfs_mk_dev: could not append to parent for 16devfs_mk_dev: could not append to parent for 17devfs_mk_dev: could not append to parent for 18devfs_mk_dev: could not append to parent for 19devfs_mk_dev: could not append to parent for 20devfs_mk_dev: could not append to parent for 21devfs_mk_dev: could not append to parent for 22devfs_mk_dev: could not append to parent for 23devfs_mk_dev: could not append to parent for 24devfs_mk_dev: could not append to parent for 25devfs_mk_dev: could not append to parent for 26devfs_mk_dev: could not append to parent for 27devfs_mk_dev: could not append to parent for 28devfs_mk_dev: could not append to parent for 29devfs_mk_dev: could not append to parent for 30devfs_mk_dev: could not append to parent for 31devfs_mk_dev: could not append to parent for 32devfs_mk_dev: could not append to parent for 33devfs_mk_dev: could not append to parent for 34devfs_mk_dev: could not append to parent for 35devfs_mk_dev: could not append to parent for 36devfs_mk_dev: could not append to parent for 37devfs_mk_dev: could not append to parent for 38devfs_mk_dev: could not append to parent for 39devfs_mk_dev: could not append to parent for 40devfs_mk_dev: could not append to parent for 41devfs_mk_dev: could not append to parent for 42devfs_mk_dev: could not append to parent for 43devfs_mk_dev: could not append to parent for 44devfs_mk_dev: could not append to parent for 45devfs_mk_dev: could not append to parent for 46devfs_mk_dev: could not append to parent for 47devfs_mk_dev: could not append to parent for 48devfs_mk_dev: could not append to parent for 49devfs_mk_dev: could not append to parent for 50devfs_mk_dev: could not append to parent for 51devfs_mk_dev: could not append to parent for 52devfs_mk_dev: could not append to parent for 53devfs_mk_dev: could not append to parent for 54devfs_mk_dev: could not append to parent for 55devfs_mk_dev: could not append to parent for 56devfs_mk_dev: could not append to parent for 57devfs_mk_dev: could not append to parent for 58devfs_mk_dev: could not append to parent for 59devfs_mk_dev: could not append to parent for 60devfs_mk_dev: could not append to parent for 61devfs_mk_dev: could not append to parent for 62devfs_mk_dev: could not append to parent for 63devfs_mk_dev: could not append to parent for 64devfs_mk_dev: could not append to parent for 65devfs_mk_dev: could not append to parent for 66devfs_mk_dev: could not append to parent for 67devfs_mk_dev: could not append to parent for 68devfs_mk_dev: could not append to parent for 69devfs_mk_dev: could not append to parent for 70devfs_mk_dev: could not append to parent for 71devfs_mk_dev: could not append to parent for 72devfs_mk_dev: could not append to parent for 73devfs_mk_dev: could not append to parent for 74devfs_mk_dev: could not append to parent for 75devfs_mk_dev: could not append to parent for 76devfs_mk_dev: could not append to parent for 77devfs_mk_dev: could not append to parent for 78devfs_mk_dev: could not append to parent for 79devfs_mk_dev: could not append to parent for 80devfs_mk_dev: could not append to parent for 81devfs_mk_dev: could not append to parent for 82devfs_mk_dev: could not append to parent for 83devfs_mk_dev: could not append to parent for 84devfs_mk_dev: could not append to parent for 85devfs_mk_dev: could not append to parent for 86devfs_mk_dev: could not append to parent for 87devfs_mk_dev: could not append to parent for 88devfs_mk_dev: could not append to parent for 89devfs_mk_dev: could not append to parent for 90devfs_mk_dev: could not append to parent for 91devfs_mk_dev: could not append to parent for 92devfs_mk_dev: could not append to parent for 93devfs_mk_dev: could not append to parent for 94devfs_mk_dev: could not append to parent for 95devfs_mk_dev: could not append to parent for 96devfs_mk_dev: could not append to parent for 97devfs_mk_dev: could not append to parent for 98devfs_mk_dev: could not append to parent for 99devfs_mk_dev: could not append to parent for 100devfs_mk_dev: could not append to parent for 101devfs_mk_dev: could not append to parent for 102devfs_mk_dev: could not append to parent for 103devfs_mk_dev: could not append to parent for 104devfs_mk_dev: could not append to parent for 105devfs_mk_dev: could not append to parent for 106devfs_mk_dev: could not append to parent for 107devfs_mk_dev: could not append to parent for 108devfs_mk_dev: could not append to parent for 109devfs_mk_dev: could not append to parent for 110devfs_mk_dev: could not append to parent for 111devfs_mk_dev: could not append to parent for 112devfs_mk_dev: could not append to parent for 113devfs_mk_dev: could not append to parent for 114devfs_mk_dev: could not append to parent for 115devfs_mk_dev: could not append to parent for 116devfs_mk_dev: could not append to parent for 117devfs_mk_dev: could not append to parent for 118devfs_mk_dev: could not append to parent for 119devfs_mk_dev: could not append to parent for 120devfs_mk_dev: could not append to parent for 121devfs_mk_dev: could not append to parent for 122devfs_mk_dev: could not append to parent for 123devfs_mk_dev: could not append to parent for 124devfs_mk_dev: could not append to parent for 125devfs_mk_dev: could not append to parent for 126devfs_mk_dev: could not append to parent for 127SyncLink MultiPort driver $Revision: 4.29 $, tty major#252Supermount version 2.0.4 for kernel 2.6loop: loaded (max 8 devices)hdc: ATAPI 52X CD-ROM drive, 128kB Cache, DMAUniform CD-ROM driver Revision: 3.20PCI: Found IRQ 10 for device 0000:00:0a.03c59x: Donald Becker and others. http://www.scyld.com/network/vortex.html0000:00:0a.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.19ip_conntrack version 2.1 (2047 buckets, 16376 max) – 248 bytes per conntrackip_tables: (C) 2000-2002 Netfilter core teamFloppy drive(s): fd0 is 1.44MFDC 0 is a post-1991 82077NET: Registered protocol family 17PCI: Found IRQ 10 for device 0000:00:0a.0eth0: Setting promiscuous mode.device eth0 entered promiscuous modeNET: Registered protocol family 10Disabled Privacy Extensions on device c03b26e0(lo)eth0: Setting promiscuous mode.eth0: Setting promiscuous mode.IPv6 over IPv4 tunneling driverDisabled Privacy Extensions on device cec47c00(sit0)ip_tables: (C) 2000-2002 Netfilter core teambootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 0 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 1 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 2 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 3 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 4 changed to onbootsplash 3.1.6-2004/03/31: looking for picture…<6>…found (800×600, 10640 bytes, v3).bootsplash: status on console 5 changed to oneth0: no IPv6 routers presentlease broken – owner pid = 16727lease broken – owner pid = 16635команду man я знаю, смотрелvi /var/log/syslogJul 17 04:07:00 Q3 : – /var/spool/postfix/private/traceJul 17 04:07:00 Q3 : – /var/spool/postfix/private/uucpJul 17 04:07:00 Q3 : – /var/spool/postfix/private/verifyJul 17 04:07:00 Q3 : – /var/spool/postfix/private/virtualJul 17 04:07:00 Q3 : – /var/spool/postfix/public/cleanupJul 17 04:07:00 Q3 : – /var/spool/postfix/public/flushJul 17 04:07:00 Q3 : – /var/spool/postfix/public/pickupJul 17 04:07:00 Q3 : – /var/spool/postfix/public/qmgrJul 17 04:07:00 Q3 : – /var/spool/postfix/public/showqJul 17 04:07:00 Q3 : – /wwwJul 17 05:01:00 Q3 CROND[8592]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 06:01:00 Q3 CROND[8607]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 07:01:00 Q3 CROND[8622]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 08:01:00 Q3 CROND[8637]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 09:01:00 Q3 CROND[8652]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 10:01:00 Q3 CROND[8667]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 11:01:01 Q3 CROND[8682]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 12:01:00 Q3 CROND[8697]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 13:01:00 Q3 CROND[8712]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 14:01:00 Q3 CROND[8727]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 15:01:00 Q3 CROND[8742]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 15:52:06 Q3 arpwatch: changed ethernet address 192.168.2.56 0:50:bf:44:b5:96 (0:7:95:ce:ed:7)Jul 17 15:52:06 Q3 postfix/sendmail[8756]: warning: My hostname Q3 is not a fully qualified name – set myhostname or mydomain [25;1Hin /etc/postfix/main.cfJul 17 04:52:06 Q3 postfix/postdrop[8757]: warning: My hostname Q3 is not a fully qualified name – set myhostname or mydomain [27;1Hin /etc/postfix/main.cfJul 17 15:52:37 Q3 arpwatch: new station 192.168.2.75 0:50:bf:44:b5:96Jul 17 15:52:37 Q3 postfix/sendmail[8758]: warning: My hostname Q3 is not a fully qualified name – set myhostname or mydomain [30;1Hin /etc/postfix/main.cfJul 17 04:52:37 Q3 postfix/postdrop[8759]: warning: My hostname Q3 is not a fully qualified name – set myhostname or mydomain [32;1Hin /etc/postfix/main.cfJul 17 16:01:00 Q3 CROND[8761]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 17:01:00 Q3 CROND[8780]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 18:01:00 Q3 CROND[8796]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 19:01:00 Q3 CROND[8811]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 20:01:00 Q3 CROND[8826]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 21:01:00 Q3 CROND[8898]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 22:01:00 Q3 CROND[8969]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 17 23:01:01 Q3 CROND[8984]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 18 00:01:00 Q3 CROND[8999]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 18 01:01:00 Q3 CROND[9014]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)Jul 18 02:01:00 Q3 CROND[9029]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly)boot.log надо?

    #1941173
    Demiurg
    Участник

    В принципе меня это не особо волнует просто с мандрой такое не в первый раз вижу, может кому известно решение?

    #1941174
    Brain
    Участник

    а тебя что именно смущает?Эти строчки?append to parent for 6devfs_mk_dev: could not append to parent for 7devfs_mk_dev: could not append to parent for 8devfs_mk_dev: could not append to parent for 14

    #1941177
    Demiurg
    Участник

    вот именно эта лажа меня и смущает. Для чего я юзаю dmesg? для того чтоб глянуть что у меня за девайсы есть какие чипы на матери стоят и прочее, а тут заместо нормального вывода параша какая-то сыпется.

    #1941180
    Brain
    Участник

    В принципе уже нет Mandrake а есть Mandriva.И народ говарит что качество дистриба упало.Я для начинаюших советовал бы SuSe, а те кто болие мения опытен Debian (перевожу все на него).А этот глюк в Мандриве кажись стандарный.http://linuxforum.ru/index.php?showtopic=12683http://forum.linux.by/viewtopic.php?p=42590&sid=2ab9fe434aeca90bfa051484f26a9a6cВозможно что это даже и не глюк. А такой способ поиск дров. Пытается перебором грузить модули.PSНе советую это дистриб.PPSИзобрази мне uname -a.

    #1941183
    Demiurg
    Участник

    не знаю на кой тебе unameLinux Q3 2.6.11-6mdk #1 Tue Mar 22 16:04:32 CET 2005 i686 Pentium III (Katmai) unknown GNU/Linuxваще в принципе пофиг какой дистриб потому как ядро разрабатывает 1 команда, а туча фирм лепит дистрибы, похрен ваще какой дистриб лишь бы ядро stable ветки. не нахожу особых различий между дистрибами линуха кроме фирменных средств настройки системы и тем как они ставятся (из rpm или src) – работает абсолютно одинаково. Кстати у Мандры на мой взгляд самая дружественная морда установщика рядом стоит Slakware там кстати похожая байда c dmesg только пишет по другому

    #1941185
    Demiurg
    Участник

    хм кстати вспомнил, пытался поставить acronis под linux чо та этой твари надо было от моих исходников ядра, и хотел он мне модуль поставить dkms тока не встал он потом я его убил (модуль всмысле). кажись после этого все началось. Наверно это сцылка на несуществующий модуль, хм…А если dmesg перебором грузит модули но 1 не находит то либо segmentation fault либо то что у меня. Нда… Копать…

    #1941189
    Brain
    Участник

    [quote name='Demiurg'] ваще в принципе пофиг какой дистриб потому как ядро разрабатывает 1 команда, а туча фирм лепит дистрибы, похрен ваще какой дистриб лишь бы ядро stable ветки. не нахожу особых различий между дистрибами линуха кроме фирменных средств настройки системы и тем как они ставятся (из rpm или src) – работает абсолютно одинаково. [/quote]Нужно учить мат часть. Тогда бы небыло таких речей. Почитай чем (и что такое) Ванильное ядро и дисрибутивное. Далие у тебя еспользуется devfs, а от этой бяки уже довно отказались в пользу udev. А ты не какой разници.А комбинации тенхнологий devfs, udev, hal, dbus …… могут быть очень большими.PSНе линух, ляпих и т.п. А linux.

    #1941194
    Demiurg
    Участник

    не нам судить о том что лучше udev либо devfs мы не писали эту ось,Ванильное, это ядро от разработчиков ядра. А ядра которые идут в дистрибутиве – это уже ядра от разработчиков дистрибутива со всякими там запладками.Ну наложили разработчики патчей похерили devfs на udev и что? Пусть udev круче там чем-либо не читал пока, но тов. Линус тоже не идиот ведь зачем то ядра изначально именно на devfs 🙂

    #1941196
    Brain
    Участник

    [quote name='Demiurg'] не нам судить о том что лучше udev либо devfs мы не писали эту ось,Ванильное, это ядро от разработчиков ядра. А ядра которые идут в дистрибутиве – это уже ядра от разработчиков дистрибутива со всякими там запладками.Ну наложили разработчики патчей похерили devfs на udev и что? Пусть udev круче там чем-либо не читал пока, но тов. Линус тоже не идиот ведь зачем то ядра изначально именно на devfs 🙂 [/quote]Молодец. Но за домашние задание 4 🙂 .Вот именно, что горячий финский дядя Тровальдс не дурак и выкинул devfs с новых ядер. И теперь mainstream это udev. PSХотя разработчики embeded систмем просили оставить.PPSLinux это не ОС. [smile :))] Mandriva, Debian, SlackWare, RedHead, SuSe, вот это ОСи [smile :))].

    #1941201
    Demiurg
    Участник

    Почитал. Красиво пишут. Почитал форумы – тот еще траходром. Спора нет что udev прогрессивнее devfs но мне нахрен эти возможности не нужны, стоит у меня эта машина и стоит у нее даже моника с клавиатурой нет ни флешек в не не тыкается ничерта… Последний раз я из нее пыль вытаскивал зимой наверно… Ну так зачем мне udev?

    #1941206
    Brain
    Участник

    [quote name='Demiurg'] Почитал. Красиво пишут. Почитал форумы – тот еще траходром. Спора нет что udev прогрессивнее devfs но мне нахрен эти возможности не нужны, стоит у меня эта машина и стоит у нее даже моника с клавиатурой нет ни флешек в не не тыкается ничерта… Последний раз я из нее пыль вытаскивал зимой наверно… Ну так зачем мне udev? [/quote]Mandriva позиционируется как для Desctop. А по твоим описание у тебя сервак. Страный выбор для сервера.PSТы что то путаешь, я тебе и не предлогал ставить udev.

Просмотр 15 сообщений - с 1 по 15 (из 22 всего)
  • Для ответа в этой теме необходимо авторизоваться.