Re: Stable does not boot after make buildworld, ... Was: HEADS UP! Always use the 'make buildkernel' target to make yerkernels
Christoph Sold wrote: IMHO, when big changes like aout-elf, or, recently, new tool chain tools make changes to the build process unavoidable, /prominent/ hints for stupid stable-only-readers like me should be placed everywhere*) -- in case of aout-elf, I was warned, so that went through. This time I plainly missed the warnings. rant This situation has been mishandled from the very beginning. People did the changes to current, where people are expected to be able to handle such things, and never really went back to make the situation acceptable for -stable users when -current became 4.x-stable. I warned, but people don't heed warnings, they heed patches. shrug /rant Sorry this caused you trouble. The instructions ought to be corrected, IMHO. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "There is no spoon." -- Kiki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! Always use the 'make buildkernel' target tomake your kernels
Brad Knowles wrote: At 1:29 PM +0200 2000/7/11, Peter van Heusden wrote: My only (minor) concern, from a useability point of view, is that there is no default BUILDKERNEL value - shouldn't it default to GENERIC if nothing else is specified? That way you won't actually be able to do a 'buildkernel' without building a kernel. Hmm. Good idea. Until then, this needs to be mentioned in the documentation. Notice that KERNEL can be set from make.conf, and there is a default in there. Either it is commented out, or the complain just apply to the first time around, before running mergemaster. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] "There is no spoon." -- Kiki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Disk error and No /boot/loader
Roddie Hasan wrote: Booting above 8 Gb is not supported, due to BIOS problems. If you don't believe that, trying booting Windows above 8 Gb... :-) Understood - But why would it have worked with 3.4 and the *exact* same configuration? (When I upgraded, I deleted the partition during install, and recreated it the same way). Perhaps you used boot0cfg to configure "packet mode" under 3.4, and forgot to repeat that step? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPL certainly doesn't meet Janis Joplin's definition of freedom: "Freedom is just another word for nothing left to lose." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Disk error and No /boot/loader
Booting above 8 Gb is not supported, due to BIOS problems. If you don't believe that, trying booting Windows above 8 Gb... :-) Alas, one developer had some interesting ideas on how to solve this problem recently. There is _unsupported_ options to make this work, but we can't activate them by default because not all hardware/firmware is compatible with it. Roddie Hasan wrote: Hi all, Running 4.0-STABLE (though I had the same issue in 4.0-RELEASE). I've got a 10 gig IDE Hard drive with two FAT32 paritions taking 2 gig and 6 gig, and then a 2.4 gig FreeBSD partition. /- 100 megs /var - 100 megs swap - 268 megs /usr - 1800 megs On bootup, I get the following: FreeBSD/i386 BOOT Default: 0:ad(0,a)? boot: /load /boot/loader Disk error 0x1 (lba=0xfc093c) No /boot/loader The system continues to boot /kernel automatically and runs fine from there. (I've patched the kernel per kern/17422 to get top, vmstat etc. working). For the record, /boot/loader *does* exist. I've read an explanation about the 1024 cylinder limit, but I used the exact same configuration with 3.4-STABLE and /boot/loader worked fine. Any assistance would be appreciated. Regards, Roddie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPL certainly doesn't meet Janis Joplin's definition of freedom: "Freedom is just another word for nothing left to lose." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sendmail.mc
Randy Bush wrote: /usr/src/etc/sendmail/freebsd.mc is what you are looking to replace. If you don't want future cvsup's to quash your changes you'll want to do a "chflags schg /usr/src/etc/sendmail/freebsd.mc" after you have copied the new one into place. yucchhy! [ but thanks ] is the assumption of the one-time build really that acceptable? Hey, wait a second! Why do you think SENDMAIL_CF exists? Just add it to your make.conf pointing to your own .cf file, and add the mc to the appropriate directory. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] GPL certainly doesn't meet Janis Joplin's definition of freedom: "Freedom is just another word for nothing left to loose." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: float-to-double core dump on 3.4R
Randall Hopper wrote:
#include float.h
main()
{
float f = FLT_MAX;
double d;
f = f * 2;
d = f;
}
Delete the "d=f" line and it doesn't core. Put it in and it does
(floating-point exception).
From this it appears there may be a bug in the float-to-double promotion
when f is Inf (or, at least I'd expect that f is Inf).
Any comments? If not, I'll file the PR.
Sure. If you delete the last line, the compiler will optimize away f = f
* 2, I bet. Try with -O0 (that's oh-zero :).
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
The size of the pizza is inversely proportional to the intensity of the
hunger.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: What does Voxware still supported in 4.0 mean exactly?
active developer exists. If a driver has no developers... While I can certainly appreciate the FreeBSD development team's desire for a more modern, unified and well-integrated driver than Voxware, until such time as it can provide the same functionality as the older driver, I do strongly believe that Voxware should continue to be supported, and that pcm still should be considered as an "experimental" option only. Yeah, well, you are right. Wait just a second while I remove support for Alpha and USB In addition, I really would like to see user control over PnP devices (via the pnp boot config command) brought back. It's just way too useful a thing to throw away altogether. There is nothing useful about it. That's not how PnP devices are supposed to work. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Compiler problems with -O2 (was Re: CVS Trouble, even under4.0-RELEASE (alpha) HELP!)
Charles Cox wrote: I would like to add that some of us who do a lot of numerically intensive programming, and that need to squeeze every last available cycle out of our CPU's would really appreciate having -O2 available for userland programs. To me, getting rid of the -O2+ switch would be like outlawing cars because someone had a really bad car accident. Just like driving a car, using gcc and the -O2 switch safely are the USER's responsibility. Having said this though, I do fully support having comments in make.conf, and documentation elsewhere that cautions against compiling a kernel with -O2. Whatever. Remember, though, that compiling with -O2 *WILL* result in bad code. It's not that someone had an accident. Is that the breaks don't work one time out of five. Just wait your turn... -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: dangerously dedicated
"Brandon D. Valentine" wrote: On i386 machines this is usually something lame like: NO ROM BASIC SYSTEM HALTED despite the fact that no machine has included a ROM BASIC since the last of the IBM PS/2 386s came out. However most of the BIOSes until *very* recently still contained code that would check for a ROM BASIC after searching the entire drive list and try booting from that. Now if only we could convince them to put that back in except have it look for a forth interpreter in ROM. Nah, that's the wrong approach. The right approach is for that BIOS *be* written in Forth to begin with. OpenBoot, anyone? :-) -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP: 3.x - 4.0-STABLE upgrade instructions
Warner Losh wrote: When I tried the installkernel it installed things as /YOUR_KERNEL_HERE I'll have to update things. Well, for people who like to build multiple kernels like me, the above works... :-) Alas, I have kernel="/DCS" in my /boot/loader.conf. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Parallel port in GENERIC (Was FreeBSD 3.4 and printing)
Kazutaka YOKOTA wrote: It's fine that GENERIC is used for installation. But, GENERIC is supposed to be for "generic" use, in which more people are expected to use the parallel port for printing than for PLIP. I would suggest the parallel port should be configured with the "tty" mask in GENERIC. The kernel for the install floppy can change it to the "net" mask; the kernel configuration file for the install floppy is generated from GENERIC by modifying bits and pieces anyway. Go talk to the Release Engineer. I don't make this kind of decisions. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Parallel port in GENERIC (Was FreeBSD 3.4 and printing)
"Jordan K. Hubbard" wrote: I really don't like special-casing this for the installation. There's got to be a more technically correct solution for this and I urge you guys to pursue it. :) Jordan, might I remind you that this is a volunteer project, and nobody with the right skills and appropriate knowledge seems to be concerned enough to spend hours working out a fix for a problem that can be solved changing a "net" to a "tty" on the kernel configuration file? Might I then point out that not being able to print out-of-the-box is a major violation of the POLA, and has direct impact on FreeBSD's reputation? No? Oh, well, I tried. :-) -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: JFS
Cy Schubert wrote: Due to the lack of interest, FreeBSD's LFS has fallen into disrepair over the years. With the implementation of softupdates in FreeBSD I don't think there is any need for LFS any more. Repeat that over and over the next time you wait fsck finish a 40 Gb filesystem checkup, and see if you manage to convince yourself of that. Read the CVS logs and tell me how you could interpret the comments any differently: 1.21 Fri Jan 30 11:33:40 1998 UTC by phk CVS Tags: HEAD Diffs to 1.20 FILE REMOVED Retire LFS. If you want to play with it, you can find the final version of the code in the repository the tag LFS_RETIREMENT. If somebody makes LFS work again, adding it back is certainly desireable, but as it is now nobody seems to care much about it, and it has suffered considerable bitrot since its somewhat haphazard integration. R.I.P Obviously you don't know what you're talking about either. Do you? I do know. The main reason why LFS was never updated isn't that it was made obsolete by softupdates, as claimed above, but that it was made obsolete by JFS. Why work on LFS if it is not up to a JFS? Unfortunately, the people who have to suffer enourmous waits after crashes usually have way more to do, even if they have the skills to fix LFS. With the disks getting bigger and bigger, this is due to change. BTW, NetBSD is happy with _their_ _functional_ LFS. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: More than just logging, Re: JFS
Alfred Perlstein wrote: Bad news: people running depending on _only_ logging are kidding themselves. Yeah. Funny how they have been doing so without getting bitten, eh? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Temperature Findings
Ted Sikora wrote: The voltage readings by the winbond IC in the bios are accurate. The case temperature was 5F cooler than reported. So I would conclude the readings from the bios are a fairly accurate representation of the machines current condition. Was this tested with both Linux (or an UP kernel) *and* FreeBSD 3.4R? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Nice try, Lao Che." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Installworld fails repeatedly
"¶³¹q¤§· Michael Wu" wrote: When I do make -j4 installworld, I keep getting the following error: installworld target is not paralelizable (sp?). -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: easyboot far into disk
Roelof Osinga wrote: 1) boot the installation disks until sysinstall comes up. 2) select the Fixit option (the one that mentiones a shell, y'know) on the main menu. Alas, won't work. Root is most definitely not the root on the hard disk. You can do thing within the fixit environment but not much else. Also the fixit option is part of the installation menu. A menu that when you exit it reboots the machine. mount wd0a /mnt? Is it too much typing for you? This is more a leven I can relate too g. Actually I'm going to try another tack. I wiped the disk and will now see if I can get it to install, and boot, using raw geometry. This by creating two partitions. The first small enough to reside in first 1024 cyls, holding but one slice with the root partition. The other covering the rest of the disk and containing the rest of the usual slices. You mean two _slices_, one on the first 1024, and the other at the end of the disk containing the usual _partitions_ (FreeBSD terminoloy -- not getting religious here, just clarifying)? This is a common work-around. Theoretically it ought to work. The question is is the install flexible enough to allow one to create multiple partitions as well as the needed slices within those partitions. AFAIK, it should be relatively trivial. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: easyboot far into disk
Roelof Osinga wrote: "Daniel C. Sobral" wrote: mount wd0a /mnt? Is it too much typing for you? And then they tell *me* to stop being sarcastic! HAH! Since when, pray tell, does root reside below mnt? /me sighs mount wd0a /mnt mount /mnt/dev/wd... /... chroot /mnt You mean two _slices_, one on the first 1024, and the other at the end of the disk containing the usual _partitions_ (FreeBSD terminoloy -- not getting religious here, just clarifying)? This is a common work-around. Nope, I mean two *partitions*. You see, *I* did RTFM. FYI what you suggest is nonsense. Won't work since that is not the way things work. Would work in, say, Linux, not in FreeBSD. Nor, I think but it's been awhile, in OpenBSD. Sure it works. Eg: First slice: FreeBSD on low cylinders Second slice: Other Operating System Third slice: FreeBSD on high cylinders mount /dev/wd0s1a / mount -t whatever /dev/wd0s2 /otheroperatingsystem mount /dev/wd0s3f /usr mount /dev/wd0s3... ... -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problem adding aic driver to kernel
"Lowkrantz, Goran" wrote: What does the following text in the release notes mean in the current context? [snipp] The following drivers were supported under the old SCSI subsystem, but are NOT YET supported under the new CAM SCSI subsystem: [snipp] I would interpret this as I can get them working somehow in 3.3R. Huh? What part of "NOT YET supported" don't you understand? Now, I *hate* not having AIC support, as it prevents me from having X and a cvs tree in my computer, but the statement looks pretty clear to me. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problem adding aic driver to kernel
"Lowkrantz, Goran" wrote: Just as a note, there is not a word in the release notes that the old SCSI and the CAM SCSI can't exist at the same time on the same machine. If CAM is the only SCSI subsystem that can live on a 3.x system, I would say that all the cards that use a driver not available in CAM is not supported on a FreeBSD 3.x. Then they should not be in the list of supported cards. The way I interpret the word supported, if something is supported in an operating system, it works. Feel free to have any other interpretation but then it's marketing. This information is there so that people who have one of these cards can find that it is no longer supported. If we kept silent, people would try to upgrade systems that rely on non-supported hardware just because it was previously supported. It was wishful reading on your part. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Cdrecord problems to record 1 CD
nn is a track number . pregap info cdrecord -blank=fast -audio -useinfo audio*.wav -blank=fast blanks your CD-RW for CD-R don't include this command -audiosets audio cd recording -useinfo use the pregap info generated by cdd2wav *.inf files Issues: In the list there was an exchange of using the tool team for buffering vs cdrecord's own buffering scheme: "Another possibility, if you have the RAM, is to use the team(1) program (it's in the ports) to buffer the data as it goes to the burner. You basically put it into the pipeline between mkisofs and cdrecord, and it buffers up to 5MB in memory (default, adjustable). Of course, you've got to have enough RAM to not go into swap during the operation. It's a very nice program, and I've been told that, with enough memory (32-64MB), you can be running X11 and compiling programs while the CD is burning (this is with a 2X burner, though)." "It should be noted that the 'cdrecord' program implements a FIFO itself, and you can specify the size. The default is 2MB. cdrecord uses a shared memory segment and forks so the process buffering the data is made independant of the buffer draining it. Modern CD writers usually have 1-2MB of buffer internally. The newer Yamahas, for example, have 2MB. So right off the bat we have around 4MB. Still, when you are writing at 600KB/sec it is possible to get behind if the filesystem you are building has lots of small files. Apart from writing the mkisofs output to a file, the easiest solution is to tell cdrecord to burn at a slower rate - e.g. 1x or 2x instead of 4x or 6x. Possible Problem and we need clarification And to head off another question: When you are recording to a CD-RW you can do a 'quick erase' of the media using 'cdrecord blank=fast'. This does not actually erase the data, so if you have used say 100MB you will only have 550MB left. You can actually erase the media using 'cdrecord blank=all', which takes a while. In my experience, this is not true. I have used blank=fast on a CDRW that has over 500 MB written, and then written another 500 MB without a problem. I have the same experience. Maybe someone into the physics of the media can explain what the pros-cons are as far as the media itself is concerned? Hardware : Yamaha CRW6416sz scsi 2 internal cd recorder I bought the Yamaha CRW6416sz scsi 2 iternal because it is somewhat cheap and reliable . You can buy one at CompUSA for $300. Reported scsi CD recorders which work and by no means this list is not exhaustive rather is nice to know from a FreeBSD user that it works on their boxes. 1. JKH swears by his Smart and Friendly Rocket Recorder scsi cd recorder 8) Honest is probably a good drive because JKH burns quite a few CDs. 2. Plextor scsi recorders 4x and 8x good recommendation from the list. 3. Philips CDD-3600 CDRW drive 4. Yamaha 4416 scsi recorder known to work on FreeBSD, Linux, SCO, HP/UX, and NT 5. Yamaha 6416sz scsi cd recorder. Hidetoshi Shimokawa [EMAIL PROTECTED] reported: I bought DVD-RAM drive for $400. 5.2GB(double side) media is around $35, you can use them as 2.3GB x 2 disks. Enabling raw-write in scsi_cd.c, you can newfs/mount DVD-RAM as UFS. Write speed is around 500KB/s, and read speed is around 1.4MB/s. Now this sounds like a very nice scsi cd recorder . Further input on DVD-RAM is welcome . -- Amancio Hasty [EMAIL PROTECTED] And now, for more stuff: From: Amancio Hasty [EMAIL PROTECTED] 08/19/99 04:09 Subject: CD writer : Baby Hacker II To: [EMAIL PROTECTED] 1. Modify cdrecord so that if a device is not specified it will do a -scanbus . Present the user with a choice of cd recorders from which to chose from . Ideally there should be a generic device query interface to the system so other similar utilities can do the same thing . 2. Create an LDAP schema to store the configuration for cdrecord. the entry should have: host , InetOrgPerson, cd recorder brand/model, device name, scsibus address, CD-R speed, CD-RW speed... I can provide a servlet which can manage the configuration of the LDAP server. If you are interested on LDAP see: http://www.openldap.org and/or send me email. 3. A bit more dificult. Create a shared library module out of cdrecord with an interface similar to netscape's plug-in . Pick a graphical utility for instance gcombust and interface it to the plug-in. 4. Pie in the sky: Do step 2 and use xml as your protocol . For instance , if an app such gcombust sents a status query to the plug-in its response should be encapsulated in xml : detailing the device , current status : recording/pause/playing/stop. Enjoy -- Amancio Hasty [EMAIL PROTECTED] -- Daniel C. Sobral(8-DCS)
Re: Cdrecord problems to record 1 CD
Michael Robinson wrote: Eliezer Rodriguez Gonzalez [EMAIL PROTECTED] ^^ I take this opportunity to say that the choice of downloading the first CD out of the 4 CDs set is very welcome for all of us uncapable of purchasing our own copies due to many reasons I won't explain here. This is so amazingly cool, I'm beside myself with glee. Viva el BSD Libre! The translation might be "gratis" instead of "libre", depending on your view. (If Linuxen, "gratis" is definitely more appropriate :). -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Signal 11 on 3.3 installation
Michael Endsley wrote: Mike, Here is what is happening. Here is what you are doing wrong when reporting it. When it catches sig 11, it shows a hole bunch of meaningless data, right? Well, this meaningless data is the stuff we use to trace bugs. Until you provide that information, we cannot do anything. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Interesting ways to print 3000 spaces...
"Jordan K. Hubbard" wrote: Um, has everyone here gone INSANE? We have a crash bug. It needs to be fixed. We DO NOT need to know how to print 3000 spaces in 11 different languages! :-) I concur. But if anyone wants to do it with loader, : 3kbl 3000 0 do bl emit loop ; 3kbl will do the trick. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] - Come on. - Where are we going? - To get what you came for. - What's that? - Me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 2.2.7 - 3.2 STABLE upgrade changes root password???
Shashi Joshi wrote: The password problem was my stupidity. I had tcsh as default shell for root. When I rebuilt in 3.2 elf format, it didn't rebuild tcsh since it is not part of basic system Damn, I forgot the most important question. Did you update /etc before rebooting? It *ought* to have worked, even with the old tcsh. While I have your attention, one thing that came up. I have a new Pentium III 450 , 378 MB 3 SCSI disk system with 3.2-stable updated. I worked with it for 2 months all fine. I moved 2GB worth tar files from old computer all fine. Then since 23rd Jul, I started doing daily backups from one FS to another. It starts around midnight. 3 times it reboot the system in the middle of the backup process (dump/restore and tars). Then once it hung up, no auto reboots. It had to be manually started. Then yesterday night it didn't respond to the monitor. Today the ISP staff started it again, I am yet to find their explanation of what thye found out. Is this a 3.2-release or -stable? This seems like a honest bug. We would like to trace that, if you could help us. Could you read the session on the handbook on kernel debugging, get a crash dump, and send us the backtrace? Also, more information is needed. From the above, it would seem that no network is involved. Can you confirm that? What is(are) the SCSI interface(s) you are using? What mount options are you using? Are you using softupdates? Is there any chance you may have run out of space/inodes/swap? Do these backups stop at random points? Are there any crashes at any other time? -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Is it true that you're a millionaire's son who never worked a day in your life?" "Yeah, I guess so." "Lemme tell you, son, you ain't missed a thing." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: comconsole
Doug wrote: [about boot -P] Hrrm... it works fine in /boot/loader.rc on -current, maybe it doesn't work in -stable. My apologies if so. If it works on -current, is by some magic trick. :-) I just checked the source, for the sake of it... Agreed, however there are two issues here. First, the man pages all say that /boot.config is deprecated. Also, what I'd *really* like to do is get a 'boot -P' in as early as possible, then still have the autoboot option in loader. As far as I can see, that's just not possible, although I'd love to be proven wrong. Options (as far as loader goes): load kernel -h or set console=comconsole Both will set up boot through the serial console, without interfering with normal working of autoboot. A -P in /boot.config is prefered, though, for the reasons Nordier gave. Wow where were you last week when I asked for a list like this. :-/ Could you add one more detail to this list, namely what config files get executed when in this schedule? It would be really helpful to me, and I'm sure others. I've read the man pages till I'm going loopy on them and it's sinking in very slowly, but not fully there yet. Patches to the man pages would be welcomed. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Would you like to go out with me?" "I'd love to." "Oh, well, n... err... would you?... ahh... huh... what do I do next?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: comconsole
Robert Nordier wrote: The loader "boot" command means "boot immediately", as documented in the help. The "autoboot" command means "boot after a delay", as documented in the help. They're mutually exclusive, so you're right: the way you want to do it is just not possible. For the record, it is. The flags passed through "boot" can also be passed through "load", as in "load kernel -h". Using loader.conf stuff, kernel_options="-h". boot2: /boot.config [For the sake of completeness...] loader: /boot/boot.4th /boot/loader.rc /boot/defaults/loader.conf /boot/loader.conf /boot/loader.conf.local kernel: /boot/kernel.conf The last one above, only if loaded by loader. And, then, any file of the type userconfig_script loaded will do. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "Would you like to go out with me?" "I'd love to." "Oh, well, n... err... would you?... ahh... huh... what do I do next?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
