RE: Upgrading FreeBSD to a new release
Ok, thank you all for response. As far as I see things now, the best way to upgrade from one stable release to the next is via source upgrade. Configuration files probably need some attention, because mergemaster cannot be run remotely. Upgrading from one major release to the next (4.x - 5.x) is practically not possible remotely, or at least _very_ difficult. Upgrade problems like the statd issue will not occur with stable branches. There is no other good way to upgrade remotely, is it? What about old files from the previous release? Will these be deleted properly with source upgrade? I've heard of occasional problems with old libraries lying around. Are there any efforts to improve the software managment in the base system? NetBSD for instance has once started a system-pkgsrc project (but does not seem to continue this), which I think is a great idea. Managing the system software with pkg_add and friends would be nice IMO. /Roman signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Upgrading FreeBSD to a new release
Hi list, One thing, that is making me _not_ using FreeBSD is, that I see no way to easily upgrade from, say 5.1 to 5.2 (just an example), over network. I mean, I have a server running, to which I have no physical access. The only way to maintain it, is over SSH. The upgrade instructions in INSTALL.txt suggest putting in the CD, and using sysinstall for a binary upgrade. That is no option for me. What I am looking for is an upgrade method which - can be used over an SSH connection - is not too difficult (like manually placing each piece in the right place) - does not leave old stuff on the HD (like the sysinstall method does, AFAIK) ... to make it short, something like the ports system (especially portupgrade) does with non-system apps would be cool. Is there a way to achieve that? This would be the one bit, which would make me switch to FreeBSD. /Roman signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Upgrading FreeBSD to a new release
Hi, One thing, that is making me _not_ using FreeBSD is, that I see no way to easily upgrade from, say 5.1 to 5.2 (just an example), .. Apart from that i updated my systems many times, without being in single user mode, with an ssh connection. This doesn't work on the upgrade to 5.2 from 5.1. You have to boot into single user mode to do the installworld. You have incompatible features at this upgrade. Exactly these kinds of hassles I don't want. I am wondering - FreeBSD has built such a nice thing like the ports system. It's a work of genius. Only that the install/upgrade process of the system itself is completely different (and not very convenient IMO). Is it not possible to 'port' the System stuff into the ports system (or a different ports system, say, the 'system ports' or something like that). Just an idea. Ok, are there other ways? Isn't there a script, which places the new archives over the old ones, and removes the stuff, that's left from the old system? Or is this a too-difficult task? /Roman signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Upgrading FreeBSD to a new release
Am Mo, den 07.06.2004 schrieb Kent Stewart um 0:03: On Sunday 06 June 2004 02:55 pm, Roman Kennke wrote: Hi, One thing, that is making me _not_ using FreeBSD is, that I see no way to easily upgrade from, say 5.1 to 5.2 (just an example), .. Apart from that i updated my systems many times, without being in single user mode, with an ssh connection. This doesn't work on the upgrade to 5.2 from 5.1. You have to boot into single user mode to do the installworld. You have incompatible features at this upgrade. Exactly these kinds of hassles I don't want. I am wondering - FreeBSD has built such a nice thing like the ports system. It's a work of genius. Only that the install/upgrade process of the system itself is completely different (and not very convenient IMO). Is it not possible to 'port' the System stuff into the ports system (or a different ports system, say, the 'system ports' or something like that). Just an idea. Ok, are there other ways? Isn't there a script, which places the new archives over the old ones, and removes the stuff, that's left from the old system? Or is this a too-difficult task? The problem with 5.1 5.2 is called statfs. See, /usr/src/UPDATING. It will run with a new kernel and not the old kernel. If you do an installworld before you do an installkernel, you have to use the fixit CD to fix it. For a while, they thought you had to do a clean install. Ugly. I am not too familiar with the internals of FreeBSD. But I really think, that in the long run, FreeBSD must have a more clever software managment for the system stuff. Something like 'apt-get dist-upgrade' comes to mind, or 'emerge -Ud world'. It should be possible to track what changes from one point release to the next one, and do most of the upgrade stuff automatically (excluding most configuration) and without a CD. Rebuilding the ports tree stuff after the upgrade is not the problem (because this is already managed in a very good way). All I want is not reinstalling the system after every few releases. The FreeBSD team should care about an possibility to easily upgrade from at least one point release to another. Only my suggestion. Best regards, Roman signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
DMA problem with DVD drive
Hi there, I am not able to enable DMA for my DVD drive. When I issue 'atacontrol mode 1 UDMA100 XXX' and access the drive, first the drive access hangs, and after a view seconds the machine locks up completely. This also hold true for all other DMA modes. I am running FreeBSD 5.2 on a Fujitsu-Siemens Amilo A Notebook. I would send more info about the ATA/IDE controller, and the error messages but I don't know, how to get to this info. BTW: I know that DMA works for this drive. I have got it working at least with linux 2.4.22, althought I also had alot of DMA problems with other versions, so I suspect the hardware (controller) is flakey. Any help is appreciated. Here follows some output from dmesg: moonlight# dmesg | grep ata atapci0: AcerLabs Aladdin UDMA100 controller port 0xa000-0xa00f at device 4.0 on pci0ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 28615MB FUJITSU MHR2030AT [58140/16/63] at ata0-master UDMA100 acd0: CDRW TOSHIBA DVD-ROM SD-R2212 at ata1-master PIO4 Ciao, Roman -- SOAP for Python http://interview-machine.com/soap/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DMA problem with DVD drive
Hi there, I am not able to enable DMA for my DVD drive. When I issue 'atacontrol mode 1 UDMA100 XXX' and access the drive, first the drive access hangs, and after a view seconds the machine locks up completely. This also hold true for all other DMA modes. I am running FreeBSD 5.2 on a Fujitsu-Siemens Amilo A Notebook. I would send more info about the ATA/IDE controller, and the error messages but I don't know, how to get to this info. BTW: I know that DMA works for this drive. I have got it working at least with linux 2.4.22, althought I also had alot of DMA problems with other versions, so I suspect the hardware (controller) is flakey. Any help is appreciated. Here follows some output from dmesg: moonlight# dmesg | grep ata atapci0: AcerLabs Aladdin UDMA100 controller port 0xa000-0xa00f at device 4.0 on pci0ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ad0: 28615MB FUJITSU MHR2030AT [58140/16/63] at ata0-master UDMA100 acd0: CDRW TOSHIBA DVD-ROM SD-R2212 at ata1-master PIO4 Ciao, Roman -- SOAP for Python http://interview-machine.com/soap/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA problem with DVD drive
I am not able to enable DMA for my DVD drive. I have a similar drive on my Toshiba Satellite A30-514 and to set UDMA mode on boot I have put the following line in /boot/loader.conf: hw.ata.atapi_dma=1 Here's the relevant part of dmesg output: acd0: CDRW TOSHIBA DVD-ROM SD-R2412 at ata1-master UDMA33 I also tried this. As well as hw.ata.ata_dma=1 no success with that. I suppose its a f***cked up controller. I think I have to go with Linux for things which need DMA, like DVD playback. Best regards, ROman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
