Re: Small LAN problem
Thanks for your assurances. Unfortunately, I am without a hub, so a crossover cable is my only option. If the cable was made incorrectly, then that would account for at least some of my troubles -- could you point me to some literature describing how a xover cable is made, or else explain the process on list? I would appreciate it. I always understood a crossover cable to be a cable that routed pin 1 to pin 8, pin 2 to pin 7, etc. If this is incorrect, I would like to know the correct way... thanks again, -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! pgpc7HOeP3dn6.pgp Description: PGP signature
Small LAN problem
-a) that it correctly discerned it. (that would be 192.168.0.255). Do any of you know where this can be set manually? On my sun box, when I try to telnet to my debian box I get a 'network is unreachable' error. On my debian box, I get a 'No route to host'. So, from this, were any of you able to tell easily which (or both) is the culprit responsible for my non-networked-ness, and how I might be able to fix it? Sorry to spam you all with so much Solaris crap, but the people who claim to know solaris on IRC are most unhelpful (contrasted to Linux people!) and the docs (when they exist) are cryptic at best. I'm starting to get frustrated, so I hope someone on here can help me out. I only have one monitor for my two boxes, so everytime I need to do something on the other I have to take the cable out of one, stick it in the other, etc... you know, major pain. It'll be delicious when they are networked. Thanks in advance. -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! pgpGE7yS2mzDO.pgp Description: PGP signature
Problem reading Windows CDR
Hi folks. I have a rather large collection of MP3s that I burned onto CDs using my step-brother's burner, which is on a Windows box. I burned it on using the DirectCD system. Anyway, I compiled Joliet extension support into my kernel and can mount the CDs fine; I get a directory listing, and all seems to work okay. However, I was unable to play the MP3s off the CD -- I presumed this was because I have an old computer whose CD read speed was simply too slow. So I decided to copy the file onto my drive. Upon doing so, cp hangs for a long time as the CD sounds like it's 'trying' to read. Eventually, I get cp: reading 'Foo - Bar.mp3': Input/output error on stderr. However, the cp was partially successful: a portion of the file does seem to transfer. I know this isn't a problem with my drive because my Debian CD, which I burned on the same CD burner (albeit without the DirectCD stuff) reads quite correctly, even with large files (like tetex-base). Of course, that's ISO9660 + rockridge instead of joliet extensions. I can get small text files and such off of the CD. The partially cp'd mp3 is not corrupted in any way, it's just not complete. I know it isn't the CD, because I can read them properly with my roomate's Windows computer. So basically, I'm at a loss. Has anyone had similar problems? I have an ATAPI compat cd-rom drive, am running linux 2.4.2, Debian/testing. This problem occured also when my box was stable with a 2.2.17 kernel. This is a CDR, not a CDRW, btw. Thanks for any help you can give. I'm at a loss w/o my music! -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! pgpaRTkw0wrqS.pgp Description: PGP signature
Re: quick howto-command questions?
ls -a | grep .c$ This is silly, of course, but if you want to be rigorous about it you probably should do 'ls -a | grep \\.c$' because grep (unlike the shell) uses proper regex syntax -- in which '.' is a special character (match any char). Thus 'ls -a | grep .c$ would list files such as 'fooc', so escaping the . is necessary. Two backslashes are required to get through the shell escaping. Apropos, I have a question: frequently I am in a directory (such as /dev, for example) which has more stuff in it than I can see in one screenful. Normally I pipe it through less, but am bothered by the 'one file per line'-isms that ls spits out in this case. I understand the necessity of this behaviour, but I was wondering, is there some option which forces columnated output regardless of the presence of a filter? -C is documented as column-formatting, but it is ignored in a pipe. In a related question, can one force sort by rows instead of by columns, ie, a b c\nd e f instead of a c e\nb d f? I say related because when viewing copious output through a pager, it would be useful to have sort by rows instead of by columns, which is the default behaviour. -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! pgpjLChwx9ZYK.pgp Description: PGP signature
Re: Problem reading Windows CDR
On Thu, Mar 22, 2001 at 02:20:15PM +1100, Matthew Dalton wrote: How slow? I'm actually not sure, because I didn't buy the computer. Is there some way to tell how fast Debian thinks it is? But 2x, maybe 4x at most would be my guess. I used to have problems reading some (not all) CD-Rs with my old 2x cdrom. The problem was just that the drive was not designed to read those CDs -- it was just too old. I suspect that the varying amounts of success I had (ie some CDRs worked, others didn't) was due to the dye types used in the different CDRs. I never worked out which dyes were better than others. Now I have a cdrom that reads everything (including CDRWs) so there's no problem. Well, as it happens, the CDR that works (the Debian one) and the CDRs that don't (the MP3 M$ formatted ones) are the same dye type -- in fact, they are from the same box. Also, the fact that I can get varying amounts of data off the CD seems to further discredit this theory. Why should I be able to read some of it, and not other parts? Of course, I know next to nothing about CDs, CDRs, and the like... -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! pgpTWRGwXrVN8.pgp Description: PGP signature
virtual terminals
hey folks. i was just wondering about virtual terms -- is there an easy way to change how many there are? debian seems to default at 6 running getty, and X opens up 7. presumably i can use as many as 12? how does this work? is it as simple as running getty from init, or is there a kernel definition somewhere that specifies how many i can have, or a little of both? is there some documentation on the subject somewhere? -- Alexander Poquet| We leave the obvious generalizations to the [EMAIL PROTECTED]| reader. -- Israel Herstein Use of PGP preferable in reply | Use Linux! pgpFXolmkpsQm.pgp Description: PGP signature
base floppy installation on i386 problem (newbie)
hi, im installing (or trying to) potato on an older p100 i have and everything was going well. i chose the rescue floppy installation method (which i know isn't as convienient as with a CD) and had gotten to the point where it was time to install my base system. the first time i tried it, all seemed ok -- up until disk 5, which almost completed and then fed me an error message. The error message was 'Success', which seemed a little strange. dbootstrap then proceeded to try to inflate base2_2.tgz and of course failed (as it hadn't completed creating it yet). Well, I figured my drive or my diskette was messed up which had happened before, so I went to my other computer to re rawrite a new disk 5 and began installing the base system again. this time, the same error happened, but with disk 4; it then, on my next try, happened with disk 3 and then disk 2, always the same error message. it continued to choke this way on disk 2 for some time. now, it won't finish disk 1, though it no longer gives me the bizarre 'Success' error. it just starts trying to gunzip base2_2.tgz right off the bat... is this a bug with dbootstrap, or has someone else had a similar error? the success error seemed to happen right before it would normally finish copying, so i thought maybe dbootstrap was misinterpreting a success response from the copying subroutine as an error and displaying it. i tried looking at the disks themselves by switching to the virtual console and mounting /dev/fd0 to see if i might be able to do it manually, but the disks don't appear to be in a mountable format. im confused. i tried looking around in the backlogs of the user-list and couldn't find any references, but i hope one of you can shed some light on this. thanks...
Question
When will debian get support for BusLogic FlashPoint LT SCSI adapters? More specifically, I want to install Debian onto my computer at work, whose hard drive is SCSI (along with the CD-ROM). The disks-i386 directory for the current debian release doesnt have a Rescue disk compatible with that card... -alexander
