You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(59) |
Sep
(57) |
Oct
(5) |
Nov
(45) |
Dec
(21) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(13) |
Feb
(22) |
Mar
(14) |
Apr
(7) |
May
(33) |
Jun
(57) |
Jul
(25) |
Aug
(40) |
Sep
(53) |
Oct
(58) |
Nov
(75) |
Dec
(22) |
2003 |
Jan
(101) |
Feb
(101) |
Mar
(103) |
Apr
(125) |
May
(85) |
Jun
(57) |
Jul
(62) |
Aug
(42) |
Sep
(76) |
Oct
(214) |
Nov
(290) |
Dec
(274) |
2004 |
Jan
(187) |
Feb
(172) |
Mar
(313) |
Apr
(209) |
May
(169) |
Jun
(147) |
Jul
(118) |
Aug
(193) |
Sep
(227) |
Oct
(125) |
Nov
(246) |
Dec
(191) |
2005 |
Jan
(244) |
Feb
(175) |
Mar
(165) |
Apr
(130) |
May
(217) |
Jun
(122) |
Jul
(188) |
Aug
(235) |
Sep
(165) |
Oct
(133) |
Nov
(209) |
Dec
(88) |
2006 |
Jan
(66) |
Feb
(89) |
Mar
(108) |
Apr
(91) |
May
(29) |
Jun
(45) |
Jul
(64) |
Aug
(42) |
Sep
(44) |
Oct
(81) |
Nov
(64) |
Dec
(9) |
2007 |
Jan
(24) |
Feb
(122) |
Mar
(55) |
Apr
(50) |
May
(84) |
Jun
(13) |
Jul
(80) |
Aug
(70) |
Sep
(78) |
Oct
(45) |
Nov
(56) |
Dec
(42) |
2008 |
Jan
(65) |
Feb
(3) |
Mar
(51) |
Apr
(151) |
May
(54) |
Jun
(72) |
Jul
(73) |
Aug
(47) |
Sep
(55) |
Oct
(123) |
Nov
(16) |
Dec
(4) |
2009 |
Jan
(23) |
Feb
(39) |
Mar
(27) |
Apr
(36) |
May
(35) |
Jun
(51) |
Jul
(11) |
Aug
(14) |
Sep
(40) |
Oct
(67) |
Nov
(38) |
Dec
(13) |
2010 |
Jan
(15) |
Feb
(35) |
Mar
(40) |
Apr
(11) |
May
(26) |
Jun
(10) |
Jul
(5) |
Aug
(50) |
Sep
(86) |
Oct
(67) |
Nov
(36) |
Dec
(11) |
2011 |
Jan
(50) |
Feb
(6) |
Mar
(13) |
Apr
(13) |
May
(29) |
Jun
(27) |
Jul
(26) |
Aug
(27) |
Sep
(21) |
Oct
(7) |
Nov
(27) |
Dec
(4) |
2012 |
Jan
(11) |
Feb
(20) |
Mar
(48) |
Apr
(18) |
May
(8) |
Jun
(19) |
Jul
|
Aug
(15) |
Sep
(3) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
2013 |
Jan
(13) |
Feb
(7) |
Mar
(4) |
Apr
(25) |
May
(2) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(5) |
Dec
(10) |
2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(20) |
May
(5) |
Jun
|
Jul
(2) |
Aug
|
Sep
(8) |
Oct
(21) |
Nov
(4) |
Dec
(7) |
2015 |
Jan
(10) |
Feb
(9) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(11) |
Oct
|
Nov
(17) |
Dec
(32) |
2016 |
Jan
(10) |
Feb
(15) |
Mar
(4) |
Apr
(7) |
May
(10) |
Jun
(11) |
Jul
(15) |
Aug
(26) |
Sep
(13) |
Oct
(10) |
Nov
(16) |
Dec
(6) |
2017 |
Jan
(9) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(6) |
Nov
(8) |
Dec
|
2018 |
Jan
(12) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Erik C. <eri...@ki...> - 2002-05-22 17:49:30
|
How about the oposite problem: One LAN and two WAN Ports... What I really want is the ability to connect two LAN's across the internet using multiple ISP's for redundancy. Something similar to the following: <=><CableProvider><=> [PrivateLanA]<=>[RouterA] [RouterB]<=>[PrivateLanB] <=><ADSLProvider><=> Assuming Devil-Linux boxes as the routers how would/could you handle the routing? (Load balancing isn't my primary concern. I'm more interested in redundancy and uptime - but I'm sure others would be interested in the increased bandwidth possibilities) The next logical step is multihomed VPN's Any thoughts? E _________________________________ Erik Christensen > Date: Sat, 18 May 2002 13:44:41 -0700 (MST) > Subject: Re: [Devil-Linux-discuss] multiple NIC's for LAN? > From: "Sancho2k Lists" <li...@sa...> > To: <jan...@us...> > Cc: <dev...@li...> > Reply-To: li...@sa... > > > Jan Suhr said: > > Hello! > > I would like to use two networkcards to connect two LAN's. A third > > networkcard connect them to the internet with ADSL. Is this > > possible with Devil Linux? > very much so. In /etc/sysconfig/nics/ you can define multiple eth* > cards. Load the proper module for them, and you're in business. > In /etc/sysconfig/config you can put your default route out to the > internet. Other local routes are created automatically from the NIC > configurations. Addtitional routes (not locally connected) can be put > into the firewall script in /etc > > > > > Thank you very much for your help, Jan > > > > > > > > |
From: Sancho2k L. <li...@sa...> - 2002-05-18 19:52:02
|
Jan Suhr said: > Hello! > I would like to use two networkcards to connect two LAN's. A third > networkcard connect them to the internet with ADSL. Is this > possible with Devil Linux? very much so. In /etc/sysconfig/nics/ you can define multiple eth* cards. Load the proper module for them, and you're in business. In /etc/sysconfig/config you can put your default route out to the internet. Other local routes are created automatically from the NIC configurations. Addtitional routes (not locally connected) can be put into the firewall script in /etc > > Thank you very much for your help, Jan > > > > > _______________________________________________________________ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss -- Darren Spruell www.sancho2k.net |
From: Jan S. <jan...@us...> - 2002-05-18 19:45:26
|
Hello! I would like to use two networkcards to connect two LAN's. A third networ= kcard connect them to the internet with ADSL. Is this possible with Devil Linux= ? Thank you very much for your help, Jan |
From: Walter H. <wal...@gm...> - 2002-05-15 14:11:22
|
Hi! Unfortunately a small typo slipped through (bad cut & paste...) ! Line 42 of linuxrc /sbin/mke2fs -q $DATA_PART print_status success || print_status is missing a '&&' and should read: /sbin/mke2fs -q $DATA_PART && print_status success || print_status Sorry for the inconvenience! Walter PS: Another hint: Make sure linuxrc is executable! -- Walter Haidinger <wal...@gm...> For contact information or PGP/GPG public key please refer to http://haidinger.webhop.org/contact.html |
From: Heiko Z. <hz...@pr...> - 2002-05-15 14:01:11
|
Hey, thanks for the howto. cu Heiko On 05/15/2002 06:24:49 AM "Walter Haidinger" wrote: >Hi! > >I've successfully installed Devil-Linux this weekend on an old machine= >(486/66) with just 24 MB of RAM. I think that even 16 MB would be >sufficient. >However, in order to do that I had to make Devil-Linux boot onto a >harddisk partition instead of a ramdisk. I was forced to do this >because _both_ of my 32MB SIMMs turned out to be defective... :-( >Well, here's what I did. Perhaps it helps somebody who has a similar >problem. How about adding a docs section like "installing Devil-Linux >on machines with less than 64 MB RAM" ? >This may have been done already but I didn't search the mailing-list >archives when I did it because I had no internet access at that time. > >Anyways, here goes: > >With my setup, I used three partitions (on an old 200+ MB IDE drive): >* /dev/hda1 - DOS (C:), about 50 MB > Required because that old machine could not boot from CD-Rom and if > I have to use a harddisk anyways we can as well use it for booting >too. > Please note that the floppy containing the config is still required > any may have to configure the BIOS to boot from HD first. >* /dev/hda2 - Linux SWAP, 64 MB > I have free disk space so why not extend the already limited physica= l > memory and set up a swap partition? >* /dev/hda3 - Linux ext2, about 100 MB > Used as subsitute for the ramdisk. I've hacked the initrd to use > this partition instead of /dev/shm (see below). > >After setting up a DOS partition to boot from (C:), I copied the >boot directory from the CD (to C:\boot). Next, I had to modify to >linuxrc script of initrd.gz. >To do this, follow these steps (under Linux): >1. Copy the initrd.gz from the CD-Rom somewhere, e.g. > > cp /cdrom/boot/initrd.gz /tmp >2. Unpack it > > gunzip /tmp/initrd.gz >3. Mount the file using the loopback-device: > > mount /tmp/initrd -o rw,loop=3D/dev/loop0 /mnt >4. Modify /mnt/linuxrc with your favourite editor according to the > next section below. > > your-editor /mnt/linuxrc >5. Copy your /sbin/swapon and /sbin/mkswap files to /mnt/sbin > Make sure that the binaries run on your Devil-Linux Version. > For me, binaries from SuSE-Linux 7.3 run on Devil-Linux 0.5. >6. Unmount again > > umount /mnt >7. Pack the modified image > > gzip initrd >8. Copy the new initrd.gz to the boot directory of the DOS partition > (C:\boot) > >Now for the fun part: Howto modify linuxrc >(I've modifed linuxrc v1.7 from the 0.5rc1 distribution) > >Here are the diffs in detail: > >28a29,32 >> SWAP_PART=3D/dev/hda2 >> echo "Adding swapspace on $SWAP_PART" >> /sbin/swapon $SWAP_PART && print_status success || print_status >failure >> > >Add the swap partition. You might add a /sbin/mkswap $SWAP_PART right >before swapon but I doubt that this is necessary. Well, of course you >need to create the swap-space _once_ ! >31a36,43 >> DATA_PART=3D/dev/hda3 >> echo "Using $DATA_PART as ramdisk substitute:" >> test -d /hd || mkdir /hd >> echo -n "Creating ext2 filesystem on $DATA_PART" >> /sbin/mke2fs -q $DATA_PART print_status success || print_status >failure >> echo -n "Mounting $DATA_PART" >> mount -t ext2 -o rw $DATA_PART /hd && print_status success || >> print_status failure> > >Use partition set by DATA_PART as the ramdisk substitute. >First create a mountpoint, then create the filesystem and mount it. >*** WARNING: >The partition is created _without_ question! Any previously stored >data is lost! Actually, that is a good thing as it really simulates >ramdisk behaviour and is therefore a security benefit. >Also, you can simply turn off the machine without shutting down which >is good if you have users power on/off the router without further >knowledge.However, it can be *very* disastrous if you edit your >partition table >and forget to assign the correct partition in DATA_PART. >33,35c45,49 >< test -d /dev/shm || mkdir /dev/shm >< echo -n "Mounting SHM FS on /dev/shm" >< mount -t shm -o size=3D40g shmfs /dev/shm && print_status success ||= >print_status failure--- >> #test -d /dev/shm || mkdir /dev/shm >> #echo -n "Mounting SHM FS on /dev/shm" >> #mount -t shm -o size=3D40g shmfs /dev/shm && print_status success |= | >> print_status failure> rm -rf /dev/shm > /dev/null 2>&1 >> ln -s /hd /dev/shm >39c53,54 >< ln -s /dev/shm /ram >--- >> #ln -s /dev/shm /ram >> ln -s /hd /ram > >Remove (comment) the shared memory stuff and replace it by symlinks. >This allows transparent usage of the partition instead of /dev/shm, >i.e. not subsequent scripts need to be modified. > >That are all changes made to linuxrc. >I've attached a context diff with the changes. >To apply it, run (replacing step 4 above) in /mnt after saving the >attachment (to, say, /tmp): > patch < ../tmp/linuxrc.diff > >*** Security warning: >If you store the boot files (kernel, initrd, ...) on the harddisk >(i.e. if you do _not_ create a CD containing the new initrd.gz), that >files _can_ be modified.Therefore, the integrity of the boot files >_have_ to be verified! >e.g.: Use MD5 hashes! > >1. Get md5sum.exe for DOS from http://etree.org/md5com.html > and put it on your config floppy. >2. Create md5 checksums for all files that are on the harddisk, > e.g. (write on one line): > md5sum.exe C:\boot\initrd.gz C:\boot\loadlin.exe > C:\boot\vmlinuz > A:\boot.md5 >3. In autoexec.bat of your boot floppy, add the following 2 lines: > md5sum -vc boot.md5 > if errorlevel 1 exit >4. Don't forget to write-protect your floppy again! > >Now, if anyone modifies the files on the harddisk, md5sum fails the >check and the autoexec.bat is aborted. >That's finally it! I just hope that I forgot nothing as I wrote this >mostly from memory... > >Anyways, comments *are* welcome! > >Regards, Walter > >PS: Yes, I know this is a (bad) hack and there are better ways > (that is, more configurable) to do this. > However, I had to get the system up and that is what did it. > You're free to do it any other way you desire! ;-) = |
From: Walter H. <wal...@gm...> - 2002-05-15 10:26:19
|
Hi! I've successfully installed Devil-Linux this weekend on an old machine (486/66) with just 24 MB of RAM. I think that even 16 MB would be sufficient. However, in order to do that I had to make Devil-Linux boot onto a harddisk partition instead of a ramdisk. I was forced to do this because _both_ of my 32MB SIMMs turned out to be defective... :-( Well, here's what I did. Perhaps it helps somebody who has a similar problem. How about adding a docs section like "installing Devil-Linux on machines with less than 64 MB RAM" ? This may have been done already but I didn't search the mailing-list archives when I did it because I had no internet access at that time. Anyways, here goes: With my setup, I used three partitions (on an old 200+ MB IDE drive): * /dev/hda1 - DOS (C:), about 50 MB Required because that old machine could not boot from CD-Rom and if I have to use a harddisk anyways we can as well use it for booting too. Please note that the floppy containing the config is still required any may have to configure the BIOS to boot from HD first. * /dev/hda2 - Linux SWAP, 64 MB I have free disk space so why not extend the already limited physical memory and set up a swap partition? * /dev/hda3 - Linux ext2, about 100 MB Used as subsitute for the ramdisk. I've hacked the initrd to use this partition instead of /dev/shm (see below). After setting up a DOS partition to boot from (C:), I copied the boot directory from the CD (to C:\boot). Next, I had to modify to linuxrc script of initrd.gz. To do this, follow these steps (under Linux): 1. Copy the initrd.gz from the CD-Rom somewhere, e.g. > cp /cdrom/boot/initrd.gz /tmp 2. Unpack it > gunzip /tmp/initrd.gz 3. Mount the file using the loopback-device: > mount /tmp/initrd -o rw,loop=/dev/loop0 /mnt 4. Modify /mnt/linuxrc with your favourite editor according to the next section below. > your-editor /mnt/linuxrc 5. Copy your /sbin/swapon and /sbin/mkswap files to /mnt/sbin Make sure that the binaries run on your Devil-Linux Version. For me, binaries from SuSE-Linux 7.3 run on Devil-Linux 0.5. 6. Unmount again > umount /mnt 7. Pack the modified image > gzip initrd 8. Copy the new initrd.gz to the boot directory of the DOS partition (C:\boot) Now for the fun part: Howto modify linuxrc (I've modifed linuxrc v1.7 from the 0.5rc1 distribution) Here are the diffs in detail: 28a29,32 > SWAP_PART=/dev/hda2 > echo "Adding swapspace on $SWAP_PART" > /sbin/swapon $SWAP_PART && print_status success || print_status failure > Add the swap partition. You might add a /sbin/mkswap $SWAP_PART right before swapon but I doubt that this is necessary. Well, of course you need to create the swap-space _once_ ! 31a36,43 > DATA_PART=/dev/hda3 > echo "Using $DATA_PART as ramdisk substitute:" > test -d /hd || mkdir /hd > echo -n "Creating ext2 filesystem on $DATA_PART" > /sbin/mke2fs -q $DATA_PART print_status success || print_status failure > echo -n "Mounting $DATA_PART" > mount -t ext2 -o rw $DATA_PART /hd && print_status success || > print_status failure> Use partition set by DATA_PART as the ramdisk substitute. First create a mountpoint, then create the filesystem and mount it. *** WARNING: The partition is created _without_ question! Any previously stored data is lost! Actually, that is a good thing as it really simulates ramdisk behaviour and is therefore a security benefit. Also, you can simply turn off the machine without shutting down which is good if you have users power on/off the router without further knowledge.However, it can be *very* disastrous if you edit your partition table and forget to assign the correct partition in DATA_PART. 33,35c45,49 < test -d /dev/shm || mkdir /dev/shm < echo -n "Mounting SHM FS on /dev/shm" < mount -t shm -o size=40g shmfs /dev/shm && print_status success || print_status failure--- > #test -d /dev/shm || mkdir /dev/shm > #echo -n "Mounting SHM FS on /dev/shm" > #mount -t shm -o size=40g shmfs /dev/shm && print_status success || > print_status failure> rm -rf /dev/shm > /dev/null 2>&1 > ln -s /hd /dev/shm 39c53,54 < ln -s /dev/shm /ram --- > #ln -s /dev/shm /ram > ln -s /hd /ram Remove (comment) the shared memory stuff and replace it by symlinks. This allows transparent usage of the partition instead of /dev/shm, i.e. not subsequent scripts need to be modified. That are all changes made to linuxrc. I've attached a context diff with the changes. To apply it, run (replacing step 4 above) in /mnt after saving the attachment (to, say, /tmp): patch < ../tmp/linuxrc.diff *** Security warning: If you store the boot files (kernel, initrd, ...) on the harddisk (i.e. if you do _not_ create a CD containing the new initrd.gz), that files _can_ be modified.Therefore, the integrity of the boot files _have_ to be verified! e.g.: Use MD5 hashes! 1. Get md5sum.exe for DOS from http://etree.org/md5com.html and put it on your config floppy. 2. Create md5 checksums for all files that are on the harddisk, e.g. (write on one line): md5sum.exe C:\boot\initrd.gz C:\boot\loadlin.exe C:\boot\vmlinuz > A:\boot.md5 3. In autoexec.bat of your boot floppy, add the following 2 lines: md5sum -vc boot.md5 if errorlevel 1 exit 4. Don't forget to write-protect your floppy again! Now, if anyone modifies the files on the harddisk, md5sum fails the check and the autoexec.bat is aborted. That's finally it! I just hope that I forgot nothing as I wrote this mostly from memory... Anyways, comments *are* welcome! Regards, Walter PS: Yes, I know this is a (bad) hack and there are better ways (that is, more configurable) to do this. However, I had to get the system up and that is what did it. You're free to do it any other way you desire! ;-) -- Walter Haidinger <wal...@gm...> For contact information or PGP/GPG public key please refer to http://haidinger.webhop.org/contact.html |
From: Walter H. <wal...@gm...> - 2002-05-10 09:57:32
|
On Thu, 9 May 2002, Friedrich Lobenstock wrote: > hz...@pr... wrote: > > > > the problem is the file "linux.bat" on the CD. > > This is already fixed in the CVS tree, Friedl can you send him the actual > > version? > > Hello Walter! > > Please download a new linux.bat at: > ftp://ftp.devil-linux.org/pub/releases/add-0.5b6/ > or > ftp://ftp.fl.priv.at/pub/devil-linux/0.5b6/ > Linux.bat contains: loadlin \boot\vmlinuz initrd=\boot\initrd.gz root=/dev/ram0 init=/linuxrc rw This is odd! I thought that I've already tried to use /dev/ram0 as the root fs. Anyways, it works now. Thanks! Regards, Walter |
From: Friedrich L. <fl...@fl...> - 2002-05-09 12:40:10
|
hz...@pr... wrote: > > the problem is the file "linux.bat" on the CD. > This is already fixed in the CVS tree, Friedl can you send him the actual > version? Hello Walter! Please download a new linux.bat at: ftp://ftp.devil-linux.org/pub/releases/add-0.5b6/ or ftp://ftp.fl.priv.at/pub/devil-linux/0.5b6/ -- MfG / Regards Friedrich Lobenstock |
From: <hz...@pr...> - 2002-05-09 05:27:05
|
Hey folks, I decided to extend my vacation until Sunday, so I won't be able to do = any work/support with DL before Monday. BTW: Puerto Rico is really a nice place for a vacation. ;-) cu Heiko= |
From: <hz...@pr...> - 2002-05-09 05:27:05
|
Hi, the problem is the file "linux.bat" on the CD. This is already fixed in the CVS tree, Friedl can you send him the actu= al version? Thanks Heiko = |
From: Michael W. <mi...@pr...> - 2002-05-08 17:06:37
|
Hi Mr./Mrs. Sancho2k ;-) On 08.05.2002 17:16:20 "Sancho2k Lists" wrote: >Greetz all, > >[Cross-posted to forums as well - sorry] > >When we put new routes into our devil linux boxes, Is there a way to >save this out to the etc.tar.gz on floppy so as to have the routes sta= y >after a reboot? I'm curious whether the save-config script will handl= e >that, or is this something that needs to be put into a network script >(such as init.d/network)? > >TIA I normally put the routes in the firewall.rules script ;-) until we hav= e a working routing boot-script......... HTH micha = |
From: Sancho2k L. <li...@sa...> - 2002-05-08 15:05:20
|
Greetz all, [Cross-posted to forums as well - sorry] When we put new routes into our devil linux boxes, Is there a way to save this out to the etc.tar.gz on floppy so as to have the routes stay after a reboot? I'm curious whether the save-config script will handle that, or is this something that needs to be put into a network script (such as init.d/network)? TIA -- Darren Spruell www.sancho2k.net |
From: Friedrich L. <fl...@fl...> - 2002-05-07 23:14:04
|
Walter Haidinger wrote: > On Tue, 7 May 2002, Friedrich Lobenstock wrote: > >>Another question before we get to the real problem, how much ram have you >>got in that machine? > > 128MB. > > I'm experiencing the problem on my test machine (K6-2/400, 128MB, could > boot from CD-Rom). The actual target machine (still lying around in > parts, though...) will feature an 486/100 with 64MB which should be > sufficent as I'm using just few packages. Ok I see. Then mail me (in a private mail) an image of your boot floppy and I'll try to reproduce this with vmware to see where's the problem. But as I'll be travelling from Graz to Innsbruck tomorrow wednesday, I can not promise to test it before saturday. You know long weekend stuff ;-) -- MfG / Regards Friedrich Lobenstock |
From: Walter H. <wal...@gm...> - 2002-05-07 22:22:39
|
On Tue, 7 May 2002, Friedrich Lobenstock wrote: > Another question before we get to the real problem, how much ram have you > got in that machine? 128MB. I'm experiencing the problem on my test machine (K6-2/400, 128MB, could boot from CD-Rom). The actual target machine (still lying around in parts, though...) will feature an 486/100 with 64MB which should be sufficent as I'm using just few packages. Walter |
From: Friedrich L. <fl...@fl...> - 2002-05-07 12:18:29
|
Walter Haidinger wrote: > Hi! > > I'd like to run devel-linux-0.5b6 on an old machine (486/100) which cannot > boot from cdrom. Another question before we get to the real problem, how much ram have you got in that machine? -- MfG / Regards Friedrich Lobenstock |
From: Walter H. <wal...@gm...> - 2002-05-07 07:07:31
|
Hi! I'd like to run devel-linux-0.5b6 on an old machine (486/100) which cannot boot from cdrom. Therefore, I followed the footnote in the documentation and I'm booting from a Floppy using Loadlin. However, the kernel panics after installing the packages because it cannot mount its root fs: [--everything upto here is ok--] Starting up final system... Usage: init 0123456Ss... FAT: bogus logical sector size 0 FAT: bogus logical sector size 0 read_super_block: can't find a reiserfs filesystem on (dev 01:01, block 64, size 1024) read_super_block: can't find a reiserfs filesystem on (dev 01:01, block 8, size 1024) Kernel panic: VFS: Unable to mount root fs 01:01 If I boot directly from the very same CD for testing (on a more modern system which can boot from cdrom), everything is fine, i.e. I'm able to login. I think there is some trouble because /dev/ram1 (which is device 01:01) is already used for booting with initrd. So mounting root on the very same device fails. However, this is just an assumption as I haven't had time to dig into the boot process of devel-linux... Any hints are appreciated! Regards, Walter |
From: Heiko Z. <he...@zu...> - 2002-05-04 02:30:08
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey guys, I will be on vacation the next couple of days and won't have access to the internet. I'll be back on Thursday 05/09/02. Please watch the forum on the website and help the newbies. - -- cu ~ Heiko We are Penguin, Resistance is futile! http://www.devil-linux.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6-2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAjzTRr0ACgkQzRJAyNsjWPmimQCfVjoWZboDdlmPAznSZGgJkfml c6sAn0xHa60n1t9P4HWfXXjnwkxNKcws =bpOe -----END PGP SIGNATURE----- |
From: Heiko Z. <he...@zu...> - 2002-04-23 02:49:58
|
Hey, I created a new poll on the website to see how many DL installations our users have running. Would be nice if you vote, too. -- cu Heiko We are Penguin, Resistance is futile! http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2002-04-22 14:10:04
|
English: http://www.portazero.info/modules.php?name=Sections&sop=viewarticle&artid=25 Italian: http://www.portazero.info/modules.php?name=Sections&sop=viewarticle&artid=24 -- cu Heiko We are Penguin, Resistance is futile! http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2002-04-11 23:00:06
|
Hey folks, I'm out of town until end of next week. It's not sure that I'll have Internet access, so I would appreciate it, when you could watch the forum on the website and answer emails to the mailinglist. Thanks -- cu Heiko We are Penguin, Resistance is futile! http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2002-04-11 00:00:11
|
no...@so... wrote: > Initial Comment: > I can't access some webpages, e.g.: > http://www.compaq.com > http://www.pharmacongress.net > > Somebody else uses Squid with DL? > > Made package with old Squid v2.4stable6, but it's the > same. This is really a big problem for me right now, is somebody else using Squid with DL ? -- cu Heiko We are Penguin, Resistance is futile! http://www.devil-linux.org |
From: Heiko Z. <hz...@pr...> - 2002-04-01 19:36:03
|
Hi, I recognized this problem, too. Squid is not exiting immediately, when he gets the TERM signal. Workaround: edit /etc/init.d/squid, so the "stop" part looks like this: stop) echo -n "Shutting down $NAME: " killproc $DAEMON sleep 60 ;; cu Heiko= |
From: Marco S. <mar...@cl...> - 2002-04-01 17:03:57
|
Hi, I use two machines with Devil-Linux 0.5Beta6. Both machines are running squid. I use the LVM-support. /var/data/squid is for caching and /var/squid is for logging. One machine is running squid as transparent proxy and one not (I have to enable the proxy in the browser there). When installing the LVM I used Friedrich Lobenstocks Howto. When shutting down, I get the message on both machines, that /var/squid could not be umounted, because the device is busy. When stopping squid minutes before shutting down the machine, the error still occurs. So reiserfs checks on boot the system on /var/squid and is doing a rollback from the journal. Does anyone have the same problems? Greetings from sunny Bonn, Germany marco |
From: Heiko Z. <he...@zu...> - 2002-03-26 03:30:23
|
autsch.... I found it: edit the file /etc/init.d/snort and write the line with PARAMETER= like this: PARAMETER="-D -c /etc/snort/snort.conf" -- cu Heiko http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2002-03-26 02:40:31
|
On Mon, 25 Mar 2002 15:38:00 +0100 "Marco Schierle" <mar...@cl...> wrote: > I thought the same and tested if a fresh config file without changing > anything works. But I got the same message. I can reproduce this error, but couldn't find the problem yet. I keep on investigating. -- cu Heiko http://www.devil-linux.org |