can't freebsd-update from 7.1-PRERELEASE
Hi, Apparently 7.1-PRERELEASE has been pulled from freebsd-update's server while I was being lazy: calvin% sudo freebsd-update --debug upgrade -r 7.1-BETA2 Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 7.1-PRERELEASE from update1.FreeBSD.org... fetch: http://update1.FreeBSD.org/7.1-PRERELEASE/i386/latest.ssl: Not Found failed. No mirrors remaining, giving up. Any workarounds? -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Desired behaviour of "ifconfig -alias"
* Oliver Fromme <[EMAIL PROTECTED]> [20070212 19:11]: > But you called it "confusing". That's just your personal > perception. It doesn't mean it is confusing to everybody. > In fact it might be useful to others. It _is_ useful to > me, for example, and I would object for that syntax to go > away. Also note that it doesn't hurt anybody. Until it appears on a system startup script that ends up dropping your connection (so, go fix rc.d/jail ...). qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sed and comma-delimited file
* SigmaX asdf <[EMAIL PROTECTED]> [20060919 18:31]: > I have a series of comma-delimited text files with fourteen columns of > data and several hundred rows. I want to use a short shell script to > strip them of the last 9 columns, leaving the same file but with just > five of its columns. I can do it in C++, but that seems like > overkill. How would I go about doing it with sed or a similar > utility? cut -d ',' -f 1-5 qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath(4) and 802.11g speed
* Damian Gerow <[EMAIL PROTECTED]> [20060309 00:12]: > # ifconfig ath0 media DS/54Mbps > ifconfig: unknown media subtype: DS/54Mbps > # DS/54 doesn't exist. Try OFDM/54Mbps instead. qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PXE Installation
* Karel Miklav <[EMAIL PROTECTED]> [20060120 03:34]:
> I tried to follow the spirit and did a PXE boot from the installation
> CD (6.0-RELEASE-i386-bootonly.iso) files. It started well, displayed
> the FreeBSD boot menu, listed devices, mounted NFS share and finally
> crashed with:
>
> Lookup of /dev for devfs, error 2
> init:not found in path ...
> panic: no init
>
> Please give me a hand, I'm playing with this for whole week.
I've succesfully installed PXE booting from the release discs. You need
to setup a TFTP server (which you probably already have), a DHCP server
and an NFS server. Details of my setup are:
#in dhcpd.conf
subnet 192.168.124.0 netmask 255.255.255.0 {
filename "/boot/pxeboot";
option root-path "192.168.124.1:/tftpboot";
next-server 192.168.124.1;
range 192.168.124.64 192.168.124.127;
}
515,p1,0$ grep ^tftp /etc/inetd.conf
tftpdgram udp waitroot/usr/libexec/tftpd tftpd -l -s
/tftpboot
506,p1,0$ ls -l /tftpboot
lrwxr-xr-x 1 root wheel 4 Oct 29 14:20 /tftpboot -> /mnt
507,p1,0$ mount |grep mnt
/dev/vn0 on /mnt (cd9660, NFS exported, local, read-only)
513,p1,0$ grep mnt /etc/exports
/mnt -alldirs -ro -network 192.168.124.0 -mask 255.255.255.0 192.168.124.1
With this setup I boot into the live CD, and from there I use the
install.sh scripts to copy the distribution.
qvb
--
pica
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Creating a system RAID-10 device
* Sven Willenberger <[EMAIL PROTECTED]> [20060117 22:06]: > over 3 mirror raid arrays that would encompass the entire filesystem > including the /boot and root partitions. > > Generally I would create a RAID10 from 6 disks as follows: > > gmirror label -v -b round-robin md1 da0 da1 > gmirror label -v -b round-robin md2 da2 da3 > gmirror label -v -b round-robin md3 da4 da5 > > gstripe label -v -s 131072 > md0 /dev/mirror/md1 /dev/mirror/md2 /dev/mirror/md3 > > newfs /dev/stripe/md0 > > naturally the problem here is that it cannot be done on a system that > booted from da0. I have seen the example of setting up a mirrored system > drive > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html ) > > which won't quite work for my case either. Using this method I could > probably get the one mirror (md1) to work, but I know of no way of then > adding the other 2 mirror sets and then redoing the system to stripe > across all 3 mirrored sets. Uhm. The problem is that you can't mount the root fs from a striped partition. Create an extra slice on each drive and either configure a 6-way mirror or a mirror-of-3-sripes to boot from. > The only thing I could think of was to boot from the livecd and create > the 6-disk array and then trying to install FreeBSD onto this > filesystem. In order to do this the installer would have to > recognize /dev/stripe/md0 as a valid "drive" -- is there any way to have > this happen? I don't believe sysinstall is smart enough, but you can always use the install.sh scripts on the distribution. However, the above still aplies. qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gvinum/vinum on 6.0
* Brian Szymanski <[EMAIL PROTECTED]> [20060111 13:01]: > >> But most importantly, gvinum configuration (at least for a raid-5 plex) > >> still doesn't persist across a reboot :( > > > > That's a bug; I think it might be related to compiling gvinum in the > > kernel > > as opposed to loading it from /boot/loader.conf. I also think there is a > > fix already commited to 6-STABLE. > > Hmm, I upgraded to 6-STABLE and I'm still having the problem. > > Here's basically how it happens: > gvinum create /etc/vinum.cnf > newfs /dev/gvinum/VOLUME > mount /dev/gvinum/VOLUME /mnt > #screw with /mnt, everything works and is happy, yay! > reboot > > At this point I call "gvinum l" (which loads geom_vinum.ko) by hand (after > the reboot). My configuration mostly seems to persist - except or the > "drives" section... I believe you don't have the proper STABLE version. I'm setting up a new system and after encountering the same problem I can currently reboot successfully and even mount / from vinum: gromit# dmesg |grep 'mount root' Trying to mount root from ufs:/dev/gvinum/std-root I'm using (long lines): gromit# ident /mnt/src/sys/geom/vinum/* | grep FreeBSD ident warning: no id keywords in /mnt/src/sys/geom/vinum/CVS $FreeBSD: src/sys/geom/vinum/geom_vinum.c,v 1.16.2.3 2005/12/10 14:36:17 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum.h,v 1.9.2.1 2005/11/26 11:06:11 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_drive.c,v 1.18.2.4 2005/12/10 14:36:17 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_init.c,v 1.10.2.1 2005/10/09 04:36:44 delphij Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_list.c,v 1.3 2005/01/06 18:27:30 imp Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_move.c,v 1.2.2.1 2005/11/26 11:06:11 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_plex.c,v 1.15.2.1 2005/08/19 08:48:04 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_raid5.c,v 1.10 2004/11/26 11:59:51 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_raid5.h,v 1.6 2005/01/06 18:27:30 imp Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_rename.c,v 1.3.2.1 2005/11/26 11:06:11 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_rm.c,v 1.6.2.3 2005/11/26 11:06:11 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_share.c,v 1.4 2004/11/15 12:30:59 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_share.h,v 1.2 2004/11/15 12:30:59 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_state.c,v 1.7 2005/01/21 18:27:23 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_subr.c,v 1.13 2005/01/19 13:57:09 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_var.h,v 1.8.2.1 2005/08/19 08:48:04 le Exp $ $FreeBSD: src/sys/geom/vinum/geom_vinum_volume.c,v 1.8.2.2 2005/10/09 04:35:42 delphij Exp $ qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Using jails and djbdns
* Tony Arcieri <[EMAIL PROTECTED]> [20050513 03:21]: > Is there some easy way to reverse this order, so svscan is started first and > jails started afterward? Follow the author's instructions, and put this line into /etc/rc.local: csh -cf '/command/svscanboot &' qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: updating from 5.2.1 to RELENG_5
* Phil Brennan <[EMAIL PROTECTED]> [20050401 12:19]: > Will it be ok just to cvsup, rebuild kernel and world, mergemaster, > (etc) like any normal update? Or do I have to do a reinstall? Read UPDATING (all of it). Read UPDATING (all of it). Did you notice the 20041001 entry? You should be able to use libmap.conf to work around it until you recompile all your ports. qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic on 5.3-STABLE w/ ACPI
* Admin @ InterCorner <[EMAIL PROTECTED]> [20050129 20:09]: > I have sent this message before (Wed, 19 Jan 2005 04:11:40 +0100), but > without respons. So I'll try again. You didn't provide enough info to help with ACPI debugging http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html and your questions on disabling acpi might be more appropiate in [EMAIL PROTECTED] Try the following: echo hint.acpi.0.disabled="1" >> /boot/loader.conf For details, man acpi, man loader.conf qvb -- pica ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mismatching vinum configurations
Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic way to recover the data? Most of the data is mirrored over da0 & da1, but I can't start any of the mirrored volumes (I get 'Drive is down') What should I do to access the mirrored volumes? tks -- pica ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (da0:ahc0:0:0:0): Unexpected busfree in Data-in phase and other weirdness
On Sat, Mar 01, 2003 at 12:50:31AM +0100, Joan Picanyol i Puig wrote: > Please have a look at the excerpt of kernel logs at > http://biaix.org/pk/debug/. messages.1.kernel shows what happened (look After a _long_ exchange of mails with [EMAIL PROTECTED] I found out that this drive Tags Queue is only 64 commands deep (I guess I could have found that but myself). Could this be related to the problem I am having? Would 'camcontrol tags 0:0 -N 64 fix it (it doesn't modify maxtags :o)? qvb -- pica To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
palm m500 and USB (was Re: Sony Cybershot ...)
* Greg 'groggy' Lehey <[EMAIL PROTECTED]> [20030311 01:00]: > There's a bug somewhere which stops pilot-link working with USB. I've > been talking to the author about it, and he's not very motivated to > fix it, particularly because we can't exclude the possibility that > the bug is in the USB stack. Well, I can only say I'll test any patch thrown at me... qvb -- pica To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Sony Cybershot should be in hardware notes (supported by umass)
* Doug Barton <[EMAIL PROTECTED]> [20030311 00:14]: > > > I think it's already covered by the statement "Owing to the generic > > > nature of most USB devices, with some exceptions any device of a given > > > class will be supported, even if not explicitly listed here." > > I can't sync my Palm m500 through USB even though the release notes say > > it's supported :(and yeah, it's detected, but of no use :() > I'm sorry to say I don't have a solution for you, but I'm curious. What > are you syncing it to, and what software are you using? I have a palm, and > the only useful sync stuff I've found is all windows based. Ideally, I'd sync it against Evolution through pilot-link, but it doesn't work. Searching the pilot-link archives will show you that the people there think it's FreeBSD's fault... qvb -- pica To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Sony Cybershot should be in hardware notes (supported by umass)
* Peter Jeremy <[EMAIL PROTECTED]> [20030310 21:12]: > I think it's already covered by the statement "Owing to the generic > nature of most USB devices, with some exceptions any device of a given > class will be supported, even if not explicitly listed here." I can't sync my Palm m500 through USB even though the release notes say it's supported :(and yeah, it's detected, but of no use :() qvb -- pica To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: (da0:ahc0:0:0:0): Unexpected busfree in Data-in phase and other weirdness
* Andre Albsmeier <[EMAIL PROTECTED]> [20030306 15:32]: > On Sat, 01-Mar-2003 at 10:49:34 +0100, Francesco Casadei wrote: > (I assume the cabling/termination has been checked already.) Yep, I also run the controler's BIOS drive check on the drives. > I had bus problems with my DNES until I upgraded the firmware to: > > da2: Fixed Direct Access SCSI-3 device > > In general, I have often seen bus problems when a lot of different > devices are hanging on the same SCSI bus and some drives are being > hit really hard. That could be my case: 2 drives 1 cdrw, cd burning and compiling (if that qualifies as 'really hard'. > I have written a program to upgrade the firmware on IBM and Plextor > (and some other devices) under FreeBSD in case you are interested... Does it work for Seagate drives? (20:29:52 <~>) 0 $ camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 2 lun 0 (pass1,cd0) at scbus0 target 6 lun 0 (pass2,da1) qvb -- pica To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
