You can subscribe to this list here.
1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(15) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2000 |
Jan
(6) |
Feb
(1) |
Mar
(39) |
Apr
(13) |
May
(24) |
Jun
(11) |
Jul
(23) |
Aug
(85) |
Sep
(12) |
Oct
(103) |
Nov
(79) |
Dec
(112) |
2001 |
Jan
(52) |
Feb
(82) |
Mar
(84) |
Apr
(65) |
May
(105) |
Jun
(188) |
Jul
(174) |
Aug
(182) |
Sep
(103) |
Oct
(137) |
Nov
(143) |
Dec
(98) |
2002 |
Jan
(258) |
Feb
(236) |
Mar
(386) |
Apr
(307) |
May
(238) |
Jun
(170) |
Jul
(252) |
Aug
(230) |
Sep
(278) |
Oct
(394) |
Nov
(336) |
Dec
(194) |
2003 |
Jan
(290) |
Feb
(182) |
Mar
(175) |
Apr
(220) |
May
(209) |
Jun
(286) |
Jul
(279) |
Aug
(164) |
Sep
(208) |
Oct
(324) |
Nov
(204) |
Dec
(380) |
2004 |
Jan
(344) |
Feb
(332) |
Mar
(395) |
Apr
(357) |
May
(349) |
Jun
(352) |
Jul
(279) |
Aug
(269) |
Sep
(374) |
Oct
(442) |
Nov
(428) |
Dec
(253) |
2005 |
Jan
(225) |
Feb
(219) |
Mar
(245) |
Apr
(249) |
May
(203) |
Jun
(157) |
Jul
(171) |
Aug
(194) |
Sep
(200) |
Oct
(232) |
Nov
(190) |
Dec
(195) |
2006 |
Jan
(158) |
Feb
(190) |
Mar
(235) |
Apr
(161) |
May
(134) |
Jun
(169) |
Jul
(117) |
Aug
(161) |
Sep
(170) |
Oct
(297) |
Nov
(230) |
Dec
(205) |
2007 |
Jan
(197) |
Feb
(132) |
Mar
(151) |
Apr
(97) |
May
(109) |
Jun
(99) |
Jul
(57) |
Aug
(110) |
Sep
(56) |
Oct
(119) |
Nov
(39) |
Dec
(45) |
2008 |
Jan
(101) |
Feb
(116) |
Mar
(141) |
Apr
(98) |
May
(133) |
Jun
(61) |
Jul
(43) |
Aug
(76) |
Sep
(20) |
Oct
(32) |
Nov
(22) |
Dec
(41) |
2009 |
Jan
(35) |
Feb
(15) |
Mar
(18) |
Apr
(13) |
May
(13) |
Jun
(26) |
Jul
(12) |
Aug
(32) |
Sep
(21) |
Oct
(41) |
Nov
(35) |
Dec
(12) |
2010 |
Jan
(3) |
Feb
(35) |
Mar
(28) |
Apr
(20) |
May
(5) |
Jun
(14) |
Jul
(6) |
Aug
(8) |
Sep
(20) |
Oct
(20) |
Nov
(10) |
Dec
(12) |
2011 |
Jan
(14) |
Feb
(10) |
Mar
(14) |
Apr
(14) |
May
(13) |
Jun
(43) |
Jul
(13) |
Aug
(50) |
Sep
(30) |
Oct
(23) |
Nov
(15) |
Dec
(49) |
2012 |
Jan
(15) |
Feb
(28) |
Mar
(7) |
Apr
|
May
(12) |
Jun
(13) |
Jul
(28) |
Aug
(11) |
Sep
(19) |
Oct
(27) |
Nov
(5) |
Dec
(25) |
2013 |
Jan
(18) |
Feb
(19) |
Mar
(56) |
Apr
(26) |
May
(38) |
Jun
(24) |
Jul
(42) |
Aug
(24) |
Sep
(4) |
Oct
(3) |
Nov
(18) |
Dec
(4) |
2014 |
Jan
(10) |
Feb
(9) |
Mar
(3) |
Apr
|
May
(12) |
Jun
(34) |
Jul
(8) |
Aug
(18) |
Sep
(3) |
Oct
(27) |
Nov
(2) |
Dec
(1) |
2015 |
Jan
|
Feb
(10) |
Mar
(49) |
Apr
(2) |
May
(4) |
Jun
(7) |
Jul
(1) |
Aug
(17) |
Sep
(7) |
Oct
(35) |
Nov
(40) |
Dec
(4) |
2016 |
Jan
(9) |
Feb
|
Mar
(6) |
Apr
|
May
(10) |
Jun
(2) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
(1) |
2017 |
Jan
(2) |
Feb
(4) |
Mar
(1) |
Apr
(4) |
May
(31) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(2) |
2018 |
Jan
|
Feb
|
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Jeff D. <jd...@ka...> - 2000-07-16 02:59:35
|
> #define UTS_RELEASE "2.4.0-test4-1um" > #define UTS_VERSION "#1 Sat Jul 15 17:59:50 PDT 2000" > #ifndef UTS_SYSNAME > #define UTS_SYSNAME "Linux" > #endif > #ifndef UTS_MACHINE > #define UTS_MACHINE "unknown" > #endif > #ifndef UTS_NODENAME > #define UTS_NODENAME "(none)" /* set by sethostname() */ > #endif > #ifndef UTS_DOMAINNAME > #define UTS_DOMAINNAME "(none)" /* set by setdomainname() */ > #endif Strange. That all looks fine. How about doing: gcc -D__KERNEL__ -I/usr/local2/uml/linux/include -Wall -Wstrict-prototypes -O2 -g -U__i386__ -D__arch_um__ -fwritable-strings -DSUBARCH=\"i386\" -DNESTING=0 -fno-strict-aliasing -DUTS_MACHINE='"um"' -E init/version.c > version.i at the top of the pool, extracting the initialization of system_utsname from the cpp output, and sending it in? Jeff |
From: Jeff D. <jd...@ka...> - 2000-07-16 01:52:04
|
I made a small SuSE 6.4 filesystem. It basically contains the base system and nothing else. Get it from http://sourceforge.net/project/filelist.php?group_id=429 Note that when you run it, you have to put 'devfs=nomount' on the command line. Jeff |
From: Eugene K. <ek...@hi...> - 2000-07-16 00:52:48
|
Jeff Dike wrote: > > ek...@hi... said: > > I get some errors compiling 2.4.0-test4 with patch-2.4.0-test4.bz2. > > It's my first time trying to compile a kernel with the uml patch, so > > please forgive me if I missed something obvious. > > It looks like the patch went in ok. 'make dep' isn't really necessary on the > first build because it's a full build, so full dependencies don't buy you > anything. > > Can we see the contents of include/linux/version.h, include/linux/compile.h, > and include/linux/uts.h from that pool? > > Jeff Thanks for your reply. Here are those three files : include/linux/version.h : -------------- #define UTS_RELEASE "2.4.0-test4-1um" #define LINUX_VERSION_CODE 132096 #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) include/linux/compile.h : -------------- #define UTS_VERSION "#1 Sat Jul 15 17:59:50 PDT 2000" #define LINUX_COMPILE_TIME "17:59:50" #define LINUX_COMPILE_BY "ekoontz" #define LINUX_COMPILE_HOST "hiro-tan.dhs.org" #define LINUX_COMPILE_DOMAIN "dhs.org" #define LINUX_COMPILER "gcc version 2.95 19990728 (release)" include/linux/uts.h : --------------- #ifndef _LINUX_UTS_H #define _LINUX_UTS_H /* * Defines for what uname() should return */ #ifndef UTS_SYSNAME #define UTS_SYSNAME "Linux" #endif #ifndef UTS_MACHINE #define UTS_MACHINE "unknown" #endif #ifndef UTS_NODENAME #define UTS_NODENAME "(none)" /* set by sethostname() */ #endif #ifndef UTS_DOMAINNAME #define UTS_DOMAINNAME "(none)" /* set by setdomainname() */ #endif #endif |
From: Jeff D. <jd...@ka...> - 2000-07-16 00:34:25
|
ek...@hi... said: > I get some errors compiling 2.4.0-test4 with patch-2.4.0-test4.bz2. > It's my first time trying to compile a kernel with the uml patch, so > please forgive me if I missed something obvious. It looks like the patch went in ok. 'make dep' isn't really necessary on the first build because it's a full build, so full dependencies don't buy you anything. Can we see the contents of include/linux/version.h, include/linux/compile.h, and include/linux/uts.h from that pool? Jeff |
From: Eugene K. <ek...@hi...> - 2000-07-15 21:56:29
|
Hi uml users, I get some errors compiling 2.4.0-test4 with patch-2.4.0-test4.bz2. It's my first time trying to compile a kernel with the uml patch, so please forgive me if I missed something obvious. Here are the steps I followed : --------------- tar xfz linux-2.4.0-test4.tar.gz # from ftp.kernel.org cd linux cp ../patch-2.4.0-test4.bz2 . # from uml download page on sourceforge cat patch-2.4.0-test4.bz2 | bunzip2 - | patch -p1 # patch gives no errors make config # I just hit return every time to enable the default configuration make dep # http://user-mode-linux.sourceforge.net/UserModeLinux-HOWTO-2.html#ss2.2 omits this step, is the ommission intensional? I get the same errors below, regardless. make linux --------------- (my gcc --version is 2.95; compiling the kernel without the uml patch seems to work ok.) Thanks for any help! The output of "make linux" is as follows : cd /usr/local2/uml/linux/include/asm-um && ln -sf ../asm-i386 arch cd /usr/local2/uml/linux/arch/um/include && ln -sf sysdep-i386 sysdep gcc -D__KERNEL__ -D__KERNEL__ -Wall -Wstrict-prototypes -O2 -g -U__i386__ -D__arch_um__ -fwritable-strings -DSUBARCH=\"i386\" -DNESTING=0 -fno-strict-aliasing -I../include -c -o /usr/local2/uml/linux/arch/um/main.o /usr/local2/uml/linux/arch/um/main.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/split-include scripts/split-include.c scripts/split-include include/linux/autoconf.h include/config gcc -D__KERNEL__ -I/usr/local2/uml/linux/include -Wall -Wstrict-prototypes -O2 -g -U__i386__ -D__arch_um__ -fwritable-strings -DSUBARCH=\"i386\" -DNESTING=0 -fno-strict-aliasing -c -o init/main.o init/main.c gcc -D__KERNEL__ -I/usr/local2/uml/linux/include -Wall -Wstrict-prototypes -O2 -g -U__i386__ -D__arch_um__ -fwritable-strings -DSUBARCH=\"i386\" -DNESTING=0 -fno-strict-aliasing -DUTS_MACHINE='"um"' -c -o init/version.o init/version.c init/version.c:20: initializer element is not constant init/version.c:20: (near initialization for `system_utsname.sysname') init/version.c:20: initializer element is not constant init/version.c:20: (near initialization for `system_utsname.nodename') init/version.c:20: initializer element is not constant init/version.c:20: (near initialization for `system_utsname.release') init/version.c:20: initializer element is not constant init/version.c:20: (near initialization for `system_utsname.version') init/version.c:21: initializer element is not constant init/version.c:21: (near initialization for `system_utsname.machine') init/version.c:22: initializer element is not constant init/version.c:22: (near initialization for `system_utsname.domainname') make: *** [init/version.o] Error 1 [/usr/local2/uml/linux] $ |
From: Jeff D. <jd...@ka...> - 2000-07-15 04:14:30
|
The user-mode port of 2.4.0-test4 is available. It's been updated to 2.4.0-test4. The rest of the changes are bug fixes. The two big bugs fixed are the one that prevented it from running on newer kernels due to the increased size of the signal stack frame and the one that caused a hang when run with a stacksize limit that's not a multiple of 4 meg. If you're interested, see http://user-mode-linux.sourceforge.net/diary.html for more complete descriptions of these problems. The project's home page is http://user-mode-linux.sourceforge.net The project's download page is http://sourceforge.net/project/filelist.php?grou p_id=429 Jeff |
From: Jeff D. <jd...@ka...> - 2000-07-02 15:31:34
|
I added a page (http://user-mode-linux.sourceforge.net/thanks.html) to my site thanking people who have contributed to the project. If you are one of the following people, have a look and see if you are happy with your entry: Rusty Russell Peter Moulder Bill Stearns Yuri Pudgorodsky Gerald Britton Ian Wehrman Let me know if you want any changes made if you're not. If you're not listed and you think you should be, let me know. The criteria I used is that if what you did is in and working in whatever way makes sense, then you should be listed. There are a few things which are in progress which will get listed when they work. I also added a diary page which I may keep somewhat up to date with what's going on. Or I may not. Jeff |
From: Jeff D. <jd...@ka...> - 2000-07-01 20:12:39
|
la...@no... said: > It's also very appropriate that he's the one to make sure deadlines > are met. :) OK, so I missed the RTLinux reference... :-) Jeff |
From: Jeff D. <jd...@ka...> - 2000-07-01 19:22:38
|
la...@no... said: > Jeff Dike <jd...@ka...> writes: > > That makes it sound like Victor is going to come over here and break > > fingers if I don't make the deadline... > It's also very appropriate that he's the one to make sure deadlines > are met. :) Why? Do you know something about him that I don't? Should I plan on moving and changing my name if I don't meet the deadlines :-) Jeff |
From: lars b. <la...@no...> - 2000-07-01 15:40:35
|
Jeff Dike <jd...@ka...> writes: > That makes it sound like Victor is going to come over here and break fingers > if I don't make the deadline... It's also very appropriate that he's the one to make sure deadlines are met. :) |
From: Jeff D. <jd...@ka...> - 2000-07-01 13:37:03
|
I submitted an abstract to the Atlanta Symposium a while back and it's been accepted. So, if any of you are going to be there, MAKE SURE YOU ATTEND THIS VITALLY IMPORTANT TALK :-) There is a slightly humorous part of the email I got from Ted T'so: > Each paper has been assigned a member of the program committee to act > as a shepherd [ who is Victor Yodaiken - jd ]. The role of the shepherd is to > ... > ensure that you produce an appropriate paper by the August 24th > deadline. That makes it sound like Victor is going to come over here and break fingers if I don't make the deadline... Jeff |
From: Jeff D. <jd...@ka...> - 2000-06-29 22:33:22
|
OK, I can't reproduce either of these problems (Ian was complaining privately about a hang, so I decided to merge the two threads...). Are you willing to get in there with gdb and poke around? If so, you'll need a debuggable kernel (the one I put out for download is compiled with no -g and it's stripped). You can either grab a kernel pool and the patch, and build it yourself or I can give you one. Let me know what you'd like to do. Jeff |
From: Gord R. L. <gl...@uf...> - 2000-06-29 15:29:52
|
Already tried that; same thing. :/ - Gord R. Lamb (gl...@uf...) Systems Architect U|Force Inc. On Thu, 29 Jun 2000, Jeff Dike wrote: > Just for the hell of it, could you give it more physical memory (add > "mem=64M" or "mem=128M" to the command line)? I've seen problems that > look like they're my fault at first, but turn out to be the kernel running > short of memory. > > Jeff |
From: Jeff D. <jd...@ka...> - 2000-06-29 15:00:27
|
Just for the hell of it, could you give it more physical memory (add "mem=64M" or "mem=128M" to the command line)? I've seen problems that look like they're my fault at first, but turn out to be the kernel running short of memory. Jeff |
From: Gord R. L. <gl...@uf...> - 2000-06-29 14:46:07
|
Hi Jeff, Here is the console dump: 9 root@sigh (~)# ./linux-2.4.0-test2 tracing thread pid = 12262 Linux version 2.4.0-test2-1um (jd...@cc...) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Jun 27 14:32:31 EST 2000 On node 0 totalpages: 4096 zone(0): 256 pages. zone(1): 3840 pages. zone(2): 0 pages. Kernel command line: root=/dev/ubd0 Calibrating delay loop... 495.45 BogoMIPS Memory: 16080k available Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 4096 (order: 2, 16384 bytes) kmem_create: Poisoning requested, but con given - bdev_cache Inode-cache hash table entries: 1024 (order: 1, 8192 bytes) kmem_create: Poisoning requested, but con given - inode_cache VFS: Diskquotas version dquot_6.4.0 initialized POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.3 Based upon Swansea University Computer Society NET3.039 kmem_create: Poisoning requested, but con given - skbuff_head_cache NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 1024) Starting kswapd v1.6 pty: 256 Unix98 ptys configured RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: registered device at major 7 loop: enabling 8 loop devices Initializing stdio console driver Initializing software serial port version 0 serial line 0 assigned pty /dev/ptyp0 ssl receive thread is pid 12268 devfs: v0.101 (20000621) Richard Gooch (rg...@at...) devfs: devfs_debug: 0x0 devfs: boot_options: 0x0 VFS: Mounted root (ext2 filesystem) readonly. Mounted devfs on /dev INIT: version 2.76 booting Kernel panic: Double fault on 0xbffff87b - panicing because it wasn't fixed the first time The full slackware root filesystem is also in that directory: 2 root@sigh (~)# ls -l root_fs -rw-r--r-- 1 root root 629145600 Jun 28 13:15 root_fs - Gord R. Lamb (gl...@uf...) Systems Architect U|Force Inc. On Wed, 28 Jun 2000, Jeff Dike wrote: > Can we see the entire console output, including the command line? > > That address is on the main process stack, which is somewhat strange since > that stack isn't used for very much. In fact, that address is on the top > page of the stack, which definitely ought to be there. > > Jeff |
From: Jeff D. <jd...@ka...> - 2000-06-28 23:57:33
|
Can we see the entire console output, including the command line? That address is on the main process stack, which is somewhat strange since that stack isn't used for very much. In fact, that address is on the top page of the stack, which definitely ought to be there. Jeff |
From: Gord R. L. <gl...@uf...> - 2000-06-28 21:32:22
|
Hi everyone, Sorry if this question has been asked before (didn't see it in the faqs or list archive), but I'm having an interesting problem running the user mode linux kernel. It seems to be panicing shortly after init starts: <snip> VFS: Mounted root (ext2 filesystem) readonly. Mounted devfs on /dev INIT: version 2.76 booting Kernel panic: Double fault on 0xbffff874 - panicing because it wasn't fixed the first time </snip> It happens with both 2.4.0-pre1 and -pre2, running under host kernels 2.2.16 and 2.4.0-pre2. Also, I've tried two different systems (one uniprocessor, the other with 2 processors). I've tried the debian and slackware (small/large) root fs's. Any suggestions? - Gord R. Lamb (gl...@uf...) Systems Architect U|Force Inc. |
From: Jeff D. <jd...@ka...> - 2000-06-27 20:01:00
|
The user-mode port of 2.4.0-test2 is available. Not much is new in this one. It's updated to 2.4.0. I also added a 'no-xterm' switch to tell the console driver not to bring up xterms. It will grab a pty and tell you what it is via printk. You have to attach to it with minicom or kermit or something. The project's home page is http://user-mode-linux.sourceforge.net The project's download page is http://sourceforge.net/project/filelist.php?grou p_id=429 Jeff |
From: Jeff D. <jd...@ka...> - 2000-06-25 17:16:47
|
I have produced two bootable SlackWare 7.0 root filesystems. The small one is a minimal filesystem containing only the A (base system) series. The big one is a fairly complete system containing: A (base system) AP (base applications) D (development) E (The One True Editor :-) N (networking) XAP (X applications) The little one is 16 Meg compressed, the big one is 112 Meg. They're available at the project download page: http://sourceforge.net/project/filelist.php?group_id=429 Jeff |
From: Jeff D. <jd...@ka...> - 2000-06-22 01:29:38
|
Another release of the user-mode port of 2.3.99-pre9 is available. NOTE: The fhd device and its use of block major 62 are now GONE. If you haven't already, you need to update your filesystems to use ubd, block major 98, instead. Your fstab should refer to /dev/ubd/* rather than /dev/disk/* (if you're using devfs) or /dev/ubd* rather than /dev/fhd* (if you're not, and in this case, you also need to create the /dev/ubd* entries that you use). A number of bugs have been fixed, including the sporadic process seg faults and the network hang. Disk I/O is now asynchronous and interrupt driven. This is done by having a separate I/O thread which actually does the operations, and notifies the kernel when they are done. The project's home page is http://user-mode-linux.sourceforge.net The project's download page is http://sourceforge.net/project/filelist.php?grou p_id=429 Jeff |
From: Jeff D. <jd...@ka...> - 2000-06-01 12:54:28
|
pa...@su... said: > Nice. (I was hoping you did it other way: framebuffer driver in uml > which knows how to do X would be even cooler; the way you done it evil > application could connect to your X server directly and capture your > keystrokes; something what framebuffer driver would not allow). I did it that way to exercise the kernel and to demonstrate that it could run its own local X server. If you were running it as a sandbox, you would put the Xnest outside, running on the host. You'd make sure that it accepted connections from the virtual machine and that your native X server didn't. That way, the only server available to evil proggies running inside the virtual machine is the Xnest, which can be made to go away with a click of the mouse if it starts trying nasty things like creating infinite windows. Jeff |
From: Pavel M. <pa...@su...> - 2000-06-01 10:37:31
|
Hi! > > > This is most easy to > > > reproduce under X (start an xterm and a window manager and wave the > > > mouse in > > > and out of the xterm, and after a while, the xterm will stop blinking > > > and the > > > mouse will stop changing shape), but I've also seen it affect ping. > > > Does that mean that you can now run X under uml? > > Yeah, that's actually worked for a while. I just haven't gone out of my way > to publicize it. > > This is how to do it: > > Install the X clients in your favorite user-mode root filesystem. Make sure > you get Xnest. > Boot it up and bring the network up if it isn't already. > If necessary, xhost the virtual machine on the host. > In the virtual machine run 'DISPLAY=host:0 Xnest &' > You'll get an Xnest window, and you can then set your DISPLAY to :0 and run > whatever X clients you want. What I normally do is 'DISPLAY=:0 fvwm2 &' That > gives me a window manager and enough of an environment to do what I want > without needing to go back to the console. Nice. (I was hoping you did it other way: framebuffer driver in uml which knows how to do X would be even cooler; the way you done it evil application could connect to your X server directly and capture your keystrokes; something what framebuffer driver would not allow). Pavel -- I'm pa...@uc.... "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents me at di...@li... |
From: Jeff D. <jd...@ka...> - 2000-05-31 20:03:50
|
pa...@su... said: > > This is most easy to > > reproduce under X (start an xterm and a window manager and wave the > > mouse in > > and out of the xterm, and after a while, the xterm will stop blinking > > and the > > mouse will stop changing shape), but I've also seen it affect ping. > Does that mean that you can now run X under uml? Yeah, that's actually worked for a while. I just haven't gone out of my way to publicize it. This is how to do it: Install the X clients in your favorite user-mode root filesystem. Make sure you get Xnest. Boot it up and bring the network up if it isn't already. If necessary, xhost the virtual machine on the host. In the virtual machine run 'DISPLAY=host:0 Xnest &' You'll get an Xnest window, and you can then set your DISPLAY to :0 and run whatever X clients you want. What I normally do is 'DISPLAY=:0 fvwm2 &' That gives me a window manager and enough of an environment to do what I want without needing to go back to the console. This is a rerun url (I ran it last week as a demo of the virtual network), but have a look at http://user-mode-linux.sourceforge.net/net.html. It's a screenshot of a virtual net, but Xnest is also involved. Jeff |
From: Pavel M. <pa...@su...> - 2000-05-31 19:10:36
|
Hi! > The user-mode port of 2.3.99-pre9 is available. > > There is now a real hardware interrupt mechanism, which I got by copying the > i386 irq code, and wrapping user-mode stuff around it. The consoles and > network device now do their I/O off interrupts rather than the timer, which > greatly reduces latency. The interactive feel is much better, especially > under X. > > As a side-effect of this, 'cat /proc/interrupts' will no longer hang the > kernel :-) > > I fixed the stair-stepping problem with the console output. > > I also fixed the problem that some people had running kernels that they had > built themselves. So, if you built a -pre8 kernel from source, and it did > nothing but hang, that's fixed. > > I've also got some caveats to go with this batch of good news. Now that this > port is much more interrupt-driven, it is more prone to races. I've fixed a > bunch of them, but I still see an occasional process segfault. > > There is also a slight difficulty at times with the network. Sometimes > packets will stop flowing. I have no idea why, but typing at a console will > wake things up and get those packets flowing again. This is most easy to > reproduce under X (start an xterm and a window manager and wave the mouse in > and out of the xterm, and after a while, the xterm will stop blinking and the > mouse will stop changing shape), but I've also seen it affect ping. Does that mean that you can now run X under uml? -- I'm pa...@uc.... "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents me at di...@li... |
From: Jeff D. <jd...@ka...> - 2000-05-31 14:03:36
|
ua...@al... said: > I have read the how to on how to debug linux-uml, but I can't do the > following: > + a syscall > + bottom halves and other kernel contetxt processing > any comment would be greatly appreciated This is slightly complicated because the threads are already being ptraced, so gdb can't attach to them. What you do is get the thread you want to debug to stop where you want to debug it. Something like this is what I do: printk("here I am"); stop(); Send that thread a SIGUSR1, which tells the tracing thread to detach it. Attach to it with gdb. 'return' in gdb until you're out of the stop(). You're in business. Lars wrote some code that makes this simpler. I haven't bothered to integrate it in yet. It has the tracing thread ptrace gdb, and fake all of gdb's ptraces. That would make debugging the kernel a lot more like debugging a normal process. Jeff |