From: Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] --resend-- Major 254 to Major 250
Date: Sat, 12 Feb 2005 12:17:41 +1300 [thread overview]
Message-ID: <1108163861.7659.9.camel@localhost.localdomain> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 249 bytes --]
Email formatting mashed the previous patch I sent in, so please find
attached a new copy which works around the 'could not major 254' error
by moving the kqemu device to major 250.
Cheers,
--
Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
[-- Attachment #1.2: Type: text/html, Size: 644 bytes --]
[-- Attachment #2: major_250.patch --]
[-- Type: text/x-patch, Size: 707 bytes --]
diff -ru qemu/kqemu/install.sh qemu_major250/kqemu/install.sh
--- qemu/kqemu/install.sh 2005-02-11 11:10:28.000000000 +1300
+++ qemu_major250/kqemu/install.sh 2005-02-12 11:23:14.000000000 +1300
@@ -20,5 +20,5 @@
# Create the kqemu device. No special priviledge is needed to use kqemu.
device="/dev/kqemu"
rm -f $device
-mknod $device c 254 0
+mknod $device c 250 0
chmod 666 $device
diff -ru qemu/kqemu/kqemu.h qemu_major250/kqemu/kqemu.h
--- qemu/kqemu/kqemu.h 2005-02-11 11:10:28.000000000 +1300
+++ qemu_major250/kqemu/kqemu.h 2005-02-12 11:23:30.000000000 +1300
@@ -1,7 +1,7 @@
#ifndef KQEMU_H
#define KQEMU_H
-#define KQEMU_MAJOR 254
+#define KQEMU_MAJOR 250
#define KQEMU_VERSION 0x010000
next reply other threads:[~2005-02-11 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 23:17 Darryl Dixon [this message]
2005-02-11 23:40 ` [Qemu-devel] [PATCH] Major 254 Jim C. Brown
2005-02-12 0:43 ` Darryl Dixon
2005-02-12 1:06 ` Jim C. Brown
2005-02-12 1:21 ` Mark Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1108163861.7659.9.camel@localhost.localdomain \
--to=esrever_otua@pythonhacker.is-a-geek.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).