RE: [Unattended] Compaq/HP DL360/380 Gig interfaces
Thanks for all your help. 4.4-rc1 linux boot worked without any problems. Thanks Glen -Original Message- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 03, 2004 12:44 PM To: Niels S. Richthof; Bunting, Glen, IG Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] Compaq/HP DL360/380 Gig interfaces Niels S. Richthof [EMAIL PROTECTED] writes: man smb.conf look for name mangling the install-share should have: case sensitive = no I am skeptical that this is the problem, for two reasons. First, case sensitive = no is the default. You would have to explicitly set it to yes to break things, which would be a strange thing to do. Second, the reports suggest that this problem is related to using mount.cifs instead of smbmount. If the Samba server had case sensitive = yes, it would never have worked. My guess is that mount.cifs (which invokes the fancy new Linux CIFS client) is allowing the Linux client and server to negotiate unix extensions, including some kind of case sensitivity even when the server is not configured for it. Also, we have some evidence that checking for the existence of txtsetup.sif (when the actual name is TXTSETUP.SIF) works, but trying to open it fails. Glen Bunting writes: That makes sense. Any idea as to why it was unable to run: winnt /rx:lang /s:Z:\os\win2ksp4\i386 /u:C:\netinst\unattend.txt ? Maybe winnt.exe is upper case, and FreeDOS does not print a proper diagnostic? Hard to say for sure, but whatever the problem is, I highly suspect it has the same underlying cause. I uploaded a 4.4-rc1 to http://unattended.sourceforge.net/testing/ earlier today, with the smbmount code re-enabled. Care to give that a try? - Pat * If you are not the intended recipient of this e-mail, please notify the sender immediately. The contents of this e-mail do not amend any existing disclosures or agreements unless expressly stated. * --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Bunting, Glen, IG [EMAIL PROTECTED] writes: I tried using the 4.4-test5 cd and was able to make the initial connection using the ip instead if the server name. However when it is scanning for the os directory it errors out with the following: Unable to open /z/os/win2ksp4/i386/txtsetup.sif No such file at /z/lib/Unattend/IniFile.pm Which is correct. There is no txtsetup.sif file located there. Do I need one for the Linux boot cd? If so what do I need to put in it? There is a txtsetup.sif file in the i386 directory of every Windows CD. It is how Unattended identifies Windows installation media... Check again? Something very strange is happening here. We check for the existence of the txtsetup.sif file before we try to open it, so it should not crash. What kind of file server are you using? - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Bunting, Glen, IG [EMAIL PROTECTED] writes: I think I figured out part of the problem. I am running a Samba Server. The problem appears to be that when the script was looking for txtsetup.sif, it is case sensitive. I did have a TXTSETUP.SIF. This is very similar to a problem reported earlier today on the unattended-devel list. In a future revision can you make it so the script is case insensitive? Case sensitivity is more a property of the server than the client. I suspect if you set unix extensions = off in your smb.conf file it will fix the problem. This is my guess, anyway; it would be nice to know for certain. In any event, our next actual release will have smbmount re-enabled, which apparently avoids this problem by not supporting Samba's unix extensions. - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Hi! Case sensitivity is more a property of the server than the client. I suspect if you set unix extensions = off in your smb.conf file it will fix the problem. This is my guess, anyway; it would be nice to know for certain. man smb.conf look for name mangling the install-share should have: case sensitive = no cu Niels -- A: Weil es die Lesbarkeit des Textes verschlechtert. F: Warum ist TOFU so schlimm? A: TOFU F: Was ist eins der groesste Aergernisse in E-Mails? --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
RE: [Unattended] Compaq/HP DL360/380 Gig interfaces
That makes sense. Any idea as to why it was unable to run: winnt /rx:lang /s:Z:\os\win2ksp4\i386 /u:C:\netinst\unattend.txt ? Thanks Glen -Original Message- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 03, 2004 11:59 AM To: Bunting, Glen, IG Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] Compaq/HP DL360/380 Gig interfaces Bunting, Glen, IG [EMAIL PROTECTED] writes: I think I figured out part of the problem. I am running a Samba Server. The problem appears to be that when the script was looking for txtsetup.sif, it is case sensitive. I did have a TXTSETUP.SIF. This is very similar to a problem reported earlier today on the unattended-devel list. In a future revision can you make it so the script is case insensitive? Case sensitivity is more a property of the server than the client. I suspect if you set unix extensions = off in your smb.conf file it will fix the problem. This is my guess, anyway; it would be nice to know for certain. In any event, our next actual release will have smbmount re-enabled, which apparently avoids this problem by not supporting Samba's unix extensions. - Pat * If you are not the intended recipient of this e-mail, please notify the sender immediately. The contents of this e-mail do not amend any existing disclosures or agreements unless expressly stated. * --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Niels S. Richthof [EMAIL PROTECTED] writes: man smb.conf look for name mangling the install-share should have: case sensitive = no I am skeptical that this is the problem, for two reasons. First, case sensitive = no is the default. You would have to explicitly set it to yes to break things, which would be a strange thing to do. Second, the reports suggest that this problem is related to using mount.cifs instead of smbmount. If the Samba server had case sensitive = yes, it would never have worked. My guess is that mount.cifs (which invokes the fancy new Linux CIFS client) is allowing the Linux client and server to negotiate unix extensions, including some kind of case sensitivity even when the server is not configured for it. Also, we have some evidence that checking for the existence of txtsetup.sif (when the actual name is TXTSETUP.SIF) works, but trying to open it fails. Glen Bunting writes: That makes sense. Any idea as to why it was unable to run: winnt /rx:lang /s:Z:\os\win2ksp4\i386 /u:C:\netinst\unattend.txt ? Maybe winnt.exe is upper case, and FreeDOS does not print a proper diagnostic? Hard to say for sure, but whatever the problem is, I highly suspect it has the same underlying cause. I uploaded a 4.4-rc1 to http://unattended.sourceforge.net/testing/ earlier today, with the smbmount code re-enabled. Care to give that a try? - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
RE: [Unattended] Compaq/HP DL360/380 Gig interfaces
I tried using the 4.4-test5 cd and was able to make the initial connection using the ip instead if the server name. However when it is scanning for the os directory it errors out with the following: Unable to open /z/os/win2ksp4/i386/txtsetup.sif No such file at /z/lib/Unattend/IniFile.pm Which is correct. There is no txtsetup.sif file located there. Do I need one for the Linux boot cd? If so what do I need to put in it? Thanks Glen -Original Message- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 3:04 PM To: Bunting, Glen, IG Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] Compaq/HP DL360/380 Gig interfaces Bunting, Glen, IG [EMAIL PROTECTED] writes: Booting from the 4.4-test cd, I was able to get an ip address, but when I tried to connect to the share, I was unable to. I received a: Unable to connect to share smbmount did not work mount.cifs did not work mount error: could not find target server TCP name not found rc=4 Sorry; I left in some debugging stuff (skipping smbmount to test mount.cifs). Try giving the fully-qualified DNS name of the server, or just using 4.4-test5 which I just uploaded to http://unattended.sourceforge.net/testing/. - Pat * If you are not the intended recipient of this e-mail, please notify the sender immediately. The contents of this e-mail do not amend any existing disclosures or agreements unless expressly stated. * --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Bunting, Glen, IG [EMAIL PROTECTED] writes: I have two question/problems. 1.I am successfully able to run unattended using a dos floppy with an add on NIC (e10b). This is on a Compaq/HP DL360/380 G3. However when I try to do the same thing with the linux boot cd, it is unable to recognize the hard drive. I Get an error message that states: Found no hard drives (amiraid/ar0 ataraid/d0 cciss/c0d0 iz0/had ida/c0d0 rd/c0d0 had sda hdc) under /sys/block Your /sys/block contains ram0 - ram 15. How can I get the linux boot up cd to recognize the hard drives? Is this using a Compaq RAID? My script to decide which drivers to load was buggy. Please try 4.4-test4 at http://unattended.sourceforge.net/testing/ and let me know if it works any better. Failing that, please send me the output of this command: lspci -n | grep 'Class 01' 2. When I use the dos boot disk on the same servers as above with the integrated gig NICs, I am able to get the DHCP address, but then the server hangs. It is not able to go any further. It displays the ip address and the MAC address and that's all. When I try to do the same thing with the linux boot disk, I am able to make the connection, I just can't see the hard drives. Why does the dos startup hang, but the linux startup work? This is using the Tigon chip, b57, choice for dos and that is what linux cd autodetect. Basically, FreeDOS is broken six ways to Sunday. But we cannot distribute MS-DOS. You can copy the files to your own MS-DOS based disk, or you can try messing with the UMB providers in config.sys. (Using umbpci.sys instead of emm386.exe, or *neither*, might help.) I would rather work with you to fix our Linux boot disk. - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Bunting, Glen, IG [EMAIL PROTECTED] writes: Booting from the 4.4-test cd, I was able to get an ip address, but when I tried to connect to the share, I was unable to. I received a: Unable to connect to share smbmount did not work mount.cifs did not work mount error: could not find target server TCP name not found rc=4 Sorry; I left in some debugging stuff (skipping smbmount to test mount.cifs). Try giving the fully-qualified DNS name of the server, or just using 4.4-test5 which I just uploaded to http://unattended.sourceforge.net/testing/. - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
RE: [Unattended] Compaq/HP DL360/380 Gig interfaces
Thanks for your quick response. I downloaded the 4.4-test files and burned a new linux boot disk. I copied over the linuxboot zip and extracted it to our Samba server. Booting from the 4.4-test cd, I was able to get an ip address, but when I tried to connect to the share, I was unable to. I received a: Unable to connect to share smbmount did not work mount.cifs did not work mount error: could not find target server TCP name not found rc=4 Booting from the 4.3 linux boot cd, I was able to connect to the share and received the same error as before. Here is the output from lspci -n | grep 'Class 01' 00:0f.1 Class 0101: 1166:0212 (rev93) 01:03.0 Class 0104: 0e11:b178 (rev01) 03:01.0 Class 0104: 0e11:b060 (rev02) Thanks Glen -Original Message- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 12:13 PM To: Bunting, Glen, IG Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] Compaq/HP DL360/380 Gig interfaces Bunting, Glen, IG [EMAIL PROTECTED] writes: I have two question/problems. 1.I am successfully able to run unattended using a dos floppy with an add on NIC (e10b). This is on a Compaq/HP DL360/380 G3. However when I try to do the same thing with the linux boot cd, it is unable to recognize the hard drive. I Get an error message that states: Found no hard drives (amiraid/ar0 ataraid/d0 cciss/c0d0 iz0/had ida/c0d0 rd/c0d0 had sda hdc) under /sys/block Your /sys/block contains ram0 - ram 15. How can I get the linux boot up cd to recognize the hard drives? Is this using a Compaq RAID? My script to decide which drivers to load was buggy. Please try 4.4-test4 at http://unattended.sourceforge.net/testing/ and let me know if it works any better. Failing that, please send me the output of this command: lspci -n | grep 'Class 01' 2. When I use the dos boot disk on the same servers as above with the integrated gig NICs, I am able to get the DHCP address, but then the server hangs. It is not able to go any further. It displays the ip address and the MAC address and that's all. When I try to do the same thing with the linux boot disk, I am able to make the connection, I just can't see the hard drives. Why does the dos startup hang, but the linux startup work? This is using the Tigon chip, b57, choice for dos and that is what linux cd autodetect. Basically, FreeDOS is broken six ways to Sunday. But we cannot distribute MS-DOS. You can copy the files to your own MS-DOS based disk, or you can try messing with the UMB providers in config.sys. (Using umbpci.sys instead of emm386.exe, or *neither*, might help.) I would rather work with you to fix our Linux boot disk. - Pat * If you are not the intended recipient of this e-mail, please notify the sender immediately. The contents of this e-mail do not amend any existing disclosures or agreements unless expressly stated. * --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
