Re: [vox-tech] Recovering data
I love mc. It is an editor, viewer, directory browser. rsyncer, and many more things. You can even look inside tar and rpm files with it. For some reason, it's always been popular on Europe, but not so much here. On Tue, 2003-03-18 at 23:35, Charles Polisher wrote: > Have you checked if ls is correctly reporting the file size? > Maybe du / df or some such would help confirm the fire is > actually small. > > Find midnite commander, it has a Linux un-rm feature that > rocks. It might already be installed as mc, but you can also > find it at http://www.gnome.org/mc/ > > > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Burning CD's in Linux
In order to do the cd burning, you need to compile the kernel w/ certain options, such as scsi emulation, so the cd writer looks like a scsi device. You also need to use mkisofs to create the image. It is not point and click, like nero. You need to read carefully, and set the correct options. I don't think there is a shortcut to this. On Tue, 2003-03-04 at 16:46, Robert G. Scofield wrote: > I'm trying to get my CDRW to work under Linux. I'm following some directions > from the CD Write How To, and from another website. I'm at the point where I > am supposed to type "cdrecord -scanbus." I get this error message when I do: > > "cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI > driver. > cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are > root." > > I do not have a /dev/pg, whatever that is. Does anyone know what this error > message means? > > Also, isn't there an easier program one can use to burn CD's with? > > Thank you. > > Bob > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] rdate servers and apt-get for redhat
Uh oh. I didn't know it was anything but some government service. Do you know any ntp servers which are less restrictive? I don't want to have bad dreams about stratum 1 servers. They sound a little scary. On Sunday 15 December 2002 17:57, Rick Moen wrote: > Quoting Eric Nelson ([EMAIL PROTECTED]): > > Here is what I use in crontab: > > 59 * * * * /usr/sbin/ntpdate ntp-dec.usno.navy.mil >> /dev/null > > The hostname is a CNAME for usno.pa-x.dec.com, operated by Compaq > in Palo Alto for the U.S. Naval Observatory. It's a stratum 1 > server. Posted access policy is "Access Policy: open access for > stratum 2 servers, Compaq, others by arrangement." > (http://tycho.usno.navy.mil/ntp.html) > > USNO states at the top of the listing at the top of the page: "All > of the following stratum 1 NTP servers are open to stratum 2 > servers within the same time zone and to others by arrangement." > > http://www.eecis.udel.edu/~mills/ntp/servers.html states: "Please > respect the access policy as stated by the responsible person. It > is very important that potential clients avoid use of servers not > listed as open access, unless approved first by the responsible > person. This especially includes indiscriminate use of servers not > listed in the list, since this can be disruptive. The responsible > person should always be notified upon establishment of regular > operations with servers listed as open access. Servers listed as > closed access should NOT be used without prior permission, since > this may disrupt ongoing activities in which these servers are > involved." > > That page clarifies about what is meant by a stratum 2 server: > "The secondary server provides synchronization to a sizable > population of other servers and clients on the order of 100 or > more." (There's more.) > > It is not unknown for members of the general public who sync to > statum 1 servers without prior arrangement to find their entire IP > blocks blocked by the statum 1 server operator. > > On the bright side, doing the sort of periodic ntpdate you discuss > is less likely to risk the wrath of a statum 1 server than would > running ntpd against it -- as I've seen people urge on other > mailing lists that I guess should go nameless. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] rdate servers and apt-get for redhat
Here is what I use in crontab: 59 * * * * /usr/sbin/ntpdate ntp-dec.usno.navy.mil >> /dev/null On Sunday 15 December 2002 10:54, Henry House wrote: > On Sun, Dec 15, 2002 at 10:49:57AM -0800, Rod Roark wrote: > > On Sunday 15 December 2002 10:09 am, Henry House wrote: > > > One more suggestion: try ntpdate, a daemonless version of NTP. > > > It will not abruptly change the system time like rdate if the > > > local clock is off by a large amount... > > > > Don't you mean a small amount? From > > http://www.eecis.udel.edu/~ntp/ntp_spool/html/ntpdate.html: > > > > Time adjustments are made by ntpdate in one of two ways. > > If ntpdate determines the clock is in error more than > > 0.5 second it will simply step the time by calling the > > system settimeofday() routine. If the error is less than > > 0.5 seconds, it will slew the time by calling the system > > adjtime() routine. The latter technique is less > > disruptive and more accurate when the error is small, > > and works quite well when ntpdate is run by cron every > > hour or two. > > Er, yes. Thanks. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] How to make an OEM style "system recovery disk"
On Monday 28 October 2002 21:10, Ryan Castellucci wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I'm looking to build a bootable CD to give to a friend along with a > computer that when booted will offer to overwrite the hard drive > from a compressed disk image. I looked on freshmeat, but didn't see > anything well suited to this. The box in question will have windows > on it (They want windows, I don't feel like arguing). Anyone know > of a project that can do this? > > What about linux boot CDs that can easily be customized to run a > shell script at boot time? Maybe I misunderstand what you are looking for, but Timo's Rescue CD (rescuecd.sourceforge.net) provides a bootable Debian System that only fills part of the CD, is easily customizable, and contains all (most?) of the tools you will need. I am sure you could add a shell script to format the disk, and put a windows image on it. I'm not sure about the bootable part, but you could just use grub. If you go NTFS, it may be more challenging. It's an excellent project. :) > > All the stuff i saw on freshmeat looked like it just restored files > from a backup. > > - -- > PGP/GPG Fingerprint: 3B30 C6BE B1C6 9526 7A90 34E7 11DF 44F3 7217 > 7BC7 On pgp.mit.edu, import with `gpg --keyserver pgp.mit.edu > --recv-key 72177BC7` Also available at > http://www.cal.net/~ryan/ryan_at_mother_dot_com.asc -BEGIN PGP > SIGNATURE- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE9vhgyEd9E83IXe8cRAgcwAJ41pcoRT1sWwI3r/ykXp1WA17fw+gCbBUA5 > nYDKJSFUMJ5mQksGjhjS/xI= > =CPP1 > -END PGP SIGNATURE- > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] how *not* to load the serial module at boot time?
Also, take a look at /etc/modules.conf. This is where the command line parameters to the modules come from. Also, if you use modprobe instead of rmmod, insmod, it will use the dependency information in /lib/modules - it is much more intelligent than insmod. On Friday 20 September 2002 23:38, Mark K. Kim wrote: > On Fri, 20 Sep 2002, Matt Holland wrote: > > > I think /dev/ttyS0 defaults to IRQ4 + IO 0x03f8 with no > > > configuration whatsoever. AFAIK, there is no driver to load or > > > unload; you just tell the kernel what the settings are. > > > > This would seem to suggest otherwise: > > > > $ /sbin/lsmod | grep serial > > lirc_serial 8928 1 (autoclean) > > serial 59392 0 (autoclean) > > > > Also, if there's no driver, what's this? > > > > /lib/modules/2.4.18-5-lirc-0/kernel/drivers/char/serial.o > > Let's see... > >$vi /usr/src/linux/drivers/char/serial.c > > It looks like it's got code to forward what's written to /dev/ttySN > to the proper port I/O, and it's got stuff to do serial terminal. > I didn't realize you can make a module out of this. Oh well. > ::shrug:: > > Still, I'd think it wouldn't interfere with anything, but the code > is more complicated than I'd thought it'd be. It's probably > complicated because of all the serial terminal stuff. > > But I'm still not sure if the driver getting loaded first is the > problem because you said: > >Nothing works until >I do: > ># setserial /dev/ttyS0 uart none ># rmmod lirc_serial ># insmod lirc_serial > > but if the driver itself was interfering, you'd have to unload it, > like: > ># rmmod serial ># rmmod lirc_serial ># insmod lirc_serial > > but obviously you don't, so it's the default configuration of the > serial driver that's problem not the driver itself; and the > configuration should be settable by creating /etc/rc.d/rc.serial. > But if you can't, try creating /etc/rc.serial instead (check your > /etc/rc.d/rc.sysinit -- whichever file it looks for and executes is > the one you should create). Put some debugging output so you can at > least check that the file gets executed. BTW, make sure you chmod > the created file with executable permission after you create it. > > Later! > > -Mark ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] how *not* to load the serial module at boot time?
I guess if you're looking for something elegant, don't read on. But if you don't want the kernel to load serial.o, just: . compile it as a module, which you did . move it out of /lib/modules/2.4.x.-y then, the kernel can't find it. Also, by looking at error messages, maybe you can see what loads it. I imagine there is a kernel command line parameter to keep it unloaded also. On Thursday 19 September 2002 23:32, Matt Holland wrote: > Hey all, > > Does anyone out there know how RedHat (7.3, if it matters) decides > when (and if) to load the serial port driver, and if so, how to > stop it from loading? I ask because I've just started playing with > lirc (Linux Infrared Remote Control -- very nifty) with my > newly-built home-brew serial IR receiver, but the lirc_serial > driver can't grab the port if the serial driver has already been > loaded. I compiled the serial driver as a module when I built my > kernel, but I still get: > > Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT > SHARE_IRQ SER > IAL_PCI ISAPNP enabled > ttyS00 at 0x03f8 (irq = 4) is a 16550A > ttyS01 at 0x02f8 (irq = 3) is a 16550A > ... > lirc_serial: port 03f8 already in use, proceeding anyway > lirc_serial: compile the serial port driver as module and > lirc_serial: make sure this module is loaded first > lirc_serial: auto-detected active low receiver > > in my dmesg output. The problem is that the serial driver is > getting loaded before anything listed in /etc/modules.conf. > Nothing works until I do: > > # setserial /dev/ttyS0 uart none > # rmmod lirc_serial > # insmod lirc_serial > > It's possible that I had to restart lircd after that... I don't > remember for certain whether I did or not. In any case, it seems > clear that I could just put those commands (followed by the daemon > restart, if necessary) at the end of rc.local, and learn to ignore > the error messages during boot (after all, I have no problem > ignoring X when it complains about missing fonts ;). However, it > seems like just stopping the serial module from loading in the > first place would be the more elegant solution. > > For those eager Debian users out there... the lirc documentation > mentioned modifying /etc/serial.conf on Debian... no such file in a > RedHat installation. Also, I grep'ed the init scripts for 'serial' > and didn't find anything enlightening. > > Incidentally, for those of you who don't always sit *at* your > computer when listening to mp3's, watching DVD's, whatever, I > highly recommend looking into lirc (www.lirc.org). I'm a firm > believer that a little soldering now and then is good for the soul > :) I can't say enough about the coolness of this project! > > Thanks, > Matt > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Modem Questions...
On Thursday 19 September 2002 18:53, Richard Crawford wrote: > And I'm afraid they don't really involve Linux. > > My wife and I have taken new jobs! Whee! > > The company -- Citicorp, of all things -- will be giving us laptop > computers to take on the road with us, with modems. Said computers > will not be including network cards, unfortunately, though I don't > mind shelling out the money for those myself. > > But the modems raise a couple of issues. > > First, is there such a thing as a modem splitter -- such that my > wife and I can both be plugged in to the same phone line in a hotel > room or something like that and be doing separate things? The only way that could be feasable is if you are in different bands, like you are using 56K and she is using 9600, or something. The modem is using signals from a certain frequency band, and 2 similar modems will just wreak havoc w/ each other. You should probably investigate one connection (one modem, one line), and maybe someone can tell you how to have both of you use the same connection, like network the pc's, and use one connection. > > Second, is there any such thing as a "modem emulator"? Let me > explain. The project involves logging in via a phone line to > Citicorp's central servers. The VPN software that's involved wants > modem lines, and won't accept network lines... so my network at > home is useless. Is there some piece of software or hardware that > I can hook up to our laptops to make the central servers *think* > we're coming through a modem when we're really using a DSL > connection? > > All of this stuff involves Windows XP (shudder) on Dell Inspiron > laptops. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Modem Questions...
On Thursday 19 September 2002 19:12, Eric Nelson wrote: > On Thursday 19 September 2002 18:53, Richard Crawford wrote: > > And I'm afraid they don't really involve Linux. > > > > My wife and I have taken new jobs! Whee! > > > > The company -- Citicorp, of all things -- will be giving us > > laptop computers to take on the road with us, with modems. Said > > computers will not be including network cards, unfortunately, > > though I don't mind shelling out the money for those myself. > > > > But the modems raise a couple of issues. > > > > First, is there such a thing as a modem splitter -- such that my > > wife and I can both be plugged in to the same phone line in a > > hotel room or something like that and be doing separate things? > > The only way that could be feasable is if you are in different > bands, like you are using 56K and she is using 9600, or something. > The modem is using signals from a certain frequency band, and 2 > similar modems will just wreak havoc w/ each other. On further thought, a phone connection is point to point, so just further reason that 2 modems wont work. You would need something pretty sophisticated at the other end, and you would both have to be talking to the same place! :-) But, it's cheaper to use one connection anyway. > > You should probably investigate one connection (one modem, one > line), and maybe someone can tell you how to have both of you use > the same connection, like network the pc's, and use one connection. > > > Second, is there any such thing as a "modem emulator"? Let me > > explain. The project involves logging in via a phone line to > > Citicorp's central servers. The VPN software that's involved > > wants modem lines, and won't accept network lines... so my > > network at home is useless. Is there some piece of software or > > hardware that I can hook up to our laptops to make the central > > servers *think* we're coming through a modem when we're really > > using a DSL connection? > > > > All of this stuff involves Windows XP (shudder) on Dell Inspiron > > laptops. > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Re: random number in C
Not an expert on this, but I think the kernel adds entropy, from keypresses and other things considered 'random', so results are not entirely deterministic. You can look at the code in the random driver, random.c in /usr/src/linux/drivers/char for some background. After all, random is used to generate keys used in security, and those hackers are pretty smart, and repeatable random sequences would allow certain attacks. On Tuesday 02 April 2002 06:26 pm, you wrote: > > Date: Tue, 2 Apr 2002 14:47:20 -0800 > > [CODE SNIPPED] > > So this is when the program is seeded to /dev/random: > >p@satan% ./ising2-jfunc 4.0 > >T: 4.0e+00 beta: 2.500e-01 trials: 1000 N: 10 M: 10 seed: > > 3497451914 Average Energy: -1.273893 > >Average magnetization: 0.425220 > >Average |magnetization|: 0.531100 > >Average magnetic susceptibility: 34.746600 > > And this is when the code is seeded to 1: > >T: 4.0e+00 beta: 2.500e-01 trials: 1000 N: 10 M: 10 seed: > > 3497451914 Average Energy: -1.326747 > >Average magnetization: 0.495320 > >Average |magnetization|: 0.495320 > >Average magnetic susceptibility: 28.645040 > > And you've established that if you run it repeatedly you keep getting the same thing: > >T: 4.0e+00 beta: 2.500e-01 trials: 1000 N: 10 M: 10 seed: > > 3497451914 Average Energy: -1.326747 > >Average magnetization: 0.495320 > >Average |magnetization|: 0.495320 > >Average magnetic susceptibility: 28.645040 > > BUT four hours earlier: > > Date: Tue, 2 Apr 2002 10:05:34 -0800 > > This is when you seed it to /dev/random: > > T: 4.0e+00 beta: 2.500e-01 trials: 100 > > N: 10 M: 10 seed: 208006379 > > Average Energy: -1.057143 > > Average magnetization: 0.002008 > > Average |magnetization|: 0.251765 > > Average magnetic susceptibility: 8.948655 > > And this is when you seed it to 1: > > T: 4.0e+00 beta: 2.500e-01 trials: 100 > > N: 10 M: 10 seed: 208006379 > > Average Energy: -1.050182 > > Average magnetization: 0.030723 > > Average |magnetization|: 0.246092 > > Average magnetic susceptibility: 8.692724 > > Why did 4 hours of time change the results when you seed it to 1 ??? > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] need to debug boot crash
Charles Polisher wrote: > On Sun, Mar 24, 2002 at 09:49:56PM -0800, eric nelson wrote: > > ME wrote: > > > > > On Sun, 24 Mar 2002, eric nelson wrote: > > > > Its not panicking. I'm doing an nfs mount of the os, and something went > > > > wrong init the initscripts. The shift-pageup is a really good idea, I didn't > > > > know about that. The problem is that so many errors spewed out that I > > > > coulldn't get far enough back. > > > > > > You doing network booting of a client with an NFS root from a server? > > > > > > We have about 80 diskless workstations doing net-booting here from the > > > same "ro" NFS export. What specific errors are being reported? > > > > First, something about mount program didn't pass correct address, then > > RPC: sendmsg returned error 101 > > nfs: RPC call returned error 101 > > over and over > > > > There are so many errors, that I can't scroll back. I'll need to redo the kernel > > w/ the option Peter Jay Salzman mentioned. > > > > I'm not doing the kind of mount straight from the bios, but I want to learn how to > > do that one, later. I have a boot floppy which loads a kernel, then gets an > > address from dhcp server, then mounts on nfs. I'm sure the problem is in init > > scripts, or fstab or something. > > > > It's good to know someone is doing this, it's a great approach. > > If you can snoop the wire (from another box), the trace > might diagnose the problem. Something like: > > # tcpdump -i eth0 -nvvvxl -s100 host foo > > where foo is the troubled host. Etherreal or some such utility might > be easier to interpret. Anyway, if you can watch the conversation > taking place between the host and client, the problem sometimes > jumps right out - eg., if it's an authentication error. > I'll be able to set this up at work, once I get through some tasks of a more mundane nature. I'm sure that this approach will help understand the whole process. Appreciate the idea. ;~) > > HTH, > > Chuck Polisher > -- > The best way to get information on Usenet is not by asking a question, but > by posting inaccurate information. > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] need to debug boot crash
ME wrote: > Sorry for the delay, I am going through my mail now... > > On Mon, 25 Mar 2002, eric nelson wrote: > > Thanks for the major breakdown of the project. It's going to take me > > a little while to read these docs., and go through the whole process, > > but we want to use this for two things: > > > > 1) testing an os we are putting together. we can work on the os on a > > host machine, then boot it on the target to test, so the target is a > > simple machine and the host has full development enviroment. > > This is a good idea. I'll also suggest copying the tree to a backup before > exporting it in testing as rw. Why? If you test station boots, but does > not shutdown, files will be left behind in /var/lock and /tmp that may > cause problems with the next booting station - especially if the > production system's root export is a ro export. > > Also, avoid using tar to creat backups of the exporte system root. It has > a history of bugs. I used it for the longest time, and was a die-hard user > of it, but finally gave up on it for archived system roots like netbooting > system roots. > > Instead of tar, try " cp -aR " the "a" is for archive (permissions and > special flags) and the capitail "R" does recursive like "r" but deals with > device special files as you would most likely want (no tries to read the > contents of the device - yeeech) > > Yes it uses up more space than a tarball, and is not compressed, *but* it > seems to work with all of the files, and is short/easy to remember. (Dont > use " cp -ar " as it will probably try to read the contents of devices > like /dev/sda and make copies of the contents instead of the c/b/f special > devices.) > > (Had problems with tar and some dev special files, some permissions not > being copied as they should and certain major numbers that were "too > high" not being copied and.. and... and... Yes, yes, i know about all the > special flags for tar, and had a command line tar command that was 3 lines > long at one time to almost get things to work as well as " cp -aR ".) > > > 2) we are developing a linux based product, which will net boot as an > > option, so we need to understand the whole process very well. > > Though it is not *exactly* the same thing, I reverse engineered Apple's > Propritary NetBoot-ing protocol and published papers on how it works. You > may be able to grab some useful information on the pages I created for > this "how-to" as it is very close the the "standard" *NIX diskless client > system (using modified DHCP with vendor extentions instead of the standard > method and AFP/IP instead of NFS.) > > Others out there have written much better pages on Linux and diskless > client booting. > > http://mike.passwall.com/macnc/ > > > I have read that people use this technique to boot multiple diskless > > workstations. Is that what you use it for? > > Yep, about 80 or more diskless client workstations (no local HD, no local > floppy disk, no moving parts except the fan on the CPU and power > supply.) The root is mounted as a ro NFS root, and is exported from the > server as such (for better security.) Having diskless client do their work > from a root filesystem that is readonly is a bit tricky, but possible. (We > have use the 2.0.x and 2.2.x kernels, but are now using the 2.4.x kernels > for this.) > > Have used it home on a private network with firewall rules and did some > with roots being (rw) but dont suggest this on more open networks with > NFS. Also, no two machine should share the same system roots (when /var, > /tmp and others) are part of that root when the roots are mounted as (rw). > > Also, based on som complaints from another user doing netbooting, there > may be problems with having the server use reiserfs or ext3 with nfs > exports as root for the clients. (Not experienced this as I use ext2 for > this still. Also, no references for this other than, "some guy said this > was a problem.") > > Done many kind sof netbooting including use of a BSD based system on an > Sun 3/60 with XTerm support for remot processing and local display. > > Wa back when, I wanted to do netbooting of windows too, but have heard > netbooted windows stability rating makes normal desktop windows look like > a happy thing as interruptions to networking cause delays for file access > of the OS that are unbearable to the OS. > > I am far from a netbooting guru, but I may be able to answer some of the > simple questions if you should wish to ask. > Well, my queue is filling up w/ all this information, it's going to take some t
Re: [vox-tech] need to debug boot crash
ME wrote: > On Sun, 24 Mar 2002, eric nelson wrote: > > First, something about mount program didn't pass correct address, then > > RPC: sendmsg returned error 101 > > nfs: RPC call returned error 101 > > over and over > > > > There are so many errors, that I can't scroll back. I'll need to redo > > the kernel w/ the option Peter Jay Salzman mentioned. > > > > I'm not doing the kind of mount straight from the bios, but I want to > > learn how to do that one, later. I have a boot floppy which loads a > > kernel, then gets an address from dhcp server, then mounts on nfs. > > I'm sure the problem is in init scripts, or fstab or something. > > > > It's good to know someone is doing this, it's a great approach. > > First, check out the netboot howto/docs. > > Second, make sure the server is exporting the filesystems in question on a > non-netbooting box/session with normal > # mount -t nfs host.name:/export/path /local/mount/point > > Why? You can make sure the server's /etc/hosts.[allow||deny] is set up in > such a way to allow portmap and nfs stuff from a client's IP address to > work. > > If that works, then try to test the next step. Start up a netbootable > kernel with loadlin or lilo (special entry on a disk-booting system) to > tell it to netboot instead of use the local disk. Certainly, it will still > grab a kernel from the local disk but shyould do the rest over the network > like it was diskless. > > Checkout /usr/src/linux/Documentation/nfsroot.txt > > You should be able to add an entry to lilo.conf (or at the lilo > prompt) like: > > (Use IP addresses to eliminate DNS as yet another piece to work out.) > > LILO: > Boot: mykernel root=/dev/nfs nfsroot=IP.Addr.Of.Srvr:/path/to/root/export > ip=::* > > *= See the above mentioned linux kernel doc for this line. > > It is a good idea to test with a hand-enetered IP address for client and > server as well as all other info to eliminate bootp/dhcp from the list of > possible problems. > > And you could, of course, have added those items into a separate > lilo.conf entry to save re-entry of those keystrokes every single time. > > If that works, then remove the client ip and let everything else be > determined except for server ip, > > next drop server IP and let it all be dynamic, and then try to shift to > let the special bootp/dhcp response include the nfsroot. > > (At this point, if all else works, then you would only be passing the: > root=/dev/nfs > ) > > Next, if you want it to be true network booting (bootp/dhcp then tftp of > kernel, and finally boting kernel get nfsroot and goes) then you will > likely need some sort of modification to your final compiled kernel that > would be dl via tftp (a boot strapper of sorts.) I use the netboot stuff > with programmed EPROMS dropped into the ethernet cards. ( > http://sourceforge.net/projects/netboot ) Thanks for the major breakdown of the project. It's going to take me a little while to read these docs., and go through the whole process, but we want to use this for two things: 1) testing an os we are putting together. we can work on the os on a host machine, then boot it on the target to test, so the target is a simple machine and the host has full development enviroment. 2) we are developing a linux based product, which will net boot as an option, so we need to understand the whole process very well. I have read that people use this technique to boot multiple diskless workstations. Is that what you use it for? > > > I have found testing each part, one-at-a-time save troubleshooting and > leads to a steady advance to solutions. > > Of course, there is a great sense of accomplishment when you take a big > project with lots of pieces, throw it all together and note that it all > works the first time too. ]:> > > -ME > > -BEGIN GEEK CODE BLOCK- > Version: 3.12 > GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-) C++$() U$(+$) P+$>+++ > L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP > t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++> h(++)>+ r*>? z? > --END GEEK CODE BLOCK-- > decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] need to debug boot crash
ME wrote: > On Sun, 24 Mar 2002, eric nelson wrote: > > Its not panicking. I'm doing an nfs mount of the os, and something went > > wrong init the initscripts. The shift-pageup is a really good idea, I didn't > > know about that. The problem is that so many errors spewed out that I > > coulldn't get far enough back. > > You doing network booting of a client with an NFS root from a server? > > We have about 80 diskless workstations doing net-booting here from the > same "ro" NFS export. What specific errors are being reported? First, something about mount program didn't pass correct address, then RPC: sendmsg returned error 101 nfs: RPC call returned error 101 over and over There are so many errors, that I can't scroll back. I'll need to redo the kernel w/ the option Peter Jay Salzman mentioned. I'm not doing the kind of mount straight from the bios, but I want to learn how to do that one, later. I have a boot floppy which loads a kernel, then gets an address from dhcp server, then mounts on nfs. I'm sure the problem is in init scripts, or fstab or something. It's good to know someone is doing this, it's a great approach. > > > -ME > > -BEGIN GEEK CODE BLOCK- > Version: 3.12 > GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-) C++$() U$(+$) P+$>+++ > L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP > t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++> h(++)>+ r*>? z? > --END GEEK CODE BLOCK-- > decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] need to debug boot crash
Peter Jay Salzman wrote: > remember that not every "error" is a real error. for instance, a micro > channel driver can search your system buses for a micro channel device > and not find one. it'll print something vaguely error-ish to screen. > > you didn't say if your kernel is panicking or not. > > assumming your kernel isn't panicked, you can do shift-pageup to scroll > up on the console. > Its not panicking. I'm doing an nfs mount of the os, and something went wrong init the initscripts. The shift-pageup is a really good idea, I didn't know about that. The problem is that so many errors spewed out that I coulldn't get far enough back. > > you can also look in /var/log/messages or dmesg | less. > > note that most module related errors upon boot don't make it into the > error log. some kernel developers are working on that. there's a good > reason for it (but i can't recall). > > if your kernel is panicking, your options are a bit more limited. the > easiest way (assumming you're not henry house who knows how to do the > serial console thing) is to take a picture of your monitor with a > digital camera. however, most kernel panics usually don't print tons of > error messages for this exact reason. if the problem is a root > filesystem that can't be found or a bona-fide "oops", you'll see 2 or 3 > lines of error at most. > > note, a very, very, very, very worthwhile thing is to extend the buffer > that your kernel allocates for the scrollback. it's in the linux FAQ. > basically, you need to recompile your kernel and define something like: > > #define VIDEOCARD_CAN_DO_32_MEGS I will do this. The picture thing is a good idea. I was finally able to get a handle on things by putting a call to bash in the first init script. Now I can look at the initialization, by putting the call to bash in different places, and finding where it goes wrong. Thanks. ;~) > > > (this isn't it -- you'll have to look up the exact define). i do it > each time i compile a new kernel. it gives you ALOT more scroll back > buffer space. > > pete > > begin eric nelson <[EMAIL PROTECTED]> > > I have an error occuring during boot. However, the pertinant > > information flys by, and I just get a long list of error messages on the > > screen. Is there a way to record the messages during the late part of > > kernel boot, or to make it slow down, or require a prompt, or something? > > > > ___ > > vox-tech mailing list > > [EMAIL PROTECTED] > > http://lists.lugod.org/mailman/listinfo/vox-tech > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] need to debug boot crash
I have an error occuring during boot. However, the pertinant information flys by, and I just get a long list of error messages on the screen. Is there a way to record the messages during the late part of kernel boot, or to make it slow down, or require a prompt, or something? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] stopping serial console
On Tuesday 12 March 2002 08:37 pm, you wrote: > On Tue, Mar 12, 2002 at 05:57:23PM -0800, eric nelson wrote: > > I built a kernel today, and checked 'support console on serial port'. > > Then, I wanted to set up minicom between the pc and another box, and I > > got a login (duh, that's what I set up). But, I don't really want a > > login, I just want to use the port, and don't want to recompile the > > kernel. > > > > Anyway to stop this behavior? > > You should be able to stop the kernel logs on boot up by specifing a > console=tty1 via lilo as already suggested. > > To stop the login prompt (if there is one), you should comment out the > appropriate getty on that tty port from /etc/inittab. I'll try that tomorrow, the machines are at work. Does anyone know how the getty determines something is there? Is it just receiving any character? Because I had hardware flow turned off, and a breakout box on the serial line, and all the control lines, RTS, CD, DTR, etc. seemed to be doing nothing. So it must start the login when it gets a character, or newline, or something. But, it's not that critical. Anyway, I better get the getty off. heh-heh ;~) Does all this mean that getty won't work if the console on serial port is not compiled into the kernel? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] stopping serial console
I built a kernel today, and checked 'support console on serial port'. Then, I wanted to set up minicom between the pc and another box, and I got a login (duh, that's what I set up). But, I don't really want a login, I just want to use the port, and don't want to recompile the kernel. Anyway to stop this behavior? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] trouble running recursive grep
Thanks for the good ideas, guys. I'll try them all, and learn something. ;~) On Sunday 10 March 2002 12:23 pm, you wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I'd try somthing like. > > grep -r pci_dev . | grep .h > > this greps the results of the first grep for lines containing .h and since > the filename is included, should be somewhat helpful. > > On Sunday, March 10 2002 10:56 am, eric nelson wrote: > > Why doesn't this work: > > > > (as root) > > cd /usr/src/linux/include > > grep -r pci_dev *.h > > > > > > I get the error > > grep: *.h No such file or directory > > > > In general, what is the best way to search system include files for > > specific strings? > > ___ > > vox-tech mailing list > > [EMAIL PROTECTED] > > http://lists.lugod.org/mailman/listinfo/vox-tech > > - -- > No Microsoft products were used in any way for the creation of this > message. PGP Public key at > http://mother.com/~ryan/ryan_at_mother_dot_com.asc It is also on the > servers: Key ID 0x72177BC7 > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE8i8DCEd9E83IXe8cRAkCEAKCsjjnzObOKCRlsaSluNzIDhSskdgCdEXbC > rodKjFf3kuD65EW1gYYLjRM= > =Rn21 > -END PGP SIGNATURE- > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] trouble running recursive grep
Why doesn't this work: (as root) cd /usr/src/linux/include grep -r pci_dev *.h I get the error grep: *.h No such file or directory In general, what is the best way to search system include files for specific strings? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] PC power supplies
I think it's just the nature of switching supplies that they need a load. when I want to make one work, sometimes I add extra load, like an extra CD rom or something. On Saturday 23 February 2002 09:21 pm, you wrote: > I don't it would be applicable to all power supplies. > > As I do with all incomplete questions... Why do you ask? > > -sp > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > Subject: Re: [vox-tech] PC power supplies > > I once thought I killed the power supply on a system, but it recovered > sometime later. I still don't know what happened exactly, but I think > it > was some sort of a protection circuit. Couldn't tell you if it exists > on > all power supplies. > > -Mark > > On Sat, 23 Feb 2002, Peter Jay Salzman wrote: > > do pc power supplies have an automatic kill circuit to not let the > > power > > > supply on when it's not loaded? > > > > if so, is this a feature of all power supplies or some power supplies? > > > > pete > > -- > Mark K. Kim > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] time jumps 8 hours
On Friday 15 February 2002 11:07 pm, you wrote: > On Fri, 15 Feb 2002, eric nelson wrote: > > Thanks. I did find today that there is nothing in the cron. I'll check > > inetd. Do you recommend setting the bios clock to local time? I guess I > > should use a high debug level of logging, so there's lots of data. What > > other files besides /var/log/messages? > > I'll be away from work 3 days, might get back to you if I still can't > > figure it out. make files don't work too well with this situation :~( > > Not all jobs will always show up in cron as by root or local users. I have > found /etc/cron.*/* > anacrontab > cron.d > cron.daily > cron.monthly > cron.weekly > crontab > cvs-cron.conf > > See if you have these, and review them too. > > If after checking /var/spool/cron, /etc/cron*, /etc/at* and verifying that > you have no other at/cron packages (cron, anacron, etc) installed, and no > daemonized ntp clients, and reviewing log files to see when the > date/time-stamps change (the change in time should tell you *when* the > problem is occuring) and none of these helps you to find the offending > app, perhaps it is being called into being by another system update > tool.(?) > > This makes it more difficult. The time that the event occurs should help > you to narrow the group of apps that could call it. Disable half and see > if it goes away, if it does, then examine the half you disabled and > re-enable half. If it comes back, then suspect the 25% you have > left. Continue in this binary search and divide till you find it. > > Also? Maybe do a man -k date and man -k clock and man -k time looking for > applications that can change the clock. Then mv these to different names > (like $0.oirg) and then write a bash wrapper that records PPID and > date/time into a file as well as a ps -auxw | grep $PPID to see the name > of the process and dump this info into a file, and then pass on the args > $@ to the real application $0.orig) > > This seems time consuming, but is one of the many many approaches you > have available at your disaposal to solve this problem. Others here may > have other alternatives. > > If you have found all clock/date modifying binaries on your system, and > wrapped them to still find nothing, suspect multiple personality disorder > or someone pulling a prank on you. (Hope my general joke is not > offensive.) > > When you all were talking about Linux newbies: > I still consider myself a *NIX newbie. ]:> > > Yatta! > -ME Aren't we'all newbies!!?? Linux is like life, you only know a little bit about this and that. Anyway, I appreciate the detailed answer, wish I could remotly log in to the pc to do this stuff now, but, oh well. ;~P > > -BEGIN GEEK CODE BLOCK- > Version: 3.12 > GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-) C++$() U$(+$) P+$>+++ > L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP > t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++> h(++)>+ r*>? z? > --END GEEK CODE BLOCK-- > decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html > > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] time jumps 8 hours
On Thursday 14 February 2002 09:59 pm, you wrote: > On Thu, 14 Feb 2002, eric nelson wrote: > > It is supicious about the 8 hour offset. I had ntp running, but turned > > it off about a week ago when I saw this problem. I don't think there are > > any other cron jobs, but I'll check tomorrow. > > Things to check out: > > tzconfig > > exaine your log files. Most are date/time stamped. If your clock changes, > you should be able to see around the time this took place according to > the logs files. > > Log files may also let you know what application/service may have been > changing your clock. > > inspect your clock (in BIOS) to see if it is in GMT. > > See if you have somehow installed more than one ntp client (one that say > only starts up via cron job every 24 hours vs one that is > daemonized/inetd(on demand). > > -ME Thanks. I did find today that there is nothing in the cron. I'll check inetd. Do you recommend setting the bios clock to local time? I guess I should use a high debug level of logging, so there's lots of data. What other files besides /var/log/messages? I'll be away from work 3 days, might get back to you if I still can't figure it out. make files don't work too well with this situation :~( > > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] time jumps 8 hours
On Thursday 14 February 2002 07:46 pm, you wrote: > On Thu, 14 Feb 2002, eric nelson wrote: > > My Red Hat 6.2 system at work has the clock jump back about 8 hours, then > > forward again. I don't really know when it happens. Perhaps I need a > > way to, say record the time every 5 minutes, and try to figure it out. > > Any ideas? What could cause this? > > Our offset from GMT is 8. Check your ntp client stuff and config for your > system and see what at/cron jobs you have that are executed from your > system. It is supicious about the 8 hour offset. I had ntp running, but turned it off about a week ago when I saw this problem. I don't think there are any other cron jobs, but I'll check tomorrow. > > > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] time jumps 8 hours
My Red Hat 6.2 system at work has the clock jump back about 8 hours, then forward again. I don't really know when it happens. Perhaps I need a way to, say record the time every 5 minutes, and try to figure it out. Any ideas? What could cause this? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Xwindows problem
On Sunday 20 January 2002 08:06 pm, you wrote: > On Sun, Jan 20, 2002 at 07:46:54PM -0800, Eric Nelson wrote: > > On Sunday 20 January 2002 04:01 pm, you wrote: > > > Keywords: X, XFree86, XF86Config, XConfigurator, ct69000, embedded > > > system > > > > Thanks for the reply. > > > > Since the last posting, I upgraded to 4.1.0. Now, X won't even come up. > > I have the correct values for my terminal. It looks like the system > > thinks there is only 256K on the card, and it can't find a mode, even not > > enough ram for 320x200, so it fails. > > > > It could be a bios problem, this is a custom system, built for a specific > > project, and an early version of the bios. I started to think that I > > could by a new cpu board and have something that works for all the hours > > I'm putting in. So I don't want to waste peoples time, until I have a > > problem that is real, at least. :~). > > Okay, but you might as well try explicitly declaring the amount of video > RAM in the configuration file. Example from my /etx/X11/XF86Config-4: > > Section "Device" > Identifier "Generic Video Card" > Driver "glint" > VideoRam 8192 > EndSection I did. from XF86Config: snip- # Any number of graphics device sections may be present # Standard VGA Device: Section "Device" Identifier "Standard VGA" VendorName "Unknown" BoardName "Unknown" # The chipset line is optional in most cases. It can be used to override # the driver's chipset detection, and should not normally be specified. #Chipset"generic" # The Driver line must be present. When using run-time loadable driver # modules, this line instructs the server to load the specified driver # module. Even when not using loadable driver modules, this line # indicates which driver should interpret the information in this section. Driver "vga" # The BusID line is used to specify which of possibly multiple devices # this section is intended for. When this line isn't present, a device # section can only match up with the primary video device. For PCI # devices a line like the following could be used. This line should not # normally be included unless there is more than one video device # intalled. # BusID "PCI:0:3:0" VideoRam 2048 #Clocks 25.2 28.3 EndSection snip-- from /var/log/XFree86.0.log snip- [16] 0 0x03b0 - 0x03bb (0xc) IS[B] [17] 0 0x03c0 - 0x03df (0x20) IS[B] (II) Setting vga for screen 0. (**) VGA(0): Depth 16, (--) framebuffer bpp 16 (==) VGA(0): RGB weight 565 (==) VGA(0): Default visual is TrueColor (==) VGA(0): Using gamma correction (1.0, 1.0, 1.0) (**) VGA(0): videoRam: 2048 kBytes (using 256 kBytes). (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor="The XFree86 Project" compiled for 4.1.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (--) VGA(0): Pixel clocks available: (--) VGA(0): pixel clocks: 28.320 28.322 28.320 28.320 (II) VGA(0): v95: Using hsync range of 30.00-95.00 kHz (II) VGA(0): v95: Using vrefresh range of 50.00-160.00 Hz (II) VGA(0): Not using default mode "640x350" (insufficient memory for mode) (II) VGA(0): Not using default mode "640x400" (insufficient memory for mode) (II) VGA(0): Not using default mode "720x400" (insufficient memory for mode) (II) VGA(0): Not using default mode "640x480" (insufficient memory for mode) (II) VGA(0): Not using default mode "640x480" (insufficient memory for mode) (II) VGA(0): Not using default mode "640x480" (insufficient memory for mode) (II) VGA(0): Not using default mode "640x480" (insufficient memory for mode) (II) VGA(0): Not using default mode "800x600" (insufficient memory for mode) (II) VGA(0): Not using default mode "800x600" (insufficient memory for mode) (II) VGA(0): Not using default mode "800x600" (insufficient memory for mode) (II) VGA(0): Not using default mode "800x600" (insufficient memory for mode) (II) VGA(0): Not using default mode "800x600" (insufficient memory for mode) (II) VGA(0): Not using default mode "1024x768" (insufficient memory for mode) (II) VGA(0): Not using default mode "1024x768" (insufficient memory for mode) (II) VGA(0): Not using default mode "1024x768" (insufficient memory for mode) (II) VGA(0): Not using default mode "1024x768" (insufficient me
Re: [vox-tech] Xwindows problem
On Sunday 20 January 2002 04:01 pm, you wrote: > Keywords: X, XFree86, XF86Config, XConfigurator, ct69000, embedded system Thanks for the reply. Since the last posting, I upgraded to 4.1.0. Now, X won't even come up. I have the correct values for my terminal. It looks like the system thinks there is only 256K on the card, and it can't find a mode, even not enough ram for 320x200, so it fails. It could be a bios problem, this is a custom system, built for a specific project, and an early version of the bios. I started to think that I could by a new cpu board and have something that works for all the hours I'm putting in. So I don't want to waste peoples time, until I have a problem that is real, at least. :~). > > What choices did you make with XConfigrator? What "conservative values" > did you use? Did you try Ctrl-Alt-+? Also, post your /etc/X11/XF86Config. > > -Mark > > On Sat, 19 Jan 2002, Eric Nelson wrote: > > I have been trying to get X configured for several days, and I can't get > > through this problem. > > > > I am using xfree86 3.3.6, redhat 6.2, w/ a chips & technologies ct69000, > > which I believe uses some type of frame buffer. When I run > > XConfigurator, it recognizes the ct69000 fine. When I enter my monitor > > type, and it tests itself, the screen doesn't come up, and it says > > something about a problem w/ the configuration, and backs up. But, it I > > enter a custom monitor, w/ some conservative values it does come up OK, > > and I can finish Xconfigurator. > > > > Then I do startx > foo 2>&1 > > > > It comes into X, and brings up a few apps. But, the resolution looks > > like 640x480, or less. It looks like I am just seeing the upper left > > corner of the screen, and can't get to the icons and task bar down at the > > bottom. My log file says I am at 1024x768, but, NOT! > > > > Note, I am using an embedded board we had built for a project. But I had > > the same board runnig fine w/ RedHat 7.2, so I don't think there is a > > hardware problem. I downloaded the latest source for xfree86 and built > > it. > > > > Should I go to version 4xxx? Is that a lot of trouble? I don't want to, > > because we are developing an embedded product, and the older X is > > probably smaller. > > > > Any help would be greatly appreciated. > > ___ > > vox-tech mailing list > > [EMAIL PROTECTED] > > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] Xwindows problem
I have been trying to get X configured for several days, and I can't get through this problem. I am using xfree86 3.3.6, redhat 6.2, w/ a chips & technologies ct69000, which I believe uses some type of frame buffer. When I run XConfigurator, it recognizes the ct69000 fine. When I enter my monitor type, and it tests itself, the screen doesn't come up, and it says something about a problem w/ the configuration, and backs up. But, it I enter a custom monitor, w/ some conservative values it does come up OK, and I can finish Xconfigurator. Then I do startx > foo 2>&1 It comes into X, and brings up a few apps. But, the resolution looks like 640x480, or less. It looks like I am just seeing the upper left corner of the screen, and can't get to the icons and task bar down at the bottom. My log file says I am at 1024x768, but, NOT! Note, I am using an embedded board we had built for a project. But I had the same board runnig fine w/ RedHat 7.2, so I don't think there is a hardware problem. I downloaded the latest source for xfree86 and built it. Should I go to version 4xxx? Is that a lot of trouble? I don't want to, because we are developing an embedded product, and the older X is probably smaller. Any help would be greatly appreciated. ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Questions about building my own box
On Wednesday 16 January 2002 09:09 pm, you wrote: > Preface: I'm not starting a war, but > > I have my linux (HP, Sun et al) machines where I run Oracle, write my perl > scripts, monkey with DBI/DBD/Mod_perl stuff, but I like the M$ Office > suite, IE, and outlook. > > I don't love M$, but I like their above products. I tried to make the > switch to a linux desktop but didn't like the apps. I promise you guys, if > M$ ported Office, IE, and Outlook to *nix, you'd all be using them. Run win4lin or vmware, so you can run those apps., but have a 'real' OS underneath. ;~) > > Jay > > - Original Message - > From: "Ryan" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, January 16, 2002 6:00 PM > Subject: Re: [vox-tech] Questions about building my own box > > > Hey now, chill out. It's entirely like that he did not know AMD made CPUs. > > You don't need to flame his for using outlook express (although it does > suck), perhaps he is unable to get online under linux for some reason. > > Also, it's quite rude to accuse people of spam, if it was a spam attempt > there likely would have been some mention of a 'great deal' or 'sale' > > On Wednesday, January 16 2002 03:34 pm, Takashi Ishihara wrote: > > On Wed, Jan 16, 2002 at 03:17:19PM -0600, Jay Strauss wrote: > > > I'm thinking about building a new box, unfortunately I don't know > > > anything about hardware > > > > How unreasonable ppl are these days. > > Kids say the same thing. The difference btwn kids and this guy is > > kids don't know the fact that they are idiot, and this guy at least know > > that he does not know anything. > > > > And this guy is using wintel + outlook. > > For this kind of person, the only convinsing factors are > > 1. bigger is better. > > 2. faster is better. > > Go to fry's or compusa or wherever and ask the sales person. > > They tell you the same. > > > > > I'm using www.spartantech.com (because they're out where I live), my > > > first > > > > Does this line implies that you expect ppl on the mailing list to visit > > aforementioned uri, browse their products, and configure the system for > > you? Or was he hired by that company, and send this kind of ads to the > > mailing lists? > > > > > choice it the chip: > > > > Sure you should stick w/ wintel + rambus. > > > > > I have to choose: > > > socket 423 vs 478 > > > > Bigger is better. Naturally the answer would be 478. > > > > > bus speed 256 vs 512 > > > > Wider is better. Naturally the answer would be 512. > > > > > chip speed - I know what this is. > > > > Make sure to get the fastest one. > > > > > Is the 423 an older style than the 478? the 478 is less expensive, is > > > that good? > > > bus speed, how will that impact the system, is it worth the price? It > > > seems I have have to buy the fastest chip in order to get the bigger > > > bus (maybe it just doesn't make sense with a slower chip?) > > > > Newer ones are a bit more expensive in general, but you should get new > > stuffs. Get the latest ones. They're faster and better. > > > > > Jay > > > > Hi Jay, > > so you're going to install xp on it, aren't you? > > > > > _ > > > Do You Yahoo!? > > > Get your free @yahoo.com address at http://mail.yahoo.com > > > > > > ___ > > > vox-tech mailing list > > > [EMAIL PROTECTED] > > > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Problems with dual boot system (Win 98/RH 7.2)
On Monday 14 January 2002 11:02 am, you wrote: > OK, here's what I did. > > My Windows 98SE crashed to the point where I couldn't do an emergency > backup of important files or even run win98 setup to restore the > corrupted system files. So I repartitioned and formatted my slave drive > which had RedHat 7.2 on it (I was running a dual boot) to an extended > DOS partition so I could backup Windows files to it (just some bookmark > files, Word documents, family photos, etc). Linux was actually unstable > at this point as well (kernel panic?), but I have backups of everything. > > I'm trying to rebuild my system from scratch now, but traces of grub > seem to be lingering around, even after I formatted my master hard drive > (the slave was also formatted as an extended DOS partition and contains > only my backup files). When I try to reinstall Win 98 (I've run setup > from both windows and MS-DOS), I get numerous errors regarding system > files, but I also get one that reads something like 'boot virus!' when I > run setup for windows. I went into the BIOS and turned off the boot > virus protection so that setup would run, but I still get tons of system > errors (.vxd, .dll, and stack errors). I've run Scandisk a number of > times with no errors as far as the hard drive goes, but various files > turn up missing or directory structure is screwed up somehow. > > Windows is now barely functional, extremely unstable, the boot virus > protection is still disabled, I can barely run Netscape in order to > write this e-mail, and I'm at a loss for what happened. > > I'm most likely overlooking something obvious, but... > How do I eliminate all traces of grub so I can start from scratch? > Was there an uninstall program for Linux that I missed? > What is kernel panic? I heard it mentioned on the list recently... > How can I load Linux so that it runs completely separate from Windows, > (ie. no bootloader, stability of one doesn't affect the other, etc.)? > Is this even the real problem? It sounds like you need to reformat the windows partition. Do you have a boot floppy for linux? A nice partitioning program is parted. You can load the image to a floppy, and do partitioning things. You either need to use grub, or lilo, or boot from a floppy. Kernel panic means it cant load the OS. http://www.suse.de/en/support/howto/parted/ > > Hopefully some of you dual-booters out there may have run across this > before. > > Any help is appreciated, > > Thanks, JOEY. > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] mounting woes
I On Wednesday 09 January 2002 08:07 pm, you wrote: > On Wed, Jan 09, 2002 at 07:52:15PM -0800, Eric Nelson wrote: > > My dead rat 6.2 partition was filling up, and I got a new 40 gig drive, > > so I decided to put part of the distro on a partition on the 40 gig, but > > got into trouble. > > > > First, I mounted the new partition: > > mount /dev/hdc1 /mnt/40g > > > > then I copied /home and /usr to /mnt/40g. The goal is to move them, but > > for now I just renamed: > > mv /home /home1 > > mov /usr /usr1 > > > > then I created links in / > > ln -s /mnt/40g/home home > > ln -s /mnt/40g/usr usr > > > > I fixed up fstab to mount the new partition. It seemed like everything > > should work OK, but when I tried startx, it couldn't find things, fonts > > and such. Is the basic theory OK, or am I making a conceptual problem? > > Since you did not include exact error messages, we can only provide > approximate answers. > > It sounds to me like you did not use 'cp -a' when copying, so permissions > were not set properly on the copies. I think I used cp -a, I used midnight commander, and it usually seems to do OK, but next time I will use command line to be sure. I could have done something else, like got a circular link or something that messed it up. Just wanted to know it the basic idea was correct. > > Why did you not mount /dev/hdc1 under /usr to avoid one of the symlinks? > That's the way I would do it. It ought to work either way though. That's what I wanted to do, but wasn't sure how. How do you do that? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] mounting woes
My dead rat 6.2 partition was filling up, and I got a new 40 gig drive, so I decided to put part of the distro on a partition on the 40 gig, but got into trouble. First, I mounted the new partition: mount /dev/hdc1 /mnt/40g then I copied /home and /usr to /mnt/40g. The goal is to move them, but for now I just renamed: mv /home /home1 mov /usr /usr1 then I created links in / ln -s /mnt/40g/home home ln -s /mnt/40g/usr usr I fixed up fstab to mount the new partition. It seemed like everything should work OK, but when I tried startx, it couldn't find things, fonts and such. Is the basic theory OK, or am I making a conceptual problem? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
