Date: Sat, 27 Nov 2004 12:33:06 +0530 From: Tejaswy Appalla <tejaswytej@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: freebsd-questions Digest, Vol 81, Issue 20 Message-ID: <6609b1bd041126230372926d63@mail.gmail.com> In-Reply-To: <20041126170539.43EB016A4D2@hub.freebsd.org> References: <20041126170539.43EB016A4D2@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
welll i am having trouble with installation of free bsd 5.3 here is the error "unable o write data ad0" "vty1 dma limited to udma33"1 "ad0:failure-read _dma timed out non ata66 cable or device " so plz help me out even when i tried to install free bsd 5.1 i got an error "read_dma interupt was seen but taskqueue time out LBA 78165297" "read_dma interupt was seen but taskqueue Satted LBA 78165297" any help will be appreciated On Fri, 26 Nov 2004 17:05:39 +0000 (GMT), freebsd-questions-request@freebsd.org <freebsd-questions-request@freebsd.org> wrote: > Send freebsd-questions mailing list submissions to > freebsd-questions@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > or, via email, send a message with subject or body 'help' to > freebsd-questions-request@freebsd.org > > You can reach the person managing the list at > freebsd-questions-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-questions digest..." > > Today's Topics: > > 1. Running commands at startup (Danny Browne) > 2. Diskgeometry - sysinstall bug? (Erik Norgaard) > 3. Re: Playing DVD movies with Xine (Graham Bentley) > 4. Re: WRITE_DMA failures on 5.3 (but NOT on 4.10) (Peter Risdon) > 5. Re: WRITE_DMA failures on 5.3 (but NOT on 4.10) (Peter Risdon) > 6. Re: Running commands at startup (Ion-Mihai Tetcu) > 7. Re: squid-downloads (David Landgren) > 8. Updating packages list (using cvsup?) (Olaf Greve) > 9. Re: How to boot FreeBSD from a slave IDE disk (Joshua Lokken) > 10. RE: Updating packages list (using cvsup?) > (Thomas S. Crum - AAA Web Solution, Inc.) > 11. RE: Updating packages list (using cvsup?) (Olaf Greve) > 12. Re: kernel compile error (Joshua Lokken) > 13. Re: kernel compile error (Brian Bobowski) > 14. Re: Updating packages list (using cvsup?) (Rob) > 15. Re: Error in ghostscript (Doug Van Allen) > 16. Re: kernel compile error (Gert Cuykens) > 17. Best driver setup for GeForce2 MX (Adam Maloney) > 18. Re: Restarting rc.conf (Ruben de Groot) > 19. Re: kernel compile error (Dick Davies) > 20. Re: Updating packages list (using cvsup?) (RW) > 21. Re[2]: WRITE_DMA failures on 5.3 (but NOT on 4.10) (DanGer) > 22. Re: Playing DVD movies with Xine (RL) > 23. Re: WRITE_DMA failures on 5.3 (but NOT on 4.10) (Peter Risdon) > 24. Re: Playing DVD movies with Xine (RW) > 25. loading ndis at boot ? (FreeBsdBeni) > 26. Re: shell programming challenge (Don Wilde) > 27. Re: Best driver setup for GeForce2 MX (Kees Plonsz) > 28. eject DAT tape via command? (Matthias F. Brandstetter) > 29. Re: eject DAT tape via command? (Martin Hepworth) > 30. Re: eject DAT tape via command? (lists) > 31. Re: eject DAT tape via command? (Gary Hayers) > 32. Re: eject DAT tape via command? (Matthias F. Brandstetter) > 33. Re: Xorg/Modes issue (Jake Stride) > 34. Re: Running commands at startup (Adam Fabian) > 35. How to get best results from FreeBSD-questions (Greg Lehey) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 26 Nov 2004 12:04:14 +0000 > From: "Danny Browne" <danny_browne@eircom.net> > Subject: Running commands at startup > To: "FreeBSD Mailing List" <freebsd-questions@freebsd.org> > Message-ID: <20041126120415.F260043D5D@mx1.FreeBSD.org> > Content-Type: text/plain; charset=us-ascii > > This will probobly seem like such a basic question, but where can do i put commands i want to run at startup. > > freeBSD 4.10 > > i want to run (for example) > > alias 'ls=ls -G' > alias 'vi=vim' > alias 'shutdown=shutdown -h now' > etc... > > Also, i am running fluxbox, but my mouse is very slow when it starts up. at the moment i have to enter xset m 5/1 in the terminal to speed it up. How can i get fluxbox do do this at startup? > > ____________________________________________________________ > Danny Browne > > _________________________________________________________________ > Sign up for eircom broadband now and get a free two month trial.* > Phone 1850 73 00 73 or visit http://home.eircom.net/broadbandoffer > > ------------------------------ > > Message: 2 > Date: Fri, 26 Nov 2004 13:17:47 +0100 > From: Erik Norgaard <norgaard@locolomo.org> > Subject: Diskgeometry - sysinstall bug? > To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> > Message-ID: <41A71EEB.4090301@locolomo.org> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Hi, > > I have problems making sysinstall behave, interactive or scripted. The > disk is 60GB Hitachi Travelstar, on boot the kernel FreeBSD 5.3-STABLE > identifies the geometry as: 116280/16/63, but sysinstall refuses these > values as insane, and tries to rewrite the disk geometry to 7296/255/63. > > Using all disk for slice 1 sysinstall writes the disklabel, but it fails > to initialize the swap partition claming no such device /dev/ad0s1b, or > I get write errors when I try to install. > > On reboot (pxe), even though the new partition table and geometry was > written, the kernel identifies the disk with the original geometry. It > appears that I should go with the geometry the kernel thinks. > > How do I get my disk sliced up from here? > > Thanks, Erik > > I have found the following code in disks.c which seems to be responsible: > > if (d->bios_cyl > 65536 || d->bios_hd > 256 || d->bios_sect >= 64) { > Sanitize_Bios_Geom(d); > } > > I have previously had FreeBSD 4.10 on the disk, installed from CD with > no problems. On my laptop (40GB), the disk geometry is 77520/16/63 > which should also fail in the above check I have 6.0-CURRENT, installed > originally as 5.2.1 but upgraded with cvsup. > > Running fdisk manually, I get the following output: > > parameters extracted from in-core disklabel are: > cylinders=116280 heads=16 sectors/tracks=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partions not in cyl 1 > parameters to be used for BIOS calculations are > cylinders=116280 heads=16 sectors/tracks=63 (1008 blks/cyl) > > Information from DOS bootblock is: > 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 117210177 (57231 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 567/ head 15/ sector 63 > 2: <UNUSED> > 3: <UNUSED> > 4: <UNUSED> > > Confirming to write disk, fdisk prints the following summary: > > /dev/ad0: 116280 cyl 16 hd 63 sec > Part Start Size Type Flags > 1 63 117210177 0xa5 0x80 > > This all looks OK, just like the kernel likes it... > > -- > Ph: +34.666334818 web: www.locolomo.org > S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt > Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 > Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 > > ------------------------------ > > Message: 3 > Date: Fri, 26 Nov 2004 12:30:02 +0000 > From: Graham Bentley <gbentley@uk2.net> > Subject: Re: Playing DVD movies with Xine > To: freebsd-questions@freebsd.org > Message-ID: <3.0.6.32.20041126123002.007c4290@mail.uk2.net> > Content-Type: text/plain; charset="us-ascii" > > I had to do this before Xine would recognise my DVD's > > ln -s /dev/acd0 /dev/dvd > ln -s /dev/acd0 /dev/rdvd > > Check these :- > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/video-playback.html > http://www.onlamp.com/pub/a/bsd/2002/10/03/FreeBSD_Basics.html > > Custom PC North West > Open Source Solutions > http://www.cpcnw.co.uk > > ------------------------------ > > Message: 4 > Date: Fri, 26 Nov 2004 12:46:58 +0000 > From: Peter Risdon <peter@circlesquared.com> > Subject: Re: WRITE_DMA failures on 5.3 (but NOT on 4.10) > To: craig@small-pla.net > Cc: freebsd-questions@freebsd.org > Message-ID: <41A725C2.30204@circlesquared.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > > craig wrote: > > hi, > > > > i wrote about this issue some weeks back, but have still not yet adequately > > resolved it. > > (http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-November/0638 > > 07.html) > [...] > > to repeat the original problem, when installing 5.3R it fails about 12% into > > extracting base into \ > > on the emergency terminal, there is a stream of warnings and failures > > reading: > > > > WARNING : WRITE_DMA UDMA ICRC ERROR <LBA..... blah > > FAILURE : WRITE_DMA status = 51<Ready, DSC, error>... blah > > > > this continues until i run out of patience. > > This is a really major problem that has affected every 5.3 and the more > recent 5.2.1 machines I've operated with largish [1] hard drives. The > novelty of losing several tens of gigs of data any time a drive gets > busy wears off fairly quickly. > > > > > the advice i received was : > > ... mainly about checking hardware, and this is _not_ the issue. I've > googled extensively on this and, as you did, replaced every hardware > component in the IDE lines, including the disk drives, without affecting > the problem. > > So far as I can make out, there was a change to default settings at some > point (I haven't scoured the CVS repository to find out exactly when) to > enable DMA because some newer drives require this[2]. > > This also affects some attempts to install from CD using CDRW/DVD drives[3]. > > The only answer seems to be to disable DMA and I hope to put together a > test machine in the next week to experiment with this. So far as I can > see, there's a chance that adding: > > hw.ata.ata_dma="0" > > to /boot/loader.conf might help but I haven't yet tried this. > > Peter. > > [1] - at least >80G but I'm not sure where it kicks in. > > [2] - > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-11/0078.html > > [3] - http://adam.kungfoohampster.com/lists/freebsd-stable/msg09493.shtml > > -- > > the circle squared > > network systems and software > > http://www.circlesquared.com > > ------------------------------ > > Message: 5 > Date: Fri, 26 Nov 2004 13:04:33 +0000 > From: Peter Risdon <peter@circlesquared.com> > Subject: Re: WRITE_DMA failures on 5.3 (but NOT on 4.10) > To: craig@small-pla.net > Cc: freebsd-questions@freebsd.org > Message-ID: <41A729E1.1060505@circlesquared.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Peter Risdon wrote: > > craig wrote: > > > >> hi, > >> > >> i wrote about this issue some weeks back, but have still not yet > >> adequately > >> resolved it. > >> (http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-November/0638 > >> > >> 07.html) > > > > [...] > > > >> to repeat the original problem, when installing 5.3R it fails about > >> 12% into > >> extracting base into \ > >> on the emergency terminal, there is a stream of warnings and failures > >> reading: > >> > >> WARNING : WRITE_DMA UDMA ICRC ERROR <LBA..... blah > >> FAILURE : WRITE_DMA status = 51<Ready, DSC, error>... blah > >> this continues until i run out of patience. > > > > > > This is a really major problem that has affected every 5.3 and the more > > recent 5.2.1 machines I've operated with largish [1] hard drives. The > > novelty of losing several tens of gigs of data any time a drive gets > > busy wears off fairly quickly. > > > >> > >> the advice i received was : > > > > > > ... mainly about checking hardware, and this is _not_ the issue. I've > > googled extensively on this and, as you did, replaced every hardware > > component in the IDE lines, including the disk drives, without affecting > > the problem. > > > > So far as I can make out, there was a change to default settings at some > > point (I haven't scoured the CVS repository to find out exactly when) to > > enable DMA because some newer drives require this[2]. > > > > No - apologies for wasting bandwidth. I got to this stage of research > very late a couple of nights ago and see I should have stopped a few > hours earlier. Looking again, this: > > hw.ata.atapi_dma: 0 > > in loader.conf might fix the problem with atapi drives but the > > hw.ata.ata_dma: 1 > > sysctl setting seems to have been the default in 4.10 too, so that can't > be it. > > I think I might try turning off ata dma in a 5.3 system anyway, and > putting a big drive under load to see what happens, but I fear I'm > probably back to square one. > > Peter. > > -- > > the circle squared > > network systems and software > > http://www.circlesquared.com > > ------------------------------ > > Message: 6 > Date: Fri, 26 Nov 2004 15:23:30 +0200 > From: Ion-Mihai Tetcu <itetcu@apropo.ro> > Subject: Re: Running commands at startup > To: danny_browne@eircom.net > Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> > Message-ID: <20041126152330.02968099@it.buh.tecnik93.com> > Content-Type: text/plain; charset=US-ASCII > > On Fri, 26 Nov 2004 12:04:14 +0000 > "Danny Browne" <danny_browne@eircom.net> wrote: > > > > > This will probobly seem like such a basic question, but where can do i > > put commands i want to run at startup. > > for example cron, see @reboot > > > freeBSD 4.10 > > > > i want to run (for example) > > > > alias 'ls=ls -G' > > alias 'vi=vim' > > alias 'shutdown=shutdown -h now' > > etc... > > This are a different problem > see: > > /etc/csh.* > ~/.cshrc > ~/.login > > -- > IOnut > Unregistered ;) FreeBSD "user" > > ------------------------------ > > Message: 7 > Date: Fri, 26 Nov 2004 14:37:38 +0100 > From: David Landgren <david@landgren.net> > Subject: Re: squid-downloads > To: questions@freebsd.org > Message-ID: <41A731A2.1000309@landgren.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > metallarch wrote: > >-- > >How can i deny downloads from squid? > > Here's a novel idea, how about reading the documentation? > > http://www.squid-cache.org/Doc/FAQ/FAQ-10.html > > ------------------------------ > > Message: 8 > Date: Fri, 26 Nov 2004 14:45:14 +0100 > From: "Olaf Greve" <o.greve@axis.nl> > Subject: Updating packages list (using cvsup?) > To: <freebsd-questions@freebsd.org> > Message-ID: <005501c4d3be$2865be60$1e01a8c0@sjees> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > I was wondering about a thingy. > > Whenever I use sysinstall to add a package, the list seems to be > constantly the same (i.e. often outdated), whereas more recent versions > should be available of several of the packages. Of course I can manually > d/l the packages and if necessary compile them and install them, but I > have also heard of the possibility of using cvsup to automatically > update the packages tree. > > Now, I have installed cvsup, and I quickly browsed over the man pages (I > have to admit that I have not yet been able to spend much time on this), > but I was wondering if this is really the best way to go. Sure, it does > automatically update collections, etc., but is this really the handiest > tool out there for this particular task? > > If not, can anyone please name me an alternative (approach)? > If it is, OTOH, can anyone please give me some quick pointers for > setting this up correctly, and/or point me to a page where this process > is explained. > > Thanks in advance, and cheers! > Olafo > > ------------------------------ > > Message: 9 > Date: Fri, 26 Nov 2004 07:55:21 -0600 > From: Joshua Lokken <joshua.lokken@gmail.com> > Subject: Re: How to boot FreeBSD from a slave IDE disk > To: rain cip <raincip@yahoo.com> > Cc: freebsd-questions@freebsd.org > Message-ID: <bc5b638504112605551d5afde@mail.gmail.com> > Content-Type: text/plain; charset=US-ASCII > > On Thu, 25 Nov 2004 20:26:38 -0800 (PST), rain cip <raincip@yahoo.com> wrote: > > Hello, > > > > I hope I can get some help from this list to figure out how to boot FreeBSD from a slave drive. My PC has two disks. The sysinstall sees both: ad0 and ad3. My hardware configuration is such: > > > > ad0 -- primary IDE, master (all for Win2k) > > ad3 -- secondary IDE, slave (all for FreeBSD 5.3) > > > > > > > > > > I know I must have done something wrong. But what did I do wrong? > > I'm not sure. I know that I use a tool called GAG to boot mutliple > OSes from assorted locations, and it has always worked very well for > me. > > http://gag.sourceforge.net/ > > HTH, > > -- > Joshua Lokken > Open Source Advocate > > ------------------------------ > > Message: 10 > Date: Fri, 26 Nov 2004 09:08:59 -0500 > From: "Thomas S. Crum - AAA Web Solution, Inc." > <tscrum@aaawebsolution.com> > Subject: RE: Updating packages list (using cvsup?) > To: "'Olaf Greve'" <o.greve@axis.nl>, <freebsd-questions@freebsd.org> > Message-ID: <003d01c4d3c1$7d1eb5d0$0200a8c0@wolf> > Content-Type: text/plain; charset="us-ascii" > > Packages are pre-compiled so there is little ability to configure them, > should you need to. Although I still know many people who prefer using > packages. Do not use sysinstall to accomplish this. Also, there is no need > to 'download or update' your 'packages'. Simply follow the below command to > install the current package. > > # pkg_add -r some_package > > I would recommend ports and cvs to anyone. > > Below is a config to install cvsup and run it to update your ports > collection. Remember though, ports are not precompiled and you will > actually need to move into the /usr/ports/whatever_port/whatever_program dir > to install them. > > # pkg_add -r cvsup-without-gui > # cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile > // change 'changethis' to cvsup2, cvsup3, etc. > # ee /root/ports-supfile > // REBOOT SERVER > # shutdown -r now > // Run CVsup to make ports current. (will take approx. 1 hour over > broadband) > # cvsup -g -L 2 /root/ports-supfile > > Also there is a wealth of information in the FreeBSD handbook and I would > consider giving that a read. > > Best, > > Thomas S. Crum > > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Olaf Greve > Sent: Friday, November 26, 2004 8:45 AM > To: freebsd-questions@freebsd.org > Subject: Updating packages list (using cvsup?) > > Hi all, > > I was wondering about a thingy. > > Whenever I use sysinstall to add a package, the list seems to be > constantly the same (i.e. often outdated), whereas more recent versions > should be available of several of the packages. Of course I can manually > d/l the packages and if necessary compile them and install them, but I > have also heard of the possibility of using cvsup to automatically > update the packages tree. > > Now, I have installed cvsup, and I quickly browsed over the man pages (I > have to admit that I have not yet been able to spend much time on this), > but I was wondering if this is really the best way to go. Sure, it does > automatically update collections, etc., but is this really the handiest > tool out there for this particular task? > > If not, can anyone please name me an alternative (approach)? > If it is, OTOH, can anyone please give me some quick pointers for > setting this up correctly, and/or point me to a page where this process > is explained. > > Thanks in advance, and cheers! > Olafo > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > ------------------------------ > > Message: 11 > Date: Fri, 26 Nov 2004 15:22:20 +0100 > From: "Olaf Greve" <o.greve@axis.nl> > Subject: RE: Updating packages list (using cvsup?) > To: "'Thomas S. Crum - AAA Web Solution, Inc.'" > <tscrum@aaawebsolution.com>, <freebsd-questions@freebsd.org> > Message-ID: <005d01c4d3c3$57404610$1e01a8c0@sjees> > Content-Type: text/plain; charset="us-ascii" > > Hi Thomas (and others), > > First off: thanks a lot for your answer, this is indeed what I was > looking for... Then some specifics: > > > Packages are pre-compiled so there is little ability to configure > them, > > should you need to. Although I still know many people who prefer using > > packages. > > I find them handy at times, but indeed some of them are hopelessly > outdated (like Clamd)...:) > > > Do not use sysinstall to accomplish this. Also, there is no need to > 'download or > > update' your 'packages'. Simply follow the below command to install > the current package. > > I know. I didn't express myself correctly: what I meant to say was to > update the tree of 'packages', but then, as you stated, what I actually > should have been referring to is the tree of 'ports'. :P > > > Below is a config to install cvsup and run it to update your ports > > collection. Remember though, ports are not precompiled and you will > > actually need to move into the > /usr/ports/whatever_port/whatever_program dir > > to install them. > > Yes, that's fine thanks! > > So the below should do the trick. > > > # pkg_add -r cvsup-without-gui > > # cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile > > // change 'changethis' to cvsup2, cvsup3, etc. > > # ee /root/ports-supfile > > // REBOOT SERVER > > # shutdown -r now > > // Run CVsup to make ports current. (will take approx. 1 hour over > > broadband) > > # cvsup -g -L 2 /root/ports-supfile > > Cool. Sounds easy enough. So I guess if I were to schedule the 'cvsup -g > -L 2 /root/ports-supfile' command using cron, a weekly task should do. > > > Also there is a wealth of information in the FreeBSD handbook and I > would > > consider giving that a read. > > Thanks, indeed I have printed that (for the 5.1 version, but that should > be o.k.) and I shall check that out as well... > > Cheers! > Olafo > > ------------------------------ > > Message: 12 > Date: Fri, 26 Nov 2004 08:27:49 -0600 > From: Joshua Lokken <joshua.lokken@gmail.com> > Subject: Re: kernel compile error > To: Kris Kennaway <kris@obsecurity.org> > Cc: Rob <spamrefuse@yahoo.com> > Message-ID: <bc5b638504112606273f80a71@mail.gmail.com> > Content-Type: text/plain; charset=US-ASCII > > > On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote: > > > Matt Emmerton wrote: > > > >>/usr/src/sys/pci/if_rl.c:122:23: miibus_if.h: No such file or directory > > > >>mkdep: compile failed > > > > > > > > > > > >You need "device miibus" in your kernel config if you want to use "device > > > >rl". > > > Having such a mechanism, would prevent lots of beginners in the > > > kernel compiling stuff, to get frustrated with errors like above. > > Also, as you see, it's well-documented in the kernel config file ;) > > -- > Joshua Lokken > Open Source Advocate > > ------------------------------ > > Message: 13 > Date: Fri, 26 Nov 2004 09:32:08 -0500 > From: Brian Bobowski <bbobowski@cogeco.ca> > Subject: Re: kernel compile error > To: Joshua Lokken <joshua.lokken@gmail.com> > Cc: Rob <spamrefuse@yahoo.com> > Message-ID: <41A73E68.9020509@cogeco.ca> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Joshua Lokken wrote: > > >>On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote: > >> > >> > >>>Matt Emmerton wrote: > >>> > >>> > >>>Having such a mechanism, would prevent lots of beginners in the > >>>kernel compiling stuff, to get frustrated with errors like above. > >>> > >>> > >Also, as you see, it's well-documented in the kernel config file ;) > > > > > While this is true, it's also easy enough for someone to snip the > directions when slicing things out of the config file. Assuming that the > user won't do things the wrong way is a sure way to succumb to Murphy's > Law(the real one). > > The main barrier I can see to this is getting whatever parses the config > file to recognise such dependencies; as it is, it's the compiler that > runs into the problem, not the program that calls the compiler. The > compiler doesn't know where the relevant source is if not told to > include it, after all. > > -BB > > ------------------------------ > > Message: 14 > Date: Fri, 26 Nov 2004 23:23:30 +0900 > From: Rob <spamrefuse@yahoo.com> > Subject: Re: Updating packages list (using cvsup?) > To: FreeBSD <freebsd-questions@freebsd.org> > Message-ID: <41A73C62.2090609@yahoo.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Thomas S. Crum - AAA Web Solution, Inc. wrote: > > Packages are pre-compiled so there is little ability to configure them, > > should you need to. Although I still know many people who prefer using > > packages. Do not use sysinstall to accomplish this. Also, there is no need > > to 'download or update' your 'packages'. Simply follow the below command to > > install the current package. > > > > # pkg_add -r some_package > > > > I would recommend ports and cvs to anyone. > > > > Below is a config to install cvsup and run it to update your ports > > collection. Remember though, ports are not precompiled and you will > > actually need to move into the /usr/ports/whatever_port/whatever_program dir > > to install them. > > > > # pkg_add -r cvsup-without-gui > > # cp /usr/share/examples/cvsup/ports-supfile /root/ports-supfile > > Or forget about making a copy, and do directly: > > # cvsup -g -L2 -h cvsup.foo.bar /usr/share/examples/cvsup/ports-supfile > > Rob. > > ------------------------------ > > Message: 15 > Date: Fri, 26 Nov 2004 09:39:06 -0500 > From: Doug Van Allen <dvanallen@gmail.com> > Subject: Re: Error in ghostscript > To: Adam Fabian <afabian@austin.rr.com>, freebsd-questions@freebsd.org > Message-ID: <2063a95c0411260639dd021f6@mail.gmail.com> > Content-Type: text/plain; charset=US-ASCII > > Tried that and it didn't work. > > > On Thu, 25 Nov 2004 10:23:39 -0600, Adam Fabian <afabian@austin.rr.com> wrote: > > > I had an error building afl ghostscript a while ago. It required > > > svgalib, which wasn't pulled in as a dependency. (Kind of snuck at it > > > the back way by having drivers that required it.) Anyway, try > > > installing the svgalib port and picking up the compile. > > > -- > > > Adam Fabian (afabian@austin.rr.com) > > > > > > > > > > > > > ------------------------------ > > Message: 16 > Date: Fri, 26 Nov 2004 15:38:49 +0100 > From: Gert Cuykens <gert.cuykens@gmail.com> > Subject: Re: kernel compile error > To: Brian Bobowski <bbobowski@cogeco.ca> > Cc: Rob <spamrefuse@yahoo.com> > Message-ID: <ef60af09041126063811983afc@mail.gmail.com> > Content-Type: text/plain; charset=US-ASCII > > On Fri, 26 Nov 2004 09:32:08 -0500, Brian Bobowski <bbobowski@cogeco.ca> wrote: > > Joshua Lokken wrote: > > > > >>On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote: > > >> > > >> > > >>>Matt Emmerton wrote: > > >>> > > >>> > > >>>Having such a mechanism, would prevent lots of beginners in the > > >>>kernel compiling stuff, to get frustrated with errors like above. > > >>> > > >>> > > >Also, as you see, it's well-documented in the kernel config file ;) > > > > > > > > While this is true, it's also easy enough for someone to snip the > > directions when slicing things out of the config file. Assuming that the > > user won't do things the wrong way is a sure way to succumb to Murphy's > > Law(the real one). > > > > The main barrier I can see to this is getting whatever parses the config > > file to recognise such dependencies; as it is, it's the compiler that > > runs into the problem, not the program that calls the compiler. The > > compiler doesn't know where the relevant source is if not told to > > include it, after all. > > > > -BB > > > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > > this is how a teletubie config file look like , teletubies dont like > big files the prefer small ones. > > machine amd64 > cpu HAMMER > ident GERT > > options SCHED_4BSD # ????? > options INET # InterNETworking > options INET6 # IPv6 communications protocols > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directories > options MD_ROOT # MD is a potential root device > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options NTFS # NT File System > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_GPT # GUID Partition Tables. > options COMPAT_IA32 # Compatible with i386 binaries > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B real-time extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options AHC_REG_PRETTY_PRINT # Print register bitfields in debug > output. Adds ~128k to driver. > options AHD_REG_PRETTY_PRINT # Print register bitfields in debug > output. Adds ~215k to driver. > options ADAPTIVE_GIANT # Giant mutex is adaptive. > options NO_MIXED_MODE # SK8N > options ATA_STATIC_ID # Static device numbering > options UDF # DJO > > device atpic # 8259A compatability > device acpi # Bus support > device isa # Bus support > device pci # Bus support > device fdc # Floppy drives > device ata # ATA and ATAPI devices > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > device atapist # ATAPI tape drives > device scbus # SCSI bus (required for SCSI) > device ch # SCSI media changers > device da # Direct Access (disks) > device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > device ses # SCSI Environmental Services (and SAF-TE) > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > device vga # VGA video card driver > device splash # Splash screen and screen saver support > device sc # syscons is the default console > driver, resembling an SCO console > device cbb # cardbus (yenta) bridge > device pccard # PC Card (16-bit) bus > device cardbus # CardBus (32-bit) bus > device sio # 8250, 16[45]50 based serial ports > device ppc # Parallel port > device ppbus # Parallel port bus (required) > device lpt # Printer > device plip # TCP/IP over parallel > device ppi # Parallel port interface device > device rl # RealTek 8129/8139 > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > device sl # Kernel SLIP > device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > device bpf # Berkeley packet filter > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > device ugen # Generic > device uhid # "Human Interface Devices" > device ukbd # Keyboard > device ulpt # Printer > device umass # Disks/Mass storage - Requires scbus and da > device ums # Mouse > device uscanner # Scanners > device rue # RealTek RTL8150 USB Ethernet > device firewire # FireWire bus code > device sbp # SCSI over FireWire (Requires scbus and da) > device fwe # Ethernet over FireWire (non-standard!) > device fwip # DJO > device sound # DJO > device atapicam # DJO > device snd_ich # sound sk8n > > ------------------------------ > > Message: 17 > Date: Fri, 26 Nov 2004 08:32:44 -0600 (CST) > From: Adam Maloney <adam@whee.org> > Subject: Best driver setup for GeForce2 MX > To: freebsd-questions@freebsd.org > Message-ID: <Pine.GSO.4.60.0411260823440.5400@titan> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > Hi All, > > I've got a 5-STABLE box with a GeForce2 MX 32M card (dual-head and SVideo > out). My last card was a 4M Rage Pro (Nethack was AWESOME on this card!), > so I don't have any experience with any of these fancy new-fangled > graphics accelerators. > > Anyways, I'm having trouble figuring out the driver setup for this guy. > I'm running xorg-server-6.7.0_9. I have the card working using the > built-in NV driver, but no GL. I tried the FreeBSD drivers from NVidia, > but they caused X to crash in various spectacular ways. My understanding > is that these drivers are for XFree, and not Xorg? > > In any case, I'd like to know what combination of drivers, X, and animal > sacrifices to use to get the most out of this card. Now that my graphics > hardware is in the 21st century, I'd really like to see some > graphics-accelerated love under FreeBSD. > > Regards, > > Adam > > ------------------------------ > > Message: 18 > Date: Fri, 26 Nov 2004 16:00:36 +0100 > From: Ruben de Groot <mail25@bzerk.org> > Subject: Re: Restarting rc.conf > To: Rob <spamrefuse@yahoo.com> > Cc: FreeBSD <freebsd-questions@freebsd.org> > Message-ID: <20041126150036.GA14314@ei.bzerk.org> > Content-Type: text/plain; charset=us-ascii > > On Thu, Nov 25, 2004 at 02:54:39PM +0900, Rob typed: > > > This does not work if a service has been changed from YES to NO (or has > > been removed from rc.conf). Therefore I think this is better: > > > > foreach dir in /etc/rc.d /usr/local/etc/rc.d > > do > > cd $dir > > foreach file in * > > do > > $file forcestop > > $file start > > done > > done > > Have you actually tested this? I think not. (Hint: look at the scripts that > are in /etc/rc.d and what they actually do. Then RTM rcorder(8).) > > ------------------------------ > > Message: 19 > Date: Fri, 26 Nov 2004 15:03:49 +0000 > From: Dick Davies <rasputnik@hellooperator.net> > Subject: Re: kernel compile error > To: Brian Bobowski <bbobowski@cogeco.ca> > Cc: FreeBSD Questions <freebsd-questions@freebsd.org> > Message-ID: <20041126150349.GJ8520@lb.tenfour> > Content-Type: text/plain; charset=us-ascii > > * Brian Bobowski <bbobowski@cogeco.ca> [1134 14:34]: > > Joshua Lokken wrote: > > > > >>On Fri, Nov 26, 2004 at 04:03:52PM +0900, Rob wrote: > > >> > > >> > > >>>Matt Emmerton wrote: > > >>> > > >>> > > >>>Having such a mechanism, would prevent lots of beginners in the > > >>>kernel compiling stuff, to get frustrated with errors like above. > > >>> > > >>> > > >Also, as you see, it's well-documented in the kernel config file ;) > > > > > > > > While this is true, it's also easy enough for someone to snip the > > directions when slicing things out of the config file. Assuming that the > > user won't do things the wrong way is a sure way to succumb to Murphy's > > Law(the real one). > > Yeah, but assuming a user who can't read a comment is happy enough to > go editing a kernel config file, that's their funeral. > > "we'll err on the side of handing out rope and guns to all interested > parties while hoping you have enough smarts to keep from hanging yourself > or shooting yourself in the foot." - html, the definitive guide > > > The main barrier I can see to this is getting whatever parses the config > > file to recognise such dependencies > > I agree it should be fixed in config if anywhere, but it's worth bearing > in mind that kernel compiles on any platform are still non-trivial. > > I did a kernel build on Debian yesterday and it took half a dozen goes to > get a USB mouse working because usbhid wasn't there. No warnings, just > shedloads of insmod failures on reboot. Nice. > > At least our compiler craps out :) > > -- > What have you done to the cat? It looks half-dead. - Schroedinger's wife > Rasputin :: Jack of All Trades - Master of Nuns > > ------------------------------ > > Message: 20 > Date: Fri, 26 Nov 2004 15:25:13 +0000 > From: RW <list-freebsd-2004@morbius.sent.com> > Subject: Re: Updating packages list (using cvsup?) > To: freebsd-questions@freebsd.org > Message-ID: <200411261525.14104.list-freebsd-2004@morbius.sent.com> > Content-Type: text/plain; charset="iso-8859-1" > > On Friday 26 November 2004 14:22, Olaf Greve wrote: > > Hi Thomas (and others), > > > > First off: thanks a lot for your answer, this is indeed what I was > > > > looking for... > > I should also install portupgrade if I were you, it make managing ports a lot > easier. > > It also has the -P and -PP options (and corresponding per port settings > in /usr/local/etc/pkgtools.conf) which are useful for combining ports and > packages. For example a full KDE upgrade from ports takes me 3 days, but by > allowing portupgrade to install some of the less-important kde components > from fully up-to-date packages, I cut that down to one day. > > ------------------------------ > > Message: 21 > Date: Fri, 26 Nov 2004 16:26:22 +0100 > From: DanGer <danger@wilbury.sk> > Subject: Re[2]: WRITE_DMA failures on 5.3 (but NOT on 4.10) > To: Peter Risdon <peter@circlesquared.com>, questions@freebsd.org > Message-ID: <859059364.20041126162622@wilbury.sk> > Content-Type: text/plain; charset=us-ascii > > Hi Peter, > > Friday, November 26, 2004, 2:04:33 PM, you wrote these comments: > > >>> > >>> WARNING : WRITE_DMA UDMA ICRC ERROR <LBA..... blah > >>> FAILURE : WRITE_DMA status = 51<Ready, DSC, error>... blah > >>> this continues until i run out of patience. > >> > >> > >> This is a really major problem that has affected every 5.3 and the more > >> recent 5.2.1 machines I've operated with largish [1] hard drives. The > >> novelty of losing several tens of gigs of data any time a drive gets > >> busy wears off fairly quickly. > >> > >>> > >>> the advice i received was : > >> > >> > >> ... mainly about checking hardware, and this is _not_ the issue. I've > >> googled extensively on this and, as you did, replaced every hardware > >> component in the IDE lines, including the disk drives, without affecting > >> the problem. > >> > >> So far as I can make out, there was a change to default settings at some > >> point (I haven't scoured the CVS repository to find out exactly when) to > >> enable DMA because some newer drives require this[2]. > >> > > > No - apologies for wasting bandwidth. I got to this stage of research > > very late a couple of nights ago and see I should have stopped a few > > hours earlier. Looking again, this: > > > hw.ata.atapi_dma: 0 > > > in loader.conf might fix the problem with atapi drives but the > > > hw.ata.ata_dma: 1 > > > sysctl setting seems to have been the default in 4.10 too, so that can't > > be it. > > > I think I might try turning off ata dma in a 5.3 system anyway, and > > putting a big drive under load to see what happens, but I fear I'm > > probably back to square one. > > > Peter. > > i have the same issue on brand new 200gb ata maxtor hard drive. i had > the same issue on 5.2.1, but when i upgraded to 5.3 i decided to turn on > ata dma but after 9 days of uptime it froze..no logs, whatever...so i > turned ata dma off for now, and i will stay and watch what will happen.. > > but there should be some other fix, because i don't want to keep my > disc in pio mode :/ > > -- > Best Regards, > > +----------==/\/\==----------+ (__) FreeBSD > | DanGer <danger@wilbury.sk> | \\\'',) The > | DanGer@IRCnet ICQ261701668 | \/ \ ^ Power > | http://danger.homeunix.org | .\._/_) To > +----------==\/\/==----------+ Serve > > [ "Sometimes out big splashes are just ripples in the pool" ] > > ------------------------------ > > Message: 22 > Date: Fri, 26 Nov 2004 10:32:23 -0500 > From: RL <rlurman@gmail.com> > Subject: Re: Playing DVD movies with Xine > To: freebsd-questions@freebsd.org > Message-ID: <e6ceb9d4041126073273e8bba2@mail.gmail.com> > Content-Type: text/plain; charset=US-ASCII > > I have that already. I already had /dev/dvd linked > > ------------------------------ > > Message: 23 > Date: Fri, 26 Nov 2004 15:45:59 +0000 > From: Peter Risdon <peter@circlesquared.com> > Subject: Re: WRITE_DMA failures on 5.3 (but NOT on 4.10) > To: DanGer <danger@wilbury.sk> > Cc: questions@freebsd.org > Message-ID: <41A74FB7.4010907@circlesquared.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > > DanGer wrote: > [...] > > > > > > i have the same issue on brand new 200gb ata maxtor hard drive. i had > > the same issue on 5.2.1, but when i upgraded to 5.3 i decided to turn on > > ata dma but after 9 days of uptime it froze..no logs, whatever...so i > > turned ata dma off for now, and i will stay and watch what will happen.. > > That's very helpful, thank you. The behaviour you describe - machine > freezing - is exactly what I have experienced. I'm feeling vaguely > optimistic now :-) > > > > > but there should be some other fix, because i don't want to keep my > > disc in pio mode :/ > > Absolutely. But I guess, since I'm not going to try to produce a fix > myself, I can't whinge too loudly. A workaround is what I need right now > and I hope you've confirmed that this is one. > > Peter. > > -- > > the circle squared > > network systems and software > > http://www.circlesquared.com > > ------------------------------ > > Message: 24 > Date: Fri, 26 Nov 2004 15:53:19 +0000 > From: RW <list-freebsd-2004@morbius.sent.com> > Subject: Re: Playing DVD movies with Xine > To: freebsd-questions@freebsd.org > Message-ID: <200411261553.19777.list-freebsd-2004@morbius.sent.com> > Content-Type: text/plain; charset="iso-8859-1" > > On Friday 26 November 2004 12:30, Graham Bentley wrote: > > I had to do this before Xine would recognise my DVD's > > > > ln -s /dev/acd0 /dev/dvd > > ln -s /dev/acd0 /dev/rdvd > > > > You can setup this kind of thing inside xine, but you have to change your > "experience level" setting, otherwise it hides a lot of options. > > ------------------------------ > > Message: 25 > Date: Fri, 26 Nov 2004 17:11:16 +0100 > From: FreeBsdBeni <freebsdbeni@spymac.com> > Subject: loading ndis at boot ? > To: freebsd-questions@freebsd.org > Message-ID: <200411261711.20405.freebsdbeni@spymac.com> > Content-Type: text/plain; charset="iso-8859-15" > > Hi, > > How do I load the ndis.ko driver at boot/startup ? I've followed the > instructions on how to get the ndisulator working for my Z-Com wi-fi mini pci > card and got a (working) ndis0 dev now. I can kldload the ndis.ko and > if_ndis.ko but is there a way to automate this via /boot/loader.conf > or /etc/rc.conf ? And if so, what do I need to put in those files ? Something > like "ndis_load="YES" ? > > Thanks for any info ! > > I'm running 5.3-REL-p1. > -- > Beni. > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20041126/bb463ce7/attachment-0001.bin > > ------------------------------ > > Message: 26 > Date: Fri, 26 Nov 2004 09:15:11 -0700 > From: Don Wilde <Don@Silver-Lynx.com> > Subject: Re: shell programming challenge > To: freebsd-questions@freebsd.org > Cc: Jan Grant <Jan.Grant@bristol.ac.uk> > Message-ID: <41A7568F.3000906@Silver-Lynx.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > > > > > If you have the option to modify it, ensure that your script exits via > > "exec sh". Alternatively a wrapper that does this is straightforward to > > build. > > > It's looking more and more that I need to make a temporary file that > packages both the init file and the program command line (eval > "blah...") before running. These will not be just shell scripts, they > will be tool programs and x applications. Didn't want to do that because > of the risk of leaving junk in /tmp. > > -- > Don Wilde ---------> Silver Lynx <---------- > Raising the Trajectory of Human Development > --------------------------------------------- > http://www.Silver-Lynx.com > > ------------------------------ > > Message: 27 > Date: Fri, 26 Nov 2004 17:40:38 +0100 > From: Kees Plonsz <kees@jeremino.homeunix.net> > Subject: Re: Best driver setup for GeForce2 MX > To: freebsd-questions@freebsd.org > Message-ID: <200411261740.38265.kees@jeremino.homeunix.net> > Content-Type: text/plain; charset="us-ascii" > > I got the driver from the NVIDIA site and it works without any problems. > My system is 5.3 release and the card I use is: > > nvidia0: <GeForce2 MX/MX 400> mem 0xd0000000-0xd7ffffff,0xde000000-0xdeffffff > irq 16 at device 0.0 on pci1 > > I excluded Module "dri" ( I dont remember why ) and I use the Xorg library. > > Maybe you better not use 5 stable but 5.3 release instead. > > ------------------------------ > > Message: 28 > Date: Fri, 26 Nov 2004 17:42:06 +0100 > From: "Matthias F. Brandstetter" <haimat@lame.at> > Subject: eject DAT tape via command? > To: freebsd-questions@freebsd.org > Message-ID: <200411261742.06785.haimat@lame.at> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > is it possible to eject a DAT tape via a command from CLI? > "eject" does not seem to work :( > > Greets and TIA, Matthias > > -- > Oh, honey, I didn't get drunk, I just went to a strange fantasy world. > > -- Homer Simpson > El Viaje Misterioso De Nuestro Jomer > > ------------------------------ > > Message: 29 > Date: Fri, 26 Nov 2004 16:46:58 +0000 > From: Martin Hepworth <martinh@solid-state-logic.com> > Subject: Re: eject DAT tape via command? > To: "Matthias F. Brandstetter" <haimat@lame.at> > Cc: freebsd-questions@freebsd.org > Message-ID: <41A75E02.3040902@solid-state-logic.com> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Matthias > > mt -f /dev/sa0 rewoff > > replace /dev/sa0 with required device... > > -- > Martin Hepworth > Snr Systems Administrator > Solid State Logic > Tel: +44 (0)1865 842300 > > Matthias F. Brandstetter wrote: > > Hi all, > > > > is it possible to eject a DAT tape via a command from CLI? > > "eject" does not seem to work :( > > > > Greets and TIA, Matthias > > > > ********************************************************************** > > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > This footnote confirms that this email message has been swept > for the presence of computer viruses and is believed to be clean. > > ********************************************************************** > > ------------------------------ > > Message: 30 > Date: Fri, 26 Nov 2004 17:47:36 +0100 > From: lists <lists@sleektech.nl> > Subject: Re: eject DAT tape via command? > To: "Matthias F. Brandstetter" <haimat@lame.at> > Cc: freebsd-questions@freebsd.org > Message-ID: <41A75E28.9040907@sleektech.nl> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Try: > mt -f /dev/<tape> rewoffl > > Regards, > > Matthias F. Brandstetter wrote: > > >Hi all, > > > >is it possible to eject a DAT tape via a command from CLI? > >"eject" does not seem to work :( > > > >Greets and TIA, Matthias > > > > > > > > ------------------------------ > > Message: 31 > Date: Fri, 26 Nov 2004 16:50:16 +0000 > From: Gary Hayers <gary@hayers.org> > Subject: Re: eject DAT tape via command? > To: "Matthias F. Brandstetter" <haimat@lame.at>, > freebsd-questions@freebsd.org > Message-ID: <41A75EC8.80802@hayers.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Matthias F. Brandstetter wrote: > > >Hi all, > > > >is it possible to eject a DAT tape via a command from CLI? > >"eject" does not seem to work :( > > > >Greets and TIA, Matthias > > > > > > In my backup script I have > > # Wait 5 minutes for rewind > sleep 300 > > if [ $EJECT -eq 1 ] > then > mt offline > fi > > # > > mt offine does it for me :) > > ------------------------------ > > Message: 32 > Date: Fri, 26 Nov 2004 17:55:58 +0100 > From: "Matthias F. Brandstetter" <haimat@lame.at> > Subject: Re: eject DAT tape via command? > To: freebsd-questions@freebsd.org > Message-ID: <200411261755.58314.haimat@lame.at> > Content-Type: text/plain; charset="iso-8859-1" > > ---------- quoting Matthias F. Brandstetter ---------- > > is it possible to eject a DAT tape via a command from CLI? > > "eject" does not seem to work :( > > thanks guys for all this *quick* answers! > greets, Matthias > > -- > Around the house, I never lift a finger > As a husband and father I'm sub-par > I'd rather drink a beer > than win Father of the Year > I'm happy with things the way they are > > -- Homer Simpson > Simpsoncalifragilisticexpiala(annoyed grunt)ocious > > ------------------------------ > > Message: 33 > Date: Fri, 26 Nov 2004 16:59:30 +0000 > From: Jake Stride <nsuk@users.sourceforge.net> > Subject: Re: Xorg/Modes issue > To: freebsd-questions@freebsd.org > Message-ID: <41A760F2.3050908@users.sourceforge.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Adam Fabian wrote: > > >>(II) I810(0): Not using mode "1280x1024" (no mode of this name) > >> > >> > > > >1280x1024@75Hz looks like it might be the name of a mode. Otherwise, > >you could just write a modeline that does what you want. > > > > > OK I have fixed this issue, it seems I missed the fact that the bios had > set the video ram to 1meg, putting it up to 8med has sorted it! > > Thanks > > Jake > > ------------------------------ > > Message: 34 > Date: Fri, 26 Nov 2004 10:58:52 -0600 > From: Adam Fabian <afabian@austin.rr.com> > Subject: Re: Running commands at startup > To: FreeBSD Mailing List <freebsd-questions@freebsd.org> > Message-ID: <20041126165852.GA93504@turingmachine.mentalsiege.net> > Content-Type: text/plain; charset=us-ascii > > On Fri, Nov 26, 2004 at 12:04:14PM +0000, Danny Browne wrote: > > > > This will probobly seem like such a basic question, but where can do i > > put commands i want to run at startup. > > > > freeBSD 4.10 > > > > i want to run (for example) > > > > alias 'ls=ls -G' alias 'vi=vim' alias 'shutdown=shutdown -h now' > > etc... > > This is typically a function of your shell, unless you want to do it > on a system-wide basis. (A little while ago, I was trying to figure > out how to change the environment that processes inheirit from init on > FreeBSD but didn't have much luck.) csh and derivatives tend to use > .login and .cshrc, sh and derivatives tend to use .profile and .shrc. > > > Also, i am running fluxbox, but my mouse is very slow when it starts > > up. at the moment i have to enter xset m 5/1 in the terminal to speed it > > up. How can i get fluxbox do do this at startup? > > Put the command in your .xinitrc if you're using a display manager, > and your .Xsession (I think) if you're not. (It will be X that > executes the command, not fluxbox.) > > -- > Adam Fabian (afabian@austin.rr.com) > > ------------------------------ > > Message: 35 > Date: Fri, 26 Nov 2004 17:02:00 +0000 (GMT) > From: grog@FreeBSD.ORG (Greg Lehey) > Subject: How to get best results from FreeBSD-questions > To: FreeBSD-questions@FreeBSD.org > Message-ID: <20041126170200.8F9BC16A4CF@hub.freebsd.org> > > How to get the best results from FreeBSD questions. > =================================================== > > Last update $Date: 2004/09/19 02:40:48 $ > > This is a regular posting to the FreeBSD questions mailing list. If > you got it in answer to a message you sent, it means that the sender > thinks that at least one of the following things was wrong with your > message: > > - You left out a subject line, or the subject line was not appropriate. > - You formatted it in such a way that it was difficult to read. > - You asked more than one unrelated question in one message. > - You sent out a message with an incorrect date, time or time zone. > - You sent out the same message more than once. > - You sent an 'unsubscribe' message to FreeBSD-questions. > > If you have done any of these things, there is a good chance that you > will get more than one copy of this message from different people. > Read on, and your next message will be more successful. > > This document is also available on the web at > http://www.lemis.com/questions.html. > > ===================================================================== > > Contents: > > I: Introduction > II: How to unsubscribe from FreeBSD-questions > III: Should I ask -questions, -newbies or -hackers? > IV: How to submit a question to FreeBSD-questions > V: How to answer a question to FreeBSD-questions > > I: Introduction > =============== > > This is a regular posting aimed to help both those seeking advice from > FreeBSD-questions (the "newcomers"), and also those who answer the > questions (the "hackers"). > > Note that the term "hacker" has nothing to do with breaking > into other people's computers. The correct term for the latter > activity is "cracker", but the popular press hasn't found out > yet. The FreeBSD hackers disapprove strongly of cracking > security, and have nothing to do with it. > > In the past, there has been some friction which stems from the > different viewpoints of the two groups. The newcomers accused the > hackers of being arrogant, stuck-up, and unhelpful, while the hackers > accused the newcomers of being stupid, unable to read plain English, > and expecting everything to be handed to them on a silver platter. Of > course, there's an element of truth in both these claims, but for the > most part these viewpoints come from a sense of frustration. > > In this document, I'd like to do something to relieve this frustration > and help everybody get better results from FreeBSD-questions. In the > following section, I recommend how to submit a question; after that, > we'll look at how to answer one. > > II: How to unsubscribe from FreeBSD-questions > ============================================== > > When you subscribed to FreeBSD-questions, you got a welcome message > from freebsd-questions-request@FreeBSD.ORG. In this message, amongst > other things, it told you how to unsubscribe. Here's a typical > message: > > Welcome to the freebsd-questions@freebsd.org mailing list! > > If you ever want to unsubscribe or change your options (eg, switch to > or from digest mode, change your password, etc.), visit your > subscription page at: > > http://lists.freebsd.org/mailman/options/freebsd-questions/me@me.org > > (obviously, substitute your mail address for "me@me.org"). You can > also make such adjustments via email by sending a message to: > > freebsd-questions-request@freebsd.org > > with the word 'help' in the subject or body (don't include the > quotes), and you will get back a message with instructions. > > You must know your password to change your options (including > changing the password, itself) or to unsubscribe. > > Normally, Mailman will remind you of your freebsd.org mailing list > passwords once every month, although you can disable this if you > prefer. This reminder will also include instructions on how to > unsubscribe or change your account options. There is also a button on > your options page that will email your current password to you. > > Here's the general information for the list you've > subscribed to, in case you don't already have it: > > FREEBSD-QUESTIONS User questions > This is the mailing list for questions about FreeBSD. You should not > send "how to" questions to the technical lists unless you consider the > question to be pretty technical. > > Normally, unsubscribing is even simpler than the message suggests: you > don't need to specify your mail ID unless it is different from the one > which you specified when you subscribed. > > If Majordomo replies and tells you (incorrectly) that you're not on > the list, this may mean one of two things: > > 1. You have changed your mail ID since you subscribed. That's where > keeping the original message from majordomo comes in handy. For > example, the sample message above shows my mail ID as > grog@lemis.de. Since then, I have changed it to > grog@lemis.com. If I were to try to remove grog@lemis.com from > the list, it would fail: I would have to specify the name with > which I joined. > > 2. You're subscribed to a mailing list which is subscribed to > FreeBSD-questions. If that's the case, you'll have to figure out > which one it is and get your name taken off that one. If you're > not sure which one it might be, check the headers of the > messages you receive from freebsd-questions: maybe there's a > clue there. > > If you've done all this, and you still can't figure out what's going > on, send a message to Postmaster@FreeBSD.org, and he will sort things > out for you. Don't send a message to FreeBSD-questions: they can't > help you. > > III: Should I ask -questions, -newbies or -hackers? > =================================================== > > Two mailing lists handle general questions about FreeBSD, > FreeBSD-questions and FreeBSD-hackers. In addition, the > FreeBSD-newbies list caters specifically for people who are new to > FreeBSD and may be having trouble getting used to the environment. In > some cases, it's not really clear which group you should ask. The > following criteria should help for 99% of all questions, however: > > If the question is of a general nature, first check whether this > isn't a Frequently Asked Question (FAQ). There's a list of these > questions at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/index.html, > and also on your own system (once you've installed it) at > /usr/share/doc/en/books/faq/index.html. Check there, and if you > don't find an answer, ask FreeBSD-questions. Examples might be > questions about installing FreeBSD or the use of a particular > UNIX utility. > > If you think the question relates to a bug, but you're not sure, > or you don't know how to look for it, send the message to > FreeBSD-questions. > > If the question relates to a bug, and you're almost sure that > it's a bug (for example, you can pinpoint the place in the code > where it happens, and you maybe have a fix), then send the > message to FreeBSD-hackers. You should also enter a problem > report with the send-pr utility. > > If the question relates to enhancements to FreeBSD, and you can > make suggestions about how to implement them, then send the > message to FreeBSD-hackers. > > If the question is of particularly technical nature, such as > implementation details or suggestions for improvements, then send > the message to FreeBSD-hackers. > > If you're new to FreeBSD, and the message is about your own > relationship to FreeBSD, send the message to FreeBSD-newbies. > > There are also a number of other specialized mailing lists, for > example FreeBSD-isp, which caters to the interests of ISPs (Internet > Service Providers) who run FreeBSD. If you happen to be an ISP, this > doesn't mean you should automatically send your questions to > FreeBSD-isp. The criteria above still apply, and it's in your > interest to stick to them, since you're more likely to get good > results that way. > > IV: How to submit a question > ============================= > > When submitting a question to FreeBSD-questions, consider the > following points: > > 1. Remember that nobody gets paid for answering a FreeBSD question. > They do it of their own free will. You can influence this free > will positively by submitting a well-formulated question > supplying as much relevant information as possible. You can > influence this free will negatively by submitting an incomplete, > illegible, or rude question. It's perfectly possible to send a > message to FreeBSD-questions and not get an answer even if you > follow these rules. It's much more possible to not get an > answer if you don't. In the rest of this document, we'll look > at how to get the most out of your question to > FreeBSD-questions. > > 2. Not everybody who answers FreeBSD questions reads every message: > they look at the subject line and decide whether it interests > them. Clearly, it's in your interest to specify a subject. > ``FreeBSD problem'' or ``Help'' aren't enough. If you provide > no subject at all, many people won't bother reading it. If your > subject isn't specific enough, the people who can answer it may > not read it. > > 3. When sending a new message, well, send a new message. Don't > reply to some other message, erase the old content and change > the subject line. That leaves an In-reply-to: header which many > mail readers use to thread messages, so your message shows up as > a reply to some other message. People often delete messages a > whole thread at a time, so apart from irritating people, you > also run a chance of having the message deleted unread. > > 4. Format your message so that it is legible, and PLEASE DON'T > SHOUT!!!!!. We appreciate that a lot of people don't speak > English as their first language, and we try to make allowances > for that, but it's really painful to try to read a message > written full of typos or without any line breaks. A lot of > badly formatted messages come from bad mailers or badly > configured mailers. The following mailers are known to send out > badly formatted messages without you finding out about them: > > Eudora > exmh > Microsoft Exchange > Microsoft Internet Mail > Microsoft Outlook > Netscape > > As you can see, the mailers in the Microsoft world are frequent > offenders. If at all possible, use a UNIX mailer. If you must > use a mailer under Microsoft environments, make sure it is set > up correctly. Try not to use MIME: a lot of people use mailers > which don't get on very well with MIME. > > For further information on this subject, check out > http://www.lemis.com/email.html. > > 5. Make sure your time and time zone are set correctly. This may > seem a little silly, since your message still gets there, but > many of the people you are trying to reach get several hundred > messages a day. They frequently sort the incoming messages by > subject and by date, and if your message doesn't come before the > first answer, they may assume they missed it and not bother to > look. > > 6. Don't include unrelated questions in the same message. Firstly, > a long message tends to scare people off, and secondly, it's > more difficult to get all the people who can answer all the > questions to read the message. > > 7. Specify as much information as possible. This is a difficult > area, and we need to expand on what information you need to > submit, but here's a start: > > If you get error messages, don't say ``I get error > messages'', say (for example) ``I get the error message 'No > route to host'''. > > If your system panics, don't say ``My system panicked'', say > (for example) ``my system panicked with the message 'free > vnode isn't'''. > > If you have difficulty installing FreeBSD, please tell us > what hardware you have. In particular, it's important to > know the IRQs and I/O addresses of the boards installed in > your machine. > > If you have difficulty getting PPP to run, describe the > configuration. Which version of PPP do you use? What kind of > authentication do you have? Do you have a static or dynamic > IP address? What kind of messages do you get in the log file? > > 8. If you don't get an answer immediately, or if you don't even see > your own message appear on the list immediately, don't resend > the message. Wait at least 24 hours. The FreeBSD mailer > offloads messages to a number of subordinate mailers around the > world, and sometimes it can take several hours for the mail to > get through. And once it gets through, the one person who might > know the answer will probably just have gone to bed in his part > of the world. > > 9. If you do all this, and you still don't get an answer, there > could be other reasons. For example, the problem is so > complicated that nobody knows the answer, or the person who does > know the answer was offline. If you don't get an answer after, > say, a week, it might help to re-send the message. If you don't > get an answer to your second message, though, you're probably > not going to get one from this forum. Resending the same > message again and again will only make you unpopular. > > To summarize, let's assume you know the answer to the following > question (yes, it's the same one in each case :-). You choose which of > these two questions you would be more prepared to answer: > > Message 1: > Subject: (none) > > I just can't get hits damn silly FereBSD system to workd, and Im really good at this tsuff, but I have never seen anythign sho difficult to install, it jst wont work whatever I try so why don't y9ou guys tell me what I doing wrong. > > ---------------------------------------------------------------------- > > Message 2: > Subject: Problems installing FreeBSD > > I've just got the FreeBSD 2.1.5 CD-ROM from Walnut Creek, and I'm > having a lot of difficulty installing it. I have a 66 MHz 486 with 16 > MB of memory and an Adaptec 1540A SCSI board, a 1.2GB Quantum Fireball > disk and a Toshiba 3501XA CD-ROM drive. The installation works just > fine, but when I try to reboot the system, I get the message "Missing > Operating System". > > ---------------------------------------------------------------------- > > V: How to follow up to a question > ================================= > > Often you will want to send in additional information to a question > you have already sent. The best way to do this is to reply to your > original message. This has three advantages: > > 1. You include the original message text, so people will know what > you're talking about. Don't forget to trim unnecessary text out, > though. > > 2. The text in the subject line stays the same (you did remember to > put one in, didn't you?). Many mailers will sort messages by > subject. This helps group messages together. > > 3. The message reference numbers in the header will refer to the > previous message. Some mailers, such as mutt, can thread messages, > showing the exact relationships between the messages. > > VI: How to answer a question > ============================ > > Before you answer a question to FreeBSD-questions, consider: > > 1. A lot of the points on submitting questions also apply to > answering questions. Read them. > > 2. Has somebody already answered the question? The easiest way to > check this is to sort your incoming mail by subject: then > (hopefully) you'll see the question followed by any answers, all > together. > > If somebody has already answered it, it doesn't automatically mean > that you shouldn't send another answer. But it makes sense to > read all the other answers first. > > 3. Do you have something to contribute beyond what has already been > said? In general, "Yeah, me too" answers don't help much, > although there are exceptions, like when somebody is describing a > problem he's having, and he doesn't know whether it's his fault or > whether there's something wrong with the hardware or software. If > you do send a "me too" answer, you should also include any further > relevant information. > > 4. Are you sure you understand the question? Very frequently, the > person who asks the question is confused or doesn't express > himself very well. Even with the best understanding of the system, > it's easy to send a reply which doesn't answer the question. This > doesn't help: you'll leave the person who submitted the question > more frustrated or confused than ever. If nobody else answers, and > you're not too sure either, you can always ask for more > information. > > 5. Are you sure your answer is correct? If not, wait a day or so. > If nobody else comes up with a better answer, you can still reply > and say, for example, "I don't know if this is correct, but since > nobody else has replied, why don't you try replacing your ATAPI > CD-ROM with a frog?". > > 6. Unless there's a good reason to do otherwise, reply to the sender > and to FreeBSD-questions. Many people on the FreeBSD-questions > are "lurkers": they learn by reading messages sent and replied to > by others. If you take a message which is of general interest off > the list, you're depriving these people of their information. Be > careful with group replies; lots of people send messages with > hundreds of CCs. If this is the case, be sure to trim the Cc: > lines appropriately. > > 7. Include relevant text from the original message. Trim it to the > minimum, but don't overdo it. It should still be possible for > somebody who didn't read the original message to understand what > you're talking about. > > 8. Use some technique to identify which text came from the original > message, and which text you add. I personally find that prepending > ``> '' to the original message works best. Leaving white space > after the ``> '' and leave empty lines between your text and the > original text both make the result more readable. > > 9. Put your response in the correct place (after the text to which it > replies). It's very difficult to read a thread of responses where > each reply comes before the text to which it replies. > > 10. Most mailers change the subject line on a reply by prepending a > text such as ``Re: ''. If your mailer doesn't do it > automatically, you should do it manually. > > 11. If the submitter didn't abide by format conventions (lines too > long, inappropriate subject line), please fix it. In the case of > an incorrect subject line (such as ``HELP!!??''), change the > subject line to (say) ``Re: Difficulties with sync PPP (was: > HELP!!??)''. That way other people trying to follow the thread > will have less difficulty following it. > > In such cases, it's appropriate to say what you did and why you > did it, but try not to be rude. If you find you can't answer > without being rude, don't answer. > > If you just want to reply to a message because of its bad format, > just reply to the submitter, not to the list. You can just send > him this message in reply, if you like. > > $Id: Howto-ask-questions,v 1.5 2004/09/19 02:40:48 grog Exp $ > _______________________________________________ > > Thanks to Josh Paetzel for updating this document to describe mailman. > > ------------------------------ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > End of freebsd-questions Digest, Vol 81, Issue 20 > ************************************************* >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6609b1bd041126230372926d63>