Re: pw
On Tue, Jun 04, 2013 at 01:47:55AM +, gs_stol...@juno.com wrote: > > > > NetZero now offers 4G mobile broadband. Sign up now. > http://www.netzero.net/?refcd=NZINTISP0512T4GOUT1 > > I have 2 FreeBSD systems (they are using versions 4.3 and 4.7 of the > FreeBSD Operating System) that I have not used for a long time, and I have > forgotten their passwords. I have information on these systems that I want > to retrieve but I have not been able to log into these Systems. My problem > was put on the internet several years ago and the usual ways of getting into > the systems (basically by being the operator) were suggested and tried, > unsuccressfully. A friend and I discussed my problem and he suggested that I > zero out the root password so that I can get in as rooy (to set a new > password and then continue operating as root). > Does the FreeBSD community have a program (either on a floppy or a CD > ROM, preferably the latter) that can do this? If not, I suggest that you > write one that would work with all the (formats of) password files that have > ever been used. If it can determine the format of password files just by > examining them, that would be fine. If it can't, then it should ask the user > in which version of the FreeBSD Operating System the password file was used, > try to verify it by the structure of the password file and if it is verified > make a copy of the password file (in case something goes wrong, so that the > system can be restored to its original condition and so undo anything that > this program has done), and zero out the root password. After this is done, > one could log in as root to set the root password and afterwards (as root) > set other user passwords. > > Operating Systems that have ever been run. > You could set it up to look Hello, You can follow the steps detailed here[1] to reset your root password. [1]: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#idp75977264 Regards. Victor. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FreeBSD has serious problems with focus, longevity, and lifecycle
On Mon, Jan 16, 2012 at 02:28:09PM -0800, John Kozubik wrote: > > Friends, > > I was disappointed to see that 8.3-RELEASE is now slated to come out in > March of 2012. This will be ~13 months since 8.2-RELEASE and is typical > of a trend towards longer gaps between minor releases. > > I also see that undercutting the current release before wide deployment > and maturity is continuing. 7.0 came (barely) after 6.3, which was bad > enough, but not as bad as 8.0 arriving with 7.2, and now 9.0 with 8.2. > > Finally, the culture of "that's fixed in CURRENT" or "we built those > changes into (insert next major release)" continues to get worse. It's > difficult to escape the notion that FreeBSD is becoming an operating > system by, and for, FreeBSD developers. > Hello John, With my sysadmin hat on i can echo your feelings, but i guess that your proposals are more focused on a company environment than a collaborative environment. First i would like to remember the last stage of FreeBSD 4.x for those people (not you) who are arguing in the thread about long "stable" releases. Those of us who used FreeBSD 4.x on the late release cycle will remember a few of this problems: - New hardware didn't work because no ACPI support was in 4.x until 4.11 or 4.12 (can't remember). Even then, it was considered a bad idea to backport it because it was a huge change for a -STABLE branch. - Because SMPng project involved a lot of changes, it was not easy to backport drivers. - SMP performance was horrible. As libc_r was the only option on 4.x you got various performance and stability problems with apps designed for a better threading model. A good example is MySQL performance. At that time started the whole "mysql performance issues of FreeBSD vs linux" that last until today. - Porting some new apps was troublesome because a lot of libraries had missing bits pending the big SMPng changes on 5.x. Mostly related to thread libs. - 5.x was a huge change relating to POLA. Eg: init scripts changed to new rc.d framework (iirc imported or based on NetBSD work). At that time you had two options: - Use rock solid FreeBSD 4.x and be unable to run more or less recent apps and hardware without huge problems. - Use FreeBSD 5.x which was unstable and slow compared to 4.x Because of this problems some people migrated to Linux, a fork of FreeBSD with the idea of an easier SMP model was created, etc. FreeBSD project learnt a good lesson: If you wait too much for great features to came to a reality instead of releasing often, you will not have features or stability. Ie: The stable release is unusable because backporting drivers and libs is harder and you end with unsupported new hardware as time passes, apps are harder to port because missing APIs, etc. And the new "current" release is unusable because there are too many things in testing and breaks in a lot of places. At that time (maybe 6.x? can't remember for sure, maybe someone else will remember better) the FreeBSD project announced a new way of doing releases. Release Timely instead of release based on features. If you don't have a feature ready when it's time for releases, just skip until next one instead of waiting. Now a few years later as sysadmins we find that there are too many releases that don't last too much. We waste a lot of time testing upgrades and once they're in production releases don't last often enough for the effort to be worthwile. Hence, John mail. I agree with John on the problems, but i disagree on solutions and the causes. No solution is going to work if you expect volunteers to do anything for a long time that's boring. You lost interest and stop working on that. What i really think it's the problem: If you try to maintain a few servers without much resources you end replicating half FreeBSD's project release infraestructure: - You find a bug, report, get a patch and apply. After that, you lost forever the option of using freebsd-update. You need to reinstall the system to get freebsd-update again - You want binary updates with custom kernel or patches? -> Your only option is cutting your own releases or forget about freebsd-update. - You want to track packages on various machines? -> create your tinderbox because binary package upgrades is a no-op with standard packages distributed by the project. - You want to apply a security update to a custom kernel? -> no binary option - Do you want to apply just one security update but no other to a standard kernel? -> no option freebsd-update will just allow you all patches or none. - Performance problems? Usually involves recompiling with different compiler or kernel/userland options. Again: no easy binary upgrade
Re: Missing dependencies on shared libraries
On Sat, Apr 15, 2006 at 12:26:57PM -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Daniel Eischen <[EMAIL PROTECTED]> writes: > : On Sat, 15 Apr 2006, M. Warner Losh wrote: > : > : > In message: <[EMAIL PROTECTED]> > : >Daniel Eischen <[EMAIL PROTECTED]> writes: > : > : On Sat, 15 Apr 2006, M. Warner Losh wrote: > : > : > : > : > In message: <[EMAIL PROTECTED]> > : > : > Daniel Eischen <[EMAIL PROTECTED]> writes: > : > : > : On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > : > : > : > : > : > : > Hi, > : > : > : > I found that ldd doesn't report libc as a dependency on most > (all?) > : > : > : > libraries: > : > : > : > > : > : > : > pato> ldd /usr/lib/libfetch.so > : > : > : > /usr/lib/libfetch.so: > : > : > : >libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > : > : > : >libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > : > : > : > > : > : > : > does anyone know why? > : > : > : > : > : > : AFAIK, it's being worked on. It's not just libc either, -pthread > : > : > : also has to start linking to libpthread. > : > : > > : > : > We don't record libc dependencies into shared libraries right now. If > : > : > we did, that would create some problems and solve some problems. With > : > : > symbol versioning, it most likely will become moot, since we'll never > : > : > have to bump libc major version again... > : > : > : > : kan stated he was working on doing this, which is what I was > : > : referring to above. > : > > : > That makes sense. If you explicitly include libc on the command line > : > to build the library, it is included... > : > : Here's the link to his original reply to -current. Also, if you > : look at linux shared libraries, you'll note they have dependencies > : to libc. > > I guess what I'm saying is that on FreeBSD, the system built shared > libraries don't have libc recorded in them because we don't add -lc on > the commnad line to build them. If i try to add -lc ldd doesn't show it as a dependency, but readelf/dumpelf does show it as NEEDED. Is this the expected behavior? Why isn't ldd showing the dependency? -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Missing dependencies on shared libraries
On Fri, Apr 14, 2006 at 03:20:41PM -0400, Daniel Eischen wrote: > On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > > >On Fri, Apr 14, 2006 at 02:41:06PM -0400, Daniel Eischen wrote: > >>On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > >> > >>>Hi, > >>>I found that ldd doesn't report libc as a dependency on most (all?) > >>>libraries: > >>> > >>>pato> ldd /usr/lib/libfetch.so > >>>/usr/lib/libfetch.so: > >>> libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > >>> libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > >>> > >>>does anyone know why? > >> > >>AFAIK, it's being worked on. It's not just libc either, -pthread > >>also has to start linking to libpthread. > > > >Thanks for your fast reply. > > > >I'm trying to create a dependency in some libraries, but it does > >have the same problem as the libc. Is there any way to workaround it? > > Well, you can always try adding -lc. I tried, but it doesn't work. ldd continues to tell me that libc is not a dependency, but if i use objdump -p it does appear as NEEDED. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Missing dependencies on shared libraries
On Fri, Apr 14, 2006 at 02:41:06PM -0400, Daniel Eischen wrote: > On Fri, 14 Apr 2006, Victor Balada Diaz wrote: > > >Hi, > >I found that ldd doesn't report libc as a dependency on most (all?) > >libraries: > > > >pato> ldd /usr/lib/libfetch.so > >/usr/lib/libfetch.so: > > libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) > > libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) > > > >does anyone know why? > > AFAIK, it's being worked on. It's not just libc either, -pthread > also has to start linking to libpthread. Thanks for your fast reply. I'm trying to create a dependency in some libraries, but it does have the same problem as the libc. Is there any way to workaround it? -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Missing dependencies on shared libraries
Hi, I found that ldd doesn't report libc as a dependency on most (all?) libraries: pato> ldd /usr/lib/libfetch.so /usr/lib/libfetch.so: libssl.so.3 => /usr/lib/libssl.so.3 (0x4816a000) libcrypto.so.3 => /lib/libcrypto.so.3 (0x48198000) does anyone know why? -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: adding new sysctl
On Sat, Jan 14, 2006 at 04:55:14PM +, Tofik Suleymanov wrote: > Could someone show me how to add new sysctl to the system ? You have an example in /usr/share/examples/kld/dyn_sysctl/. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: speed up port compiling using RAM (tmpfs) ???
On Sun, Jan 15, 2006 at 02:45:30AM -0500, Ashok Shrestha wrote: > Hi, > > I am curious to know if there is a way to compile a port such as X11 > or KDE faster. > > I know in Gentoo, you can mount a part of RAM and compile in that. > This substantially decreases the compile time. Reference: > http://gentoo-wiki.com/TIP_Speeding_up_portage_with_tmpfs > > Does anyone know how to do this in Freebsd? You should take a look at mdconfig(8) and ports(7). With mdconfig you create the ram-based disk and with WRKDIRPREFIX you tell the ports to use that disk instead of the default workdir. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: help me with C languaje please, re: files.
On Sun, Jun 05, 2005 at 01:35:21AM -0400, Pablo Mora wrote:
> #include
> #include
>
> int main(void) {
>
> FILE *p_to_f;
> char buf[1024];
> int i, j = 0;
>
> p_to_f = fopen("test","r");
>
> if(p_to_f == NULL) {
> perror("fopen");
> exit(EXIT_FAILURE);
> }
>
> for(i = 0; i < 4 && !feof(p_to_f); i++) {
> fgets(buf,1024,p_to_f);
> printf("%s", buf);
> }
>
> fclose(p_to_f);
>
> return 0;
>
> }
>
> I expect that be well what I did. Thanks Victor.
>
> PD Corrigeme Si hay algo malo. :D
You don't use j, in the for should be || instead of && and you don't
check for errors in fgets.
Btw, i think that this is not the best place for ask this questions,
you should ask in a c programming list.
--
La prueba mas fehaciente de que existe vida inteligente en otros
planetas, es que no han intentado contactar con nosotros.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: help me with C languaje please, re: files.
On Sat, Jun 04, 2005 at 02:11:01PM -0400, Pablo Mora wrote: > Hi all, > > I am programming in C and I need to read a quantity of lines of a > file. How can I know when a line arrives at his end? exists some > special character? exists some file in C in the kernel of FreeBSD > (4.11) where I can find somewhat similar? > > example: how read four lines of a file. Take a look at fgets(3). The end of line character (in FreeBSD) is '\n'. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
