1) There is a link in /lib/modules/2.4.0.11: build->/usr/src/linuxcreated by the Makefile (make modules_install). What for?
2) (Answered)
3) (Answered)
4) Some of the device special files are missing when using devfs.
devfsd is running (loaded at the beginning of rc.S by init).
There was no /dev/lp0 on my system, even though module lp was loaded.
After creating this file explicitly with mknod, the printer worked.
5) This problem is probably the fault of X11 - it doesn't repaint the screen properly
after coming out of console mode. I have to switch back and forth several times
before I get a proper repaint. May be related to using framebuffer with X.
X crashes and locks completely when using sound. Anyone know why?
6) When going through the bash command history (using the arrow keys)
while in framebuffer mode, there will be a pause for about 3 seconds - during this time,
the system is totally frozen until this pause has expired. Any ideas on this?
I know this is a problem with bash - this problem doesn't occur when using tcsh.
7) How does one disable the display of the penguin logo when booting in framebuffer
mode so that all video lines are available for text? I know this can be removed with setfont
and possible fbset, but I would prefer the video display be "normal" from the start. Thanks.
-- Ted
[Android]
> 1) There is a link in /lib/modules/2.4.0.11: build->/usr/src/linuxcreated by the Makefile (make modules_install). What for?
Many people limit their e-mail messages to 80 columns. What for?
The 'build' symlink is to make it easier for external module
installation scripts to find the build directory for a given kernel.
This build directory, in turn, will yield the correct header files,
correct .config, correct compiler flags, etc., all of which can be
important for building a working module.
Peter
Peter Samuelson wrote:
>
<snip>
> Many people limit their e-mail messages to 80 columns. What for?
>
CF'mon, linebreaks are bloat! Those extra characters all around :-)
> The 'build' symlink is to make it easier for external module
> installation scripts to find the build directory for a given kernel.
> This build directory, in turn, will yield the correct header files,
> correct .config, correct compiler flags, etc., all of which can be
> important for building a working module.
>
I hope 2.4.0 then does that better than 2.2.17:
$ ls /lib/modules/2.2.17*/build -l
/lib/modules/2.2.17/build -> /usr/src/linux
/lib/modules/2.2.17i10-0001/build -> /usr/src/linux
/lib/modules/2.2.17i8-0001/build -> /usr/src/linux
/lib/modules/2.2.17i8-0002/build -> /usr/src/linux
/lib/modules/2.2.17i8p2/build -> /usr/src/linux
though in all cases /usr/src/linux was only a symlink to the
corresponding tree in /usr/src/Linux/2/2/17/...
Should that not be first converted to paths that contain no symlinks?
Marc
--
Marc Mutz <[email protected]> http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics
PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
[Marc Mutz <[email protected]>]
> Should that not be first converted to paths that contain no symlinks?
I agree.
--- Makefile~ Tue Nov 28 21:53:31 2000
+++ Makefile Fri Dec 1 12:25:28 2000
@@ -10,7 +10,7 @@
CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
else if [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi ; fi)
-TOPDIR := $(shell if [ "$$PWD" != "" ]; then echo $$PWD; else pwd; fi)
+TOPDIR := $(shell pwd -P)
HPATH = $(TOPDIR)/include
FINDHPATH = $(HPATH)/asm $(HPATH)/linux $(HPATH)/scsi $(HPATH)/net
Peter Samuelson wrote:
>
<snip>
> +TOPDIR := $(shell pwd -P)
<snip>
That is specific to the bash builtin 'pwd'. GNU sh-util's pwd does not
know that option (at least not my version, which is: "pwd (GNU sh-utils)
1.16")
I just wanted to note that...
Marc
--
Marc Mutz <[email protected]> http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics
PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
[Marc Mutz]
> > +TOPDIR := $(shell pwd -P)
> That is specific to the bash builtin 'pwd'. GNU sh-util's pwd does
> not know that option (at least not my version, which is: "pwd (GNU
> sh-utils) 1.16")
It passed my 5-second shell feature portability test (ash). Checking
again, I see that the ash 'pwd' just ignores its arguments, but doesn't
need '-P' because it doesn't maintain an internal pwd.... Oh well.
Peter