martouf

cough, cough, hack! I was consuming a beverage as I read the opening two sentences, and nearly choked as I read the second sentence (the question aka opening salvo). aheeemmm... hhhhrrrkkkk.. cough. I can't believe d_p actually seems to think there's a valid comparison between OS/2 and GNU/Linux. Deviant, perhaps. Troll, certainly. I'm conjuring up the sound of Jabba the Hut's rolling chuckle provoked by Han Solo's bold but futile action in Episode 6. Not that I'm making comparisons, mind you, as they'd be just as much a distraction as Leia in that little leather number. But I'm feeling amused right now... hey, there must be a reason why the Government of Brazil, the City Government of Munich, IBM, and now even the State Goverment of California are all relying on GNU/Linux. ya think? Hey, Professor, the Land of 'THIMK' is now the Land of 'Linux'!

"goofle"? what is this goofle? a new search engine? danleff: a very excellent précis on 'architecture' (the non-urban kind)

I don't understand why your email service provider (ESP) does not offer you both incoming and outgoing mail service. I've never encountered such a thing. Perhaps you might want to change your ESP?

your ISP is wise to disable email relaying. why don't you use the smtp service which the pop3 email provider should be offering? pop3 for inbound, smtp for outbound ... with user authentication in both cases. that way the email you're sending out is actually from the place you're having it say it is from.

for initial testing, how about instead of mounting the WinXP share try using "smbclient" instead? can you issue a 'dir' command from smbclient to see the contents of your WinXP share?

interesting. and without rebooting or changing the network configuration of the system whose conditions you have documented in your previous post: "arp -a" and "ping 192.168.1.1" ?? you see, I notice there's no interface 'eth0:9' reported by ifconfig.. in fact, it looks entirely correct and normal..

when you say "burned correctly" do you mean you actually checked the md5sum of the ISO files before you did the burn? and there were no errors during the burn? If you mean only that there were no errors during the burn, you can't be so certain you've made good discs. After you've verified the md5sums of your ISO files, check to see if there's an option when you do your image burn to enable/disable padding or if there's an option to do track-at-once (TAO) burning instead of disc-at-once (DAO). If you have your burning software add padding to a disc image already mastered with padding then you'll only create spoiled media. Conversely, you may need to have your burning software add padding to an image mastered without.

please reboot and attempt to configure your network interface (set addr 192.168.1.2 etc..) (you may leave your resolv.conf file "as is" for the time being) having done what you think is right, then please provide the output of the following commands: "netstat -r" "ifconfig -a" samyscoub: thanks for trying to help, but BTierens has more basic problems to get fixed before working out any DNS configuration issues.

DDan: if you mean by 'install' that you compiled Xine from sources, then yes, you'd need to have the "-devel" packages installed. If you're using a precompiled Xine, I don't think there's a packaging error that would cause you to need them. brodee: looks like the software you need is present and accounted for.. I'm thinking the problem is related to xv/fb issues. That is, the video images are getting written to video RAM alright, but not the part of RAM which is mapped to the area inside the Xine video window. What happens when you tell Xine to favor simplicity over performance? try: "xine --verbose=2 --video-driver xshm" The possible xine video driver choices are: xv syncfb fb xshm none

if you're intending to support a number of Debian hosts from one Debian package caching server, then refer to the apt-proxy homepage. the "README and FAQ" file has step-by-step instructions, and there's even an example apt-proxy.conf file.

if you're intending to support a number of Debian hosts from one Debian package caching server, then refer to the apt-proxy homepage. the "README and FAQ" file has step-by-step instructions, and there's even an example apt-proxy.conf file. ps: sorry about the double-posting. forgot to cut-n-paste the URI. :x

I think this thread is more directly applicable. The ".md5" file you downloaded is what you use to ensure the ".iso" file is not corrupted in any way and is the whole file with nothing missing. One small error in the ".iso" download can render it useless. So be sure to verify the image before you burn it. In the 'Helpful Stuff' section of LinuxISO.org you'll find some step-by-step instructions for popular CD burning software. If you need additional help, then just post your question here.

if you're trying "java NameOfClass" and getting an error message instead of what you expect, try: "java -classpath /dir1:/dir2/foo/bar/baz.jar:/dir3/blur/blue/arch.zip NameOfClass" instead. this will specify /dir1 is to be searched for class files, baz.jar is to be searched for classes within, and so too should arch.zip be searched. otherwise, java only looks in the factory-default-and-don't-mess-with-them locations.

if you do a long listing ("ls -l") of /dev and grep for the block major number mentioned in the 'notification' message (it isn't exactly an 'error' message), you'll probably get a good idea which driver is being modprobe'd for a device you don't actually have installed. viz: the message says "can't find block-major-7", so you check up on this with // ls -l /dev | grep " 7," // (the stuff between the double slash chars) You can do a quick check of the block major numbers of all active devices and drivers by doing "cat /proc/devices".

hmm, do you mean you've already set up a local apt repository? or are you simply trying to get apt set up to grab packages off of an Internet repository?

good. you're on the right track. I guess this means you've not only discovered the images directory but also the dosutils directory provided by the Mandrake distro. 8) If the "cdrom.img" on a floppy disk doesn't help you, then you might try the "boot.iso" image burned to a disc. Given the size of the boot.iso image, I'll guess it has an initrd with lots of drivers in addition to the kernel. The floppy disk images are best for systems having hardware the kernel recognizes right away, without needing additional modules loaded. You also may need to switch to one of the other virtual terminals as the hdcdrom_usb.img loads to see the information about your external CD drive you need to help the kernel find the install media. (CTRL-ALT-F1 is the vty you've been looking at.. the others are CTRL-ALT-F2 through -F6 and -F9 through -F12)

xine is pretty good about reporting every component it finds as it initializes, and installing the libdvdcss RPM should have rebuilt the linker cache. you can check xine by asking it to say more about what it's doing as it initializes by starting it from a shell with the --verbose parameter, viz: "xine --verbose" you can check the linker cache by looking through the output of "/sbin/ldconfig -p | grep dvd" to be certain libdvdcss is among the libraries listed. I'd like to know what the video and sound hardware is on your Asus motherboard.

If you read through this document, I think you'll see that unless you have the Intel ICH5/6 SATA hardware, you're going to have to delve into building kernel modules. The SATA document lists only beta support for your SATA hardware, and the time reference of May 2004. Mmmm, fresh code. Yummy! As TimMadDammit says, you're going to have to consider adding a plain IDE interface and IDE disk to your system to load a distro. It's that or build a custom install disk on another system.

Hi NeoSeeker, and welcome.. You have bravely ventured forward to the very leading edge of supported storage technology. SATA support is an area of ongoing development. It would help to know which distro you're loading before anyone can really guide you specifically.

sorry, but there aren't any Broadcom drivers except those provided for Windows. You can use the Windows drivers under Linux, however, if you purchase the inexpensive "DriverLoader" product from Linuxant.

Don't forget to verify the ISO files you've downloaded before attempting to burn them. It seems WinRAR has gotten in the act and confused things. If you verify the "rar" files to confirm the correct MD5sum, and the md5sums are all correct, then a simple renaming of the files from ".rar" to ".iso" should make your burning software happy. Are you sure they aren't ".iso" files but WinExplorer just lists them as WinRAR files? Open Explorer go to the "Tools" menu item -> Folder Options -> View -> and uncheck the "Hide extensions for known file types" option in the Files and Folders section. If they are already ".iso" files and you didn't know it, then there's no need to rename them. Be sure to avail yourself of all of the helpful information in the middle of the "Helpful Stuff" box on the lower left of the LinuxISO.org homepage.

Hi rfsoulrebel, and welcome! 8) if what you downloaded were three big (600+ MB) files, then chances are good you have the ISO files you're expecting. Knowing the URI you used to grab the files would help me confirm this for you. Assuming what you have are indeed the ISO files, you do not extract them. You burn them as an image to disc. Double-check your burner software settings before you start the burn to ensure you're burning an image to disc, and not burning them as regular files to disc. Until you know your burner well enough to know if it works reliably at a high speed, choose the slowest speed available for burning your discs. hope to hear news of your success...

reporting your CPU (type, speed), video display, and audio hardware would help the helpers help you, too.

that's lovely, outsane. Plus points for not making any mistakes that time. but you did all that over a dialup connection just like bobeverywhere, right? maybe only having burned maybe 3 bootdiscs before in your entire life? oh, well then, didn't think so.... Considering an under $10 purchase versus the cost of spoiled media and at least some value for your time was not an invitation for oneupmanship, outsane. sorry. My own experience is I've had better success using cdrecord under VMware than I've had using a well-known burner under WinXP. YMMV. But of course, one must have a successful distro install before you've got cdrecord available to make new discs. Hence, the need to consider a small purchase for a meta-bootstrapping.

I hear ya, bobeverywhere, but consider: (not including the value of your time) you've probably already spent $2.00 burning four discs you can't boot from (the SRPMs), and now you're going to spend another $2.00 burning four more discs which might boot. What's so bad about spending $4.95 for 4 CDs which will boot?