RE: Daily FreeBSD updates (was: Re: priority on rc script caused panic)
> >>From: Giorgos Keramidas <[EMAIL PROTECTED]> >>To: pura life CR <[EMAIL PROTECTED]> >>CC: [EMAIL PROTECTED] >>Subject: Daily FreeBSD updates (was: Re: priority on rc script caused >panic) >>Date: Tue, 20 Jul 2004 10:57:24 +0300 >> >>On 2004-07-19 10:58, pura life CR <[EMAIL PROTECTED]> wrote: >> >Giorgos Keramidas <[EMAIL PROTECTED]> wrote: >> >> I regularly (almost daily) upgrade my CURRENT installation and >the >> >> set of commands I use when the single user shell fires up is: >> >> >> >> adjkerntz -i # allow system time updates to work >> >> swapon -a # enable all swap partitions >> >> fsck -p # check any filesystems that need it >> >> mount -u / # remount root fs as read-write >> >> mount /usr # mount /usr as read-write >> >> >> >> cd /usr/src # upgrade sequence >> >> make installworld # - // - >> >> mergemaster # - // - >> > >> > This should not be done. >> > >> > You dont really need to upgrade daily, you are just overloading >freebsd >> > cvsup servers. >> >>That's not true... >> >>I'm running FreeBSD 5.2-CURRENT. Keeping a local CVS mirror which is >>updated once a day and test build/run on my machine is the least I >can >>do to help in testing the -CURRENT branch. The mirror I use is the >one >>that is closest to me (cvsup2.gr.freebsd.org). > >[snip] > >My comment is still applicable. If you just run a cvs mirror, >just fetch the source code. You dont need to test to know whether if >compiles or not. I think noone really helps to freebsd by compiling >the source code every day looking for errors. Maybe I'm way off here because I do not do any such testing as Giorgos suggests, but how are the developers supposed to supply patches for problems if -CURRENT builds are in fact not built, and build-errors not found? I would think that it would be easier to mirror the tree, and build daily/weekly etc to find build errors than it would be to review the source code line-for-line to find the bugs. > It is better to test and >contribute code. How do you suggest testing without building? I believe that Giorgos is suggesting that *is* what he is doing...building, locating bugs, fixing (contributing/committing code). Could someone with more experience clarify this? This is quite a confusing thread. Steve > > > _ > >MSN Amor [1]Busca tu ½ naranja > > References > >1. http://g.msn.com/8HMBES/2752??PS=47575 > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Daily FreeBSD updates (was: Re: priority on rc script caused panic)
>From: Giorgos Keramidas <[EMAIL PROTECTED]> >To: pura life CR <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED] >Subject: Daily FreeBSD updates (was: Re: priority on rc script caused panic) >Date: Tue, 20 Jul 2004 10:57:24 +0300 > >On 2004-07-19 10:58, pura life CR <[EMAIL PROTECTED]> wrote: > >Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > >> I regularly (almost daily) upgrade my CURRENT installation and the > >> set of commands I use when the single user shell fires up is: > >> > >> adjkerntz -i # allow system time updates to work > >> swapon -a # enable all swap partitions > >> fsck -p # check any filesystems that need it > >> mount -u / # remount root fs as read-write > >> mount /usr # mount /usr as read-write > >> > >> cd /usr/src # upgrade sequence > >> make installworld # - // - > >> mergemaster # - // - > > > > This should not be done. > > > > You dont really need to upgrade daily, you are just overloading freebsd > > cvsup servers. > >That's not true... > >I'm running FreeBSD 5.2-CURRENT. Keeping a local CVS mirror which is >updated once a day and test build/run on my machine is the least I can >do to help in testing the -CURRENT branch. The mirror I use is the one >that is closest to me (cvsup2.gr.freebsd.org). [snip] My comment is still applicable. If you just run a cvs mirror, just fetch the source code. You dont need to test to know whether if compiles or not. I think noone really helps to freebsd by compiling the source code every day looking for errors. It is better to test and contribute code. _ MSN Amor [1]Busca tu ½ naranja References 1. http://g.msn.com/8HMBES/2752??PS=47575 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Daily FreeBSD updates (was: Re: priority on rc script caused panic)
On 2004-07-19 10:58, pura life CR <[EMAIL PROTECTED]> wrote: >Giorgos Keramidas <[EMAIL PROTECTED]> wrote: >> I regularly (almost daily) upgrade my CURRENT installation and the >> set of commands I use when the single user shell fires up is: >> >> adjkerntz -i # allow system time updates to work >> swapon -a# enable all swap partitions >> fsck -p # check any filesystems that need it >> mount -u / # remount root fs as read-write >> mount /usr # mount /usr as read-write >> >> cd /usr/src # upgrade sequence >> make installworld# - // - >> mergemaster # - // - > > This should not be done. > > You dont really need to upgrade daily, you are just overloading freebsd > cvsup servers. That's not true... I'm running FreeBSD 5.2-CURRENT. Keeping a local CVS mirror which is updated once a day and test build/run on my machine is the least I can do to help in testing the -CURRENT branch. The mirror I use is the one that is closest to me (cvsup2.gr.freebsd.org). I don't think that this can be called "overloading" the CVSup servers. If you *do* think that it's an overkill, perhaps you should explain why you think this is so and why the tests I'm privately doing of -CURRENT are so completely and utterly worthless that they're considered overkill, overload or anything else similarly redundant :-P > Also, why to make all the source tree if you just get few modifications > per day? It would be wise to know what part or the tree was updated and > just compile it or let the whole compilation for later. Because this is the recommended way of building everything to see how it fits together. The "make buildworld" target is what the end-user will see when they try to build FreeBSD 5.X one day. If this is broken, a full build is going to catch it very quickly. There are times -- i.e. when I'm preparing patches to a particular part of the source tree -- that I build only parts using the Makefiles of the proper SUBDIRs. These are special purpose builds though and I know when or why I'm doing a partial build. > If you want to see your machine working at 100% cpu, learn prolog. Spare me the irony, please. I don't need it. The list doesn't need it. I was trying to contribute to the thread in a positive manner, showing an example of commands that can be used to bring a FreeBSD system from single user mode up to the point where all the disks are mounted and real work can be done. If you have nothing positive to add to the discussion or you haven't spotted something wrong in what I wrote and feel like correcting me, I'd be glad if you didn't make bad-tempered jokes about it all. Regards, Giorgos PS: I would appreciate it very much if you posted in plain text and not in the HTML-only format that Hotmail defaults to. Thanks... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: priority on rc script caused panic
>From: Giorgos Keramidas <[EMAIL PROTECTED]> >To: Henrik W Lund <[EMAIL PROTECTED]> >CC: pura life CR <[EMAIL PROTECTED]>, [EMAIL PROTECTED] >Subject: Re: priority on rc script caused panic >Date: Mon, 19 Jul 2004 13:43:24 +0300 > >On 2004-07-19 11:34, Henrik W Lund <[EMAIL PROTECTED]> wrote: > > pura life CR wrote: > > > I added a process with high priority (nice -20) to be loaded each time > > > system boots. It is located in /usr/local/etc/rc.d. > > > > > > Apparently, the process consume too much cpu time which make it > > > imposible to log in. > > > > > > I cant do anything from the boot loader, because i cant cd to /usr to > > > remove the script. > > > > Have you tried this? > > > > 1. When the countdown starts, right after the BTX loader has > > finished, press any key other than for the prompt. > > 2. Type boot -s to boot into single user mode. > > 3. When asked for a shell for root, hit (this will give you > > the sh shell). Alternatively, type /bi n/csh, then . This > > will give you the C shell, and tab completion. Essential if you are > > to do much of anything, IMO. > > 4. fsck -y > > 5. mount /usr > > 6. Do whatever it is you want to do in /usr, and reboot. > > > > You may have to provide the absolute paths for fsck and mount, I > > don't recall at the moment if PATH is set in single user mode. > >You don't need to fiddle with the PATH. It's set to a reasonable >default that can be used even for upgrading the system with the >"make installworld" procedure. > >I regularly (almost daily) upgrade my CURRENT installation and the set >of commands I use when the single user shell fires up is: > > adjkerntz -i # allow system time updates to work > swapon -a # enable all swap partitions > fsck -p # check any filesystems that need it > mount -u / # remount root fs as read-write > mount /usr # mount /usr as read-write > > cd /usr/src # upgrade sequence > make installworld # - // - > mergemaster # - // - This should not be done. You dont really need to upgrade daily, you are just overloading freebsd cvsup servers. Also, why to make all the source tree if you just get few modifications per day? It would be wise to know what part or the tree was updated and just compile it or let the whole compilation for later. If you want to see your machine working at 100% cpu, learn prolog. > >The last three commands update the system from the compiled object >files under /usr/obj. The commands up to the command that mounts /usr >are more or less necessary to have a system that includes a read-write >root fs and the tools required for the upgrade to work. > >-- >Giorgos Keramidas keramida (at) freebsd (dot) org >FreeBSD: The Power to Serve http://www.FreeBSD.org/ _ Consigue aquí las mejores y mas recientes ofertas de trabajo en América Latina y USA: [1]Haz clic aquí... References 1. http://g.msn.com/8HMBES/2743??PS=47575 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: priority on rc script caused panic
> > pura life CR wrote: > > > Hi. > > > > I added a process with high priority (nice -20) to be loaded each time > > system boots. It is located in /usr/local/etc/rc.d. > > > > Apparently, the process consume too much cpu time which make it > > imposible to log in. > > > > I cant do anything from the boot loader, because i cant cd to /usr to > > remove the script. > > > > Any suggestion?. > > > > The system is on a virtual machine. > > > > thanks. > > > > eugene tooms. > > > > > Greetings! > > Have you tried this? > > 1. When the countdown starts, right after the BTX loader has finished, > press any key other than for the prompt. > 2. Type boot -s to boot into single user mode. > 3. When asked for a shell for root, hit (this will give you the > sh shell). Alternatively, type /bin/csh, then . This will give > you the C shell, and tab completion. Essential if you are to do much of > anything, IMO. > 4. fsck -y mount -u / > 5. mount /usr > 6. Do whatever it is you want to do in /usr, and reboot. > > You may have to provide the absolute paths for fsck and mount, I don't > recall at the moment if PATH is set in single user mode. First, I am not sure what you mean by 'virtual machine'. That may throw a monkey wrench in things if it means that literally. But, the main thing I would add is before you do the mount /usr you probably want to cause root to be remounted read/write so you can edit rc.conf. To do this, do mount -u / (or even just mount -a I think will cause it to happen nowdays) Otherwise root will be mount read only and you won't be able to change rc.conf jerry > > Hope this helps! > -Henrik W Lund ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: priority on rc script caused panic
On 2004-07-19 11:34, Henrik W Lund <[EMAIL PROTECTED]> wrote: > pura life CR wrote: > > I added a process with high priority (nice -20) to be loaded each time > > system boots. It is located in /usr/local/etc/rc.d. > > > > Apparently, the process consume too much cpu time which make it > > imposible to log in. > > > > I cant do anything from the boot loader, because i cant cd to /usr to > > remove the script. > > Have you tried this? > > 1. When the countdown starts, right after the BTX loader has > finished, press any key other than for the prompt. > 2. Type boot -s to boot into single user mode. > 3. When asked for a shell for root, hit (this will give you > the sh shell). Alternatively, type /bi n/csh, then . This > will give you the C shell, and tab completion. Essential if you are > to do much of anything, IMO. > 4. fsck -y > 5. mount /usr > 6. Do whatever it is you want to do in /usr, and reboot. > > You may have to provide the absolute paths for fsck and mount, I > don't recall at the moment if PATH is set in single user mode. You don't need to fiddle with the PATH. It's set to a reasonable default that can be used even for upgrading the system with the "make installworld" procedure. I regularly (almost daily) upgrade my CURRENT installation and the set of commands I use when the single user shell fires up is: adjkerntz -i# allow system time updates to work swapon -a # enable all swap partitions fsck -p # check any filesystems that need it mount -u / # remount root fs as read-write mount /usr # mount /usr as read-write cd /usr/src # upgrade sequence make installworld # - // - mergemaster # - // - The last three commands update the system from the compiled object files under /usr/obj. The commands up to the command that mounts /usr are more or less necessary to have a system that includes a read-write root fs and the tools required for the upgrade to work. -- Giorgos Keramidas keramida (at) freebsd (dot) org FreeBSD: The Power to Serve http://www.FreeBSD.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: priority on rc script caused panic
pura life CR wrote: Hi. I added a process with high priority (nice -20) to be loaded each time system boots. It is located in /usr/local/etc/rc.d. Apparently, the process consume too much cpu time which make it imposible to log in. I cant do anything from the boot loader, because i cant cd to /usr to remove the script. Any suggestion?. The system is on a virtual machine. thanks. eugene tooms. Greetings! Have you tried this? 1. When the countdown starts, right after the BTX loader has finished, press any key other than for the prompt. 2. Type boot -s to boot into single user mode. 3. When asked for a shell for root, hit (this will give you the sh shell). Alternatively, type /bi n/csh, then . This will give you the C shell, and tab completion. Essential if you are to do much of anything, IMO. 4. fsck -y 5. mount /usr 6. Do whatever it is you want to do in /usr, and reboot. You may have to provide the absolute paths for fsck and mount, I don't recall at the moment if PATH is set in single user mode. Hope this helps! -Henrik W Lund ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
priority on rc script caused panic
Hi. I added a process with high priority (nice -20) to be loaded each time system boots. It is located in /usr/local/etc/rc.d. Apparently, the process consume too much cpu time which make it imposible to log in. I cant do anything from the boot loader, because i cant cd to /usr to remove the script. Any suggestion?. The system is on a virtual machine. thanks. eugene tooms. _ MSN Amor [1]Busca tu ½ naranja References 1. http://g.msn.com/8HMBES/2740??PS=47575 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
