devil-linux-discuss — General Mailing List for all discussions

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Serge L. <fi...@in...>]

Hi,

Jan Hugo Prins wrote:

>> PS. Could you please check if "man" on your system works correctly with gzipped
>> man files (ex. 'man 1 cat' )? I'm not sure, but it looks like a small bug in man
>> config.
>>
>>   
> This is indeed not correct. It forgets to gunzip the man page.
> 
You can fix it in your working system. No rebuild is required. There is "-d"
missed for gzipped source.

--- etc/man.conf.wrong  2007-07-11 10:28:46.000000000 +0400
+++ etc/man.conf        1980-01-01 01:01:01.000000000 +0300
@@ -134,7 +134,7 @@
 # Decompress with given decompressor when input file has given extension
 # The command given must act as a filter.
 #
-.gz            /bin/gunzip -c
+.gz            /bin/gunzip -c -d
 .bz2           /bin/bzip2 -c -d
 .z
 .Z             /bin/zcat



--
 Serge Leschinsky

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Jan H. P. <jh...@jh...>]

Serge Leschinsky wrote:
> It will be great if you can share us the result of your customization... :-)
>
>   
Ok,
Yesterday evening I've been busy till late at night to get my router up 
and running and it looks like it is working at the momnt.
The biggest problem that I ran into was the fact that the initialisation 
script for networking are all still based on the old ifconfig 
applications instead of the newer iproute2 package that is included in 
the Devil Linux distribution. And any configuration that I tried failed 
with some error about duplicate addresses etc although there were onle 
single addresses configured in the interface files. Maybe it is time to 
create some new network initialisation scripts that use the iproute2 
package.

After some tinkering with this I decided to fully configure my 
interfaces through the fwbuilder script that I was creating anyway and I 
threw out all the interface files located under /etc/sysconfig/nic.
This put me on a track of manually configuring all interfaces from a 
interface/firewall script so I could use this script in one run for 
those missing things like SIT configuration etc.

The IPv6 firewall that I created is a bunch of lines with at the moment 
only the most basic things like nothing in except related/established stuff.
I hope to put this into fwbuilder script some day, but as far as I know 
fwbuilder IPv6 support is far from existing.

More to follow.
Jan Hugo Prins

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Jan H. P. <jh...@jh...>]

Serge Leschinsky wrote:
> ....
> Thank you. I'll try to fix it.
>
>   
Ok, I will look forward to it.

> It will be great if you can share us the result of your customization... :-)
>   
Sure, if anything usefull comes out of my customizations I will share it.

> PS. Could you please check if "man" on your system works correctly with gzipped
> man files (ex. 'man 1 cat' )? I'm not sure, but it looks like a small bug in man
> config.
>
>   
This is indeed not correct. It forgets to gunzip the man page.


Greetings,
Jan Hugo Prins

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Serge L. <fi...@in...>]

Hi,

Jan Hugo Prins wrote:

> Found something else for you, the custom-cd script uses some parameters 
> for mkisofs that are depricated:
....
Thank you. I'll try to fix it.


> 
> For the rest, next wednesday evening I'm planning on putting the CD in 
> my router and see if it works.
> Currently busy customizing with things like IPv6 SIT tunnel etc.
It will be great if you can share us the result of your customization... :-)

PS. Could you please check if "man" on your system works correctly with gzipped
man files (ex. 'man 1 cat' )? I'm not sure, but it looks like a small bug in man
config.

-- 
 Serge Leschinsky

Re: [Devil-Linux-discuss] Build problem for devil linux 1.2.14; quagga doc does not install

[<ee...@fr...>]

Hi Franz,

Franz Regensburger a écrit :
> Hello all,
> two days ago I was downloading and building
> 	devil linux from CVS with tag 'rel-1-2-patches'
> This is currently a 1.2.14.
> I use lfssystem-for-DL-1.0_and_up
>
>   
that's what I use and seems the good one,

> make build: OK
> make install: yields an error for componet quagga:
>
> # executing quagga with option install (in /data/build/tmp/quagga-0.99.7)
> # ERROR
> # /data/build/scripts/quagga install failed
> # check log file /data/build/tmp/LOGS/install/quagga for details
>
> Reason: the bulding of the texinfo files does not work.
> Command tex2dvi reports lots of errors during processing of file
> 	routeserver.texi
> Unknown command @float ....
>
> When I disable the processing of file routeserver.texi (remove the include 
> directive) I get similar errors for the other *.texi files.
> The texinfo environment seems to be broken somehow.
>
>   

Never had this kind of errors about .texi files ...
I did a lot of builds last weeks, and when I encounter "stranges" build
errors, I start from scratch with a fresh new lfssystem install ...

Move your .../data/build/src/ directory out of the lfssystem path to
save you from downloading again all the sources files which is the
longer and bandwidth consumming part ;)
And restore it after the cvs sync; then do an update_src against n°1 in
the list to ensure nothing has changed in the last hours ... you should
have no md5sum errors.

> Is this a known bug?
>
>   
Hope it helps,

Regards,

MaNU

> If I disable QUAGGA in .config the rest works fine (install,iso,dist)
>
> Regards,
>
> Franz
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>   

[Devil-Linux-discuss] Build problem for devil linux 1.2.14; quagga doc does not install

[Franz R. <Fra...@od...>]

Hello all,
two days ago I was downloading and building
	devil linux from CVS with tag 'rel-1-2-patches'
This is currently a 1.2.14.
I use lfssystem-for-DL-1.0_and_up

make build: OK
make install: yields an error for componet quagga:

# executing quagga with option install (in /data/build/tmp/quagga-0.99.7)
# ERROR
# /data/build/scripts/quagga install failed
# check log file /data/build/tmp/LOGS/install/quagga for details

Reason: the bulding of the texinfo files does not work.
Command tex2dvi reports lots of errors during processing of file
	routeserver.texi
Unknown command @float ....

When I disable the processing of file routeserver.texi (remove the include 
directive) I get similar errors for the other *.texi files.
The texinfo environment seems to be broken somehow.

Is this a known bug?

If I disable QUAGGA in .config the rest works fine (install,iso,dist)

Regards,

Franz

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Jan H. P. <jh...@jh...>]

Serge Leschinsky wrote:
> Hi,
>
> Jan Hugo Prins wrote:
>   
>> But when I do a shutdown -h now it tries to do a  rmdir 
>> (/dev/.udev/failed) but  he comes back with some readonly error and this 
>> keeps scrolling.
>> Don't know where this comes from yet.
>>     
>
> It should help.
>   
Thanks, that fixed this one indeed.
Found something else for you, the custom-cd script uses some parameters 
for mkisofs that are depricated:

       -P     Outdated  option  reserved  by  POSIX.1-2001,   use   
-publisher
              instead.   This  option  will  get  POSIX.1-2001  
semantics with
              mkisofs-2.02.

       -publisher publisher_id
              Specifies a text string that will be  written  into  the  
volume
              header.   This  should describe the publisher of the 
CDROM, usu-
              ally with a mailing address and phone number.  There is 
space on
              the  disc for 128 characters of information.  This 
parameter can
              also be set in the file .mkisofsrc with PUBL=.  If 
specified  in
              both places, the command line version is used.

       -L     Outdated  option  reserved  by  POSIX.1-2001,  use  
-allow-lead-
              ing-dots  instead.   This option will get POSIX.1-2001 
semantics
              with mkisofs-2.02.

For the rest, next wednesday evening I'm planning on putting the CD in 
my router and see if it works.
Currently busy customizing with things like IPv6 SIT tunnel etc.

Jan Hugo

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Serge L. <fi...@in...>]

Hi,

Jan Hugo Prins wrote:
> But when I do a shutdown -h now it tries to do a  rmdir 
> (/dev/.udev/failed) but  he comes back with some readonly error and this 
> keeps scrolling.
> Don't know where this comes from yet.

It should help.


diff -aur config/etc/init.d/mountfs config/etc/init.d/mountfs.my
--- config/etc/init.d/mountfs   2007-07-09 14:51:49.000000000 +0400
+++ config/etc/init.d/mountfs.my        2007-07-09 14:45:10.000000000 +0400
@@ -198,7 +198,7 @@

                echo -n "Unmounting file systems..."
                #/bin/umount -n -a -r
-               cat /proc/mounts | cut -f -3 -d " " | grep -v -e "shm$" -e
"rootfs$" -e "devfs$" -e " proc" | cut -f 2 -d " " | xargs -n 1 umount -rn
+               cat /proc/mounts | cut -f -3 -d " " | grep -v -e "tmpfs$" -e
"rootfs$" -e "sysfs$" -e " proc" -e "devpts" | cut -f 2 -d " " | xargs -n 1
umount -rn
                evaluate_retval

                # shutdown LVM if tools are installed

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Jan H. P. <jh...@jh...>]

> Then, how do I enable IPv6 and configure this on a interface? I mean,
> what are the options in the ifcfg-eth files?
> And the same for creating a sit tunnel. Any documentation arround about
> this?
> Somewhere in 1.1.2 the options are added but can't find them anywhere.

ok, I found the options to at a IPv6 address to an interface.
Now the sit tunnel. Maybe I just have to write a script and put it in the
startup somewhere to create a sit tunnel.

Jan Hugo

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Jan H. P. <jh...@jh...>]

Serge Leschinsky wrote:
> Hi,
>
> Jan Hugo Prins wrote:
>   
>> Hi,
>>
>> I'm currently trying to get Devil-Linux 1.3.4 working, and though my 
>> build finishes I run into troubles with the linuxrd scripts.
>> I have unpacked the initrd.gz file and added some checks to the linurc 
>> script that is included to see what modules are loaded and what devices 
>> are available just before it tries open the CDRom and load the config files.
>>     
>  Fixed. You have to rebuild busybox with new config file ( please sync again  or
> just add mdev applet to busybox).
>
>   
Check.
This works indeed.
But when I do a shutdown -h now it tries to do a  rmdir 
(/dev/.udev/failed) but  he comes back with some readonly error and this 
keeps scrolling.
Don't know where this comes from yet.

Then, how do I enable IPv6 and configure this on a interface? I mean, 
what are the options in the ifcfg-eth files?
And the same for creating a sit tunnel. Any documentation arround about 
this?
Somewhere in 1.1.2 the options are added but can't find them anywhere.

Jan Hugo

Re: [Devil-Linux-discuss] Q: IDE Flash Boot?

[Indiana E. a. C. N. <Bra...@Sk...>]

On Tue, 03 Jul 2007 08:59:35 +0200, you wrote:

>oh hi
>
>> > I guess I just need to block packets I don't specify for fowarding?
>> Is
>> > 32 MB RAM adequate for this?
>> 
>> I would guess yes, but I can't promise it.
>> It's quite a while ago since I tested DL with anything less then 64MB.
>DL boxes with 32 megs of ram work like a charm for us, terminating openvpn tunnels too :)

Thanks, that is encouraging!
-- 
Don Stauffer, Office Manager
Indiana Epilepsy and Child Neurology, Inc.

Re: [Devil-Linux-discuss] Trying to build 1.3.4 with very little enabled.

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

On Fri, July 6, 2007 04:54, Serge Leschinsky wrote:
> Heiko,
>
>
>>>> I've just updated the source and got the same error as you. Sorry
>>>> for my misunderstanding. I suggest to use syslinux 3.36 as a
>>>> temporary workaround. I'm going to investigate it but the process
>>>> can take a couple weekends.
>>> Check if it's fixed in 1.2.x, I may have simply forgotten to sync 1.2
>>> with 1.3.
>>>
>>>
>> Thank you, I'll check.
>>
>>
>
> you have forgotten nothing. Basically I still can't compile it. May be
> it's my local problem.

I may have found it, checked it in CVS already.
The name of the GCC config parameter changed, it's now CONFIG_GCC_HARDENED .

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] Trying to build 1.3.4 with very little enabled.

[Serge L. <fi...@in...>]

Heiko,

>>> I've just updated the source and got the same error as you. Sorry for my
>>> misunderstanding. I suggest to use syslinux 3.36 as a temporary
>>> workaround. I'm going to investigate it but the process can take a couple
>>> weekends.
>> Check if it's fixed in 1.2.x, I may have simply forgotten to sync 1.2 with
>> 1.3.
>>
> Thank you, I'll check.
> 

you have forgotten nothing. Basically I still can't compile it. May be it's my
local problem.

--
 Serge Leschinsky

Re: [Devil-Linux-discuss] Trying to build 1.3.4 with very little enabled.

[Serge L. <fi...@in...>]

Hi,

Jan Hugo Prins wrote:

> I have found the cause of this error.
> The PIE compile option breaks syslinux. Found this somewhere on a 
> mailinglist.
> Disabling this options and it builds again.
Probably I do something wrong but neither "gcc -nopie -fno-stack-protector" nor
"gcc -D_FORTIFY_SOURCE=0" allows me to build it. Hm... :-\


> 
> Running into an other problem though.
> Have a iso build now with VMWare drivers included but when I boot it in 
> VMWare I get the message that it can't find it's own CDRom.
> Somewhere in 2.6.20 or 2.6.21 the kernel developers ditched the old IDE 
> drivers and all disks are now /dev/sdXX. Could this be the reason that 
> the scripts fail to find the CDRom?
I use VMWare. It's ok. But the lastes busybox update requires a  small config
modification. Please sync and rebuild iso.

--
 Serge

Re: [Devil-Linux-discuss] Trying to build 1.3.4 with very little enabled.

[Serge L. <fi...@in...>]

Heiko Zuerker wrote:

>> I've just updated the source and got the same error as you. Sorry for my
>> misunderstanding. I suggest to use syslinux 3.36 as a temporary
>> workaround. I'm going to investigate it but the process can take a couple
>> weekends.
> 
> Check if it's fixed in 1.2.x, I may have simply forgotten to sync 1.2 with
> 1.3.
> 
Thank you, I'll check.

-- 
Serge

Re: [Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Serge L. <fi...@in...>]

Hi,

Jan Hugo Prins wrote:
> Hi,
> 
> I'm currently trying to get Devil-Linux 1.3.4 working, and though my 
> build finishes I run into troubles with the linuxrd scripts.
> I have unpacked the initrd.gz file and added some checks to the linurc 
> script that is included to see what modules are loaded and what devices 
> are available just before it tries open the CDRom and load the config files.
 Fixed. You have to rebuild busybox with new config file ( please sync again  or
just add mdev applet to busybox).

--
 Serge

[Devil-Linux-discuss] Version 1.3.4 with kernel 2.6.21

[Jan H. P. <jh...@jh...>]

Hi,

I'm currently trying to get Devil-Linux 1.3.4 working, and though my 
build finishes I run into troubles with the linuxrd scripts.
I have unpacked the initrd.gz file and added some checks to the linurc 
script that is included to see what modules are loaded and what devices 
are available just before it tries open the CDRom and load the config files.
What I see there is that there are no modules loaded, which could be 
because there hasn't been a modprobe at that moment. But there are also 
only 2 devices available, naimly the console and the null device.
I have tried to add the ata modules that you probebly need to the 
initrd.gz and load them by altering the probe_all_scsi_modules script 
(changing .o to .ko and removing the block behind drivers so it finds 
all the drivers that are located beneith 
/lib/modules/2.6.21-2/kernel/drivers) but this did not result in any 
more devices or loaded modules.

Searching goes on.

Jan Hugo Prins

Re: [Devil-Linux-discuss] Trying to build 1.3.4 with very little enabled.

[Jan H. P. <jh...@jh...>]

Serge Leschinsky wrote:
> Hi,
>
> I've just updated the source and got the same error as you. Sorry for my
> misunderstanding. I suggest to use syslinux 3.36 as a temporary workaround. I'm
> going to investigate it but the process can take a couple weekends.
>
> PS. I'll send madadm's fix today... and probably several other fixes.
>
> --
>  Serge
>
>   
I have found the cause of this error.
The PIE compile option breaks syslinux. Found this somewhere on a 
mailinglist.
Disabling this options and it builds again.

Running into an other problem though.
Have a iso build now with VMWare drivers included but when I boot it in 
VMWare I get the message that it can't find it's own CDRom.
Somewhere in 2.6.20 or 2.6.21 the kernel developers ditched the old IDE 
drivers and all disks are now /dev/sdXX. Could this be the reason that 
the scripts fail to find the CDRom?

Jan Hugo

Re: [Devil-Linux-discuss] Trying to build 1.3.4 with very little enabled.

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

On Thu, July 5, 2007 01:01, Serge Leschinsky wrote:
> Hi,
>
>
> I've just updated the source and got the same error as you. Sorry for my
> misunderstanding. I suggest to use syslinux 3.36 as a temporary
> workaround. I'm going to investigate it but the process can take a couple
> weekends.

Check if it's fixed in 1.2.x, I may have simply forgotten to sync 1.2 with
1.3.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] Apache pam

[<fe...@fr...>]

Here is the link for the pam module : http://pam.sourceforge.net/mod_auth=
_pam/


But since our primary goal is to authenticate user with radius, maybe it
is better to add the radius module: 

http://www.freeradius.org/mod_auth_radius/ 

Regards. 

>> Is it possible to add pam for apache?

>Do you have any links with some more infos on this?
>Then it's easier for us (once somebody got time) to add it.

>Heiko Zuerker

Nouveau: le premier abonnement ADSL sans taxe mensuelle!
Changez d=E8s =E0 pr=E9sent pour sunrise ADSL free.
http://www.sunrise.ch/fr/privatkunden/iminternetsurfen/adsl/adsl_abosundp=
reise/adsl_gelegenheitssurfer/adsl_free.htm

Re: [Devil-Linux-discuss] Trying to build 1.3.4 with very little enabled.

[Serge L. <fi...@in...>]

Hi,

I've just updated the source and got the same error as you. Sorry for my
misunderstanding. I suggest to use syslinux 3.36 as a temporary workaround. I'm
going to investigate it but the process can take a couple weekends.

PS. I'll send madadm's fix today... and probably several other fixes.

--
 Serge

Jan Hugo Prins wrote:

> I created a config and started building, hoping that it would end in a 
> usable iso image. But the build fails somewhere when it tries to build 
> SysLinux. This simply does not compile properly. The compile of syslinux 
> ends with the following error:
omething.
> 
> Could anyone help me out?

Re: [Devil-Linux-discuss] Q: IDE Flash Boot?

[Szabo E. <sz...@on...>]

oh hi

> > I guess I just need to block packets I don't specify for fowarding?
> Is
> > 32 MB RAM adequate for this?
>=20
> I would guess yes, but I can't promise it.
> It's quite a while ago since I tested DL with anything less then 64MB.
DL boxes with 32 megs of ram work like a charm for us, terminating openvpn =
tunnels too :)

             total       used       free     shared    buffers    cached
Mem:         28084      23780       4304          0       4484     11584
-/+ buffers/cache:       7712      20372
Swap:            0          0          0


--=20
=FCdv=F6zlettel,

 Szab=F3 Endre
rendszergazda

Mezogazdas=E1gi Szakigazgat=E1si Hivatal K=F6zpont (MGSZHK)
N=F6v=E9ny-, Talaj- =E9s Agr=E1rk=F6rnyezet-v=E9delmi Igazgat=F3s=E1g (NTAI=
)
(kor=E1bban: N=F6v=E9ny- =E9s Talajv=E9delmi K=F6zponti Szolg=E1lat)
Sz=E1m=EDt=E1stechnikai Oszt=E1ly
1118 Budapest, Buda=F6rsi =FAt 141-145
E-mail: Sza...@nt...
Telefon: (1) 309-1000 x1205
Telefon: (1) 309-1062
Mobil: (20) 439-2781
Fax: (1) 246-2942

Re: [Devil-Linux-discuss] Apache pam

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

On Fri, June 29, 2007 03:22, fe...@fr... wrote:
> Hello,
>
>
> Is it possible to add pam for apache?
>

Do you have any links with some more infos on this?
Then it's easier for us (once somebody got time) to add it.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] Problems trying to boot on /dev/md0

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

On Mon, July 2, 2007 17:16, ee...@fr... wrote:
> ee...@fr... a écrit :
>> Hi all,
>>
>>
> Hi,
>
>
>> I've got a hard-time trying to boot on a raid1 device /dev/md0 composed
>>  of /dev/hda1 and /dev/hdc1
>>
>> I used install-on-usb with /dev/ide/host0/bus0/target0/lun0/disc for
>> the disk and /dev/md/0 as the boot partition but I have several problems
>> :
>>
>>
>> * grub installed but try to boot on hd(0,-1) instead of hd(0,0) or
>> hd(1,0) * my md0 device seems in bad state when i send cat /proc/mdstat
>> :
>>
>>
>> md0 : inactive ide/host0/bus1/target0/lun0/part1[1] 0 blocks
>>
>
> Figured out why reading the script ...
> Not really to take raid devices into account ...
>
>
>> * It seems /dev/hda1 get inaccessible as it is listed in mount list as
>> mounted on /shm/var/adm/boot/ but is not in reality!
>>
>
> after studing linuxrc and mount_cdrom, I see why, while Iwas booting from
> an embedded CF card, the system swap to bootcd.iso which is on first
> partition of first ide disc ... but the fact ls -als /shm/var/adm/boot/
> gives empty directory listing seems a bug from elwhere! trying to re-build
> the full system with i586/i586 arch (was c3_2/i686) strangly glibc 2.3
> refuses to compile when it's about timezones ??? trying to install a fresh
> new lfssystem ...
>
>> It is completly impossible to mount it anywhere ...
>>
>>
> as the whole system is mounted from the iso on this media ...
>
>> I guessed there's a problem with the init script as bootcd.iso is on it
>>  ...
>> and it looks like the init script doesn't release it.
>>
>> I can't access it even to fix the grub config file.
>>
>>
>> Guess DL doesn't support booting on raid devices :(
>>
>>
> the more I see boot scripts, the more I'm convinced; can anyone confirme
> where/why this support has been left aside ?
>
>> but i think grub can handle booting on raid devices for a long time,
>> what's up?
>>
> Any hints to try to improve this ?

You'll have to modify the boot system quite a bit to get that working.
So far we're only supporting use of raid devices, once the system booted.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] Problems trying to boot on /dev/md0

[<ee...@fr...>]

ee...@fr... a écrit :
> Hi all,
> 
Hi,

> I've got a hard-time trying to boot on a raid1 device /dev/md0 composed
> of /dev/hda1 and /dev/hdc1
> 
> I used install-on-usb with /dev/ide/host0/bus0/target0/lun0/disc for the
> disk and /dev/md/0 as the boot partition but I have several problems :
> 
> * grub installed but try to boot on hd(0,-1) instead of hd(0,0) or hd(1,0)
> * my md0 device seems in bad state when i send cat /proc/mdstat :
> 
> md0 : inactive ide/host0/bus1/target0/lun0/part1[1]
>           0 blocks
> 

Figured out why reading the script ...
Not really to take raid devices into account ...

> * It seems /dev/hda1 get inaccessible as it is listed in mount list as
> mounted on /shm/var/adm/boot/ but is not in reality!
> 

after studing linuxrc and mount_cdrom, I see why, while Iwas booting
from an embedded CF card, the system swap to bootcd.iso which is on
first partition of first ide disc ... but the fact ls -als
/shm/var/adm/boot/ gives empty directory listing seems a bug from
elwhere! trying to re-build the full system with i586/i586 arch (was
c3_2/i686)
strangly glibc 2.3 refuses to compile when it's about timezones ???
trying to install a fresh new lfssystem ...

> It is completly impossible to mount it anywhere ...
> 
as the whole system is mounted from the iso on this media ...

> I guessed there's a problem with the init script as bootcd.iso is on it 
> ...
> and it looks like the init script doesn't release it.
> 
> I can't access it even to fix the grub config file.
> 
> Guess DL doesn't support booting on raid devices :(
> 
the more I see boot scripts, the more I'm convinced; can anyone confirme
 where/why this support has been left aside ?

> but i think grub can handle booting on raid devices for a long time,
> what's up?
> 
Any hints to try to improve this ?

> Regards,
> 
> MaNU
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>