Re: grub on 5.4
On Fri 22 Apr 05 03:14, Dick Davies [EMAIL PROTECTED] wrote: Am I missing something obvious? The HDD is'nt write protected or anything, the freebsd loader went in fine # ls /boot/grub/ device.map fat_stage1_5iso9660_stage1_5 menu.lst reiserfs_stage1_5 stage2 vstafs_stage1_5 e2fs_stage1_5 ffs_stage1_5 jfs_stage1_5minix_stage1_5 stage1 ufs2_stage1_5 xfs_stage1_5 # .. GNU GRUB version 0.95 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub find /boot/loader (hd0,0,a) grub root (hd0,0) Filesystem type unknown, partition type 0xa5 grub root (hd0,0,a) Filesystem type is ufs2, partition type 0xa5 grub find /boot/grub/stage Possible files are: stage1 stage2 grub find /boot/grub/stage1 (hd0,0,a) grub setup (hd0) Checking if /boot/grub/stage1 exists... yes Checking if /boot/grub/stage2 exists... yes Checking if /boot/grub/ufs2_stage1_5 exists... yes Running embed /boot/grub/ufs2_stage1_5 (hd0)... failed (this is not fatal) Running embed /boot/grub/ufs2_stage1_5 (hd0,0,a)... failed (this is not fatal) Running install /boot/grub/stage1 (hd0) /boot/grub/stage2 p /boot/grub/menu.lst ... failed Error 29: Disk write error grub quit When I set up grub for the first time on this box I just edited menu.1st like so (this system boots fbsd, slackware and win2k, and I like a long timeout in case I'm away from the desk): # cat /boot/grub/menu.lst default=0 timeout=90 title FreeBSD 5.4-PR root (hd0,1,a) kernel /boot/loader title Slackware 10 root (hd2,0) kernel /boot/vmlinuz ro root=/dev/hdd1 title Windows 2000 Pro rootnoverify (hd0,0) makeactive chainloader +1 boot - jt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Misleading security message output
On Wed 13 Apr 05 19:59, Andrew Reilly [EMAIL PROTECTED] wrote: I had an interesting experience, this morning. The nightly security message from a CVS server machine that runs a version of FreeBSD-4 had arrived, and it claimed that someone who hadn't done any work for us for some considerable time had had three failed login attempts, late that night. Curious. After much hunting around, and checking perimeter logs, it turned out that nothing of the sort had happened. The security log script had been fooled by the age of the messages.0.gz file, which contained messages from more than a year ago. The search pattern $yesterday doesn't contain a year, because log file timestamps don't contain years. The log file was so old because rotation is determined by size, and this machine simply doesn't have much to log, despite being used daily. It never goes down, and is basically completely stable. Well, you could modify /etc/newsyslog.conf, where it says: /var/log/messages 600 14100 * J change it to: /var/log/messages 600 14*@T00 J This assumes you want 14 message logs, rotated once a day at midnight. Any message logs over 14 days will be deleted. man newsyslog.conf This could be avoided, perhaps, with a NetBSD-style backup/diff mechanism, or (incompatibly) with daemontools/multilog-style 64-bit time stamps in the log files. It can be worked-around by forcing faster log-file rotations, now that I know about the problem. I can't think of a really good widely-applicable solution, using the existing framework, though. I'm not quite sure what you mean. Do you want a way to have the timestamp record the year as well, so that you can keep the default setting? - jt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Flash player sound solution
On Saturday 12 March 2005 05:42 am, James McNaughton [EMAIL PROTECTED] wrote: The Problem: Using native Mozilla and linuxpluginwrapper/linux-flashplugin (on 4.10-stable et al) to view flash content results in no sound and occasional Mozilla freezes. The Solution: Run esd. How: I was searching the web for the solution, and got nowhere. There didn't seem to be anyone who had gotten it to work. Linux mailing lists noted a problem with file permissions on /dev/snd or /dev/pcm* depending on the sound system drivers installed. My /dev/pcm* file permissions were all rw to begin with, so this didn't help. I wondered what device the plugin was actually trying to access, so I did strings /usr/local/lib/linux-flashplugin6/libflashplayer.so and found /dev/dsp and /dev/mixer. Nearby in the list I noticed a few lines relating to esd. From a command line I started esd and went back to view some content that had previously frozen Mozilla, and there was sound coming out my speakers and the browser did not hang. I had long suspected the browser hangs were related to sound in the flash content. My results seem to confirm that suspicion. Do you have an example (or two or more) of a page that causes the crash? I'd like to test this on 5.3-R. I know I used to have an email around here somewhere with examples ... - jt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Beastie
On Monday 29 November 2004 02:21 pm, secmgr [EMAIL PROTECTED] wrote: Michael Nottebrock wrote: Hanspeter Roth wrote: The problem here is, that the Beastie picture is disabled by default. This is obviously not compatible with the majority of people. You're not up-to-date with the latest events, the beasty menu was completely nuked from CVS yesterday after the most recent complaints and we're now stuck again with the plain old loader prompt. Why nuke the menu? I can understand (although not agree with) taking out beastie, but the menu was handy, and added useful (to me at least) functionality. Is there some way to tweak it back in? Is there any way to keep it the way it was? I like it just fine, and it seems to me that the majority of users like it or don't care. Wouldn't it be more practical to provide an alternate menu without the logo for delicate sensibilities? As far as the question of the logo itself, no, FreeBSD doesn't *need* a logo, but it does actually help provide recognition. If a few people are offended by it, not much you can do, except perhaps provide a logo-free menu, if people think that's really necessary. Same thing happened with Procter and Gamble (http://www.google.com/search?q=procter+and+gamble+satan), as well as quite a few other companies and organizations. Honestly, you can't please everyone, and if an alternate menu is provided, then I'd imagine any complaints - and it seems just a few people are complaining about this irrelevant issue - would cease. - jt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
