[vox-tech] simple stupid lockfile example?
ok, i hate it when i run tin, and then forget i have it in the background somewhere and run it again. i want to replace 'tin' with a shell script or alias that will test for a lock file (and call me a moron if it exists), make a lock file, run tin, and then delete the lock file... anyone got a good quick example they can cut and paste? (i could figure it all out in bash myself, but figured there might be caveats due to job control stuff, like ^Z suspension) thx! -- [EMAIL PROTECTED]Hire me! http://newbreedsoftware.com/bill/http://newbreedsoftware.com/bill/resume/ ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] unfound ethernet card
On Tue, Mar 18, 2003 at 05:35:47AM +, Bryce Kuklok wrote: > ethernet card is no where to be found. it's a sony vaio pcgz505lek > and i believe the card is an intel etherpro 10/100. i'm running > debian 2.4.20. at start up a line fliues by that says something along Bryce, - What things were done to your machine? (kernel compile?, pcmcia utils update? etc) - Is this a PCMCIA card? or - Is the ethernet built into the machine? - If it's PCMCIA, when you eject and insert the card do you hear beeps? Try running: === modprobe eepro100 ifconfig eth0 === - Does the ifconfig return no information? ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] simple stupid lockfile example?
On Tue, Mar 18, 2003 at 12:58:01AM -0800, Bill Kendrick wrote: > i want to replace 'tin' with a shell script or alias that will > test for a lock file (and call me a moron if it exists), make a lock file, > run tin, and then delete the lock file... = #! /bin/bash LOCK=$HOME/.tin.lock lockfile $LOCK tin rm -f $LOCK = "lockfile" is part of the procmail package. if you ^C the script, you will have to clean up and delete the lockfile on your own. there are a few ways for the script to automatically detect tin was killed, but you didn't ask for that. ;) ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] unfound ethernet card
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 17 March 2003 09:35 pm, Bryce Kuklok wrote: > hey all, > as some of you may notice i am writing this one from windows. at > the installfest this weekend we did some updating on my machine and > everything went fine. i shut it down, got home, and low and behold my > ethernet card is no where to be found. it's a sony vaio pcgz505lek > and i believe the card is an intel etherpro 10/100. i'm running > debian 2.4.20. at start up a line fliues by that says something along > the lines of "eth0: no device found". none too sure, it goes by > quickly. any help would be much appreciated. > -bryce Please do not send HTML email. This is quite annoying to read in a client with HTML rendering off. I'm fairly sure this is even aginst the mailing list rules, and I'd check but I can't access lugod.org. - -- 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 iD8DBQE+duStEd9E83IXe8cRAo/bAJwLBspagmETA6H46860BPX4fM77+ACfe+sP 5KR+DGEBaFMO6rxa8UjXWG8= =ycHY -END PGP SIGNATURE- ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] simple stupid lockfile example?
On Tue, Mar 18, 2003 at 04:09:53AM -0500, Mike Simons wrote: > > "lockfile" is part of the procmail package. Cool, thanks! :^) -bill! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Recovering data
On Mon, Mar 17, 2003 at 04:30:20PM -0800, Michael J Wenk wrote: > The system is running samba 2.2.3a. There is nothing useful that I can see > in any samba logs. I did notice something I was unaware of, the laptop that > I call buffy was not in my static DHCP table, ie, it is getting various IP > addresses and names. I wonder if that could have an effect? It is highly unlikely that the Dynamic IP had anything to do with this. It sounds like the backup software you used overwrote the file, I would recommend checking the timestamp on the tiny file to see when it happened. (after the first restore, or during the second backup, etc). > I went thru > the filesystem that I stored the backup on and tried to search for the file > with debugfs, but either because the file was too large(recover segfaulted > on me) or some other reason. Ive tried the tricks I know to recover a file, > and have failed, so Ive pretty much given up on my data, but ANY help would > be greatly appreciated. It is too late, but unmounting the partition as soon as you realize something is wrong decreases the chance of future file system activity damaging your file data, wherever it is on the filesystem. One problem you may have 'rm file' is very different from 'echo > file' in that one unlinks the file so that it's inode is intact but not attached... the echo on the otherhand truncates the file (releasing all the blocks that are part of the inode), and reuses the inode for the new file contents. >From what I understand debugfs utils can reattach unlinked inodes, but once the blocks are not recorded as part of an inode, trying to figure out what blocks were part of what file and in what order is kinda tough. If you value the information greatly, doing a lowlevel partition backup (like 'dd if=/dev/hdb1 of=/big_place/hdb1.img' style) then contacting some people doing ext2/3 filesystem development is your best chance. Good Luck, Mike Simons ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] unfound ethernet card
begin Ryan Castellucci <[EMAIL PROTECTED]> > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Monday 17 March 2003 09:35 pm, Bryce Kuklok wrote: > > hey all, > > as some of you may notice i am writing this one from windows. at > > the installfest this weekend we did some updating on my machine and > > everything went fine. i shut it down, got home, and low and behold my > > ethernet card is no where to be found. it's a sony vaio pcgz505lek > > and i believe the card is an intel etherpro 10/100. i'm running > > debian 2.4.20. at start up a line fliues by that says something along > > the lines of "eth0: no device found". none too sure, it goes by > > quickly. any help would be much appreciated. > > -bryce > > Please do not send HTML email. This is quite annoying to read in a client > with HTML rendering off. I'm fairly sure this is even aginst the mailing list > rules, and I'd check but I can't access lugod.org. thanks ryan. yeah, not sending html email is the first rule. :) www.lugod.org/mailinglists#rules pete -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] simple stupid lockfile example?
begin Mike Simons <[EMAIL PROTECTED]> > On Tue, Mar 18, 2003 at 12:58:01AM -0800, Bill Kendrick wrote: > > i want to replace 'tin' with a shell script or alias that will > > test for a lock file (and call me a moron if it exists), make a lock file, > > run tin, and then delete the lock file... > > = > #! /bin/bash > > LOCK=$HOME/.tin.lock > > lockfile $LOCK > tin > rm -f $LOCK > = > > "lockfile" is part of the procmail package. > > if you ^C the script, you will have to clean up and delete the lockfile > on your own. there are a few ways for the script to automatically > detect tin was killed, but you didn't ask for that. ;) ironically, i used to do WAY more shell programming before i ever knew what linux was, so i'm not sure this will work under bash. if you want to trap control-c (SIGINT), you can modify mike's script like so: = #!/bin/bash trap (rm -f $LOCK; exit 1) 2 LOCK=$HOME/.tin.lock lockfile $LOCK tin rm -f $LOCK = pete -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] Re: [vox] Demo today
redirected to vox-tech
begin Jonathan Stickel <[EMAIL PROTECTED]>
> I was previously unaware of the magic sysreq keys. They do look useful,
> and I read the documentation as you suggest. From what I can tell, it
> is compiled in my kernel (CONFIG_MAGIC_SYSRQ=y), but I am wondering if
> it is disabled with the run-time command: "echo "0" >
> /proc/sys/kernel/sysrq", as suggested by the documentation. In fact, my
> /proc/sys/kernel/sysrq contains the single character "0". Where would I
> find this run time command? Can I just delete it or comment it out?
> Thanks,
>
> Jonathan
have you tried to use sysreq and it didn't work?
pete
> Peter Jay Salzman wrote:
> >hi doug,
> >
> >check out /usr/src/linux-2.4.20/Documentation/sysrq.txt
> >
> >it's very short. basically, you make the kernel:
> >
> >1. flush buffers ("sync disks")
> >2. remount all partitions as read-only
> >3. reboot
> >
> >print screen == sysrq
> >
> >alt-sysrq-sflush
> >alt-sysrq-uremount partitions as read-only
> >alt-sysrq-breboot
> >
> >you can actually send TERM and KILL to all processes. this is the kind
> >of thing you should really read about before using. it's short and
> >well written.
> >
> >pete
> >
> >
> >begin R. Douglas Barbieri <[EMAIL PROTECTED]>
> >
> >>Okay, so explain to me the magic sysreq keys... :-) I experience lockups
> >>sometimes when I'm trying to start up Win4Lin. It hoses my machine so
> >>badly that Ctrl-Alt-Backspace won't even kill X (and Ctrl-Alt-Fn doesn't
> >>even work. I have to hard restart when that happens).
> >>
> >>On Sat, Mar 15, 2003 at 09:38:11PM -0800, Bill Kendrick wrote:
> >>
> >>>Today's Linux demo was pretty successful. Mike showed up (a bit late
> >>>;^) )
> >>>with the Demo machine. Before that, I just had the flyers set up, and
> >>>a couple of kids came by, and I gave them Tux Paint CDs. :^)
> >>>
> >>>When the computer showed up, we started getting many more visitors.
> >>>Questions ranged from "I use Linux at work, and the other day it
> >>>/completely/
> >>>locked up!" (Mike explained magic sysreq keys) to "Why would I want
> >>>Linux?"
> >>>(I said "for the good of humanity"; she really digged that answer, and
> >>>stuck around and talked for a long time)
> >>>
> >>>Towards the latter half, Jeff Newmiller came by and set up his laptop,
> >>>so we had one desktop, one laptop, and one PDA (which didn't get too
> >>>much use).
> >>>
> >>>
> >>>We worked on getting Apache configured to show off the LUGOD.org website,
> >>>demo'd Tux Paint a lot, and played a little with getting OCR software to
> >>>work (in response to someone's complaint about Windows).
> >>>
> >>>
> >>>Henry - we should set one up for April or May!
> >>>
> >>>--
> >>>[EMAIL PROTECTED]
> >>>Hire me!
> >>>http://newbreedsoftware.com/bill/
> >>>http://newbreedsoftware.com/bill/resume/
> >>>___
> >>>vox mailing list
> >>>[EMAIL PROTECTED]
> >>>http://lists.lugod.org/mailman/listinfo/vox
> >>
> >>--
> >>R. Douglas Barbieri
> >>[EMAIL PROTECTED]
> >>http://www.dooglio.net
> >>
> >>GPG Fingerprint : FE6A 6A57 2B95 7594 E534 BFEE 45F1 9E5E F30A 8A27
> >>MIT.edu recv-key: F6368A3D
> >>GPG Public key : http://www.dooglio.net/dooglio.asc
> >
> >
> >
> >
>
>
> ___
> vox mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox
--
Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Public Access Terminals
On Monday 17 March 2003 11:42 pm, Bill Kendrick wrote: > > The Public-Web-Browser Howto has been helpful. > > Have you got an URL handy for it? It's not the one by Jamie Zawinsky, is > it? http://www.ibiblio.org/pub/Linux/docs/HOWTO/mini/other-formats/html_single/Public-Web-Browser.html There is also the kiosk-HOWTO: http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Kiosk-HOWTO.html > Well, Galeon might be a better decision than Mozilla, especially if you're > considering Mozilla. I was going to try it yesterday, but ran out of time and didn't want to rush the install of all the gnome libs it needs. > > So, what kind of browser were you going to use and how did you plan to > > lock it down? > > As I mentioned, KDE has a 'kiosk framework' (which you can learn about > over at the KDE website... somewhere or other), which lets you do things > like say "Get rid of the 'Print' button", "Don't let the user configure > XYZ", "Don't show any icons on the desktop", and "Don't let the user save > the HTML file to the disk." Well, I'm going to try this route: 0. Slackware + kde + konqueror 1. Slackware + blackbox + konqueror 2. Slackware + blackbox + galeon 3. Slackware + blackbox + hacked mozilla I won't get specific about my goals, but the main thing is that JavaScript needs to run very well. In the past konqueror had some trouble with this which is why I was mainly looking at mozilla. I'll report back as soon as I have more info. -- Thanks Darrick ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Re: [vox] Demo today
When I try alt-sysrq-h (to display magic-sysrq help) in KDE, my cpu runs
for awhile but nothing seems to happen. I wanted to avoid testing
something more drastic, but since you asked, I entered init level 3 and
tried a few (alt-sysrq-'h', 's', 'u', and 'b'). Nothing happens at all.
Jonathan
Peter Jay Salzman wrote:
redirected to vox-tech
begin Jonathan Stickel <[EMAIL PROTECTED]>
I was previously unaware of the magic sysreq keys. They do look useful,
and I read the documentation as you suggest. From what I can tell, it
is compiled in my kernel (CONFIG_MAGIC_SYSRQ=y), but I am wondering if
it is disabled with the run-time command: "echo "0" >
/proc/sys/kernel/sysrq", as suggested by the documentation. In fact, my
/proc/sys/kernel/sysrq contains the single character "0". Where would I
find this run time command? Can I just delete it or comment it out?
Thanks,
Jonathan
have you tried to use sysreq and it didn't work?
pete
Peter Jay Salzman wrote:
hi doug,
check out /usr/src/linux-2.4.20/Documentation/sysrq.txt
it's very short. basically, you make the kernel:
1. flush buffers ("sync disks")
2. remount all partitions as read-only
3. reboot
print screen == sysrq
alt-sysrq-sflush
alt-sysrq-uremount partitions as read-only
alt-sysrq-breboot
you can actually send TERM and KILL to all processes. this is the kind
of thing you should really read about before using. it's short and
well written.
pete
begin R. Douglas Barbieri <[EMAIL PROTECTED]>
Okay, so explain to me the magic sysreq keys... :-) I experience lockups
sometimes when I'm trying to start up Win4Lin. It hoses my machine so
badly that Ctrl-Alt-Backspace won't even kill X (and Ctrl-Alt-Fn doesn't
even work. I have to hard restart when that happens).
On Sat, Mar 15, 2003 at 09:38:11PM -0800, Bill Kendrick wrote:
Today's Linux demo was pretty successful. Mike showed up (a bit late
;^) )
with the Demo machine. Before that, I just had the flyers set up, and
a couple of kids came by, and I gave them Tux Paint CDs. :^)
When the computer showed up, we started getting many more visitors.
Questions ranged from "I use Linux at work, and the other day it
/completely/
locked up!" (Mike explained magic sysreq keys) to "Why would I want
Linux?"
(I said "for the good of humanity"; she really digged that answer, and
stuck around and talked for a long time)
Towards the latter half, Jeff Newmiller came by and set up his laptop,
so we had one desktop, one laptop, and one PDA (which didn't get too
much use).
We worked on getting Apache configured to show off the LUGOD.org website,
demo'd Tux Paint a lot, and played a little with getting OCR software to
work (in response to someone's complaint about Windows).
Henry - we should set one up for April or May!
--
[EMAIL PROTECTED]
Hire me!
http://newbreedsoftware.com/bill/
http://newbreedsoftware.com/bill/resume/
___
vox mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox
--
R. Douglas Barbieri
[EMAIL PROTECTED]
http://www.dooglio.net
GPG Fingerprint : FE6A 6A57 2B95 7594 E534 BFEE 45F1 9E5E F30A 8A27
MIT.edu recv-key: F6368A3D
GPG Public key : http://www.dooglio.net/dooglio.asc
___
vox mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Re: [vox] Demo today
On Tue, Mar 18, 2003 at 11:29:13AM -0800, Jonathan Stickel wrote: > When I try alt-sysrq-h (to display magic-sysrq help) in KDE, my cpu runs > for awhile but nothing seems to happen. I wanted to avoid testing > something more drastic, but since you asked, I entered init level 3 and > tried a few (alt-sysrq-'h', 's', 'u', and 'b'). Nothing happens at all. Hrm... I'm guessing the output gets dumped to a console (e.g., Ctrl-Alt-F1) -bill! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Re: [vox] Demo today
On Tue, Mar 18, 2003 at 11:29:13AM -0800, Jonathan Stickel wrote: > When I try alt-sysrq-h (to display magic-sysrq help) in KDE, my cpu runs > for awhile but nothing seems to happen. I wanted to avoid testing > something more drastic, but since you asked, I entered init level 3 and > tried a few (alt-sysrq-'h', 's', 'u', and 'b'). Nothing happens at all. The output goes into the kernel message buffer, which will appear on the console, in dmesg, and some /var/log files depending on how you have klogd setup... After hitting A-S-h you should see something like: dmesg | tail -1 === SysRq : HELP : loglevel0-8 reBoot tErm kIll saK showMem Off showPc unRaw Sync showTasks Unmount === If you try the above and don't see the line it is probably being turned off at runtime. > > Where would I find this run time command? > > Can I just delete it or comment it out? find /etc -type f -print0 | xargs -0 grep -l sysrq 2> /dev/null | less If you find any lines that appear to be doing the echo you can comment them out, if you don't find a line you can put your own "echo 1 > " into the bootup sequence if you want... Later, Mike Simons ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] magic sysreq key
note: subject change
hi jonathan,
when not latexing or playing games, i'm usually not using X.
runlevels are not meaningful since they mean different things for
different operating systems. i'm guessing you don't use debian, so i
don't know what runlevel 3 means.
when doing anything of any importance, like trying to recover gracefully
from a kernel error, do it in console. don't run X. direct logging by
the kernel and modules may not be seen from within X. furthermore, X
can steal the key sequence like it does with ctl-alt-backspace.
i know *quite literally* nothing about KDE or GNOME other than you can
have cute little icons on your desktop, so i'm not sure of any gotchas
with kernel logging, magic keystrokes and desktop managers.
so try it in console.
one more question, and i hope this isn't insulting -- can you tell me
*precisely* the keystrokes you're hitting in excruciating detail?
something along the lines of:
i press down the alt key. while keeping the alt key pressed down, i
then press down "print screen". etc
lastly, have you read the part in sysreq.txt about "i press the sequence
and nothing happens"?
pete
begin Jonathan Stickel <[EMAIL PROTECTED]>
> When I try alt-sysrq-h (to display magic-sysrq help) in KDE, my cpu runs
> for awhile but nothing seems to happen. I wanted to avoid testing
> something more drastic, but since you asked, I entered init level 3 and
> tried a few (alt-sysrq-'h', 's', 'u', and 'b'). Nothing happens at all.
>
> Jonathan
>
>
> Peter Jay Salzman wrote:
> >redirected to vox-tech
> >
> >begin Jonathan Stickel <[EMAIL PROTECTED]>
> >
> >>I was previously unaware of the magic sysreq keys. They do look useful,
> >>and I read the documentation as you suggest. From what I can tell, it
> >>is compiled in my kernel (CONFIG_MAGIC_SYSRQ=y), but I am wondering if
> >>it is disabled with the run-time command: "echo "0" >
> >>/proc/sys/kernel/sysrq", as suggested by the documentation. In fact, my
> >>/proc/sys/kernel/sysrq contains the single character "0". Where would I
> >>find this run time command? Can I just delete it or comment it out?
> >>Thanks,
> >>
> >>Jonathan
> >
> >
> >have you tried to use sysreq and it didn't work?
> >
> >pete
> >
> >
> >>Peter Jay Salzman wrote:
> >>
> >>>hi doug,
> >>>
> >>>check out /usr/src/linux-2.4.20/Documentation/sysrq.txt
> >>>
> >>>it's very short. basically, you make the kernel:
> >>>
> >>>1. flush buffers ("sync disks")
> >>>2. remount all partitions as read-only
> >>>3. reboot
> >>>
> >>>print screen == sysrq
> >>>
> >>>alt-sysrq-sflush
> >>>alt-sysrq-uremount partitions as read-only
> >>>alt-sysrq-breboot
> >>>
> >>>you can actually send TERM and KILL to all processes. this is the kind
> >>>of thing you should really read about before using. it's short and
> >>>well written.
> >>>
> >>>pete
> >>>
> >>>
> >>>begin R. Douglas Barbieri <[EMAIL PROTECTED]>
> >>>
> >>>
> Okay, so explain to me the magic sysreq keys... :-) I experience lockups
> sometimes when I'm trying to start up Win4Lin. It hoses my machine so
> badly that Ctrl-Alt-Backspace won't even kill X (and Ctrl-Alt-Fn doesn't
> even work. I have to hard restart when that happens).
>
> On Sat, Mar 15, 2003 at 09:38:11PM -0800, Bill Kendrick wrote:
>
>
> >Today's Linux demo was pretty successful. Mike showed up (a bit late
> >;^) )
> >with the Demo machine. Before that, I just had the flyers set up, and
> >a couple of kids came by, and I gave them Tux Paint CDs. :^)
> >
> >When the computer showed up, we started getting many more visitors.
> >Questions ranged from "I use Linux at work, and the other day it
> >/completely/
> >locked up!" (Mike explained magic sysreq keys) to "Why would I want
> >Linux?"
> >(I said "for the good of humanity"; she really digged that answer, and
> >stuck around and talked for a long time)
> >
> >Towards the latter half, Jeff Newmiller came by and set up his laptop,
> >so we had one desktop, one laptop, and one PDA (which didn't get too
> >much use).
> >
> >
> >We worked on getting Apache configured to show off the LUGOD.org
> >website,
> >demo'd Tux Paint a lot, and played a little with getting OCR software
> >to
> >work (in response to someone's complaint about Windows).
> >
> >
> >Henry - we should set one up for April or May!
> >
> >--
> >[EMAIL PROTECTED]
> >Hire me!
> >http://newbreedsoftware.com/bill/
> >http://newbreedsoftware.com/bill/resume/
> >___
> >vox mailing list
> >[EMAIL PROTECTED]
> >http://lists.lugod.org/mailman/listinfo/vox
>
> --
> R. Douglas Barbieri
> [EMAIL PROTECTED]
> http://www.dooglio.net
>
> GPG Fingerprint : FE6A 6A57 2B95 7594 E534 BFEE 45F1 9E5E F30A 8A27
> >>
[vox-tech] Re: unfound ethernet card
- What things were done to your machine? (kernel compile?, pcmcia utils update? etc) it was a debian testing update as of 3pm sunday - Is this a PCMCIA card? no or - Is the ethernet built into the machine? yes - If it's PCMCIA, when you eject and insert the card do you hear >beeps? i have yet to get pcmcia or sound even working Try running: === modprobe eepro100 At run it returns modprobe: Can't locate module eepro100 ifconfig eth0 At run it returns eth0: error fetching interface information: Device not found i appreciate all the help. i am newbie so if there are any commands you would assume that i know, i would advise against it. thanks! bryce _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] magic sysreq key
btw, echo "1" > /proc/sys/kernel/sysreq to enable echo "0" > /proc/sys/kernel/sysreq to disable you most likely won't be able to delete this file (untested) because these files are not real filesystem files. they are abstractions of kernel data into a memory region which "looks like" a filesystem and gets mounted at boot time. you can certainly catch an unlink event in a /proc file, but i can't think of any official proc files that do anything useful or allow you to delete them. they're often used as switches (true/false as with sysreq) or a way to glean info from the kernel (ie /proc/cpuinfo). pete ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Re: unfound ethernet card
On Tue, Mar 18, 2003 at 08:09:09PM +, Bryce Kuklok wrote: > >- What things were done to your machine? > > (kernel compile?, pcmcia utils update? etc) > it was a debian testing update as of 3pm sunday Okay this means they could have installed a new kernel or not. - which kernel version is running? compiled where? by who? uname -a - which module directories do you have installed? ls /lib/modules - are there any copies of eepro100 around? find /lib/modules | grep eepro100 This will probably take a few more rounds... ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] magic sysreq key
Thanks Mike, Bill, and Pete for some helpful comments. I actually found
my answer with a google search
(http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/security-sysrq.html).
Here it clearly states that "Writing a 0 into /proc/sys/kernel/sysrq
will disable the magic SysRq key", so my initial guess was correct; my
default RH8 install disabled the magic sysrq keys!
It turns out there is a line in /etc/sysctl.conf which enables or
disables magic sysrq:
kernel.sysrq = [0 or 1]
I now have magic sysrq enabled and have tested it succesfully from
console with ctl-alt-h. Now I am ready the next time Linux freezes on me.
Jonathan
btw Pete: my init level 3 is multiuser mode without X. I had thought
this was generally true, but I guess not from your comments. I now know
that I can get a non-X console by simply pressing ctl-alt-f1, and can
return to X with ctl-alt-f7. That is also useful to know.
Peter Jay Salzman wrote:
note: subject change
hi jonathan,
when not latexing or playing games, i'm usually not using X.
runlevels are not meaningful since they mean different things for
different operating systems. i'm guessing you don't use debian, so i
don't know what runlevel 3 means.
when doing anything of any importance, like trying to recover gracefully
from a kernel error, do it in console. don't run X. direct logging by
the kernel and modules may not be seen from within X. furthermore, X
can steal the key sequence like it does with ctl-alt-backspace.
i know *quite literally* nothing about KDE or GNOME other than you can
have cute little icons on your desktop, so i'm not sure of any gotchas
with kernel logging, magic keystrokes and desktop managers.
so try it in console.
one more question, and i hope this isn't insulting -- can you tell me
*precisely* the keystrokes you're hitting in excruciating detail?
something along the lines of:
i press down the alt key. while keeping the alt key pressed down, i
then press down "print screen". etc
lastly, have you read the part in sysreq.txt about "i press the sequence
and nothing happens"?
pete
begin Jonathan Stickel <[EMAIL PROTECTED]>
When I try alt-sysrq-h (to display magic-sysrq help) in KDE, my cpu runs
for awhile but nothing seems to happen. I wanted to avoid testing
something more drastic, but since you asked, I entered init level 3 and
tried a few (alt-sysrq-'h', 's', 'u', and 'b'). Nothing happens at all.
Jonathan
Peter Jay Salzman wrote:
redirected to vox-tech
begin Jonathan Stickel <[EMAIL PROTECTED]>
I was previously unaware of the magic sysreq keys. They do look useful,
and I read the documentation as you suggest. From what I can tell, it
is compiled in my kernel (CONFIG_MAGIC_SYSRQ=y), but I am wondering if
it is disabled with the run-time command: "echo "0" >
/proc/sys/kernel/sysrq", as suggested by the documentation. In fact, my
/proc/sys/kernel/sysrq contains the single character "0". Where would I
find this run time command? Can I just delete it or comment it out?
Thanks,
Jonathan
have you tried to use sysreq and it didn't work?
pete
Peter Jay Salzman wrote:
hi doug,
check out /usr/src/linux-2.4.20/Documentation/sysrq.txt
it's very short. basically, you make the kernel:
1. flush buffers ("sync disks")
2. remount all partitions as read-only
3. reboot
print screen == sysrq
alt-sysrq-sflush
alt-sysrq-uremount partitions as read-only
alt-sysrq-breboot
you can actually send TERM and KILL to all processes. this is the kind
of thing you should really read about before using. it's short and
well written.
pete
begin R. Douglas Barbieri <[EMAIL PROTECTED]>
Okay, so explain to me the magic sysreq keys... :-) I experience lockups
sometimes when I'm trying to start up Win4Lin. It hoses my machine so
badly that Ctrl-Alt-Backspace won't even kill X (and Ctrl-Alt-Fn doesn't
even work. I have to hard restart when that happens).
On Sat, Mar 15, 2003 at 09:38:11PM -0800, Bill Kendrick wrote:
Today's Linux demo was pretty successful. Mike showed up (a bit late
;^) )
with the Demo machine. Before that, I just had the flyers set up, and
a couple of kids came by, and I gave them Tux Paint CDs. :^)
When the computer showed up, we started getting many more visitors.
Questions ranged from "I use Linux at work, and the other day it
/completely/
locked up!" (Mike explained magic sysreq keys) to "Why would I want
Linux?"
(I said "for the good of humanity"; she really digged that answer, and
stuck around and talked for a long time)
Towards the latter half, Jeff Newmiller came by and set up his laptop,
so we had one desktop, one laptop, and one PDA (which didn't get too
much use).
We worked on getting Apache configured to show off the LUGOD.org
website,
demo'd Tux Paint a lot, and played a little with getting OCR software
to
work (in response to someone's complaint about Windows).
Henry - we should set one up for April or May!
--
[EMAIL PROTECTED]
Re: [vox-tech] magic sysreq key
begin Jonathan Stickel <[EMAIL PROTECTED]> > > It turns out there is a line in /etc/sysctl.conf which enables or > disables magic sysrq: > > kernel.sysrq = [0 or 1] tucked away in the mental file cabinet... i wonder why redhat does this? > I now have magic sysrq enabled and have tested it succesfully from > console with ctl-alt-h. Now I am ready the next time Linux freezes on me. :) pete ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] SysRq
I've used the low-latency patches before and it also has a switch to toggle
it on and off in /proc/sys/kernel. To enable sysrq:
echo 1 > /proc/sys/kernel/sysrq
The low-latency patch allows you to select whether or not to have this
switch. Maybe the sysrq has that too in how you compile your kernel.
In X the magic-sysex keys won't show up. The help, etc will only show up
only in a console. The keys still work in X you just have to pray a bit.
However, I've been rather successful getting to a console from X via the
unRaw sysex key. This seems to free the keyboard from X. Then you can use a
Ctrl-Alt-Fn to get to a console and kill whatever is using all your CPU's or
Memory.
On Tuesday 18 March 2003 11:29 am, Jonathan Stickel wrote:
> When I try alt-sysrq-h (to display magic-sysrq help) in KDE, my cpu runs
> for awhile but nothing seems to happen. I wanted to avoid testing
> something more drastic, but since you asked, I entered init level 3 and
> tried a few (alt-sysrq-'h', 's', 'u', and 'b'). Nothing happens at all.
>
> Jonathan
>
> Peter Jay Salzman wrote:
> > redirected to vox-tech
> >
> > begin Jonathan Stickel <[EMAIL PROTECTED]>
> >
> >>I was previously unaware of the magic sysreq keys. They do look useful,
> >> and I read the documentation as you suggest. From what I can tell, it
> >>is compiled in my kernel (CONFIG_MAGIC_SYSRQ=y), but I am wondering if
> >>it is disabled with the run-time command: "echo "0" >
> >>/proc/sys/kernel/sysrq", as suggested by the documentation. In fact, my
> >>/proc/sys/kernel/sysrq contains the single character "0". Where would I
> >>find this run time command? Can I just delete it or comment it out?
> >>Thanks,
> >>
> >>Jonathan
> >
> > have you tried to use sysreq and it didn't work?
> >
> > pete
> >
> >>Peter Jay Salzman wrote:
> >>>hi doug,
> >>>
> >>>check out /usr/src/linux-2.4.20/Documentation/sysrq.txt
> >>>
> >>>it's very short. basically, you make the kernel:
> >>>
> >>>1. flush buffers ("sync disks")
> >>>2. remount all partitions as read-only
> >>>3. reboot
> >>>
> >>>print screen == sysrq
> >>>
> >>>alt-sysrq-sflush
> >>>alt-sysrq-uremount partitions as read-only
> >>>alt-sysrq-breboot
> >>>
> >>>you can actually send TERM and KILL to all processes. this is the kind
> >>>of thing you should really read about before using. it's short and
> >>>well written.
> >>>
> >>>pete
> >>>
> >>>
> >>>begin R. Douglas Barbieri <[EMAIL PROTECTED]>
> >>>
> Okay, so explain to me the magic sysreq keys... :-) I experience
> lockups sometimes when I'm trying to start up Win4Lin. It hoses my
> machine so badly that Ctrl-Alt-Backspace won't even kill X (and
> Ctrl-Alt-Fn doesn't even work. I have to hard restart when that
> happens).
>
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] magic sysreq key
On Tue, Mar 18, 2003 at 12:54:01PM -0800, Jonathan Stickel wrote: > I now have magic sysrq enabled and have tested it succesfully from > console with ctl-alt-h. Now I am ready the next time Linux freezes on me. Keep in mind sysrq works form inside X too... As long as the kernel is still running and the input layer is working you should be able to use the keys even if you can't see the results. X can not trap or block those key sequences... in fact some of the commands allow one to recover from a locked up X server, (although resetting the graphics card after a X failure may require some advanced preparation to safe the video state from before X is started). Later, Mike Simons ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] magic sysreq key
begin Mike Simons <[EMAIL PROTECTED]> > On Tue, Mar 18, 2003 at 12:54:01PM -0800, Jonathan Stickel wrote: > > I now have magic sysrq enabled and have tested it succesfully from > > console with ctl-alt-h. Now I am ready the next time Linux freezes on me. > > Keep in mind sysrq works form inside X too... > As long as the kernel is still running and the input layer is working > you should be able to use the keys even if you can't see the results. > > X can not trap or block those key sequences... mike, è that is what it looks like when i type "alt-sysreq-h" from within X. i would say that X is definitely catching the key sequence. or else the scancode is changing for some reason... pete > in fact some of the > commands allow one to recover from a locked up X server, (although > resetting the graphics card after a X failure may require some advanced > preparation to safe the video state from before X is started). > > Later, > Mike Simons > ___ > vox-tech mailing list > [EMAIL PROTECTED] > http://lists.lugod.org/mailman/listinfo/vox-tech -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] magic sysreq key
On Tue, Mar 18, 2003 at 01:33:38PM -0800, Peter Jay Salzman wrote: > begin Mike Simons <[EMAIL PROTECTED]> > > Keep in mind sysrq works form inside X too... [...] > > X can not trap or block those key sequences... > > that is what it looks like when i type "alt-sysreq-h" from within X. > > i would say that X is definitely catching the key sequence. or else the > scancode is changing for some reason... I wrote: # The output goes into the kernel message buffer, which will appear on # the console, in dmesg, and some /var/log files depending on how you have # klogd setup... # After hitting A-S-h you should see something like: # # dmesg | tail -1 # === # SysRq : HELP : loglevel0-8 reBoot tErm kIll saK showMem Off showPc unRaw # Sync showTasks Unmount # === from the documentation: % * What is the magic SysRq key? % ~~ % It is a 'magical' key combo you can hit which the kernel will respond to % regardless of whatever else it is doing, unless it is completely locked up. Pete, Type your Alt-Sysrq combo, then look at dmesg or tail -f /var/log/kern.log. The command sequence is being run. The sysrq keys would be rather useless if they didn't work inside X... since most people live in X. The kernel owns the keyboard input devices, and is always the thing interpreting the keystrokes to pass to the application running on the "active" console. This option's user interface is rather crude, which is why it's under "Kernel Hacking" in the configuration menus... it's not meant to be used by everyone, Linux isn't supposed to be unstable, and you only need it if something breaks. So test it out inside X, and let me know if it doesn't work. Later, Mike ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] magic sysreq key
begin Mike Simons <[EMAIL PROTECTED]> > On Tue, Mar 18, 2003 at 01:33:38PM -0800, Peter Jay Salzman wrote: > > begin Mike Simons <[EMAIL PROTECTED]> > > Pete, > > Type your Alt-Sysrq combo, then look at dmesg or > tail -f /var/log/kern.log. The command sequence is being run. aiee... ok, you're definitely right! :) > The sysrq keys would be rather useless if they didn't work inside X... > since most people live in X. heh. i hadn't thought of that. pete -- Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] simple stupid lockfile example?
On Tue, Mar 18, 2003 at 12:58:01AM -0800, Bill Kendrick wrote: > > ok, i hate it when i run tin, and then forget i have it in the background > somewhere and run it again. > > i want to replace 'tin' with a shell script or alias that will > test for a lock file (and call me a moron if it exists), make a lock file, > run tin, and then delete the lock file... It's not exactly what you asked for, but how about aliasing tin as something like: alias tin="screen -D -R -S tinsess tin" This will always run tin inside a screen session called 'tinsess.' Then if you try to start tin up in a different terminal, it will just re-attach to the tin session you already have running without raising an error. Matt -- * * Matt Roper <[EMAIL PROTECTED]>* * http://www.mattrope.com * * PGP Key: http://www.mattrope.com/mattrope.asc * * ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] ethernet card still not found
- which kernel version is running? compiled where? by who? uname -a Linux debian 2.4.20-debian2 #1 Sun Feb 16 18:53:38 PST 2003 i686 Pentium III (Coppermine)Genuine Intel GNU/Linux - which module directories do you have installed? ls /lib/modules 2.2.20 2.4.16-686 2.4.18-686 2.4.20 debian2 - are there any copies of eepro100 around? find /lib/modules | grep eepro100 /lib/modules/2.2.20/net/eepro100.o /lib/modules/2.2.20/net/eepro100-scyld.o /lib/modules/2.2.20/pcmcia/eepro-cb.o /lib/modules/2.4.16-686/kernel/drivers/net/eepro100.o /lib/modules/2.4.18-686/kernel/drivers/net/eepro100.o that's all the output on that. near as i can tell, that should indicate there is something there driver-wise, but i could be mistaken. -bryce _ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] simple stupid lockfile example?
On Tue, Mar 18, 2003 at 07:45:23PM -0800, Matt Roper wrote: > alias tin="screen -D -R -S tinsess tin" That is an excellent suggestion! ___ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] ethernet card still not found
- Is there really a space in the "/lib/modules/2.4.20 debian" directory?
("2.4.20 debian2" not "2.4.20-debian2)
- Tell me if you see a bunch of stuff from:
find /lib/modules/2.4.20*
(if it's just a few lines paste them here)
- Send output from the following:
grep CONFIG_EEPRO100 /usr/src/linux*/debian*
On Wed, Mar 19, 2003 at 05:23:21AM +, Bryce Kuklok wrote:
> >- which kernel version is running? compiled where? by who?
> > uname -a
> >
> Linux debian 2.4.20-debian2 #1 Sun Feb 16 18:53:38 PST 2003 i686 Pentium
> III (Coppermine)Genuine Intel GNU/Linux
The name "2.4.20-debian2" isn't a standard debian kernel name, it's
similar to my standard kernel names, when using my .deb kernel build script.
The timestamp also looks like an installfest build.
> >- which module directories do you have installed?
> > ls /lib/modules
> >
> 2.4.20 debian2
It looks like something happened to the module directory, because it
should have a dash.
> >- are there any copies of eepro100 around?
> > find /lib/modules | grep eepro100
>
> /lib/modules/2.4.16-686/kernel/drivers/net/eepro100.o
> /lib/modules/2.4.18-686/kernel/drivers/net/eepro100.o
The eepro100 driver is not available for the kernel version you are
running... it would be in /lib/modules/2.4.20-debian2/.
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] Recovering data
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
