devil-linux-develop — developer discussions

Re: [Devil-linux-develop] Abort.

[Bruce S. <bw...@ar...>]

> > >/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:214:25: #if with
> > >no expression
> > 
> > Since it's the packet scheduler, I guess the problem is the new sed command
> > from Jaroslav
> 
> Is variable CONFIG_PSCHED_CLOCK_SOURCE defined in your /build/.config 
> file? 

Nope.

> You have to rerun 'make menuconfig' to create it.

OK, I'll try again.  Thanks!

 - BS

Re: [Devil-linux-develop] Abort.

[Jaroslav K. <pe...@pe...>]

On Wed, 24 Mar 2004 hzu...@ra... wrote:

> 
> >/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:214:25: #if with
> >no expression
> 
> Since it's the packet scheduler, I guess the problem is the new sed command
> from Jaroslav

Is variable CONFIG_PSCHED_CLOCK_SOURCE defined in your /build/.config 
file? You have to rerun 'make menuconfig' to create it.

						Jaroslav

-----
Jaroslav Kysela <pe...@pe...>

Re: [Devil-linux-develop] Abort.

[<hzu...@ra...>]

On 03/24/2004 08:45:12 AM Bruce Smith wrote:
>New lfs, mrproper, after all the updates last night, except for
>grsecurity 1.19.  However, I did NOT have grsecurity selected in
>menuconfig, so that shouldn't matter.

[....]

>/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:194:25: #if with
>no expression
>/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:214:25: #if with
>no expression
>/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:252:27: #if with
>no expression
>/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:300:25: #if with
>no expression
>make[4]: *** [dev.o] Error 1
>make[4]: Leaving directory `/data/build/tmp/linux-2.4.25/net/core'
>make[3]: *** [first_rule] Error 2
>make[3]: Leaving directory `/data/build/tmp/linux-2.4.25/net/core'
>make[2]: *** [_subdir_core] Error 2
>make[2]: Leaving directory `/data/build/tmp/linux-2.4.25/net'
>make[1]: *** [_dir_net] Error 2
>make[1]: Leaving directory `/data/build/tmp/linux-2.4.25'

Since it's the packet scheduler, I guess the problem is the new sed command
from Jaroslav

Heiko

[Devil-linux-develop] Abort.

[Bruce S. <bw...@ar...>]

New lfs, mrproper, after all the updates last night, except for
grsecurity 1.19.  However, I did NOT have grsecurity selected in
menuconfig, so that shouldn't matter.


make[3]: Entering directory `/data/build/tmp/linux-2.4.25/net/core'
make all_targets
make[4]: Entering directory `/data/build/tmp/linux-2.4.25/net/core'
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=sock  -c -o sock.o sock.c
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=skbuff  -c -o skbuff.o skbuff.c
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=iovec  -c -o iovec.o iovec.c
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=datagram  -c -o datagram.o datagram.c
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=scm  -c -o scm.o scm.c
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=sysctl_net_core  -c -o sysctl_net_core.o sysctl_net_core.c
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=filter  -c -o filter.o filter.c
gcc -D__KERNEL__ -I/data/build/tmp/linux-2.4.25/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer  -pipe -mpreferred-stack-boundary=2 -march=i686   -nostdinc -iwithprefix include -DKBUILD_BASENAME=dev  -c -o dev.o dev.c
In file included from dev.c:96:
/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:194:25: #if with no expression
/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:214:25: #if with no expression
/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:252:27: #if with no expression
/data/build/tmp/linux-2.4.25/include/net/pkt_sched.h:300:25: #if with no expression
make[4]: *** [dev.o] Error 1
make[4]: Leaving directory `/data/build/tmp/linux-2.4.25/net/core'
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory `/data/build/tmp/linux-2.4.25/net/core'
make[2]: *** [_subdir_core] Error 2
make[2]: Leaving directory `/data/build/tmp/linux-2.4.25/net'
make[1]: *** [_dir_net] Error 2
make[1]: Leaving directory `/data/build/tmp/linux-2.4.25'

Re: [Devil-linux-develop] Mailing list archive?

[Bruce S. <bw...@ar...>]

> > Besides the Sourceforge mailing list archive (which is currently down), is 
> > there any other archive of the DL development and discuss lists?
> 
> Not that I'm aware of it.
> 
> > Is it possible to search through the Sourceforge mailing list archive? I've 
> > never found a way but may be missing something obvious.
> 
> I don't think there's a way.

If google indexes the sourceforge pages, you can go to the advanced
search and limit your search to the DL list archive on sourceforge.

I've done it to search other mailing list archives.  I've never tried it
on a sourceforge hosted list, so I don't know if it'll work.  Try it!

 - BS

Re: [Devil-linux-develop] Mailing list archive?

[Heiko Z. <he...@zu...>]

Martin Glazer wrote:
> Hey all,
> 
> Besides the Sourceforge mailing list archive (which is currently down), is 
> there any other archive of the DL development and discuss lists?

Not that I'm aware of it.


> Is it possible to search through the Sourceforge mailing list archive? I've 
> never found a way but may be missing something obvious.

I don't think there's a way.

Heiko

Re: [Devil-linux-develop] variable HZ patch for 2.4 kernels & more

[Jaroslav K. <pe...@pe...>]

On Tue, 23 Mar 2004, Heiko Zuerker wrote:

> > 2) the PSCHED_CLOCK_SOURCE setup is universal and independent on the 
> >    variable HZ patch, so I moved it outside CONFIG_HZ conditions
> 
> Didn't use this, since both patches are in 1 file, which means both 
> always get applied.
> 
> > 3) fixes in prepare (duplicate PSCHED_CLOCK_SOURCE work, possible 
> >    duplicate CONFIG_HZ setup)
> 
> Didn't use this, there are no duplicates.

Oops. Sorry. I was confused, because cvs merged my code with yours.
I've attached the corrected code. For sure: The PSCHED_CLOCK_SOURCE
setup modifies one line in $KERNELDIR/include/net/pkt_sched.h
which is present in both 2.4 and 2.6 kernels including vanilla,
so it's safe to use this settings separately from the variable HZ
patch. It's not a patch but the direct code modification using sed.

					Jaroslav

-----
Jaroslav Kysela <pe...@pe...>

Re: [Devil-linux-develop] variable HZ patch for 2.4 kernels & more

[Heiko Z. <he...@zu...>]

Jaroslav Kysela wrote:
> On Mon, 22 Mar 2004, Heiko Zuerker wrote:
> 
> 
>>Jaroslav Kysela wrote:
>>
>>>1) get vhz+jiffies64 patch from rml
>>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/rml/variable-HZ/v2.4/vhz-j64-2.4.23.patch
>>
>>This patch is the cause why busybox doesn't compile.
>>I'll change the build system so we can turn the patch on/off via menuconfig.
> 
> 
> Hi,
> 
> 	attached two patches fix the following problems:
> 
> 1) busybox compilation (vhz-param.patch.bz2)

Added

> 2) the PSCHED_CLOCK_SOURCE setup is universal and independent on the 
>    variable HZ patch, so I moved it outside CONFIG_HZ conditions

Didn't use this, since both patches are in 1 file, which means both 
always get applied.

> 3) fixes in prepare (duplicate PSCHED_CLOCK_SOURCE work, possible 
>    duplicate CONFIG_HZ setup)

Didn't use this, there are no duplicates.

> 
> Installation:
> 
> - copy vhz-param.patch.bz2 to $DL_DIR/src
> - apply vhz-cvs.patch to DL CVS

I'll run a test compile later today.

cu
  Heiko

Re: [Devil-linux-develop] Build 1.1 failed

[<hzu...@ra...>]

On 03/23/2004 09:28:57 AM Philippe Midol-Monnet wrote:
>Heiko Zuerker wrote:
>> Philippe Midol-Monnet wrote:
>>
>>>
>>> I try tio build version 1.1 from scratch. But the builed process
>>> failed during gcc compilation.
>>> In the log file I have the following result:
>>>
>>> stage1/xgcc -Bstage1/ -B/usr/i586-pc-linux-gnu/bin/   -g -O2 -DIN_GCC
>>> -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
>>> -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H    -I. -I.
>>> -I../../gcc-3.3.2/gcc -I../../gcc-3.3.2/gcc/.
>>> -I../../gcc-3.3.2/gcc/config -I../../gcc-3.3.2/gcc/../include -c
>>> insn-recog.c \
>>>   -o insn-recog.o
>>> xgcc: Internal error: Killed (program cc1)
>>> Please submit a full bug report.
>>> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>>> make[3]: *** [insn-recog.o] Error 1
>>> make[3]: Leaving directory `/data/build/tmp/gcc-build/gcc'
>>> make[2]: *** [stage2_build] Error 2
>>> make[2]: Leaving directory `/data/build/tmp/gcc-build/gcc'
>>> make[1]: *** [bootstrap] Error 2
>>> make[1]: Leaving directory `/data/build/tmp/gcc-build'
>>>
>>> When I run the last command by hand (insn-recog.c compilation) it
>>> works fine.
>>>
>>> Any idea ?
>>
>>
>> Did you start with a fresh lfssystem ? If not do so and also update
>from
>> CVS and FTP again.
>>
>> Sometimes you discover problems with computers while compiling DL,
>which
>> are otherwise hidden. The problems can be bad RAM, wrong RAM timing,
>> other BIOS settings. Try to use "safe" BIOS settings and replace the
>RAM
>> if the problem persists.
>
>I get around the problem. After the buid process failed, I launch by
>hand the make in the temporary build directory. The build restart and
>failed later. I relaunch the make as many time as necessary and it
>works!!
>
>May be a problem  with chroot ?? It seems a system resource became
>either full, unavailable or saturate (disk, tmp, mem...?).
>
>After that, I can restart the "make build" but I have another pb with
>grub-0.93+cvs20031021 during configure phase the gcc option
>-fno-stack-protector is unrecognised
>I'm still investigating this..

This means that the SSP patch didn't get applied to gcc.
Try to recompile gcc using our script, this has to work.

Heiko

[Devil-linux-develop] Mailing list archive?

[Martin G. <sou...@gl...>]

Hey all,

Besides the Sourceforge mailing list archive (which is currently down), is 
there any other archive of the DL development and discuss lists?

Is it possible to search through the Sourceforge mailing list archive? I've 
never found a way but may be missing something obvious.

Thanks

Martin

Re: [Devil-linux-develop] Build 1.1 failed

[Philippe Midol-M. <pmi...@so...>]

Heiko Zuerker wrote:
> Philippe Midol-Monnet wrote:
> 
>>
>> I try tio build version 1.1 from scratch. But the builed process 
>> failed during gcc compilation.
>> In the log file I have the following result:
>>
>> stage1/xgcc -Bstage1/ -B/usr/i586-pc-linux-gnu/bin/   -g -O2 -DIN_GCC 
>> -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes 
>> -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H    -I. -I. 
>> -I../../gcc-3.3.2/gcc -I../../gcc-3.3.2/gcc/. 
>> -I../../gcc-3.3.2/gcc/config -I../../gcc-3.3.2/gcc/../include -c 
>> insn-recog.c \
>>   -o insn-recog.o
>> xgcc: Internal error: Killed (program cc1)
>> Please submit a full bug report.
>> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>> make[3]: *** [insn-recog.o] Error 1
>> make[3]: Leaving directory `/data/build/tmp/gcc-build/gcc'
>> make[2]: *** [stage2_build] Error 2
>> make[2]: Leaving directory `/data/build/tmp/gcc-build/gcc'
>> make[1]: *** [bootstrap] Error 2
>> make[1]: Leaving directory `/data/build/tmp/gcc-build'
>>
>> When I run the last command by hand (insn-recog.c compilation) it 
>> works fine.
>>
>> Any idea ?
> 
> 
> Did you start with a fresh lfssystem ? If not do so and also update from 
> CVS and FTP again.
> 
> Sometimes you discover problems with computers while compiling DL, which 
> are otherwise hidden. The problems can be bad RAM, wrong RAM timing, 
> other BIOS settings. Try to use "safe" BIOS settings and replace the RAM 
> if the problem persists.

I get around the problem. After the buid process failed, I launch by 
hand the make in the temporary build directory. The build restart and 
failed later. I relaunch the make as many time as necessary and it works!!

May be a problem  with chroot ?? It seems a system resource became 
either full, unavailable or saturate (disk, tmp, mem...?).

After that, I can restart the "make build" but I have another pb with 
grub-0.93+cvs20031021 during configure phase the gcc option 
-fno-stack-protector is unrecognised
I'm still investigating this..

-- 
Philippe Midol-Monnet
pmi...@so...

Re: [Devil-linux-develop] Build 1.1 failed

[Heiko Z. <he...@zu...>]

Philippe Midol-Monnet wrote:
> 
> I try tio build version 1.1 from scratch. But the builed process failed 
> during gcc compilation.
> In the log file I have the following result:
> 
> stage1/xgcc -Bstage1/ -B/usr/i586-pc-linux-gnu/bin/   -g -O2 -DIN_GCC -W 
> -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes 
> -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H    -I. -I. 
> -I../../gcc-3.3.2/gcc -I../../gcc-3.3.2/gcc/. 
> -I../../gcc-3.3.2/gcc/config -I../../gcc-3.3.2/gcc/../include -c 
> insn-recog.c \
>   -o insn-recog.o
> xgcc: Internal error: Killed (program cc1)
> Please submit a full bug report.
> See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> make[3]: *** [insn-recog.o] Error 1
> make[3]: Leaving directory `/data/build/tmp/gcc-build/gcc'
> make[2]: *** [stage2_build] Error 2
> make[2]: Leaving directory `/data/build/tmp/gcc-build/gcc'
> make[1]: *** [bootstrap] Error 2
> make[1]: Leaving directory `/data/build/tmp/gcc-build'
> 
> When I run the last command by hand (insn-recog.c compilation) it works 
> fine.
> 
> Any idea ?

Did you start with a fresh lfssystem ? If not do so and also update from 
CVS and FTP again.

Sometimes you discover problems with computers while compiling DL, which 
are otherwise hidden. The problems can be bad RAM, wrong RAM timing, 
other BIOS settings. Try to use "safe" BIOS settings and replace the RAM 
if the problem persists.

Heiko

Re: [Devil-linux-develop] variable HZ patch for 2.4 kernels & more

[Jaroslav K. <pe...@pe...>]

On Mon, 22 Mar 2004, Heiko Zuerker wrote:

> Jaroslav Kysela wrote:
> > 1) get vhz+jiffies64 patch from rml
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/rml/variable-HZ/v2.4/vhz-j64-2.4.23.patch
> 
> This patch is the cause why busybox doesn't compile.
> I'll change the build system so we can turn the patch on/off via menuconfig.

Hi,

	attached two patches fix the following problems:

1) busybox compilation (vhz-param.patch.bz2)
2) the PSCHED_CLOCK_SOURCE setup is universal and independent on the 
   variable HZ patch, so I moved it outside CONFIG_HZ conditions
3) fixes in prepare (duplicate PSCHED_CLOCK_SOURCE work, possible 
   duplicate CONFIG_HZ setup)

Installation:

- copy vhz-param.patch.bz2 to $DL_DIR/src
- apply vhz-cvs.patch to DL CVS

						Jaroslav

-----
Jaroslav Kysela <pe...@pe...>

[Devil-linux-develop] Build 1.1 failed

[Philippe Midol-M. <pmi...@so...>]

I try tio build version 1.1 from scratch. But the builed process failed 
during gcc compilation.
In the log file I have the following result:

stage1/xgcc -Bstage1/ -B/usr/i586-pc-linux-gnu/bin/   -g -O2 -DIN_GCC 
-W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes 
-Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H    -I. -I. 
-I../../gcc-3.3.2/gcc -I../../gcc-3.3.2/gcc/. 
-I../../gcc-3.3.2/gcc/config -I../../gcc-3.3.2/gcc/../include -c 
insn-recog.c \
   -o insn-recog.o
xgcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [insn-recog.o] Error 1
make[3]: Leaving directory `/data/build/tmp/gcc-build/gcc'
make[2]: *** [stage2_build] Error 2
make[2]: Leaving directory `/data/build/tmp/gcc-build/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/data/build/tmp/gcc-build'

When I run the last command by hand (insn-recog.c compilation) it works 
fine.

Any idea ?

-- 
Philippe Midol-Monnet
pmi...@so...

Re: [Devil-linux-develop] booting from network?

[Jeroen R. <roo...@xs...>]

On 23-3-2004 01:50, Heiko Zuerker wrote:

> Physical write protection for CF cards?
> I guess I have to check the transcend website...

They are not CF cards. 
<http://www.transcendusa.com/FlashCard/FLSMod.asp?CatID=15> is the main 
page about Transcend's IDE Flash Modules. The PDFs you can get there as 
well as the page itself say: "Write-Protect function supported". I'm 
only guessing, but I take it that they don't mean loading a filesystem 
read-only there, or that they mean setting a bit on the card through 
software (which could be reset while the system is running). Of course, 
if you were to set it by way of a jumper, you'd need to open the system 
case just to change the configuration...


    Jeroen Roovers

Re: [Devil-linux-develop] variable HZ patch for 2.4 kernels & more

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:
>>>1) get vhz+jiffies64 patch from rml
>>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/rml/variable-HZ/v2.4/vhz-j64-2.4.23.patch
>>
>>This patch is the cause why busybox doesn't compile.
>>I'll change the build system so we can turn the patch on/off via menuconfig.
> 
> 
> I have grsecurity turned off, and busybox still aborted on me.

I just checked something in, which will solve this problem.
Set VHZ (Build Configuration / Processor and Memory) to OFF.

You need to do a mrproper in order to activate it.

Heiko

Re: [Devil-linux-develop] [ devil-linux-Bugs-920595 ] linux-wlan-ng have unresolved symbols with pcmcia-cs

[Heiko Z. <he...@zu...>]

Diego Torres wrote:
> On Mon, Mar 22, 2004 at 05:33:27PM -0500, Bruce Smith wrote:
> 
>>>>>wow!! we need it :)
>>>>
>>>>So you volunteer to include it ?
>>>
>>>bruce was first :)
>>
>>I was only asking about it!  :-)
>>
>>I don't think we need both.  Should we replace memtest86 with memtest+?
>>I could probably do it ...
> 
> 
> i think that memtest+ is superior to memtest86, so... i say yes :)

Why not, let's give it a try.

You could even make it selectable, which one should be included.

Heiko

Re: [Devil-linux-develop] booting from network?

[Heiko Z. <he...@zu...>]

Jeroen Roovers wrote:
> On 22-3-2004 19:14, hzu...@ra... wrote:
> 
>>> yeah, but usb sticks have to remain inserted on the router box.. and i
>>> don't want to imagine about the people that unplugs them asking "what
>>> is this shiny little thing?" :)
>>
>>
>>
>> Glue it.
> 
> 
> Or buy a 64MB-1GB IDE Flash Module from Transcend. I am having 
> tremendous fun with a brilliant 64MB Apacer S-ADM (also an IDE connected 
> flash memory device, but seemingly no longer for sale locally). It's a 
> generically looking IDE drive (to an OS) but absolutely silent and fast 
> enough for most tasks (reading mainly). The Transcend parts can even be 
> physically set to read-only, and you lock them away tightly in the 
> system case of course, instead of having them dangling out dangerously. 
> They're cheap too.

Physical write protection for CF cards?
I guess I have to check the transcend website...

Heiko

Re: [Devil-linux-develop] variable HZ patch for 2.4 kernels & more

[Bruce S. <bw...@ar...>]

> > 1) get vhz+jiffies64 patch from rml
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/rml/variable-HZ/v2.4/vhz-j64-2.4.23.patch
> 
> This patch is the cause why busybox doesn't compile.
> I'll change the build system so we can turn the patch on/off via menuconfig.

I have grsecurity turned off, and busybox still aborted on me.

 - BS

Re: [Devil-linux-develop] variable HZ patch for 2.4 kernels & more

[Heiko Z. <he...@zu...>]

Jaroslav Kysela wrote:
> 1) get vhz+jiffies64 patch from rml
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/rml/variable-HZ/v2.4/vhz-j64-2.4.23.patch

This patch is the cause why busybox doesn't compile.
I'll change the build system so we can turn the patch on/off via menuconfig.

Heiko

Re: [Devil-linux-develop] [ devil-linux-Bugs-920595 ] linux-wlan-ng have unresolved symbols with pcmcia-cs

[Diego T. <dt...@co...>]

On Mon, Mar 22, 2004 at 05:33:27PM -0500, Bruce Smith wrote:
> > > >wow!! we need it :)
> > > 
> > > So you volunteer to include it ?
> > 
> > bruce was first :)
> 
> I was only asking about it!  :-)
> 
> I don't think we need both.  Should we replace memtest86 with memtest+?
> I could probably do it ...

i think that memtest+ is superior to memtest86, so... i say yes :)
-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dtorres at anthalia dot org - Madrid / España

Re: [Devil-linux-develop] [ devil-linux-Bugs-920595 ] linux-wlan-ng have unresolved symbols with pcmcia-cs

[Bruce S. <bw...@ar...>]

> > >most popular chipsets. For exemple, on i865PE/i875P series, memtest
> > 86+ will now display FSB & Memory frequency, PAT status, memory timings, 
> > ECC status and the number of memory channels. Next version will perhaps 
> > contain several enhancements and bug-fixes.
> > >
> > >wow!! we need it :)
> > 
> > So you volunteer to include it ?
> 
> bruce was first :)

I was only asking about it!  :-)

I don't think we need both.  Should we replace memtest86 with memtest+?
I could probably do it ...

 - BS

Re: [Devil-linux-develop] booting from network?

[Jeroen R. <roo...@xs...>]

On 22-3-2004 19:14, hzu...@ra... wrote:

>>yeah, but usb sticks have to remain inserted on the router box.. and i
>>don't want to imagine about the people that unplugs them asking "what
>>is this shiny little thing?" :)
> 
> 
> Glue it.

Or buy a 64MB-1GB IDE Flash Module from Transcend. I am having 
tremendous fun with a brilliant 64MB Apacer S-ADM (also an IDE connected 
flash memory device, but seemingly no longer for sale locally). It's a 
generically looking IDE drive (to an OS) but absolutely silent and fast 
enough for most tasks (reading mainly). The Transcend parts can even be 
physically set to read-only, and you lock them away tightly in the 
system case of course, instead of having them dangling out dangerously. 
They're cheap too.


    Jeroen Roovers

Re: [Devil-linux-develop] booting from network?

[Diego T. <dt...@co...>]

On Mon, Mar 22, 2004 at 01:14:46PM -0500, hzu...@ra... wrote:
> >yeah, but usb sticks have to remain inserted on the router box.. and i
> >don't want to imagine about the people that unplugs them asking "what
> >is this shiny little thing?" :)
> 
> Glue it.

only when i have a way to update it without using gasoline to dissolve the glue :)
-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dtorres at anthalia dot org - Madrid / España

Re: [Devil-linux-develop] booting from network?

[<hzu...@ra...>]

On 03/22/2004 12:21:17 PM Diego Torres wrote:
>On Mon, Mar 22, 2004 at 08:47:44AM -0500, Heiko Zuerker wrote:
>
>> Mounting the ISO file over a network? That should be quite
>interesting....
>> This would also require some major changes to our init system, i.e.
>you
>> would need network support in the initrd.
>
>yes, i'd need a couple of networ drivers there... (i was thinking,
>booting from a wireless pcmcia card is too much, right? :))

It's doable, but I think you will have a lot of problems using the remotely
mounted ISO.
The slightest network problem and BANG.

>> I think it would be better to use a CF card or USB stick and
>implement a
>> remote update (parts are already existing).
>
>yeah, but usb sticks have to remain inserted on the router box.. and i
>don't want to imagine about the people that unplugs them asking "what
>is this shiny little thing?" :)

Glue it.

Heiko