From jh at tinysofa.org Tue Jan 3 02:45:36 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Sun May 4 12:26:17 2008 Subject: [tinysofa-devel] classic 2.0 update 3 test isos Message-ID: <20060103084536.GA1328@ws64.jh.dy.fi> 2.0 update 3 test isos (i586, x86_64 and source): http://minbar.tinysofa.org/~jh/classic/2.0U3/iso/ Unless problems show up these will be released as final. Changes: http://classic.tinysofa.org/documentation/index.cgi?TwoPointZeroChanges -- Jaakko From mikael at tinysofa.org Mon Jan 16 15:24:39 2006 From: mikael at tinysofa.org (Mikael Bak) Date: Sun May 4 12:26:17 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? Message-ID: <20060116222439.2146b7f7.mikael@tinysofa.org> Hi developers, I think I've found a small bug in the anaconda installer in tcs2.0. Today I installed on a Dell PowerEdge 1425. It has two gigabit ports (e1000). I chose to configure both and gave them both statical IP addresses, and chose to activate them at boot. But only one of them actually got configured (eth0). I took a look in /etc/sysconfig/network-scripts and found that there was no ifup-eth1. After manually creating it everything worked as expected. Unfortunately my knowlede on how anaconda works is still very... basic... so I didn't even try to debug it. I thought I'd mention it here, and if nobody else has time to fix it, then I take that as a challange to learn anaconda and python :-) Bye, Mikael -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.tinysofa.org/pipermail/tinysofa-devel/attachments/20060116/9357d5b8/attachment.bin From jh at tinysofa.org Tue Jan 17 00:57:05 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Sun May 4 12:26:17 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <20060116222439.2146b7f7.mikael@tinysofa.org> References: <20060116222439.2146b7f7.mikael@tinysofa.org> Message-ID: <20060117065705.GA1335@ws64.jh.dy.fi> Hi, On 2006-01-16, Mikael Bak wrote: > I chose to configure both and gave them both statical IP addresses, > and chose to activate them at boot. But only one of them actually got > configured (eth0). I took a look in /etc/sysconfig/network-scripts and > found that there was no ifup-eth1. /etc/modprobe.conf was OK after installation? Can you post /etc/modprobe.conf, lsmod and lspci output when both interfaces are up? > Unfortunately my knowlede on how anaconda works is still very... > basic... so I didn't even try to debug it. It's also possible that the bug is in kudzu. Please check if you have two network interfaces in /etc/sysconfig/hwconf. In addition you can try to run kudzu and see if it want's to remove eth1. > I thought I'd mention it here, and if nobody else has time to fix it, > then I take that as a challange to learn anaconda and python :-) I wonder if it's reproducible without multiport NIC. Currently I don't have one for testing. -- Jaakko From gda at tinysofa.org Tue Jan 17 01:58:26 2006 From: gda at tinysofa.org (Gerald Dachs) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? Message-ID: <34847.139.1.44.13.1137484706.squirrel@sohoserver.homelinux.net> >> Unfortunately my knowlede on how anaconda works is still very... basic... so I didn't even try to debug it. > > It's also possible that the bug is in kudzu. Please check if you have two network interfaces in /etc/sysconfig/hwconf. In addition you can try to run kudzu and see if it want's to remove eth1. Yes, I believe it is kudzu not anaconda, before the last update of kudzu it even has deleted ifcfg-eth0 during an upgrade, only if there were two (even different) nics in the system. Look into kudzu, not anaconda. Gerald From mikael at tinysofa.org Tue Jan 17 14:44:05 2006 From: mikael at tinysofa.org (Mikael Bak) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <20060117065705.GA1335@ws64.jh.dy.fi> References: <20060116222439.2146b7f7.mikael@tinysofa.org> <20060117065705.GA1335@ws64.jh.dy.fi> Message-ID: <200601171244.05944.mikael@tinysofa.org> On Monday 16 January 2006 22.57, Jaakko Heinonen wrote: > /etc/modprobe.conf was OK after installation? Can you post > /etc/modprobe.conf, lsmod and lspci output when both interfaces are up? > No, /etc/modprobe.conf said: # cat /etc/modprobe.conf alias eth0 e1000 alias scsi_hostadapter ata_piix alias usb-controller uhci-hcd alias usb-controller1 ehci-hcd alias eth2 e1000 After editing it and add ifcfg-eth1 it works. # lsmod Module Size Used by ipv6 263744 15 e1000 104500 0 usb_storage 70976 0 usbhid 49760 0 ehci_hcd 38792 0 uhci_hcd 35728 0 ext3 132104 2 jbd 79128 1 ext3 raid1 22784 3 ata_piix 9604 8 libata 47108 1 ata_piix sd_mod 19968 10 scsi_mod 144232 3 usb_storage,libata,sd_mod # lspci 00:00.0 Host bridge: Intel Corp. E7520 Memory Controller Hub (rev 09) 00:02.0 PCI bridge: Intel Corp. E7525/E7520/E7320 PCI Express Port A (rev 09) 00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) SATA Controller (rev 02) 01:00.0 PCI bridge: Intel Corp. 6700PXH PCI Express-to-PCI Bridge A (rev 09) 01:00.2 PCI bridge: Intel Corp. 6700PXH PCI Express-to-PCI Bridge B (rev 09) 02:04.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) 04:03.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) 04:0d.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] > It's also possible that the bug is in kudzu. Please check if you have > two network interfaces in /etc/sysconfig/hwconf. In addition you can try > to run kudzu and see if it want's to remove eth1. > Relevant part of /etc/sysconfig/hwconf: - class: NETWORK bus: PCI detached: 0 device: eth0 driver: e1000 desc: "Intel Corp.|82541GI/PI Gigabit Ethernet Controller" vendorId: 8086 deviceId: 1076 subVendorId: 1028 subDeviceId: 019a pciType: 1 pcibus: 2 pcidev: 4 pcifn: 0 - class: NETWORK bus: PCI detached: 0 device: eth2 driver: e1000 desc: "Intel Corp.|82541GI/PI Gigabit Ethernet Controller" vendorId: 8086 deviceId: 1076 subVendorId: 1028 subDeviceId: 019a pciType: 1 pcibus: 4 pcidev: 3 pcifn: 0 - I wonder why it's recognized as eth2... But after installation I did not have any /etc/sysconfig/network-scripts/ifcfg-eth2 > > I wonder if it's reproducible without multiport NIC. Currently I don't > have one for testing. I don't understand why the installation insists to make the second interface eth2. Please tell me what else you want me to test. Thanks, Mikael From jh at tinysofa.org Tue Jan 17 06:18:13 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <200601171244.05944.mikael@tinysofa.org> References: <20060116222439.2146b7f7.mikael@tinysofa.org> <20060117065705.GA1335@ws64.jh.dy.fi> <200601171244.05944.mikael@tinysofa.org> Message-ID: <20060117121813.GA1522@ws64.jh.dy.fi> Thanks for information. On 2006-01-17, Mikael Bak wrote: > Please tell me what else you want me to test. Red Hat has done some updates to kudzu NIC detection routine. Could you check if this version of kudzu makes any difference: http://jh.dy.fi/~jaakko/kudzu/ Run kudzu and watch for /etc/sysconfig/hwconf changes. Please try to run kudzu also with empty /etc/sysconfig/hwconf and /etc/modprobe.conf. Old values especially in /etc/modprobe.conf may cause it behave differently. -- Jaakko From mikael at tinysofa.org Tue Jan 17 16:47:26 2006 From: mikael at tinysofa.org (Mikael Bak) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <20060117121813.GA1522@ws64.jh.dy.fi> References: <20060116222439.2146b7f7.mikael@tinysofa.org> <200601171244.05944.mikael@tinysofa.org> <20060117121813.GA1522@ws64.jh.dy.fi> Message-ID: <200601171447.27790.mikael@tinysofa.org> On Tuesday 17 January 2006 04.18, Jaakko Heinonen wrote: > Run kudzu and watch for /etc/sysconfig/hwconf changes. Please try to run > kudzu also with empty /etc/sysconfig/hwconf and /etc/modprobe.conf. Old > values especially in /etc/modprobe.conf may cause it behave differently. Well, this is interesting! I did not yet install the new version of kudzu. I only removed the entries in /etc/sysconfig/hwconf and /etc/modprobe.conf and ran "kudzu -p" and got the following: [snipped] - class: NETWORK bus: PCI detached: 0 device: eth0 driver: e1000 desc: "Intel Corp.|82541GI/PI Gigabit Ethernet Controller" vendorId: 8086 deviceId: 1076 subVendorId: 1028 subDeviceId: 019a pciType: 1 pcibus: 2 pcidev: 4 pcifn: 0 - class: NETWORK bus: PCI detached: 0 device: eth1 driver: e1000 desc: "Intel Corp.|82541GI/PI Gigabit Ethernet Controller" vendorId: 8086 deviceId: 1076 subVendorId: 1028 subDeviceId: 019a pciType: 1 pcibus: 4 pcidev: 3 pcifn: 0 - [snipped] Now I have eth1 for the second nic without updating kudzu. I don't know about you but I didn't expect this to happen :-) Ok. Now still running the old kudzu version without the "-p" switch I get the same result as above (eth1). And the following /etc/modprobe.conf: alias eth0 e1000 alias eth1 e1000 alias usb-controller uhci-hcd alias usb-controller1 ehci-hcd alias scsi_hostadapter ata_piix And it looks nice to me! And it seems that the aliases comes in the right order now. My old file had the eth2 alias in the end of the file for some reason. Additionally I get an error message when kudzu exits: # kudzu sh: /usr/sbin/netconfig: No such file or directory sh: /usr/sbin/netconfig: No such file or directory # This makes me believe that it is unneccessary to try the new kudzu rpm, because with a clean state the old one is generating a good configuration. Or what do you think? Maybe there is a bad default state in some config files when kudzu runs from the installer. The only problem I can see is the absence of netconfig in tcs2.0. It was present in tcs1.1. Thanks again, Mikael From jh at tinysofa.org Tue Jan 17 07:47:31 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <200601171447.27790.mikael@tinysofa.org> References: <20060116222439.2146b7f7.mikael@tinysofa.org> <200601171244.05944.mikael@tinysofa.org> <20060117121813.GA1522@ws64.jh.dy.fi> <200601171447.27790.mikael@tinysofa.org> Message-ID: <20060117134731.GA1596@ws64.jh.dy.fi> On 2006-01-17, Mikael Bak wrote: > The only problem I can see is the absence of netconfig in tcs2.0. It was > present in tcs1.1. It's in netconfig package. kudzu should probably require it. -- Jaakko From mikael at tinysofa.org Tue Jan 17 17:14:32 2006 From: mikael at tinysofa.org (Mikael Bak) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <20060117134731.GA1596@ws64.jh.dy.fi> References: <20060116222439.2146b7f7.mikael@tinysofa.org> <200601171447.27790.mikael@tinysofa.org> <20060117134731.GA1596@ws64.jh.dy.fi> Message-ID: <200601171514.33477.mikael@tinysofa.org> On Tuesday 17 January 2006 05.47, Jaakko Heinonen wrote: > > It's in netconfig package. kudzu should probably require it. Oh sorry, and thanks! I missed that one. Now netconfig is called for each NIC found. Just as expected. Is it possible that kudzu reads the network interfaces running when scanning the system? When I ran kudzu now the eth1 was configured and running. I must deliver this machine tomorrow, so I can test only a few more things if you want to. Then I have to start installing production software on it. Mikael From jh at tinysofa.org Tue Jan 17 15:44:18 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <200601171514.33477.mikael@tinysofa.org> References: <20060116222439.2146b7f7.mikael@tinysofa.org> <200601171447.27790.mikael@tinysofa.org> <20060117134731.GA1596@ws64.jh.dy.fi> <200601171514.33477.mikael@tinysofa.org> Message-ID: <20060117214417.GA29141@ws.jh.dy.fi> On 2006-01-17, Mikael Bak wrote: > I must deliver this machine tomorrow, so I can test only a few more things if > you want to. I was able to reproduce the problem tonight. So you can deliver the machine. :) The bug is indeed in kudzu. I didn't find a fix yet though. -- Jaakko From jh at tinysofa.org Wed Jan 18 11:02:33 2006 From: jh at tinysofa.org (Jaakko Heinonen) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <20060116222439.2146b7f7.mikael@tinysofa.org> References: <20060116222439.2146b7f7.mikael@tinysofa.org> Message-ID: <20060118170232.GB1523@ws64.jh.dy.fi> Hi, On 2006-01-16, Mikael Bak wrote: > I think I've found a small bug in the anaconda installer in tcs2.0. Now fixed in svn. The problem was that kudzu was run twice during installation. First time in kudzu package %post section and second time by anaconda in the post install phase. Kudzu got confused because anaconda hadn't written /etc/sysconfig/network-scripts/ifcfg-* files before the first run. Seems that kudzu's detection routines are not perfect but now interfaces are correctly set up after installation and additional kudzu runs (after installation) work as expected. -- Jaakko From gda at tinysofa.org Wed Jan 18 13:54:51 2006 From: gda at tinysofa.org (Gerald Dachs) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] Anaconda bug in tcs2.0? In-Reply-To: <20060118170232.GB1523@ws64.jh.dy.fi> References: <20060116222439.2146b7f7.mikael@tinysofa.org> <20060118170232.GB1523@ws64.jh.dy.fi> Message-ID: <20060118205451.50bc4ba8.gda@tinysofa.org> On Wed, 18 Jan 2006 19:02:33 +0200 Jaakko Heinonen wrote: > > Hi, > > On 2006-01-16, Mikael Bak wrote: > > I think I've found a small bug in the anaconda installer in tcs2.0. > > Now fixed in svn. The problem was that kudzu was run twice during > installation. First time in kudzu package %post section and second time > by anaconda in the post install phase. Kudzu got confused because > anaconda hadn't written /etc/sysconfig/network-scripts/ifcfg-* files > before the first run. Seems that kudzu's detection routines are not > perfect but now interfaces are correctly set up after installation and > additional kudzu runs (after installation) work as expected. good job finding this, thanks Gerald From mikael at tinysofa.org Thu Jan 26 06:59:23 2006 From: mikael at tinysofa.org (Mikael Bak) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] not active Message-ID: <1138280363.3383.95.camel@localhost.localdomain> Hi developers, I haven't been active at all lately. I'm very sorry! I have had tons of work to do and I still have troubble to get a machine dedicated for tinysofa development with mach and all goodies. So right now I'm trying to set up some infrastructure, so I can more actively take part in the development. I'm writing this because I feel I haven't done one single thing in this project yet... but I want to do so much :-) One idea I would like to realize soon is Xen with tinysofa. Simply because I need it myself :-) but I think others are interesed in Xen too. I'll start this off as soon as I have my machine up and running. Cheers, Mikael -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.tinysofa.org/pipermail/tinysofa-devel/attachments/20060126/2242b946/attachment.bin From mail-lists at s235.de Thu Jan 26 13:49:21 2006 From: mail-lists at s235.de (Dominik Schips) Date: Sun May 4 12:26:18 2008 Subject: [tinysofa-devel] not active In-Reply-To: <1138280363.3383.95.camel@localhost.localdomain> References: <1138280363.3383.95.camel@localhost.localdomain> Message-ID: <200601262049.22045.mail-lists@s235.de> Hello Mikael, > So right now I'm trying to set up some infrastructure, so I can more > actively take part in the development. Yes. I also prepare a spare machine to start getting deeper into tinysoft developement. > I'm writing this because I feel I haven't done one single thing in this > project yet... but I want to do so much :-) Me too, but I don't know to much to help build packages or other development stuff at the moment. But I'll try to learn. > One idea I would like to realize soon is Xen with tinysofa. Simply > because I need it myself :-) but I think others are interesed in Xen > too. I'll start this off as soon as I have my machine up and running. Xen with tinysofa would be great. If you need someone for testing just let me know. -- Best regards, Dominik Schips From mail-lists at s235.de Fri Jan 27 16:12:43 2006 From: mail-lists at s235.de (Dominik Schips) Date: Sun May 4 12:26:18 2008 Subject: Fwd: Re: [tinysofa-devel] not active Message-ID: <200601272312.43649.mail-lists@s235.de> ---------- Weitergeleitete Nachricht ---------- Subject: Re: [tinysofa-devel] not active Date: Friday 27 January 2006 22:24 From: APerez To: Dominik Schips Hello from Canada I guess is time for me to present myself My name is Alfredo and I come from Canada. I was looking for a Linux server that could run on a very slow and old Pentium II 225Mhz. I went through several distros until I found Tinysofa. The installation went well and very fast. Right now I am planning to build my own gateway/proxy sever using squid. I would really like to contributo to this project. I have several years of experience running Linux and BSD. Presently, I am part of the Gnome-bugsquad. I also know C and Perl languages. Guys, please count of me for that Xen project. Take care Alfredo On Thu, 2006-01-26 at 20:49 +0100, Dominik Schips wrote: > Hello Mikael, > > > So right now I'm trying to set up some infrastructure, so I can more > > actively take part in the development. > > Yes. I also prepare a spare machine to start getting deeper into tinysoft > developement. > > > I'm writing this because I feel I haven't done one single thing in this > > project yet... but I want to do so much :-) > > Me too, but I don't know to much to help build packages or other > development stuff at the moment. But I'll try to learn. > > > One idea I would like to realize soon is Xen with tinysofa. Simply > > because I need it myself :-) but I think others are interesed in Xen > > too. I'll start this off as soon as I have my machine up and running. > > Xen with tinysofa would be great. > If you need someone for testing just let me know. ------------------------------------------------------- -- Best regards, Dominik Schips