Re: dot snap folder
On Mon, 16 Jan 2012 12:21:27 +, RW wrote: > On Mon, 16 Jan 2012 12:59:59 +0100 > Polytropon wrote: > > > On Mon, 16 Jan 2012 05:32:11 -0600, ajtiM wrote: > > > On Sunday 15 January 2012 23:54:52 Chip Camden wrote: > > > > Quoth Polytropon on Monday, 16 January 2012: > > > > > On Sun, 15 Jan 2012 15:40:20 -0800, Jim Pazarena wrote: > > > > > > Is it permissible to delete the dot snap folder which is > > > > > > created in a filesystem? > > > > > > > > > > First of all, it's called a directory, not a "folder". :-) > > > > > > > > After all, it doesn't fold (for that you need a little Haskell or > > > > OCaml). > > > > > > ...and the answer if is it permissible to delete .snap directory > > > is?? Thank you. > > > > The answer has been provided two times, none of them is > > quoted above or below. :-) > > > > I may repeat: It is permissible _unless_ you are running > > the dump program on a live partition using the -L option. > > > > As the question has been answered, > > I'm not sure it has. AFAIK it's also used by background fsck. That information could be obtained by conclusion and by experience. I had the experience that it might interfere with a regular fsck (not the background one) if present. Only at a background run you'd have the opportunity to remove .snap, whereas during a normal fsck run (typically at startup) you cannot do this (without interrupting fsck). Anyway, you're right: fsck_ffs's source code mentiones the .snap directory. It's line 320 and later. The comment at line 283 suggests that fsck will _create_ that directory if required, just like dump -L would do. Line numbers for /usr/src/sbin/fsck_ffs/main.c OS version 8.2-STABLE here, may differ for others. So there may be an extension of my summary: It is permissible _unless_ you are running the dump program on a live partition using the -L option -or- you are currently running (background) fsck. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dot snap folder
On Mon, 16 Jan 2012 05:32:11 -0600, ajtiM wrote: > On Sunday 15 January 2012 23:54:52 Chip Camden wrote: > > Quoth Polytropon on Monday, 16 January 2012: > > > On Sun, 15 Jan 2012 15:40:20 -0800, Jim Pazarena wrote: > > > > Is it permissible to delete the dot snap folder which is created > > > > in a filesystem? > > > > > > First of all, it's called a directory, not a "folder". :-) > > > > After all, it doesn't fold (for that you need a little Haskell or OCaml). > > ...and the answer if is it permissible to delete .snap directory is?? Thank > you. The answer has been provided two times, none of them is quoted above or below. :-) I may repeat: It is permissible _unless_ you are running the dump program on a live partition using the -L option. As the question has been answered, it's fully valid to suggest the use of the proper timmy, erm terminology, with colon-minus-close-paren appended. :-) > There is also .config directory which is made by QT or something of KDE 4 > which is possible to delete but it is recreated each time after kde 4 started. It seems to be permissible, as its absence doesn't seem to have any significant effect. As it has been explained in the quote from "man dump" regarding the -L option (again, not quoted here), in case .snap/ is required, it will be created. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: access(FULLPATH, xxx);
On Mon, 16 Jan 2012 12:03:52 +1000, Da Rock wrote: > On 01/14/12 22:06, Polytropon wrote: > > On Sat, 14 Jan 2012 20:37:14 +1000, Da Rock wrote: > >> On 01/14/12 19:54, Robert Bonomi wrote: > >>>>From owner-freebsd-questi...@freebsd.org Sat Jan 14 02:32:15 2012 > >>>> Date: Sat, 14 Jan 2012 09:28:21 +0100 > >>>> From: Polytropon > >>>> To: Robert Bonomi > >>>> Cc: freebsd-questions@freebsd.org > >>>> Subject: Re: access(FULLPATH, xxx); > >>>> > >>>> On Sat, 14 Jan 2012 02:00:12 -0600 (CST), Robert Bonomi wrote: > >>>>> To repeat some advice from one of my Computer Science professors, many > >>>>> years > >>>>> ago, whenever I asked 'how does it work' questions: "Try it and find > >>>>> out." > >>>> I bet my professor can beat up your professor. :-) > >>>> > >>>> Mine used to say several times: "Trial and error is NOT > >>>> a programming concept!" > >>> As far as writing applications goes, that is _somewhat_ correct. > >>> > >>> However, 'trial and error' is _not_ the same thing as 'try it and find > >>> out'. > >>> See the entire subject area of 'benchmarking'. > >>> > >>> And, the only way to definitively establish if an alternate approach is > >>> 'better' -- i.e. 'faster', or 'smaller', or 'more efficient', etc. -- *IS* > >>> to run a trial. > >>> > >>> Your professor undoubtedly would not of approved when I wrote bubble-sort > >>> code that _out-performed_ any other sorting technique -- up to the limits > >>> of memory. Or when I re-wrote an application that used binary searches > >>> of records, with a new version that used a brute-force linear search. I > >>> thought I could 'do it better/faster' than the existing code, but the only > >>> way to "definitively" find out was to 'try it'. And the 'trial' proved > >>> out -- the replacement code was 'merely' somewhat over 100 times faster. > >>> *grin* > >> Ha! Love it... :D > > Mee too - except that I didn't want to show that > > "typical attitude". In fact, I tried to make a > > (kinf of humourical) statement about a habit that > > I could observe at many students when I was at > > university. > > > > Background: > > > > When you write source code, you can make errors. > > Compiler shows errors. Some students started > > with "trial& error" to just silence the compiler. > > One form was that all functional parts of the > > program were enclosed in /* and */ (it was a > > C class) - no errors, but no action. A different > > approach was to arbitrarily (!) change the source > > code, something like that: > > > > void *foo(int blah, void *meow())(int ouch); > > > > Hmmm... gives me segfaults. Maybe something's > > wrong with the pointers? > > > > void *foo(int blah, void **meow())(int ouch); > > > > Not much better, segfaults too. How about that? > > > > void *foo(int blah, void meow())(int *ouch); > > > > Well... also not better. I've heared about parentheses, > > maybe those can help? > > > > void *foo(int blah), void *meow)(int ouch); > > > > Shit, doesn't even compile anymore! Uhm... _what_ did > > I change? Oh wait, I know: > > > > void *foo(int blah, (void *)meow())(int ouch); > > > > Just produces garbage, then segfaults... what could I > > change next? > > > > I think you get the idea. > > > > Other students could not understand that even if a > > program compiles without any errors, there _may_ be > > the possibility that it doesn't do what they intended > > it to do. They seemed to believe in some kind of > > magical "semantic compiler": > > > > int x, y, sum; > > x = 100; > > y = 250; > > sum = a - b; > > > > They expected the compiler to notice what's wrong here > > if you consider the _meaning_ of the identifiers. It's > > not that obvious if you use x, y, and z. :-) > > > > > > > >>> As far as 'doing it once' for the purpose of answering a 'how does it > >>> work' > >>> quest
Re: dot snap folder
On Sun, 15 Jan 2012 15:40:20 -0800, Jim Pazarena wrote: > Is it permissible to delete the dot snap folder which is created > in a filesystem? First of all, it's called a directory, not a "folder". :-) The .snap directory in a partition's root directory is used by the program "dump" to store a snapshot of a live (i. e. possibly changing) file system prior to dumping it (i. e. it dumps the snapshot). See "man dump", the -L option: This option is to notify dump that it is dumping a live file sys- tem. To obtain a consistent dump image, dump takes a snapshot of the file system in the .snap directory in the root of the file system being dumped and then does a dump of the snapshot. The snapshot is unlinked as soon as the dump starts, and is thus removed when the dump is complete. This option is ignored for unmounted or read-only file systems. If the .snap directory does not exist in the root of the file system being dumped, a warning will be issued and the dump will revert to the standard behavior. This problem can be corrected by creating a .snap directory in the root of the file system to be dumped; its owner should be ``root'', its group should be ``operator'', and its mode should be ``0770''. *** So unless you're currently running a dump -L session, you can delete that directory. Maybe you need to be member of "operator" or be "root" in order to do it due to access permissions described above. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: access(FULLPATH, xxx);
On Sat, 14 Jan 2012 20:37:14 +1000, Da Rock wrote: > On 01/14/12 19:54, Robert Bonomi wrote: > >> From owner-freebsd-questi...@freebsd.org Sat Jan 14 02:32:15 2012 > >> Date: Sat, 14 Jan 2012 09:28:21 +0100 > >> From: Polytropon > >> To: Robert Bonomi > >> Cc: freebsd-questions@freebsd.org > >> Subject: Re: access(FULLPATH, xxx); > >> > >> On Sat, 14 Jan 2012 02:00:12 -0600 (CST), Robert Bonomi wrote: > >>> To repeat some advice from one of my Computer Science professors, many > >>> years > >>> ago, whenever I asked 'how does it work' questions: "Try it and find out." > >> I bet my professor can beat up your professor. :-) > >> > >> Mine used to say several times: "Trial and error is NOT > >> a programming concept!" > > As far as writing applications goes, that is _somewhat_ correct. > > > > However, 'trial and error' is _not_ the same thing as 'try it and find out'. > > See the entire subject area of 'benchmarking'. > > > > And, the only way to definitively establish if an alternate approach is > > 'better' -- i.e. 'faster', or 'smaller', or 'more efficient', etc. -- *IS* > > to run a trial. > > > > Your professor undoubtedly would not of approved when I wrote bubble-sort > > code that _out-performed_ any other sorting technique -- up to the limits > > of memory. Or when I re-wrote an application that used binary searches > > of records, with a new version that used a brute-force linear search. I > > thought I could 'do it better/faster' than the existing code, but the only > > way to "definitively" find out was to 'try it'. And the 'trial' proved > > out -- the replacement code was 'merely' somewhat over 100 times faster. > > *grin* > Ha! Love it... :D Mee too - except that I didn't want to show that "typical attitude". In fact, I tried to make a (kinf of humourical) statement about a habit that I could observe at many students when I was at university. Background: When you write source code, you can make errors. Compiler shows errors. Some students started with "trial & error" to just silence the compiler. One form was that all functional parts of the program were enclosed in /* and */ (it was a C class) - no errors, but no action. A different approach was to arbitrarily (!) change the source code, something like that: void *foo(int blah, void *meow())(int ouch); Hmmm... gives me segfaults. Maybe something's wrong with the pointers? void *foo(int blah, void **meow())(int ouch); Not much better, segfaults too. How about that? void *foo(int blah, void meow())(int *ouch); Well... also not better. I've heared about parentheses, maybe those can help? void *foo(int blah), void *meow)(int ouch); Shit, doesn't even compile anymore! Uhm... _what_ did I change? Oh wait, I know: void *foo(int blah, (void *)meow())(int ouch); Just produces garbage, then segfaults... what could I change next? I think you get the idea. Other students could not understand that even if a program compiles without any errors, there _may_ be the possibility that it doesn't do what they intended it to do. They seemed to believe in some kind of magical "semantic compiler": int x, y, sum; x = 100; y = 250; sum = a - b; They expected the compiler to notice what's wrong here if you consider the _meaning_ of the identifiers. It's not that obvious if you use x, y, and z. :-) > > As far as 'doing it once' for the purpose of answering a 'how does it work' > > question -- where one has _not_ read the documentation, *OR* the existing > > documentation is _not_clear_, then simple experimentation -- to get *the* > > authoritative answer -- is entirly justified. > > > > When I got the 'try it and find out' advice, I was asking questions about > > situations where the language _specification_ was unclear -- there were > > two 'reasonable interpretations' of what the language inthe speciication > > said, and I just wanted to know which one was the proper interpretation. > > > > Now, given that the language in the specification _was_ abiguous and both > > interpretations were reasonsble, different compiler builders could have > > implemented differently, and 'try it and find out' was _necessary_ to > > establish what that particular implementation did. > There appears to be 2 schools of thought on this subject: a classic case > of the "old"
Re: disk problem(s)
On Sat, 14 Jan 2012 10:12:48 +0100, Bernt Hansson wrote: > 2012-01-14 09:22, Polytropon skrev: > > How many subdirectories are there? > > ls | wc -l > 32765 Seems that you have reached LINK_MAX of 32767 (according to /usr/src/sys/sys/syslimits.h). The difference of 2, I assume, is one for . and one for .. "hidden" entries. > > Could you, for example, try removing one and then > > creating a new one (assumption: success), followed > > by another try to create one (assumption: fail)? > > > That is a nono > > I'll have to pop in another disk. As the voice from the GPS navigation system tends to say: "You have reached your destination." :-) Re-arranging the content of the disk could be an option, but if you're using that disk as some kind of WORM medium (e. g. backup disk), I understand the nono. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: disk problem(s)
On Sat, 14 Jan 2012 09:22:36 +0100, Polytropon wrote:
> The mkdir() function can be found (for UFS2) in the
> file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at
> line (sources of 8.2-STABLE i386 here). If
> you examine what mkdir() does, you'll see that
> the "too many links" is true when LINK_MAX is
> exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h
> we can determine that
>
> #define EXT2_LINK_MAX 32000
>
> is defined. Can you check if 32000 is the amount
> of directories created?
Shit, what have I done... of course the files
mentioned here do correspond to ext2 (Linux stuff),
and _not_ to UFS2.
The answer is in /usr/src/sys/sys/syslimits.h where
we find the following definition:
#define LINK_MAX 32767 /* max file link count */
Can you check _that_ number against the amount of
directories created?
By the way, in cases like this it's helpful if you
provide the _command_ that you tried and the current
directory from _where_ you've tried it.
Also see /usr/src/sys/ufs/ufs/ufs_vnops.c, lines 1748
and onward, to see the UFS mkdir() system call acting
with
if ((nlink_t)dp->i_nlink >= LINK_MAX) {
error = EMLINK;
goto out;
}
when the LINK_MAX limit is reached.
Sorry for the confusion.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: access(FULLPATH, xxx);
On Sat, 14 Jan 2012 02:00:12 -0600 (CST), Robert Bonomi wrote: > To repeat some advice from one of my Computer Science professors, many years > ago, whenever I asked 'how does it work' questions: "Try it and find out." I bet my professor can beat up your professor. :-) Mine used to say several times: "Trial and error is NOT a programming concept!" However, your suggestion of creating a simple test case, together with consulting the documentation, is a fully valid approach to discover what format path should be in the int access(const char *path, int mode); function. Luckily, we _have_ that kind of documentation in FreeBSD where the answer is just "man 2 access" away. Other operating systems (or excuses thereof) do not offer this simple and still helpful thing. > You see, the *ONLY* thing that matters is 'what the machine does'. And, > a trivial test case will give an _authoritative_ answer. Anything that > anybody says about 'how it works' is merely an *opinion*, and they could > be wrong. The test case will, however, ALWAYS give you the 'hard truth' > about how it works in your environment. Especially when interpreting the content of the manual is debatable (as it is at least for me in this specific case), a simple test would reveal the truth of what will actually happen. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: disk problem(s)
On Sat, 14 Jan 2012 08:45:20 +0100, Bernt Hansson wrote: > Hello list! > > 7.3-RELEASE FreeBSD 7.3-RELEASE #0: Sun Mar 21 06:15:01 UTC 2010 > r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > Whenever a program tries to make a directory on this slice it > gets this error It's a partition, not a slice. Partitions carry file systems, slices carry partitions. :-) > mkdir: spool/text/test: Too many links So the problem seems to be related to directories, not to "any files" (inodes) per se. > This is the slice > > /dev/ad4s4d202G 37G149G20%/news/spool/text The partition; ad4s4 would be the slice. :-) > One can create a file without problems just not directories. > > Checked sysctl but don't know what to look for. A boot in the right end > would be helpful. I would suggest to find out the reason, therefore a short search though the src/ subtree reveals that this message provided by mkdir is: #if defined (EMLINK) ENTRY(EMLINK, "EMLINK", "Too many links"), #endif As the mkdir program uses the mkdir() call, we find "man 2 mkdir" with the error description for EMLINK: The new directory cannot be created because the parent directory contains too many subdirectories. How many subdirectories are there? Could you, for example, try removing one and then creating a new one (assumption: success), followed by another try to create one (assumption: fail)? Detail: The mkdir() function can be found (for UFS2) in the file /usr/src/sys/gnu/fs/ext2fs/ext2_vnops.c at line (sources of 8.2-STABLE i386 here). If you examine what mkdir() does, you'll see that the "too many links" is true when LINK_MAX is exceeded. Per /usr/src/sys/gnu/fs/ext2fs/ext2_fs.h we can determine that #define EXT2_LINK_MAX 32000 is defined. Can you check if 32000 is the amount of directories created? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: access(FULLPATH, xxx);
On Fri, 13 Jan 2012 16:05:18 -0800, Gary Kline wrote:
>
> excuse this slip of memory, but do you need the full path PLUS the
> filename to use access? or just the filename?
>
> say that i'm i n ~/tmp/foob and want to deetermine wheether i can
> access file foob. do i need to use "access("home/kline/tmp/foob", F_OK)"
> or will "access("foob", F_OK)" do the trick? i have already rub
> "chdir("~/tmp")" in main(). please note.
According to what I read from "man 2 access" I would
assume it has to be an absolute path. When you read
to the faccessat() function, you'll see:
The faccessat() system call is equivalent to
access() except in the case where path specifies
a relative path. In this case the file whose
accessibility is to be determined is located
relative to the directory associated with the
file descriptor fd instead of the current
working directory. If faccessat() is passed
the special value AT_FDCWD in the fd parameter,
the current working directory is used and the
behavior is identical to a call to access().
Also see "SECURITY CONSIDERATIONS" later on.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upgrade from 8.2 to 9.0
On Fri, 13 Jan 2012 14:42:03 +0100, Dick Hoogendijk wrote: > I possible I want my server to upgrade from 8.2-RELEASE to 9.0-RELEASE. > I guess the binary upgrade will not be a problem with "freebsd-update -r > 9.0-RELEASE fetch" If so, I do like to hear the caveats. Source update also shouldn't be a problem. Setup your CVS "supfile" to get the 9.0-RELEASE sources and follow the instructions in the handbook and in /usr/src/Makefile's comment header. > My main problem lies with the installed ports. I know the -all- have to > be recompiled, but I don't know an easy way for this job. Not "have to", but it's often considered "best practice". If you don't want to recompile all your ports, make sure two things are met: 1. You have COMPAT_FREEBSD8 in your kernel. 2. You have compat8x-i386-8.2.12345.67890 installed (or amd64 respectively). This will work as long as you're not starting to install something new (which may cause library version trouble). However, using a port management tool to do the job of "update all ports" is often highly recommended. > I always use > portmaster. Did you look into its manual already? :-) > Do I have to make a list manually for all installed ports? Depends. A possible approach is that you make a list of your "primary ports", i. e. the stuff that you are _really_ intending to use, where "secondary ports" they depend on (i. e. the dependencies) are not mentioned, as they will be installed anyway. So for example, if "firefox" is on your list as you intend to use it, there's no need to list all its dependencies as well because they are implicit. > Or is there a procedure to follow in this matter? I'd like to get some > pointers if possible. Sure. See "man portmaster", section EXAMPLES, where you'll find "Using portmaster to do a complete reinstallation of all your ports" with a complete procedure. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: BSD equivalent of GNU/Linux cp -rpu ?
On Wed, 11 Jan 2012 06:00:37 -0500, Thomas Mueller wrote: > the -u flag, for update, means not to copy files that > exist in both the source and destination unless the > source version is newer. Hmmm... sounds as if you mean cpdup (which you'll find in the ports collection). > Would I use something like rsync or pax ? Yes, rsync also sounds promising. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: starting firefox3 with defined geometry
On Tue, 10 Jan 2012 09:56:21 +0100, Matthias Apitz wrote: > El día Tuesday, January 10, 2012 a las 09:25:54AM +0100, Polytropon escribió: > > > Answer: Yes, but it's not as easy as it could have been. > > > > Unlike nearly every other X11 program, notably the "old" > > and "outdated" ones, Firefox does _not_ seem to support > > the _standard_ -geometry WxH+X+Y parameter. > > > > However, you can define the window width and height > > with command line parameters: > > > > % firefox -width 1024 -height 768 > > does not work with firefox-3.5.18 (from ports) on 9-CURRENT; Oh the joy of modern software. :-) > > ... > > There is a "workaround" for the lack of standard > > geometry support: You could have Firefox execute > > JavaScript instructions at startup > > > > window.moveTo(100, 100); > > window.resizeTo(1024, 768); > > will try this in the page source; You can also provide those as command line parameters and have Firefox execute them on startup % firefox javascript:%20resizeTo\(500,500\) This works with v6.0.1 running on WindowMaker. As you said you're running KDE, why not try to compensate Firefox's inabilities to support standard -geometry parameters? I found this tool: http://tomas.styblo.name/wmctrl/ Maybe it also works with KDE which manages the Firefox window? The program can be found at x11/wmctrl in the ports collection. KDE uses kwin as its window management subsystem which (according to the documentation) should be compatible. It's really annoying that one has to jump through such hoops just to get a 30 year old standard functionality that every other program has... Hey, even Opera can do it! And now back to history. :-) > > > UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) > > > > PDP-11 or K1600? Oh, and EC1056 here (OS/ES SVM OP1). :-) > > both, PDP-11 and the clone; Our clone or the KFKI clone? http://hampage.hu/tpa/e_tpa1140.html Did you run MUTOS or SVP on that thing? > have you ever driven a UNIX by punch cards? No, but I'm familiar with the concept of input redirection in batch mode. Even TSO could be fed via punch cards as it was represented as a batch job. :-) > does PSU ring a bell? > http://cvs.laladev.de/index.html/P8000/WEGA/contrib/ingres/dbs/tmp/ing_Vortrag?rev=1.1&content-type=text/x-cvsweb-markup Yes, it does. And I even know this text - which is easy as the material found on the Internet about this topic is very limited. :-) Do you know VMX, a UNIX running as a virtual machine on SVM? (I've also been running UNIX System III "WEGA" on a P8000 here.) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: starting firefox3 with defined geometry
On Tue, 10 Jan 2012 08:45:04 +0100, Matthias Apitz wrote: > Hello, > > Is there some way to start firefox3 in a defined geometry, something > like > > $ firefox3 -geometry 1024x768 Answer: Yes, but it's not as easy as it could have been. Unlike nearly every other X11 program, notably the "old" and "outdated" ones, Firefox does _not_ seem to support the _standard_ -geometry WxH+X+Y parameter. However, you can define the window width and height with command line parameters: % firefox -width 1024 -height 768 I've tested this with the Firefox installation I have here (which is v6.0.1). Positioning of the window is not possible by this means. Also note that those parameters do not show up when you try % firefox -h to get some help, and "man firefox" is of course fully futile. :-) There is a "workaround" for the lack of standard geometry support: You could have Firefox execute JavaScript instructions at startup window.moveTo(100, 100); window.resizeTo(1024, 768); Those can even be provided on the command line. However, that's a bad excuse for not supporting what users expect working for 30 years. > UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) PDP-11 or K1600? Oh, and EC1056 here (OS/ES SVM OP1). :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ports vs packages
On Mon, 9 Jan 2012 13:06:27 -0500, Alejandro Imass wrote: > Use pre-built binary packages to install very large > stuff like Gnome, Open Office, etc. Not an option if your required language settings or the inclusion or exclusion of desktop bindings (KDE, Gnome, CUPS) don't match the default options from wich the package has been built. Also may apply to X.org (HAL and DBUS dependencies, if they're not desired or basically useless). Otherwise, no objections. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ports vs packages
On Mon, 9 Jan 2012 12:17:37 -0500, alexus wrote: > Ports vs Packages? > > /usr/ports vs pkg_* > > pros/cons In short: ports: pro: most current, if properly updated build from source (security!) apply optimization (speed!) apply compile-time options (functionality!) highly configurable easy updating of installed stuff cons: requires time requires disk space requires CPU packages: pro: fast installation less typing works good on low resource systems cons: not "bleeding edge" not all ports available as packages primarily means of "first time installation" The list could go on for hours. Consensus: Use a port management tool (such as portmaster or even portupgrade) if you don't want to deal with "bare ports". Furthermore, consult the mailing list archives for more elaborate answers and discussions. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How To Enable ls Color?
On Sun, 08 Jan 2012 16:04:17 -0800, Drew Tomlinson wrote: > I've installed 9.0-RC3 amd64. I'm trying to enable color output for > ls. I've issued the basic 'ls -Gla' but output is not colored. Yet if > I can get colorized output by providing color codes (echo > ^[[34mhello^[[37m produces a blue "hello") at the command line so I know > my terminal is capable. > > Is there some other secret? This is a new install and I'm just trying > to set things up. Put setenv LSCOLORS ExGxdxdxCxDxDxBxBxegeg in the csh's initialisation file (typically ~/.cshrc for local use, /etc/csh.cshrc for global effect) and maybe setup an alias: alias ls 'ls -FG' alias ll 'ls -laFG' However, ls should provide colored output even if you don't set the $LSCOLORS variable. It should work with the default terminal emulation (cons25 or cons25l1). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OpenBSD disk on FreeBSD.
On Sun, 08 Jan 2012 16:13:38 -0500 (EST), R. Clayton wrote: > Thanks for your reply to my message. > > you can address the partitions on that slice (da0s4) like you would access > them > on FreeBSD. > > "mount /dev/da0s4a" didn't work. However, looking in dmesg I saw > > WARNING: R/W mount of /mnt/backups denied. Filesystem is not clean - run > fsck If you're intending to copy data FROM the disk, i. e. you want to _recover_ data, do _not_ mount something R/W (because you don't have to). Always use "-o ro", at least in early stages. The denial of the mount is justified due to file system errors which are correctly detected (and then corrected by fsck). > After running "fsck -t ufs /dev/da0s4", "mount /dev/da0s4a" still didn't > work, but > > # mount /dev/da0s4 mnt > > did work: > > # cat mnt/angkor-wat/etc/fstab > # fs-spec mount-point type options frequency pass-no > /dev/wd0a / ffs rw 1 1 > /dev/wd0h /home ffs rw,nodev,nosuid 1 2 > /dev/wd0d /tmp ffs rw,nodev,nosuid 1 2 > /dev/wd0g /usr ffs rw,nodev 1 2 > /dev/wd0e /var ffs rw,nodev,nosuid 1 2 > /dev/sd0a /mnt/backups ffs rw,nodev,nosuid 1 2 > /dev/sd0d /mnt/storage ffs rw,nodev,nosuid 1 2 > /dev/cd0a /cdrom cd9660 ro,noauto 0 0 > > # > > However, I can only mount the sd0a (OpenBSD) partition; [...] That is the root partition /, and suffixes d, e, g, h should be available. > [...] the sd0d partition is > nowhere to be found: > > $ sudo fsck -t ufs /dev/da0s4d > ** /dev/da0s4d > Cannot find file system superblock > ioctl (GCINFO): Inappropriate ioctl for device > fsck_ufs: /dev/da0s4d: can't read disk label > > $ > > On the other hand, > > $ sudo fsck -t ufs /dev/da0s4a > ** /dev/da0s4a > Cannot find file system superblock > ioctl (GCINFO): Inappropriate ioctl for device > fsck_ufs: /dev/da0s4a: can't read disk label > > $ > > so maybe the partition names are wrong. Can you obtain partitioning information via bsdlabel (disklabel) for the s4 slice to check if FreeBSD can identify the other partitions properly. If you visit the mailing list archives, you will find hints to procedures and software to do a deeper analysis of the structures that need to be accessed, such as disk labels, file system data and other stuff. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OpenBSD disk on FreeBSD.
On Sun, 08 Jan 2012 14:42:01 -0500, R. Clayton wrote: > The OpenBSD fstab is gone, and the backup copy is (of course) on the disk I > want to mount. How do I go about mounting this disk on FreeBSD? The > following > don't work: > > # mount /dev/da0 mnt > mount: /dev/da0 : Invalid argument > > # mount /dev/da0s4 mnt > mount: /dev/da0s4 : Operation not permitted According to http://www.openbsd.org/faq/faq14.html you can address the partitions on that slice (da0s4) like you would access them on FreeBSD. # mount -o ro -t ufs /dev/da0s4a /mnt This will give you the root partition. Other partitions can be mounted separately (or in sequence, after unmounting /mnt), or they can be mounted into the /mnt tree to their original locations, e. g. # mount -o ro -t ufs /dev/da0s4e /mnt/tmp # mount -o ro -t ufs /dev/da0s4f /mnt/var # mount -o ro -t ufs /dev/da0s4g /mnt/usr # mount -o ro -t ufs /dev/da0s4h /mnt/home I would suggest you _first_ mount each partition individually and see from its content what it has been designated to. If you can find a copy of the original /etc/fstab somewhere on one of the partitions, you can use its content to avoid guessing. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012 01:11:30 +0100 (CET), Marco Beishuizen wrote: > On Sun, 8 Jan 2012, the wise Polytropon wrote: > > > If this is depending on the name "[BOOT]", there are > > two ways to deal with special characters in file names, > > if you need to specify them on the command line: > > > > a) use escape sequences: > > -b \[BOOT\]/Bootable_HardDisk.img > > > > b) use quoting: > > -b "[BOOT]/Bootable_HardDisk.img" > > I used escape sequences and that works. The "no match" error is gone. By using [ and ], the shell tries to expand a regular expression where [BOOT] means "one of the letters B, O, or T; neither B/Bootable_HardDisk.img, O/Bootable_HardDisk.img or T/Bootable_HardDisk.img is present, so the shell fully correctly replies with "no match". (In a similar fashion, * and ? are interpreted by the shell.) > > Also read "man mkisofs" about the boot-related > > options, especially -b, where > > > > If the boot image is not an image of a floppy, you need to add > > one of the options: -hard-disk-boot or -no-emul-boot. If the > > system should not boot off the emulated disk, use -no-boot. > > > > is mentioned. Maybe consider using -G instead of -b? > > I tried the -G option and removed the -hard-disk-boot option and now it > created an iso without errors. The size is still 9MB though. I looked > inside the original iso and the one generated by me but I really can't see > any differences. Does this image boot successfully? If you compare your ISO with the original one, file sizes should be the same for all files; are they? A reason could be that the original one contains some "metadata" that the creating program (which will very probably _not_ be mkisofs as you're using) may have stored there. Things like for example an application ID, copyright information, media name. Maybe the original program did use a different "mechanism" to create the ISO? You can easily add the file sizes inside the original ISO and compare them to your sources (which should be equal) and see where the difference comes from. I think it will be some file system metadata (remember that the ISO-9660 file system occupies "invisible" space within the ISO file). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing FreeBSD ver. 8.2
-rw-r--r-- 1 root wheel 1563 Aug 24 06:43 /etc/rc.conf -rwxr- 1 root wheel 602 Dec 11 2009 /etc/rc.local* The asterisk indicates an executable, as well as the "x" in the attributes field at the beginning. Furthermore, the filename "/etc/rc.local" appears in bright green color. For the C shell, use setenv LSCOLORS ExGxdxdxCxDxDxBxBxegeg and for bash, use export LSCOLORS="ExGxdxdxCxDxDxBxBxegeg" to configure the colors. See "man ls" for details. Oh, and the "ll" from my example is "ls -laFG" which also includes the suffix to indicate the type of file (directory, executable, pipe and so on). > FreeBSD does not seem to use file extension labels for > this purpose. No, why should anyone do that? It's dangerous! :-) > (5) What device driver must be installed for the sound > board to be able to receive a m.i.d.i. over u.s.b. signal? > This signal would be generated by a musician's keyboard, > and would control a music synthesizer application, to be > installed. I could find no mention of this topic in the > Handbook. I'm not familiar with "modern" USB hardware for that purpose. My MIDI times are long over, sorry. :-) > (6) In the book "Absolute FreeBSD" by Urban and Tiemann, > I found a two line command to cause the bash prompt to > display the file path and current directory. Unfortunately, > the text is quite unclear as to the name of the file to > which these line are to be added, or the directory in which > this file is located. I assume that somewhere there must > be login configuration files, bearing each user's name, > that give his or her shell configuration instructions. > What are the names of such files, and where are they > located? I've put my prompt configuration for bash in ~/.-bashrc locally to my user, and the setting for a standard UNIX prompt is export PS1="\u@\h:\w\$ " which I have in that file. You can find more suggestions at http://www.gilesorr.com/bashprompt/prompts/ for customizing your bash prompt. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: creating a bootable iso for raid BIOS flash
On Fri, 6 Jan 2012 17:22:57 +0100 (CET), Marco Beishuizen wrote: > After that I tried to create the iso with: > root@yokozuna:/data2/tmp# mkisofs -r -J -b [BOOT]/Bootable_HardDisk.img > -hard-disk-boot -o raid.iso /data2/tmp > which gives an error: mkisofs: No match > > First I thought the directory name [BOOT] was weird so I changed this to > BOOT. Running mkisofs -r -J -b BOOT/Bootable_HardDisk.img -hard-disk-boot > -o raid.iso /data2/tmp creates an iso, but when I burn this to a cd it > doesn't boot. If this is depending on the name "[BOOT]", there are two ways to deal with special characters in file names, if you need to specify them on the command line: a) use escape sequences: -b \[BOOT\]/Bootable_HardDisk.img b) use quoting: -b "[BOOT]/Bootable_HardDisk.img" Also read "man mkisofs" about the boot-related options, especially -b, where If the boot image is not an image of a floppy, you need to add one of the options: -hard-disk-boot or -no-emul-boot. If the system should not boot off the emulated disk, use -no-boot. is mentioned. Maybe consider using -G instead of -b? > Strange thing also is the fact that the original iso has the size of > ~17MB, but the created iso by me is ~10MB. So it seems I'm missing some > files. You can mount the ISO you've generated and look inside to find out which files may be missing, or if there are differences in file sizes. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD on kvm
On Fri, 06 Jan 2012 18:49:41 +0100, Alessandro Baggi wrote: > On 01/06/2012 06:24 PM, Polytropon wrote: > > On Fri, 06 Jan 2012 17:50:41 +0100, Alessandro Baggi wrote: > >> Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give > >> me some "crash". > >> There is a possibility to run directly the system instead print the > >> menu? I must install lilo/grub? > > Let's first assume that you did not install the boot > > manager (which would be useless in your particular > > application case); instead, you have installed the > > standard MBR. > > > > Modify /boot/loader.conf to something like this: > > > > autoboot_delay="0" > > beastie_disable="YES" > > userconfig_script_load="NO" > > verbose_loading="YES" > > > > Refer to /boot/defaults/loader.conf for the meaning > > of the options if they're not obvious. :-) > > > > Regarding the autoboot delay, let me quote from that > > file: > > > > Delay in seconds before autobooting, > > set to -1 if you don't want user to be > > allowed to interrupt autoboot process and > > escape to the loader prompt, set to > > "NO" to disable autobooting > > > > That means ="0" would mean to boot immediately _with_ > > the option to get to the boot prompt - you just need > > to be fast at the keyboard. :-) > > > > Oh, and see "man loader.conf" for details. > > > > > Hi Polytropon, > yes, I've installed the standard mbr :/. > After this, I've make the setting, but reading on > /boot/defaults/loader.conf for meaning of userconfig_script_load, I > can't find nothing about it, and I suppose that it is an invalid option. Sorry, forgot about that - must be some cruft transitioned from older installs. Just remove that option, as I don't think it has _any_ effect here. :-) > Now it seems to work. > Thanks for the reply. Sometimes I don't remember to see manual page...my > big bug... In FreeBSD, there's a manpage for nearly everything: System binaries and command scripts, kernel interfaces, library functions, device drivers, configuration files, maintenance procedures and operation guidelines. You just have to make yourself familiar with the ideas that those actually do exist. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD on kvm
On Fri, 06 Jan 2012 17:50:41 +0100, Alessandro Baggi wrote: > Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give > me some "crash". > There is a possibility to run directly the system instead print the > menu? I must install lilo/grub? Let's first assume that you did not install the boot manager (which would be useless in your particular application case); instead, you have installed the standard MBR. Modify /boot/loader.conf to something like this: autoboot_delay="0" beastie_disable="YES" userconfig_script_load="NO" verbose_loading="YES" Refer to /boot/defaults/loader.conf for the meaning of the options if they're not obvious. :-) Regarding the autoboot delay, let me quote from that file: Delay in seconds before autobooting, set to -1 if you don't want user to be allowed to interrupt autoboot process and escape to the loader prompt, set to "NO" to disable autobooting That means ="0" would mean to boot immediately _with_ the option to get to the boot prompt - you just need to be fast at the keyboard. :-) Oh, and see "man loader.conf" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Browser
On Wed, 4 Jan 2012 22:18:33 +, RW wrote: > On Wed, 4 Jan 2012 12:56:38 -0500 > ill...@gmail.com wrote: > > > > If you have a few hours, lots of RAM, & you'd like to stress- > > test your system: > > cd /usr/ports/www/chromium && make install > > > Unless things have changed radically that sounds like a bit of an > exaggeration. Until about 9 months ago I was building it on a 7 year > old single core athlon in 1.5GB with the work-directory on tmpfs. It > was still perfectly usable as a desktop. Well, last time I tried to compile one of Firefox's recent versions from ports, it demanded to have access to X during the "make" stage. That was the point I decided _not_ to continue (as the system in question didn't have X). Maybe I did something wrong, maybe I should have dealt with building options more carefully. But anyway, you type "make" and the intended web browser wants to access X? >From within a UID=0 session? Hmmm... On the other hand, installing google's Chromium browser went through without that kind of annoying trouble. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Exact timestamp for sorting and renaming files according to creation order
On Wed, 04 Jan 2012 15:01:32 +0100, Julian H. Stacey wrote:
> Hi,
> Devin Teske wrote:
> > > -Original Message-
> > > From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-
> > > questi...@freebsd.org] On Behalf Of Polytropon
> > > Sent: Tuesday, January 03, 2012 1:00 PM
> > > To: Dan Nelson
> > > Cc: FreeBSD Questions
> > > Subject: Re: Exact timestamp for sorting and renaming files according to
> > creation
> > > order
> > >
> > > On Tue, 3 Jan 2012 14:49:02 -0600, Dan Nelson wrote:
> > > > If you ask for the date to be printed in "float" (F) format, it gives
> > > > more precision. The default is unsigned int (U) format.
> > > >
> > > > % stat -f "%N %FB" /COPYRIGHT
> > > > /COPYRIGHT 1306190895.046721049
> > >
> > > Strangely, I only get a 0 "suffix" for any time stamp, no matter
> > > if I
> > create
> > > the file or apply the command as shown above to an existing file:
> > >
> > > % stat -f "%N %FB" /COPYRIGHT
> > > /COPYRIGHT 1313951230.0
> > >
> > > Am I missing some file system feature?
> > >
> > > Otherwise, this _exactly_ looks like what I'm searching for. It doesn't
> > > need
> > to be
> > > a "human-readable" date representation.
> > >
> > > by the way, I'm running FreeBSD 8.2-STABLE/x86 of late August 2011 here,
> > > file
> > > system used is UFS2.
> >
> > On ZFS, all is well...
> >
> > % df -hT /raid1/jails/package8-1/COPYRIGHT
> > Filesystem TypeSizeUsed Avail Capacity Mounted on
> > raid1/jails/package8-1 zfs 835G672M835G 0%
> > /raid1/jails/package8-1
> >
> > % stat -f "%N %FB" /raid1/jails/package8-1/COPYRIGHT
> > /raid1/jails/package8-1/COPYRIGHT 1324356049.328275367
> >
> > But alas, on UFS2:
> >
> > % df -hT /COPYRIGHT
> > Filesystem TypeSizeUsed Avail Capacity Mounted on
> > /dev/mfid0s1a ufs 989M 64M846M 7%/
> >
> > % stat -f "%N %FB" /COPYRIGHT
> > /COPYRIGHT 1279505857.0
The idea of changing the sysctl vfs.timestamp_precision
to the value 3 worked on UFS for me. But it doesn't seem
to be the default.
Another problem might be when dealing with files that are
stored on a filesystem type different from UFS...
> I was wondering how df (& stat) could show more than seconds
> (Remembering back to 1990 & my
> http://berklix.com/~jhs/src/bsd/jhs/bin/public/statv/
> when Unix used unsigned long seconds since 1 jan 1970
> ( & MSDOS was seconds divided by 2 since 1 jan 1980 )
> )
> FreeBSD 8.2-RELEASE /usr/src/usr.bin/stat/stat.c
> line 320 etc still uses the normal fstat stat lstat.
> But man 2 stat has extended :
> #ifndef _POSIX_SOURCE
> #define st_atime st_atimespec.tv_sec
> #define st_mtime st_mtimespec.tv_sec
> #define st_ctime st_ctimespec.tv_sec
> #endif
The st_birthtime field would be the required one for
sorting here (and defaults, per definition, to seconds).
The "man 1 stat" mentions that stat uses the stat and
lstat system system calls, so this would be the value
that will be retrieved of no "finer time" can be
accessed (which would mean zeros here).
> cd /usr/include/sys ; vi -c/tv_sec /types.h stat.h
> #if __BSD_VISIBLE
> #define st_atime st_atimespec.tv_sec
> structtimespec
> #include
> time.h: #include
> timespec.h:
> struct timespec {time_t tv_sec;/* seconds */ long tv_nsec;/* nanoseconds */};
>
> I guess extended timespec may get compiled in to VFS but not UFS,
> but no time to look further, Good luck Polytropn.
At least that's a starting point. I see that changing
the sysctl mentioned above seems to be sufficient for
the current purpose. However, I'd like to see the system
defaulting (!) to a resolution better than seconds, as
this is definitely possible.
> PS Here with UFS (per Dan's tip, thanks) I see:
> sysctl vfs.timestamp_precision=2 ; stat -f "%N %FB" /etc/motd
> /etc/motd 1306839862.0
That's understandable, as the "finer time" will
be generated only upon file _creation_; for files
that are already present, 0 is the typical
result.
# sysctl vfs.timestamp_precision=3
vfs.timestamp_precision: 0 -> 3
And then:
% touch hickup.txt
% stat -f "%N %FB" hickup.txt
hickup.txt 1325686735.035925369
In comparison:
% stat -f "%N %FB" /etc/motd
/etc/motd 1309547364.0
which has been created prior to changing the
vfs.timestamp_precision sysctl.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Browser
On Wed, 4 Jan 2012 07:17:47 -0500, Daniel Lewis wrote: > Im running Free BSD 8.2 and was wondering whats a good web browser for > version 8.2? > Where and how would we install it? ( Im really new to unix) You will get many different answers for this question. :-) What are your primary requirements for a web browser? Do you have experiences with browsers so you can say which "kind" you want to use? Personally, I'm a long-time user of Opera. I've installed it from ports, but it should be no big deal to use the precompiled package version. Intermission: Read the handbook section about how to install software on FreeBSD. I'd also recommend the chapter about web browsers. http://www.freebsd.org/doc/handbook/ports.html http://www.freebsd.org/doc/handbook/desktop-browsers.html You'll find that it is very easy to follow the advice given in the Handbook and have your web browser running very quickly. Back on topic: I've also installed the Linux plugins so I can "enjoy" (bah!) "Flash" stuff if required. Note that those are already a bit out of date: opera-11.50 opera-linuxplugins-11.50 linux-f10-flashplugin-10.3r183.5 swfdec-0.8.4_3 swfdec-plugin-0.8.2_3 You can get a similar functionality with Firefox, which is my secondary browser. I'm still using version 6.0.1, but newer ones are already in the ports collection. However, there's a real fleet of web browsers waiting for you around the corner. If you're already using a desktop environment, try their built-in browsers, like for example Konqueror or Galeon or Epiphany. For some minimalism, there's lynx or dillo. And there are many more. See what /usr/ports/www has to offer. After trying many, I've always come back to Opera, as its mouse and keyboard support (!) is very well designed, the browser is fast, the UI can be turned into something usable, and it supports all the stuff I need. I don't say that Firefox is not good, but for _my_ individual needs and habits, Opera is just a little bit better suited, that's all. If you have concerns regarding web browsers spying at your browsing habits and reporting them to the authorities, maybe you re-consider using Opera. Keep in mind that even if it's free, it's not really open, if I remember correctly. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Exact timestamp for sorting and renaming files according to creation order
On Tue, 3 Jan 2012 14:49:02 -0600, Dan Nelson wrote: > If you ask for the date to be printed in "float" (F) format, it gives more > precision. The default is unsigned int (U) format. > > % stat -f "%N %FB" /COPYRIGHT > /COPYRIGHT 1306190895.046721049 Strangely, I only get a 0 "suffix" for any time stamp, no matter if I create the file or apply the command as shown above to an existing file: % stat -f "%N %FB" /COPYRIGHT /COPYRIGHT 1313951230.0 Am I missing some file system feature? Otherwise, this _exactly_ looks like what I'm searching for. It doesn't need to be a "human-readable" date representation. by the way, I'm running FreeBSD 8.2-STABLE/x86 of late August 2011 here, file system used is UFS2. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Exact timestamp for sorting and renaming files according to creation order
For a sorting script, I'm currently searching for a method to get file creation date and time as exactly as possible. The best resolution I could get was seconds. In case more than one file is created within the same second, it doesn't work precisely enough. It should work from sh script. For the purpose of preparing the sort list (that will be sorted and then be used as a template for renaming the files with a prefix and a counter), I'm using the "stat" program which creates output like this: % stat -f "%N %B" -t "%Y-%m-%d_%H:%M:%S" 1.txt 1.txt 2012-01-03_12:12:12 It's also possible to use the Epoch time format, but it doesn't provide a solution better than seconds: % stat -f "%N %B" -t "%s" 1.txt 1.txt 1325589132 I've read the manuals for stat as well as for strftime (which is the facility stat's -t parameter addresses), but found nothing that is more precise than seconds. Does anyone have a suggestion how to precisely determine the order files have been created? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Kernel Internals Documentation
On Tue, 3 Jan 2012 09:01:47 -0600, Mark Felder wrote: > On Tue, 03 Jan 2012 08:46:54 -0600, Alejandro Imass wrote: > > > I would just like to add that is FreeBSD was so crappy open sour > > software, why does it run half the Internet? > > This must be a mistake. I was just assured this weekend that FreeBSD is a > niche OS. Maybe consider the chance that a FreeBSD OS can be turned into closed source (which the license explicitely allows) and put into some embedded device, a router, a DSL modem, a managed switch... In parts like this, you won't recognize FreeBSD anymore. If you consider such devices "niche devices", think again: You'll find them near any Internet-connected computer and among the bowels of the whole Internet. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: reduce partition size. HELP
On Sat, 31 Dec 2011 08:45:32 -0700 (MST), Warren Block wrote: > On Sat, 31 Dec 2011, ??? ??? wrote: > > > , Robert. > > > > ?? ?? 31 ??? 2011 ?., 5:16:33: > > > > > > RH> =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= writes: > > > >>> Is there any way to reduce partition size on live system? > > > > RH> No. > > RH> Basic steps: > > RH> 0) go to single-user; unmount partition > > RH> 1) backup affected partition; test backup > > RH> 2) delete old partition > > RH> 3) create new/smaller partition > > RH> 4) restore from backup > > > > is there a way to goto singe-user through ssh? > > Single-user and unmounted partitions are desirable but not required. > See dump(8) about the -L option. Of course. And in addition, how about that? NOT TESTED! READ *FULLY* BEFORE DOING ANYTHING! For this example, /dev/ad0s1a is the / partition. There are other partitions (such as /var or /home) associated to other device files. Let's also assume /dev/ad0s1e is the /var partition. Onto the /var partition (or /home or any scratch oartition), copy the content from / (primarily because of /sbin, /bin and maybe /etc); maybe use this approach: # cd /var # dump -0 -L -a -u -f - /dev/ad0s1a | restore -r -f - Make sure /var does _not_ contain directory names identical to those found on the / partition! As I said, maybe use /scratch. :-) (Oh, and you can of course shorten the dump parameters to -0Lauf and restore's to -rf, but I chose this representation for making implicitely clear why to use _those_ options.) Then umount / and mount /var (I'll keep this for the example) as the new / (which now has all the things / should have): # umount /var # umount -f / ; mount -t ufs /dev/ad0s1e / Then the device associated to / should be free to be unmounted - a step desirable, but it should be no a "big" problem to operate on the device files associated with a _mounted_ partition. The more I think about it... /var is a really bad choice. Use /scratch, or at least /home. AGAIN: NOT TESTED! MAY BLOWENFUSEN & CORKENPOPPEN! :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Single user mode exits unexpectedly
On Sat, 31 Dec 2011 00:57:04 -0500, Janos Dohanics wrote: > I have just rebuilt world and kernel according to the Handbook, > installed the new kernel, rebooted, logged in, issued "sudo shutdown > now" - the machine entered single user mode, then immediately exited > without any intervention by me and continued to boot into multiuser > mode. That's not the procedure required. From the comment section of /usr/src/Makefile: 1. `cd /usr/src' (or to the directory containing your source tree). 2. `make buildworld' 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). [steps 3. & 4. can be combined by using the "kernel" target] 5. `reboot'(in single user mode: boot -s from the loader prompt). 6. `mergemaster -p' 7. `make installworld' 8. `make delete-old' 9. `mergemaster'(you may wish to use -i, along with -U or -F). 10. `reboot' 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Step 5: reboot _into_ single user mode. After installing the kernel and shutting down the system, let it come up to the kernel loader. You can enter that stage by pressing the space bar several times. If I remember correctly, you'll then see prompt Ok > _ Then enter "boot -s" to bring up the system in single user mode. After you've confirmed the shell, do # mount -a # cd /usr/src # mergemaster -p and continue with steps 7 - 10. If you have the Beastie menu, press [4] to get into the single user mode. > Here is a snippet from /var/log/messages: > > Dec 30 17:41:15 iguana rc.shutdown: 30 second watchdog timeout expired. > Shutdown terminated. > Dec 30 17:41:15 iguana init: /bin/sh on /etc/rc.shutdown terminated > abnormally, going to single user mode > Dec 30 17:41:15 iguana syslogd: exiting on signal 15<--- > Dec 30 17:41:28 iguana syslogd: kernel boot file is /boot/kernel/kernel <--- > > This seems to be happening every time in response to "shutdown now". The reason might be that you're running your updated kernel, but the world has not been properly installed? > However, I can cold boot this machine into single user mode with > nothing unusual. > > This is FreeBSD 8.2-STABLE amd64, rebuilt on 12/26/2011 > > I guess I may have unintentionally changed a config file? Where should > I look? Review your installation steps and _maybe_ redo the installation as indicated in the manual. Maybe there's really just something out of sync. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing FreeBSD ver. 8.2
On Fri, 30 Dec 2011 20:45:37 -0800 (PST), leeoliveshackelf...@surewest.net wrote: > Good evening, dear FreeBSD enthusiast. I am a newcomer, > and have installed FreeBSD 8.2 on a Hewlett-Packard xw4400. Excellent choice of OS. > After many hours of frustration, I am tearing my hair out. > I want my system to include an M-Audio Delta 1010LT sound > card, MIDI over USB driver, X-windows, and Gnome. The M-Audio Delta sound hardware is listed in the snd_envy24 sound driver. MIDI over USB... sorry, no experience with that (only "real" MIDI in ye olden times). X-Window (X11) and Gnome need to be installed, they are not part of the operating system. > The instructions in the handbook and on-disk man do not > seem to apply to this version of FreeBSD, or at least I > do not seem to know how to apply them. The basic steps should be the same. They have been nearly the same since 4.0. :-) > I type "find sound," or "find pcm," or find snd_envy24," > or "find x11," or "find gnome," and receive either a > blank response, or response of "file does not exist" to > all of these queries. That's correct. See "man find" for how to properly invoke that program. Basically, you use # find -name to find some specific files, e. g. # find /usr/ports -name gnome # find /boot -name snd_envy24\* You can add the \* wildcard (* needs to be escaped for the shell to _not_ expand it!) if you're not searching for one specific file name. > All of these items were supposedly installed at the time > of system configuration, but as to where, I cannot seem > to determine. Installed software will be in /usr/local. You can for example use the command # find /usr/local -name gnome-session\* to see if the gnome session manager has been installed. An easier approach is to make yourself familiar with ports and packages, and how to use the pkg_* family of tools, as well as how to read the content of /var/db/pkg; for example, all installed software will cause a directory to be created in that path, so you can see if it's there: # ls /var/db/pkg/gnome* will list all gnome stuff that is installed. This subtree is your "catalog of installed things". But it's _much_ easier to read "man pkg_info" and use that. It's not the time for a lecture about shell scripting right now. :-) Just in case you don't know the correct syntax for any command, or the purpose or layout of a file, use its man page. FreeBSD is known for covering all the parts of the OS with a proper manual page (system binaries and scripts, configuration files, device drivers, kernel interfaces, library functions, system operation and maintenance procedures, and introductions). > The gnome installation took twice as long as installation > of everything else. Where did sysinstall install it? Into /usr/local. Gnome is a "heavy beast" with lots of dependencies. > How do I get it to start? This is covered in the Handbook in section 6.7: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11-wm.html make sure you're running the depending services related to making Gnome functional. Additionally, in most cases you'll want to have hald_enable="YES" dbus_enable="YES" in /etc/rc.conf, the system's configuration file. Also see http://www.freebsd.org/gnome/ > The response to "startx" is "file does not exit." I realize > that I may be missing something o > b! > vious. It seems that you're missing X. :-) You need to install the xorg port (or package via pkg_add -r) along with the driver for your graphics card. If you have successfully accomplished that, Gnome should be up and running. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Kernel Internals Documentation
> is open and that everyone can use rather than be stuck with closed, crappy > OSs from Greedy corporations like Microsoft. Because exactly that attribute - greedy - makes it a successful company, and success (in terms of unit sales and therefore market share) is what defines positive aspects in our society. > > > By the way, just out of morbid curiosity, how are ASLR and KMS support > > > coming along? Doing a quick perusal it would appear that everyone but > > > FreeBSD supports them. I am sure if I am in error and FreeBSD has full > > > support for them you will inform me of same. > > > > I think KMS is still a Linuxism, such as Wayland. But > > it's possible that it will arrive in FreeBSD when an > > urgent need by its users is expressed. As long as this > > is a "niche application", I don't think support will > > be created. You know, it's _very_ deep inside the > > bowels of the OS where this work has to be done.. > > > KMS is what allows the kernel to basically restore the video display to a > functioning condition of the X server crashes? is that all it does? KMS would allow the kernel (in its early stage during OS boot) to address the graphics hardware (GPU and display) to initiate certain resolutions and color settings, which could make the booting process colorful and entertaining, providing an appealing "first sight effect". Switching between X and not-X should be easier. Doing such settings in the kernel could also benefit security as it takes the required privileges off the X server. Moving _that_ kind of functionality into the kernel could enable non-X use of graphics capabilities, I also assume. Details: see http://en.wikipedia.org/wiki/Mode-setting -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Kernel Internals Documentation
On Fri, 30 Dec 2011 10:22:31 -0500, David Jackson wrote: > Of course, those best able to document are those who wrote it in > the first place, since they already know how it works. A fact seems to be: "Modern" programmers don't bother with documenting, or coding guidelines, or style or other things that "slow down" development. This attitude isn't new in general, as it has been done that way even in IT dinosaur times: There are COBOL programs still running, and nobody knows _why_ they are running and _how_. If someone had written usable documentation at the time the program was created and maintained, skilled COBOL h4x0rs wouldn't be able to write the desired salary on the contract as _they_ wish. :-) But keep in mind: Writing code and writing documentation are two different things. There are people who are excellent coders, but bad writers. In some teams, you'll find code writers and doc writers separated, but working together. This approach isn't free of problems, but also seems to work. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Kernel Internals Documentation
On Fri, 30 Dec 2011 09:59:14 -0500, Jerry wrote: > On Fri, 30 Dec 2011 14:22:30 +0100 > Polytropon articulated: > > > >From "man iwn": > > > > Intel Wireless WiFi Link 4965/1000/5000/5150/5300/6000/6050 > > IEEE 802.11n driver > > So they actually got support for one such device. I refer you to > <http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html> > which does not even list support for "n" protocol devices. In a web forum (where certain kinds of users expect documentation to take place), the following list for support in 9.0-RELEASE can be read: Airlink101 AWLL6090 ASUS USB-N11 ASUS USB-N13 ASUS WL-160N Belkin F5D8051 ver 3000 Belkin F5D8053 Belkin F5D8055 Belkin F6D4050 ver 1 Buffalo WLI-UC-AG300N Buffalo WLI-UC-G300N Buffalo WLI-UC-GN Corega CG-WLUSB2GNL Corega CG-WLUSB2GNR Corega CG-WLUSB300AGN Corega CG-WLUSB300GNM D-Link DWA-130 rev B1 D-Link DWA-140 DrayTek Vigor N61 Edimax EW-7711UAn Edimax EW-7711UTn Edimax EW-7717Un Edimax EW-7718Un Gigabyte GN-WB30N Gigabyte GN-WB31N Gigabyte GN-WB32L Hawking HWDN1 Hawking HWUN1 Hawking HWUN2 Hercules HWNU-300 Linksys WUSB54GC v3 Linksys WUSB600N Mvix Nubbin MS-811N Planex GW-USMicroN Planex GW-US300MiniS Sitecom WL-182 Sitecom WL-188 Sitecom WL-301 Sitecom WL-302 Sitecom WL-315 SMC SMCWUSBS-N2 Sweex LW303 Sweex LW313 Unex DNUR-81 Unex DNUR-82 ZyXEL NWD210N ZyXEL NWD270N This clearly is more than "one such device". If you employ a common means of finding documentation for a certain kind of users - using google - you'll be able to determine the source of that list. > I am not sure if this is an introductory level chip or used in higher > end devices although I have my strong suspicions. In any case, newer > and more fully functional "n" devices still lack any significant, and I > use that word graciously, support. You can see from the list that there is work being done. I'm sure as soon as "all" devices are fully supported, this kind of devices will be obsoleted and replaced by something different - which _then_ will lack support. > As for your inquiry as to why I don't write one myself, fair enough. I > have a family to support, various organizations I work with or > contribute to, etcetera. To actually invest the time (and I have no > idea how much time it would entail), thereby taking it away from other > ventures I am involved in, i.e "work" for example, not to mention the > documentation that I would probably have to buy to learn how to > actually write a driver for such a device and make it work on FreeBSD > since I have never done it before, and acquire whatever other skills > and material I might need all for a grand ROI of "$0" is beyond absurd. Luckily, FreeBSD documentation comes for $0. The required documentation to access the hardware... well, that's a different question. Again, as we did discuss (and agree upon) before, supporting FreeBSD is not in the scope of hardware manufacturers. Supporting more than the platform they get "aliments" for simply wouldn't pay. The unit sales for _this_ world of IT are simply to low to justify the work. The alternative would be to release all the specs for the hardware. But if a manufacturer doesn't want to do this, primarily to _not_ publish essentials of the business, it is okay. Of course, this makes it harder for _free_ volunteers to write a driver. One could argument: The manufacturer _doesn't_ want you to use his hardware on any OS that is not "Windows" - which again is his right. > I am not a socialist asshole. I'm happy to hear that, so please don't behave like one. > I don't expect the government to bankroll > me while I sit on my ass working on a hobby. So why do _you_ bankroll the government with your tax money for sitting on their ass spying at you or doing nothing? :-) > If FreeBSD really wanted to make a quality product they would hire > competent programmers to create the drivers, etcetera that are seriously > needed. I would gladly pay any reasonable charge for a product that > worked. I am not a socialist/fascist asshole and I despise those who > are. Other OSs have all ready gone this route. I would also be willing to buy FreeBSD as an OS if the functionality I require can be purchased that way. It's not that I'm using free software exclusively. I can't do that because _my_ reqirements are 99% met by free software, and 1% isn't, and this is where I happily pay to get things working. (On the other hand, I often, nearly _regularly_ see products people pay for that do _not_ work, and they don't have any chance to get their money back, or get any other kind of compensation from the makers of that software.) On the other hand, I'd be happy to pro
Re: Same version on binary packages and updated ports
On Fri, 30 Dec 2011 13:14:35 +, RW wrote: > On Thu, 29 Dec 2011 19:53:25 +0100 > Walter Alejandro Iglesias wrote: > > > I really appreciate that you all, Jerry, Polytropon and Chuck, > > took your time to answer me. But I think some of you understood > > paragraphs like individual-separated statements, that's why you > > did not fully understand my question (my horrible English helps > > too :-)). > > > > Let's see if I can explain myself. > > > > I know that FreeBSD base system and 3rd party are "managed" > > separately. For RELEASE I meant the ports included in a fresh > > RELEASE install. The scenario is: what to do after a fresh > > RELEASE install. Once you updated the ports with 'portsnap fech > > extract update' you have newer versions at the port tree. Then > > you can upgrade the already installed software using > > portupgrade... But compiling! > > One strategy is to use csup to only update the port tree to release > tags and so use successive release packages as you update the base > system. You need to check portaudit for vulnerabilities. For such tasks, csup provides a good basis for explicitely specifying a RELEASE or security patch level. This can be applied to both the sources and the ports tree (of the corresponding date). > An alternative is to use stable packages. There are two problems with > this. The first is that whilst these packages will mostly work they are > not guaranteed to be compatible with release, or older stable, base > systems. You can eliminate this entirely by using stable and updating > world after updating the ports tree. A common rule is: If you use -STABLE for the OS, you want to keep your ports tree current and do security upgrades whenever neccessary (see portaudit for that functionality), or if the users of the production server require a certain version change. Using the ports infrastructure can also be helpful when you need to so something "extraordinary", like intendely installing an older port (see portdowngrade for this particular task) or fixing a port change from today to tomorrow (as this will show up in a csup delta, but not neccessarily as fast in a portsnap run). > The second problem is the variable lag between a port being > updated and the package becoming available. Frequent updating > exacerbates this problem. If you use portupgrade -P every day it will > probably never use a package file. In this case, I would also suggest using the compiling approach. Binary packages don't give you the flexibility to follow -STABLE or -RELEASE-p that closely in time. > If it's for a production server, you might consider building your own > packages on a separate machine. You could also designate a jail for the building process (if the server has enough power) and either use the results generated in that jail for installation or follow the suggestion of using the packages generated in that jail (/usr/ports/packages will be populated by the "make package" command). However, as you're mentioning a _production_ server, it's always wise to test the updated software before bringing it into operation for that system. The idea of using a "mirrored server" for testing comes handy here. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Kernel Internals Documentation
On Fri, 30 Dec 2011 08:05:10 -0500, Jerry wrote: > On Fri, 30 Dec 2011 22:35:46 +1000 > Da Rock articulated: > > > Was this really necessary to post to the list? Publicly? Opinions are > > your own, but this does appear rather vindictive and not really > > wanted on a friendly list. > > > > For reference Polytropon has been rather helpful many times on this > > list regardless of how many faux pas maybe made; I'm sure you're not > > without fault either. > > The fact is that Poly has taken "negativity bias" to a new level. I > fully realize that part of this is due to his socialist/fascist > upbringing; however, that in itself does not justify it. Can you please stop that shit?! You're starting impolite attribution which is not justified on this list, and not in general life. If you would live in _my_ country (luckily you don't), that would be a case for court. Be happy to have this right of expression, even if you're abusing it on nearly any occassion you can get. And replace "negative bias" with "negative experiences", so it becomes the truth. Finally, our _individual_ experiences are what forms our opinions which we turn into statements. Luckily, logic is free of subjective argumentation, and I think that's why you focus on individual statements in order to insult people instead of dealing with the logic statements they bring, because that would maybe force you to re-think your _own_ position! > I did take a class in quantum physics in college. However, I can > assure you that I would never attempt to pretend to understand it nor > lecture about it. Yet, according to his own statements, not mine, he > has no knowledge of Microsoft yet he continues to lecture on it. As I said before: Not true. You're building your argumentation on a false assumption, leading the whole statement to be wrong (logic 101). Your knowledge from the quantum physics class - it should be something that you can elaborate on, and use in discussions. Even if it was "long ago" (in college), as long as this knowledge of yours is present (and correct), you can make use of it, use it even in concluding "new" things, and putting it into relation to other theories (e. g. superstring theory, gravitation). And why shouldn't you? Knowledge you gain and that you can _apply_ opens discussion fields, even if you enter them by a false assumption or wrong conclusion. Whenever you _learn_ something, it's not worthless. Except _you_ would judge gain of knowledge always in consideration of where it can be applied, and what amount of time it consumed. That is a fully justified point. That's why I'm also paying attention what to learn - be it fundamental UNIX knowledge that made me access many different UNIX and Linux systems, or "Windows" knowledge that is obsoleted as soon as a new version is out, and you need to repeat re-learning things. After all, even the pure fact of _learning_ is good, at least for the brain (which benefits from any learning, no matter if it's short life knowledge or fundamental stuff). Learning keeps your brain healthy. > That > is pathetic. You are pathetic. > That would be akin to me reading the cover page for an > application available on FreeBSD, one that I had never used and then > giving a lecture on its use and implementation. But isn't that what you sometimes do? If I understand your intial claim correctly, you stated there was no N device documentation in FreeBSD. (Note: This is a conditional statement. You're very fast in skipping such fine details in expression, that's why I think it's worth mentioning it again: "if - then", this means "if not, then not" in this case. So read it carefully.) >From "man iwn": Intel Wireless WiFi Link 4965/1000/5000/5150/5300/6000/6050 IEEE 802.11n driver ^ Is that what you meant? Of course, this (just like the module sources) is _not_ intended as an end-user step-by-step illustrated guide on how to get networking up. And finally, there are tools to help you with that (typically coming with desktop environments). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Kernel Internals Documentation
On Fri, 30 Dec 2011 07:15:00 -0500, Jerry wrote: > On Fri, 30 Dec 2011 07:39:58 +0100 > Polytropon articulated: > > > However, there are differences in how you judge documentation > > to be _good_. Talk to a mainframer, and he will tell you a > > different story. Then talk to a "Windows" person and explain > > what documentation is, and he'll tell you that you don't > > need it. :-) > > Poly, I think you just broke your own record for retarded statements. Ah Jerry, impolite as always. :-) You're missing to identify the ":-)" symbol appended, and the MAIN STATEMENT of that sentence, which is that "good documentation" depends on _many_ factors, such as amount, location, quality, availability of translations, organisation and structure. There are many opinions of what "good documentation" is, and it depends on who you will ask. > If you were to expand your statement to include documentation for > drivers for "N" protocol devices, FreeBSD users would say that they > don't need it either since they don't have such drivers. I won't comment on this as it has been discussed already, and I think I remember that I could even agree with your standpoint in this regards. > The fact is > that Windows was designed to "just work" so that users could spend > their time on the project(s) they wanted to work on and not reading > tons of frivolous garbage on simple things like networking two or more > computers together. If the project is about developing stuff, inventing things and creating OS-related stuff, then... where can I find the "Windows" source code please? :-) How can you explain then that _I_ use FreeBSD in a "just works" state to get my projects done, whereas the praised "Windows" won't do it? Of course you'll say that I'm a minority that doesn't express in unit sales and market share, and here the discussion ends for you. What "Windows" was _designed for_... well, that is a highly debatable point which doesn't belong to this list, not even declared as off-topic. Reality - at least in my country and working field - shows that "Windows" doesn't "just work" for the majority of users here. The lack of easily accessible documentation and reasonable procedures and common standards is a main reason for people to leave this architecture. More and more of them seem to recognize that the claim "just works" is a claim, but there are more and more situations where it's not backed up, means: Does NOT work, causes downtime, causes COSTS. It might be fully different in your country and your working field, keep that in mind. > Poly, you have stated several times in a multitude of posts that you > neither use nor understand MS Windows. I have stated that I don't use it, but I understand it well enough, I can assure you. It's common practice to deny any knowledge "in the field" to not get filled up with "help requests" (i. e. "work for free") in that trouble-filled area of computing. But after all, more often than I'd like to admit I'm the guy who fixes that stuff and makes things work again, and this is due to my experience and knowledge, not because of some magic wand I carry with me. :-) > For most people, that alone > would preclude them from making a statement on said subject. Obviously, > talking about something you readily admit to having no knowledge about > is no problem for you. Pathetic. Reconsider your statement with the information of my present knowledge. Also you should know that I'm NOT "most people". "Most people" have _never_ achieved anything notable in history. This is what _exceptional_ people did, be it for good or for evil (in which case "most people" are responsible for making it happen by ambitiously helping, blindly following or ignoring). To repeat for you: You may regard my knowledge as fully sufficient to make educated statements. The fact that I avoid that in certain fields does not change that fact. Similarly, I'm not mentioning or explaining all the fields I'm familiar with, which doesn't imply that I don't have actual knowledge in those fields. You should be able to judge my credibility from the _content_ of the statements I make, seen in _context_ and interpreted properly. But maybe that's the fate of those who use a language that is not their native ones. I do know that I have certain deficites in using the english language, so this might be a reason; I'm not a native speaker. Also I'm just a man who can make mistakes. Show me a mistake and I won't be that stupid to insist on it. You know that this works (just read some of our older disputes). In fact, admitting a mis
Re: FreeBSD Kernel Internals Documentation
. If properly used Doxygen can help, but it's not the entire solution, I fully agree. Some people need to learn the hard way, just like me when I visited my _own_ source code a decade later and found something like kk[w.q].x = fbx(x,x0+a0+1+aa[q].t,dt,h,dh-1+3); which is totally ugly. :-) > One idea might be to have an official wiki that contains the template > generated by Doxygen which can then be filled in. When changes to the > source code is made, it is good practice for the commiter of such changes > to document their code as it is submitted. Also Wikis aren't for everything. I don't know how _you_ as a developer think about it, but _I_ like to have the documentation available _in_ the code I consult, offline, without the need to use a web browser, everything based on _files_ so I can use the system's powerful tools to work with them (e. g. search for information, filter, create lists and so on). FreeBSD has an official Wiki, and there are several others. Again a question arises: Would you like the documentation to be spread across arbitrary Wikis, user home pages, web forums and blogs? > This allows others who come along who need to maintain the code to more > easily understand what the code does. History teaches that this is achieved by using the code itself. :-) > Another idea which would also improve the useability of FreeBSD would be to > have a wiki which would be updated by kernel contributors whenever they add > support for a certain piece of hardware. This would make finding hardware > compatability information easier from one central, up to date and current > source of information. Those informations will typically be added to the UPDATING information, as well as to the release notes of an upcoming RELEASE. Deltas in the src/ subtree also indicate when something new is present. As FreeBSD is a _quality_ operating system, developers pay attention to write the documentation along with releasing new drivers, so you aren't stuck with an ugly-hacked kernel module full of lines that look like the fbx() example I gave above. :-) > These documentaiton ideas, for commiters to document their code when they > upload it, and document their hardware support additions, are just good > software practices that should be highly recommended and encouraged I fully agree with that statement. If you could, for example, point to documentation you judge _good_, or point at some FreeBSD documentation that you think needs heavy improvement, it would help to back your argumentation. Otherwise, it can be seen as "already done". -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: Root access policy
On Thu, 29 Dec 2011 09:15:45 -0800, Carl Johnson wrote: > Damien Fleuriot writes: > > > On 12/29/11 10:58 AM, Polytropon wrote: > >> On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote: > >>> For the first time, a customer is asking me for root access to said > >>> customer's servers. > >> > > >>> Assuming that I'll be asked to continue administering said servers, I > >>> guess > >>> I should at least enable accounting... > >> > >> You could have better success using sudo. Make sure > >> the customer is allowed to "sudo ". The > >> sudo program will log _all_ things the customer > >> does, so you can be sure you can review actions. > >> Furthermore you don't need to give him the _real_ > >> root password. He won't be able to "su root" or > >> to login as root, _real_ root. But he can use > >> the "sudo" prefix to issue commands "with root > >> privileges". > >> > > > > "sudo su -" or "sudo sh" and the customer gets a native root shell which > > does *not* log commands ! > > The sudoers manpage mention the noexec option which is designed to help > with the first problem. They also show an example using !SHELLS which > can help with the second. It's also worth mentioning "super" again - as an alternative to "sudo". But after all, if restricted in any way, both of them are _not_ requivalent to "full root access" (equals: root + root's password) which the customer initially demanded. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Same version on binary packages and updated ports
On Thu, 29 Dec 2011 17:16:11 +0100, Walter Alejandro Iglesias wrote: > Hello, > > I am giving my firsts steps with FreeBSD. > I've searched a lot in google, mailing list, forums, freebsd > handbook and I am still not clear about the following. > > In a RELEASE fresh install, after updating the ports using i.e. > portsnap, the packages downloaded with pkp_add -r are older > versions respect their port counterparts, leading to > dependencies issues. So, once the ports tree is updated: > > 1) Am I forced to compile all? No, you aren't forced to anything. :-) In case you intend to bring your _installed_ programs up to date (where "date" is indicated by the ports tree), use a tool like portmaster or portupgrade to upgrade all that need upgrading. > 2) Should I use STABLE to get the same versions with pkg_add > than compiling up to date ports? RELEASE and STABLE are related to the OS, not to the 3rd party applications found in the ports tree. If to use RELEASE (with -p security patches) or following STABLE depends on your requirements. OS and installed applications are independent (mostly). > Are STABLE packages compiled > from this ports? Yes. From time to time, a "snapshot" of the (continuously evolving) ports tree is used to build the binary packages. _Which_ set of packages will be requested by running "pkg_add -r " depends on $PACKAGEROOT. For example, if it is set to ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest it will use the latest packages (which are slightly behind actual ports in most cases). But if ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release is used, the packages of RELEASE will be used, such as you can find them on the installation media > 3) In case my assumption above is correct; taking in care that > in a production system it is advisable (handbook) to stay with > RELEASE, should I avoid updating the ports tree in i.e. a server > machine? That depends on the usage profile of that system. You should keep track of _any_ security issues you might have with the ports you use (e. g. web servers, PHP, MySQL and other "potentially dangerous" stuff). You can use freebsd-update to follow RELEASE-p to get the security updates for the RELEASE you are running. If you don't update the ports tree, it will stay at the date of RELEASE, delivering ports from exactly that date. It's often the better choice to update the ports tree and upgrade ports that need this (as I said before, primarily for security reasons, as you did mention a production system, where "bleeding edge" is often _not_ desired). > What to do with broken ports in this case? The RELEASE tree typically doesn't contain broken ports. If an updated ports tree does, update it again soon and try again. :-) In contrast to portsnap, you can use the "classic approach" of using csup to update your ports tree. For smaller deltas, this is acceptable, and it will deliver you the "freshest" ports tree available. > Resuming, is there a default way to install-update the software > keeping ports and binary packages in one piece? I don't think so. The desired method depends on your actual usage requirements. I'd suggest to have a look at a port management tool such as portmaster or portupgrade, as both can handle both building from source and using precompiled binary packages, and keep track of dependencies and automated upgrades. > What is > advisable in general terms for a desktop and what for a server? Also depends on your usage model. For example, my home system is a kind of "install once, then keep using" installation. I'm running 8.2-STABLE and ports from an updated tree. For a server, this approach might not fit - maybe you want to keep all things binary there, or from source only. > It will be enough for me if someone just point me to documentation. The FreeBSD Handbook. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: Root access policy
On Thu, 29 Dec 2011 11:23:31 +0100, Damien Fleuriot wrote: > On 12/29/11 10:58 AM, Polytropon wrote: > > On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote: > >> Obviously, I must comply. At the same time, I cannot continue be > >> accountable for those servers. > > > > Fully correct. Check the contract you made with the > > customer regarding responsibility and conclusions. > > > > Another way of doing things would be to give the customer root access on > the server, if it's entirely his, and relinquish your own root access. > > No more root access for you, no accountability considerations. Yes, that's the "other option". Full responsibility to the customer (as per his demand of a root password), no responsibility to the administrator anymore. > "sudo su -" or "sudo sh" and the customer gets a native root shell which > does *not* log commands ! S!!! Don't tell them! :-) > >> I'd appreciate comments/experience/advice from the wise... > > > > Just a thought: "Parallel administration" (you _and_ > > the customer), both capable of using the power of > > the root password, can lead to trouble. Avoid it > > whenever possible, use "sudo" to satisfy the > > demands of the customer. And make sure that - as > > he now posesses immense power - you regulate the > > responsibilities by CONTRACT: _you_ are not > > responsible if he does "sudo rm -rf /" or > > something similar. > > > > Sadly, this brings in the burden of proof. > As in, prove that *he* didn't issue the dumb command, the customer did. > > This model is endangered by the commands I cited above :/ Ah s!!! Don't point at it again! :-) But you're fully right: The logging has ways to get around it. I think "super" can be used to give a narrowed-down access, but that's not comparable to the customer demanding "root access" (which it wouldn't be). > > I'd give the customer only that much access as > > he actually needs. "Role based models" such as > > they can be done without root passwords > > (tools: sudo, super) can help here. > > > > That's more like it indeed, however it still poses security threats. True, it does. You won't have full security as long as the customer is able to do root-related things. > Say the customer can sudo commands located in /usr/local/libexec/CUSTOMER/ > > All he has to do is write a simple link to sh/bash, and sudo it. Stop that! You're hacking the system by telling all the secret things! :-) Depending on the skills of the particular customer, and of course in regards of what he _intends_ to do himself, there are many possibilities. They even get enlarged when the customer gives the root password to a 3rd person, intendedly or by careless actions. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: Root access policy
On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote: > For the first time, a customer is asking me for root access to said > customer's servers. Customer + root@server == !go; :-) > Obviously, I must comply. At the same time, I cannot continue be > accountable for those servers. Fully correct. Check the contract you made with the customer regarding responsibility and conclusions. > Is this that simple and clear cut? I'd think so. Maybe changing the contract is required. > Assuming that I'll be asked to continue administering said servers, I guess > I should at least enable accounting... You could have better success using sudo. Make sure the customer is allowed to "sudo ". The sudo program will log _all_ things the customer does, so you can be sure you can review actions. Furthermore you don't need to give him the _real_ root password. He won't be able to "su root" or to login as root, _real_ root. But he can use the "sudo" prefix to issue commands "with root privileges". > I'd appreciate comments/experience/advice from the wise... Just a thought: "Parallel administration" (you _and_ the customer), both capable of using the power of the root password, can lead to trouble. Avoid it whenever possible, use "sudo" to satisfy the demands of the customer. And make sure that - as he now posesses immense power - you regulate the responsibilities by CONTRACT: _you_ are not responsible if he does "sudo rm -rf /" or something similar. I'd give the customer only that much access as he actually needs. "Role based models" such as they can be done without root passwords (tools: sudo, super) can help here. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with pkg_upgrade
On Mon, 26 Dec 2011 00:05:16 -0500, David Jackson wrote: > The fact is, I have had problems with portupgrade as well, in fact, > portupgrade would give errors as well with not being able to download > packages, the entire upgrade process at that point would fail. That is the > reason I am trying pkg_upgrade. Make sure PACKAGEROOT is properly set (typically to ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest or *amd64* respectively) and your ports tree is up to date. You can then use portmaster with its -P and -PP options and do a full upgrade as described in the EXAMPLES section of "man portmaster". > Again, things should work better than this. It should. :-) > Things shouldnt be such a hassle. It should work similar to ubuntu apt-get, > where it just works out of the box. You type apt-get upgrade and it > automatically upgrades everything, no need to mess around, That's basically what "man portmaster" says, even though the options are different and allow more flexibility. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Clearing Login Screen on Console
On Sun, 25 Dec 2011 22:37:48 -0600, Kevin Zheng wrote: > I run FreeBSD 8.2-p5 (release) and I can clear the terminal at the login > prompt by hitting CTRL-L on my keyboard. However, I've installed FreeBSD > 9.0-R3 and CTRL-L doesn't clear the screen. > > Personally, I like having CTRL-L to clear the login prompt before and > after I log in, and I'd like to see that on FreeBSD 9 as well. Is there > something I can do with /etc/gettytab to get this behavior working again? Can you put the command "clear" or "tput clear" in the shell's login and logout files (globally /etc/csh.login and /etc/csh.logout, local to the respective user ~/.login and ~/.logout)? You can also test those two commands interactively. I think they are connected to the ^L key, just to make sure if something's wrong with the /etc/gettytab file. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Archived FreeBSD versions
On Sun, 25 Dec 2011 21:37:41 -0500, David Jackson wrote: > I have been looking for archived versions of FreeBSD back to 2.0. Where can > these be found? I have looked on the FTP site but cannot find them there. http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ You'll also find ISO-IMAGES/ in there. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: PolicyKit confusion
On Fri, 23 Dec 2011 14:18:19 +1000, Da Rock wrote: > I checked out /media/hal-* and I see that the mount occurs only as root. > How do I change that exactly? I need it showing for operator group. I've > searched high and low and googled my brains out, but anything remotely > related is for linux and udev. I think I remember I got it working some time ago (on a 7.1 system), relying on the Gnome HAL FAQ which stated something like this: File: /usr/local/etc/PolicyKit/PolicyKit.conf For "N", use your user name; I think you can also use more than one "match" section if you want to allow access for other users. However, I doubt all this HAL / DBUS / PolicyKit magic is really intended for multi-user purposes. :-) Note that HAL also has an option of "fixed mount points" to be set at compile time. I think I had set it... I'm also unsure if NFS mounts are "fixed" or "removable" in PK terminology. Regarding your second question, I can't provide any further information. I just assume it's a means to turn a safe multi-user system into an insecure single-user system, which is what users expect. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LOCALE issue: Pysycache errors on run
On Thu, 22 Dec 2011 23:57:28 +1000, Da Rock wrote: > On 12/22/11 23:20, Polytropon wrote: > > On Thu, 22 Dec 2011 23:13:53 +1000, Da Rock wrote: > >> %env LANG=en_EN.ISO8859-1 pysycache.py > > ^^ > > Isn't that supposed to be en_US or en_GB? > > I'm not sure if there's also en_AU... :-) > > > The one variation I didn't try I had tried en_US and en_AU, but not > with the encoding. I see - if I remember correctly, $LANG is just the language combination, while $LC_* do have the encoding appended, e. g. ISO8859-1, -15 or UTF-8. There's also a "precedence rule" regarding $LANG and the $LC_* settings, and $LC_ALL in relation to the others of $LC_*. > BTW there is en_AU. Cool, didn't know that (just assumed). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.4 -> 8.2
On Thu, 22 Dec 2011 13:47:09 +0100, Albert Shih wrote: > Le 24/11/2011 à 16:09:01+0100, Albert Shih a écrit > > Hi all > > > > Almost classic question about updating from 7.4 to 8.2. > > > > Anyone known if I can temporally run a 7.4 userland+service with 8.2 kernel > > ? > > > > I've ask this because I've ~ 15 jail on one server. I can update the «host» > > pretty fast but with the 15 jail I need some time. And I would like to > > known if durring this time the jail going to work «normally». > > > So I answer to myself. > > Some body tell me it's like > > "My gut reaction was "Are you familiar with the game of Russian Roulette?". > > Wellit's work...almost. > > Here what I do : > > Upgrade kernel and userland from 7.4 to 8.2 on the host. > > Upgrade all userland of my all jail to 8.2 > > Until now everything work fine. > > Delete old libs/files/man > > and...apache stop working. > > After do a > > portupgrade -fR apache > > everything work again. > > Be careful the > > portupgrade -f apache > > is not enough. I don't known which ports have some problem but I > got a SSL error. So first I just update apache. It's not good. Then > apr, etc...finally I upgrade with «-fR» and everything work again. > > For subversion you need to force upgrade neon too. You should basically be able to run v7 programs in a partially installed v8 environment as long as the COMPAT_FREEBSD7 functionality is enabled and the compat7x-i386-7.3.703000.201008_1 port or package has been installed. However, kernel and world should match each other. After an upgrade from one major version to the next one, it's the best solution to update _all_ installed ports. The "man portmaster" manpage contains a nice example for this situation. It should be similarly easy to achieve with portupgrade. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LOCALE issue: Pysycache errors on run
On Thu, 22 Dec 2011 23:13:53 +1000, Da Rock wrote: > %env LANG=en_EN.ISO8859-1 pysycache.py ^^ Isn't that supposed to be en_US or en_GB? I'm not sure if there's also en_AU... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Port, Packages, and Patching, Upgrading
SUP_UPDATE= /usr/bin/csup SUPFLAGS= -L 2 SUPHOST=cvsup.freebsd.org SUPFILE=/etc/sup/stable.sup PORTSSUPFILE= /etc/sup/ports.sup DOCSUPFILE= /etc/sup/doc.sup DOC_LANG= en_US.ISO8859-1 de_DE.ISO8859-1 (Typically alter DOC_LANG to fit your needs.) Also check what you can enable or _disable_ in /etc/make.conf and /etc/src.conf (see /usrsrc/share/examples/etc/make.conf and "man src.conf" for details), especially for systems low on resources where you intendedly want to _not_ build and install certain parts of the world, the kernel and the kernel modules. When you now do the following: # cd /usr/src # make update both source and ports will be updated. BUT: This method is more complex than using portsnap! Especially for "bigger differences" between update sessions it typically needs more time. >From this point, it's easy to recompile world and kernel, and then update ports selectively or "all in one run". Tools like portmaster, portupgrade or portmanager are a big help here. For updating the system, follow the instructions in the comment header of /usr/src/Makefile. For the ports, use your favourite tool, > Any of you that use pkg_add and Sysinstall to install packages, can you > maybe describe what you do to install updates, Patches, or just in > general, keep your system patched? If you intendedly (nothing bad here!) want to use binary packages, you can use the -P and -PP option of portupgrade and portmaster. The EXAMPLES section of the manpages have some ideas on how to do "full updates". Unless you're using a custom kernel and want to follow the RELEASE branch, including the security patches, also consider using freebsd-update. This tool updates the OS (the base system) in a binary way, also very comfortable. The combination of both ways is a usable difference to using ports and building everything from source. FreeBSD puts you in choice here, and I'm glad it does, because I prefer _this_ or _that_ method depending on the use of different systems. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .config
On Mon, 19 Dec 2011 10:48:23 -0500, ill...@gmail.com wrote: > On 30 November 2011 14:03, Polytropon wrote: > > On Wed, 30 Nov 2011 13:40:19 -0500, ill...@gmail.com wrote: > >> A dirty workaround might be to link /.config > >> to something innocuous. One could obvio- > >> usly also have /.config mounted as a tmpfs(5). > >> So it couldn't persist from boot to boot. > >> > >> The cleanest solution is to forgo qt/kde, but > >> then you're slightly more limited in what you > >> can use for office-type stuff. > > > > The question remains: > > > > How is a user-started process (e. g. when you run > > the "startx" command) supposed to create directory > > entries and files on root level /, a thing that > > only root and root-like users (and programs!) > > should be allowed to? > > > > % mkdir /.config > > mkdir: /.config: Permission denied > > > > As a normal user, you _intendedly_ can't do this. > > Why would you assume that a program you start > > can do it? > > I don't have any QT/KDE stuff but isn't kdm suid > (& owned by root)? That could be the reason: kdm, belonging to the KDE world and quite probably using Qt, running with the permissions to access /. You could temporarily try to disable kdm and replace it by xdm, or no display login manager at all. In that case, /.config shouldn't appear anymore. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: C|Net's Download.com adware, spyware, malware hijinkx.
On Fri, 9 Dec 2011 13:05:05 -0600, Ryan Coleman wrote: > > On Dec 9, 2011, at 12:03 PM, Polytropon wrote: > > > On Fri, 9 Dec 2011 09:38:59 -0600, Ryan Coleman wrote: > >> It's still not malware, it's bloatware. Why would you > >> not go to the development website to get the program anyway? > > > > Uninvitedly adding toolbars, changing web browser > > home page and default search engine are - in my > > opinion - malicious acts, so the term "malware" > > may be correct here. Maybe the term "spyware" is > > also appropriate, depending on what the "additions" > > actually do behind the curtain. > > > > Note an important thing: When careless users will > > notice the change, they will maybe blame the authors > > of the original software, not the distributor. > > This could do damage to F/O products, at least > > in "Windows" land. > > > > Luckily, those who build from source or use > > precompiled packages from a trustworthy > > vendor don't have to care for that stuff. :-) > > So, wait, Firefox is Malware? Did you notice that with FF4 > they changed it so that you didn't get prompted on launch > it overrides your default but instead it's a checkbox inside > the installer? I've never installed something in "Windows" so my opinion has limited fact-backup here. I don't even see from your post _what_ they changed in FF4 - the default browser? The home page? Additional toolbars? Some advertising? Hmmm... However, installing proprietary stuff "along with" the desired F/O software and changing user settings without dialog or notification _could_ deserve the term "malware" to apply. It's _not_ that those are a dependency! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Which Lenovo Laptop?
On Fri, 9 Dec 2011 16:50:23 +0100, 𫝆井 Pierre wrote: > If there is a setting to xorg.conf that does work for setting the > screen brightness, please tell me. Everything I tried so far turned out > negative, but maybe there's something I overlooked. Don't "modern" laptops come with keys (or key combinations, usually Fn + Cursor or Fn + PF key) to adjust brightness and contrast, or has this lowest-level functionality finally moved into the world of software, i. e. drivers? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: OT: C|Net's Download.com adware, spyware, malware hijinkx.
On Fri, 9 Dec 2011 09:38:59 -0600, Ryan Coleman wrote: > It's still not malware, it's bloatware. Why would you > not go to the development website to get the program anyway? Uninvitedly adding toolbars, changing web browser home page and default search engine are - in my opinion - malicious acts, so the term "malware" may be correct here. Maybe the term "spyware" is also appropriate, depending on what the "additions" actually do behind the curtain. Note an important thing: When careless users will notice the change, they will maybe blame the authors of the original software, not the distributor. This could do damage to F/O products, at least in "Windows" land. Luckily, those who build from source or use precompiled packages from a trustworthy vendor don't have to care for that stuff. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Playing .ASX files via/within Firefox ?
On Tue, 06 Dec 2011 16:02:24 -0800, Ronald F. Guilmette wrote: > I've been trying to look at California Dept. of Transportation webcams > using Firefox on FreeBSD and so far it simply ain't workin'. Somebody > please tell me what I'm doing wrong. > > Yes, I already installed the mozilla-mplayer port. > > Here's where you can get at the webcams: > > http://www.dot.ca.gov/dist3/departments/traffic/cameras/ > > Any help would be appreciated. Maybe not what you're searching for, but works: First I arbitrarily choose a cam from the map. A window opens with a "go to live camera" link. Right click, copy link address. I tried to directly play it with mplayer which should have worked: % mplayer "http://video.dot.ca.gov/asx/d3-whitmore-grade-80.asx"; Did not work. So I checked the actual ASX file content: % wget "http://video.dot.ca.gov/asx/d3-whitmore-grade-80.asx"; The file contained some XML: 80 at Whitmore Grade http://svdtsmsmedia.dot.ca.gov/d3-whitmore-grade-80"/> http://svdtsmsmedia1.dot.ca.gov/d3-whitmore-grade-80"/> http://svdtsmsmedia2.dot.ca.gov/d3-whitmore-grade-80"/> http://sv04msmedia.dot.ca.gov/d3-whitmore-grade-80"/> http://sv07msmedia.dot.ca.gov/d3-whitmore-grade-80"/> I then choose the first reference to test with mplayer: % mplayer "http://svdtsmsmedia.dot.ca.gov/d3-whitmore-grade-80"; After the cache has been filled, IT WORKED! It can even run in fullscreen (or you can do all the tricks mplayer and mencoder is capable of). I'm not sure how to integrate that with Firefox (as I am an Opera person), sorry. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: drivin' me nuts: permissions and cdda2wav
On Tue, 06 Dec 2011 17:14:05 +, Arthur Chance wrote: > Excellent as a general purpose diagnostic for pluggable devices, but for > a CD drive that's permanently wired to a SATA port and has its SCSI > address fixed by device hints like mine it's rather overkill. I think in such a case going with /etc/devfs.conf permissions is the easiest way to go. I'm also following such an approach. linkcd0 cdrom linkcd0 dvd own cd0 root:operator permcd0 0664 own xpt0root:operator permxpt00660 own pass0 root:operator permpass0 0660 -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: umass to /dev/da* mapping
On Mon, 5 Dec 2011 17:08:15 +, Mike Clarke wrote: > > I have a fairly simple perl script which is run by devd when I plug in a > USB memory stick. The script sets up some permissions and a link to > make life easy for a user to mount the memory stick. > > This normally works fine but there are problems if the memory stick is > already inserted before booting. > > Normally my internal 4 slot memory card reader is detected as umass0 > with devices da[0-3] and when the USB memory stick is inserted it comes > up as umass1 with device da4 and my script works on that assumption. If > the USB stick is present on booting then it appears as da0 on umass0 > and the card reader is da[1-4] on umass1 so the script fails. > > Is there any convenient way for my script to determine which da* devices > correspond to the umass device name? Maybe you could use a matching against match "bus" "0x"; match "vendor" "0x"; match "product" "0x"; match "release" "0x"; to determine which device you're currently accessing. As the USB IDs stay the same for at least the card reader, it should be easy to conclude. :-) USB devices are usually "enumerated" in the order they appear to the system. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: I am FreeBSD user.
On Sun, 4 Dec 2011 15:15:42 -0800 (PST), masayoshi wrote: > Why can I select other operation's man page on our FreeBSD webisite? Why not? :-) I'd be happy to have a centralized reference for UNIX and Linux system in one web page. > Is it for Linux emulator? At least you can apply it there. Also note that there are manuals for OpenBSD, SunOS, ULTRIX or HP-UX which are definitely not related to the Linux emulation (which is an alternative binary interface - ABI - on FreeBSD). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sudo log messages
On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote: > Tell me please how to stop sudo to food /var/log/messages? ADDITION: Of course I meant /usr/local/etc/sutoers, NOT sudo.conf. Instead of logging via syslog (to /var/log/messages), why not use a specific log file for sudo? Add those lines to the sudoers file: Defaults logfile=/var/log/sudo.log Defaults !syslog Make sure /var/log/sudo.log exists, and maybe use newsyslog.conf to deal with log rotation and archiving. However, you can easily purge sudo log information this way, if required. The file /usr/local/share/doc/sudo/sample.sudoers contains an example. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sudo log messages
On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote: > hi > > I add line to syslog.conf > and killall -HUP syslogd > > Tell me please how to stop sudo to food /var/log/messages? There is a short block for that functionality in the file /usr/local/etc/sudo.conf.sample which you can create your own sudo.conf file from. Also see the notes in "man sudo", section "SECURITY NOTES". Maybe you'll find something useful in the provided documentation at /usr/local/share/doc/sudo/. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upcoming 9.0 release
On Sat, 03 Dec 2011 16:53:24 +0100, Filippo Moretti wrote: > They seem to work anyway.I was unable to upgrade many ports due to > failure to patch properly but all the application I have still work. > I do agree they should be re-installed You can always use the "fallback method" of using the compatibility layers of FreeBSD n for n-1. This refers to the compat-* ports and the COMPAT_* kernel configuration items. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: upcoming 9.0 release
On Fri, 02 Dec 2011 14:10:30 +0100, Dick Hoogendijk wrote: > Setting up plans for the upcoming 9.0 release I have one question. > Assuming the freebsd-update utility will bring me from the 8.2-release > to the new 9.0-release I'm not sure what to do exactly with the > installed ports. > > I always use portmaster. What steps do I take to get from installed > ports on 8.2-release to 9.0? > Is there a nice and working procedure to follow? > Thanks for the advice. Basically, there are two approaches: a) Update everything. Using portmaster (and also portupgrade), you can update all ports that are installed via "all plus recursion". Make sure to read the UPDATING file regarding your installed applications. Also see "man portmaster" (or "man portupgrade") for the correct switches to portmaster so it can run without any further inter- action (which is often desired). b) Install from scratch Make a list of the ports you _intendedly_ want to use, this means do not pay much attention at dependencies that you don't want to have, but are forced to. :-) It's often helpful to make a list of installed ports from the system prior to updating. Then install the ports on your list, as they will pull in any dependencies they need. This makes sure you don't carry "cruft and bloat" from your prior installation that you _maybe_ don't have any actual use for. Needless to say, you should bring your ports tree up to date before starting either procedure. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: make buildworld powers down system
On Fri, 2 Dec 2011 03:28:09 -0500, Mehmet Erol Sanliturk wrote: > On Fri, Dec 2, 2011 at 3:05 AM, Polytropon wrote: > > > On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote: > > > The screen does go into standby and I am not > > > sure what is controling that, nothing in KDE or Xorg that I set, perhaps > > a > > > sysctl setting but I did not see one in the acpi section. > > > > This might be a dafault option. You can override it in > > your /etc/X11/xorg.conf by setting > > > >Option "DPMS" "false" > > > > in the section "Monitor" where you define the values > > for your monitor. I had a similar experience with an > > 21" CRT Eizo F980 going to sleep unintendedly. :-) > > > > -- > > Polytropon > > Magdeburg, Germany > > Happy FreeBSD user since 4.0 > > Andra moi ennepe, Mousa, ... > > > > > > > Another way may be inserting the following lines into ~/.xinitrc : > > xset s off > xset -dpms Correct, I also have those in my ~/.xinitrc together with the xorg.conf setting above. With both settings, screens shouldn't blank anymore. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: make buildworld powers down system
On Fri, 2 Dec 2011 02:06:26 -0500 (EST), d...@safeport.com wrote: > The screen does go into standby and I am not > sure what is controling that, nothing in KDE or Xorg that I set, perhaps a > sysctl setting but I did not see one in the acpi section. This might be a dafault option. You can override it in your /etc/X11/xorg.conf by setting Option "DPMS" "false" in the section "Monitor" where you define the values for your monitor. I had a similar experience with an 21" CRT Eizo F980 going to sleep unintendedly. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installing an older version of a port
On Fri, 02 Dec 2011 15:25:48 +1000, Da Rock wrote: > On 12/02/11 14:01, Adam Vande More wrote: > > On Thu, Dec 1, 2011 at 9:55 PM, Da Rock > > > <mailto:freebsd-questi...@herveybayaustralia.com.au>> wrote: > > > > I've never actually done this before, so I'm a little shaky on the > > details. > > > > ffmpeg-0.7.7,1 doesn't work for my purposes: ffserver/ffmpeg > > aren't communicating all that well- I'm still working out the > > details, but essentially either or both are borked. I've been > > working with the ffmpeg list to sort it out. > > > > FFmpeg-devel doesn't work either (for whatever reason- again > > communicating upstream for support, although the maintainer might > > put opencv as broken in that port), so I'm left with 0.7.6,1 which > > does appear to work at this point. > > > > My question is this: how do I do this exactly? The dependencies > > will require updating and could fail as well right? I tried a > > pkg_create of the port and installing it where required, but it > > requires pciids-20111002 and pciids-2009 is installed (and > > probably required by other ports). How can I install the older > > version without breaking things (at least too much- I can fix > > things but there is usually always a limit)? > > > > My system is 8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1 #1: Sun Mar 13 > > 08:45:42 EST 2011 /usr/obj/usr/src/sys/MEDIA amd64. I have > > portupgrade and updated to the latest ports (apparently that is > > the problem- although I've only been fiddling with ffmpeg and it > > is not in production with my project task per se). > > > > > > http://www.oldports.org/data/ > I already have a copy of the port required as a pkg, but how do I handle > the dependencies? You can also use the "portdowngrade" tool to checkout an older version of a port. I had success getting something to work again that has been "modernized" (and disimproved for that matter). :-) For the dependencies: In most cases, it works like this: Determine the port's dependencies and install the current versions (e. g. of other programs it depends on, or libraries). Typically, they are "downward compatible", for example if the port requires libfoobar-1.4, but 1.5 is the current version in ports, install it, and it will still work. In worst case you have to manually add a symlink for the shared library libfoobar-1.4@ -> libfoobar-1.5 so the program can "pick it by version number". Of course, this might sound strange if one takes the initial ideas of shared libraries and their versioning into mind. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Xfce and session lock (xlock)
On Fri, 2 Dec 2011 01:23:19 +0100, Patrick Lamaiziere wrote:
> I use Xfce 4.8, is there a way to lock the session when the screen goes
> to sleep?
I think you can install the port "xscreensaver" which
integrates well with Xfce. At least it did the last
time I did look at it. :-)
The xscreensaver program does show a screensaver or
use the monitor's DPMS feature after a specified
time without interaction. It will then require a
password to unlock the session.
Note: I'm using the classic "xlock" command (with
installed port "xlockmore") and usually lock the
session by pressing ("slapping") the "Help" key
(which is the double-width key on the top left on
a Sun keyboard, quite handy). I'm not sure if xlock
has an option for setting a timeout value...
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: problem formating disk with gpart
On Thu, 01 Dec 2011 02:07:41 -0600, CyberLeo Kitsana wrote: > On 11/30/2011 03:01 PM, Robert Huff wrote: > > > > One of my systems has a hot-swap eSATA device, which reports as > > "ad1". I'm trying to use this to prepare a new disk using gpart and > > something (possibly my understanding) is broken. > > After removing another disk and inserting the new one, I do: > > > >>> gpart show ad1 > > => 34 976773101 ad1 GPT (465G) > > 34 976773101 - free - (465G) > > > > ... which is the value for the disk just removed. > > If I do (to start clean): > > > >>> gpart destroy ad1 > > gpart destroy ad1 > > gpart: Input/output error > > > > Huh? > > If I remember correctly, the old ATA subsystem (ad*) does not support > hotswap notification, so the kernel will not see a device change until > reboot or reinit. You should probably be using AHCI (if the driver > supports your chipset) or very careful use of atacontrol detach, attach, > or reinit. I'm not fully sure if this applies here, but there are the following commands: atacontrol attach channel atacontrol detach channel atacontrol reinit channel atacontrol spindown device [seconds] atacontrol list It seems as they are intended to support "manual hotswapping" to be done with SATA. See "man atacontrol" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re[2]: Problem with jail network
On Wed, 30 Nov 2011 20:19:56 +0100, bsd wrote: > Le 30 nov. 2011 à 18:38, Коньков Евгений a écrit : > > > Здравствуйте, bsd. > > > > Вы писали 30 ноября 2011 г., 19:29:34: > > > > b> Le 30 nov. 2011 а 17:17, Damien Fleuriot a йcrit : > > > >>> > >>> > >>> On 11/30/11 5:05 PM, bsd wrote: > >>>> Hi, > >>>> > >>>> I have been configuring a jail system using the howto provided here : > >>>> http://www.freebsd.org/doc/handbook/jails-application.html > >>>> > >>>> The is now correctly starting, but I can't seem to use the network > >>>> stack. > >>>> > >>>> > >>>>> root@master 16:52:55 ~ -> jls > >>>>> JID IP Address Hostname Path > >>>>> 1 xx.216.yy.150 n0.no.no/jail/j/n0 > >>>> > >>>> > >>>> But I can't ping neither outside of the jail, nor inside of It. > >>>> > >>>> I am a bit confused because I don't know if I have to configure the IP > >>>> using an alias on the main Eth interface, or do something else. > >>>> > >>>>> ifconfig_bce0_alias0="inetxx.216.yy.150/32" > >>>> > >>>> > >>>> > >>>> This last command seems to have frozen my system. > >>>> > >>> > >>> Confirm that the MISSING SPACE between your "inet" and "xxx.216..." > >>> statements is only a typo and NOT present in your actual rc.conf > >>> > > > > b> This is confirmed. > > > > b> I have the equivalent of : > > > > b> ifconfig_bce0_alias0="inet 1.2.3.4/32" > > > > in this case I write full netmask: "inet 1.2.3.4 netmask 255.255.255.255" > > It works fine > > > > Ok, I'll try that with netmask 255.255.255.255 instead of /32 The hex notation should also be valid: ifconfig_bce0_alias0="inet 1.2.3.4 netmask 0xff00" -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Failed make buildworld on 8.2-RELEASE
On Wed, 30 Nov 2011 23:15:26 +0400, Антон Клесс wrote: > I don't have /usr/src/cddl in my system. Does it required to build world? Yes, unless you did use src.conf or make.conf to omit the building of the CDDL licensed parts. This subtree primarily contains stuff brought by Sun (such as ZFS or dtrace). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .config
On Wed, 30 Nov 2011 13:40:19 -0500, ill...@gmail.com wrote: > A dirty workaround might be to link /.config > to something innocuous. One could obvio- > usly also have /.config mounted as a tmpfs(5). > So it couldn't persist from boot to boot. > > The cleanest solution is to forgo qt/kde, but > then you're slightly more limited in what you > can use for office-type stuff. The question remains: How is a user-started process (e. g. when you run the "startx" command) supposed to create directory entries and files on root level /, a thing that only root and root-like users (and programs!) should be allowed to? % mkdir /.config mkdir: /.config: Permission denied As a normal user, you _intendedly_ can't do this. Why would you assume that a program you start can do it? Creating such data structures in a _user_ directory is completely okay. But in / it simply sounds WRONG. Sorry. JUST PLAIN WRONG! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: HDD formatted in FreeBSD/386 on Win XP
On Sat, 26 Nov 2011 20:56:22 +0100, Pavel Matoušek wrote: > Exist some SW for Win SW for "reading" this FreeBSD formatted HDD ? You should ask this question on a "Windows" related list. :-) But during my "data recovery journey", I came across a program that can be used to read UFS formatted disks, even though it is a recovery program in the first place. It's called "R-Studio" and runs on some kind of "Windows". Note that this program is not for free. You can try a demo version with limited capabilities, but you have to buy the full product. In the trial version, you can at least see the full content of the disk and decide if it's worth purchasing the full product. There's also "UFSExplorer", you have to buy this as well. I remember that this has been recommended to read UFS disks that are not defective (like mine was). :-) As far as I know, "Windows" does not understand standard file systems; it can only read its own ones. For everything else, you'll need additional programs or "drivers". I'm not sure if those are for free. Maybe you can try "ufs2tools": http://ufs2tools.sourceforge.net/ Also try some googling, maybe like this: http://www.google.com/search?q=read+ufs+freebsd+windows+xp Sorry for not being more specific, as I'm not a "Windows" person. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .config
On Wed, 23 Nov 2011 05:39:21 -0600, ajtiM wrote: > Hi! > > I succesfully installed FreeBSD 9.0 RC-2 and I didn't have problems with > bsdinstall and others. What I didn't have on 8.2 is when I start KDE4 with > startx I got directory .config in /. I have one .config in /home but what it > happened? When I deleted as root and I start again KDE4 as user I got it > again. Inside is a file Trolltech.conf (the same is in /home/.config). That file seems to be part of Qt. How can it be created outside your $HOME when you startx? That's somewhat strange... how _can_ that happen? % cd % touch ../bla touch: ../bla: Permission denied % touch /bla touch: /bla: Permission denied Only root permissions allow the creation of files in that specific directories. Neither /.config or /home/.config should exist. It shoud be ~/.config for your user account. I also have ~/.config/Trolltech.conf. I'm not using KDE, but one KDE program, maybe other Qt-based programs. Maybe one of them has installed the directory (at this correct location)? % ls .config/ Trolltech.conf audacious/ autostart/ gsmartcontrol/ gtk-2.0/ menus/ Okay, seems that other toolkits also use it. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Compiler
On Sun, 20 Nov 2011 18:40:41 +0200, Yordan Petrov wrote: > Hi > How could I compile some cgi files for FreeBSD Depending on the source's programming language, you'd have to use the corresponding compiler. For interpreted CGI files, the web server needs to be configured accordingly. > Is there any online tool ? I'm not aware of one, but you could use scp to transfer the source files to the server, then use ssh to call the compiler needed (e. g. cc), and then put the results into the proper locations. You could automate this process by a Makefile. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: The results of your email commands
On Sun, 20 Nov 2011 13:17:23 +0200, thanos trompoukis wrote: > I saw that the usb device is like a scsi "da" > so now I am trying this: > # mount -t msdosfs /dev/da0 /mnt/usb > mount_msdosfs: /dev/da0: Invalid argument > now what? how I have to refered on my usb device? > I do not understand a word here! Depending on he partitioning of the USB media, it's possible to access /dev/da0s1 instead of /dev/da0. The command # fdisk da0 lists the partitioning information. According to the example above, you can # mount -t msdosfs /dev/da0s1 /mnt/usb There is a section in the FreeBSD Handbook discussing the topic of how to access MS-DOS formatted media per USB. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Build options built by dialog(1)
On Tue, 15 Nov 2011 19:15:01 -0500 (EST), Chuck Bacon wrote: > I stumbled into a problem trying to get xorg up on my > current 9.0-RC1. I selected an intolerable choice, > notable PTH. Now the choice of Python causes the build > to fail, and I can't find the output of dialog(1). > Question: How can I restart the build with a new > dialog(1)? Put another way, where are the various > build variables kept? The options are stored in /var/db/ports//options. The "Frontend" to access them is: # make config # make rmconfig # make config-recursive # make rmconfig-recursive The last two options are really helpful when the problems you're encountering are provided by a dependency port. See "man 7 ports" for details. Optional, in worst case, options can also be provided my a Makefile.local in the port's directory. Also note that /etc/make.conf as well as the configuration files of port management tools may contain options. > Once again, this old 650-704-7070-PDP4-KA/KI/KL/KS-CTSS- > Convex-IBMPC-3B1 warrior needs help :-} Impressive path! =^_^= -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apps to display cpu temp
On Mon, 14 Nov 2011 15:16:49 -0800, Edward Martinez wrote: > Thanks!, Even though mbmon is about 10 degrees off from what the > BIOS is reporting. I'm still a happycamper. I had a similar observation with my P4 system: CPU temp would always "flatline" at 60 deg. C. > I have a question, is it supposed to be "device iichsmb" or "device > iicsmb" like you have listed? The example listed is from my kernel configuration of that particular P4 system, where it _worked_ properly. I had inserted "device iicsmb" as per kernel configuration notes. The OS in question was 7-STABLE. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: apps to display cpu temp
On Sat, 12 Nov 2011 18:19:57 -0800, Edward Martinez wrote: > Hi, > > > I have a Pentium 4 and i have been trying to get "coretemp" and > "sysctl hw.acpi.thermal.tz0.temperature" to display my Cpu temperture , > however i have not had any luck using them > Are there any other apps perhaps from ports that reports CPU temp? I've been using the port "xmbmon" for that, in combination with device smbus device iicbus device iicsmb device iicbb device iic in the kernel configuration file - on a Pentium 4 system. I haven't tried the sysctl method, because xmbmon did work out of the box. :-) You can also use mbmon for text output. Here's an example from ~/.xinitrc calling xmbmon: xmbmon -g 150x100+0+897 \ -tmin 20.0 -tmax 70.0 \ -cmtmb CPU -cltmb blue \ -cmtcpu CS -cltcpu cyan \ -cmtcs SYS -cltcs green \ -vmin 2.0 -vmax 3.0 -cmvc V -clvc red & Depending on the sensor installation of your particular system, check if the different values do match the hardware. Maybe check from within your CMOS setup for reference values. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: What are the technical differences between Linux and BSD?
On Sat, 12 Nov 2011 03:23:35 -0500, Allen wrote: > I'm going to go ahead and agree with the other replies on here and say > you should REALLY get some History books on Unix / Linux / BSD, and read > them. I'd recommend "Just for Fun", "A Quarter Century of Unix" and also > the DVD "25 Years of Berkeley Unix", and a few others mentioned already. For more details about SysV and explaination of historical contexts I may append: The magic garden explained. The internals of UNIX System 5 release 4. by Benny Goodheart & James Cox. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: No usb keyboard in single user mode
On Fri, 11 Nov 2011 10:41:56 +0100, David Demelier wrote: > When prompted Enter full pathname of shell or RETURN for /bin/sh:uhub3: > 6 ports with 6 removable, self powered > uhub7: 8 ports with 8 removable, self powered > ugen0.2: at usbus0 > ukbd0: > on usbus0 > kbd1 at ukbd0 > uhid0: > on usbus0 > ugen1.2: at usbus1 > ubt0: > on usbus1 > ugen0.3: at usbus0 > > So here nothing possible to do, only shutdown by power button. After the keyboard has been detected, you should be able to enter full pathname of shell or RETURN for /bin/sh. Possible obstacle if you do NOT have "device kbdmux" in your kernel configuration! > I have > heard a long time ago that legacy USB must be enabled in the BIOS and it > is in mine. I also had a similar experience in v7 with my old system. After waiting for the kernel to identify ukbd0, it could be used as intended for local logins. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On Fri, 11 Nov 2011 10:45:15 +, Traiano Welcome wrote: > And I don't seem to have a src.conf anywhere on my filesystem ... Hmmm. You'll have to create it yourself (just like /etc/make.conf). See "man src.conf" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: X server and xinit works excellent....almost.
On Wed, 09 Nov 2011 13:10:20 -0800, Chuck Swiger wrote: > Hi-- > > On Nov 9, 2011, at 12:02 PM, Michael Cardell Widerkrantz wrote: > >> And should HAL have discovered my swedish keyboard automatically in > >> the first place, so there was something going wrong there? > > > > How would HAL know that the keyboard had a Swedish layout? No such > > information is sent through USB or PS/2 when you attach a keyboard. > > True for PS/2, but not true for USB-- the USB Vendor & Product > ID can identify different keyboard types and let you infer the > country. "Can" - I think it's not standard to do so. > For example, see: > > http://www.linux-usb.org/usb.ids Just checked, and the exception is right here: I'm using a Sun USB keyboard + mouse, 0x0430 = Sun Microsystems, Inc. is correct, but 0x100e = 24.1" LCD Monitor v4 / FID-638 Mouse seems to be nonsense. It's a mouse, _infront_ of a 24" monitor, but that's an EIZO CRT. :-) In this regards, it's also strange how FreeBSD could "forget" USB information it once had. On my old 5.x system, I got dmesg lines like that: ukbd0: Sun Microsystems Type 6 USB keyboard, rev 1.00/1.02, addr 3, iclass 3/1 ums0: Sun Microsystems Type 6 USB mouse, rev 1.00/1.02, addr 2, iclass 3/1 But since 7.0 (6.0 hasn't been introduced to my home system), I get ukbd0: on uhub1 ums0: on uhub1 Note that the corresponding file in the source tree containing the USB devices still has the proper data! And I haven't changed things on hardware side. But maybe this is because the USB subsystem has had many changes... Now that I have a type 7 keyboard, the USB information still is not useful: % usbconfig -u 1 -a 3 dump_info ugen1.3: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON % usbconfig -u 1 -a 2 dump_info ugen1.2: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE % dmesg | grep "^u[km]" ukbd1: on usbus1 ums0: on usbus1 ums0: 3 buttons and [XY] coordinates ID=0 You can also see that dmesg logs different data (0x100e vs. 0x0100). > At the moment, I happen to be using a: > > Apple Pro Keyboard: > Product ID: 0x020b > Vendor ID: 0x05ac (Apple Inc.) > Version: 4.20 > Speed: Up to 12 Mb/sec > Manufacturer: Mitsumi Electric > Location ID: 0x3d111300 / 6 > Current Available (mA): 250 > Current Required (mA): 50 > > ...and this database would correctly let the system know > that I'm using US layout: > > 020b Pro Keyboard [Mitsumi, A1048/US layout] > > If you figure out that a Logitech Tangentbord K120 (or an Apple > MC184S) is connected, then you've got a Swiss keyboard, and so > forth. This is fine as long as you're going to keep that language settings. However, there are users who need a non-US language on a US keyboard layout - or vice versa. In such a case, the autodetection doesn't help. Your example with Apple hardware corresponds to my experience. I also have an older Mac keyboard which works fine on FreeBSD, including proper device identification. My assumption still is: Not _every_ keyboard manufacturer does code the layout into the USB identification. If you tell me I'm wrong with this assumption, I'll be happy. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: X server and xinit works excellent....almost.
On Thu, 10 Nov 2011 00:49:19 +0100, Samuel Magnusson wrote: > Michael Cardell Widerkrantz wrote 2011-11-09 21:02: > > Samuel Magnusson, 2011-11-09 12:06 (+0100): > >> Now I'm curious: > >> > >> Is it then so that in the "new style" Xorg the XML-method will > >> override HAL, and this is the new default way of providing opitons > >> that formerly were in the InputDevice sections in xorg.conf? > > What new style XML method? > > > > AFAIK the more modern X.org X servers uses the Linux udev instead of > > HAL. Those servers are not yet available on FreeBSD but presumably it > > would be possible to use devd for the same purpose. > I'm referring to what Polytropon said about all the "new" stuff required > by X. As I understood him he was talking about the XML-files to give > directions to HAL, and he used quotes so I think he meant "supposedly > new", or just newer than the classic configuration file but already the > "old new", as he seem to agree with you that HAL is on it's way out and > should be avoided if possible. Depends. If you are using a normal US keyboard and don't have any "deviant" needs, HAL autodetection of devices should work fine. And as it is X's default configuration, you could even omit xorg.conf if X detects your GPU and display properly. The problems start when you do something "not-normal". In such cases, it seems that you better leave HAL and DBUS out of your system, if you don't see any use for them. In that case, the "old-fashioned" configuration methods should do what you want: centralized settings for X in xorg.conf. Setup once, then use. > Anyway, I wasn't aware that the FreeBSD X server was "ancient" and > different from any other. :) There is some delay in porting X's new features from Linux to FreeBSD. Linux is the platform that mostly drives that development. Some parts used by X and by desktop environments are specific to Linux. HAL was initally meant to be a kind of "plugin system" to get independent from the OS, but it didn't get that far. Now as it (almost?) works on FreeBSD, it's already deprecated by new Linux concepts such as udev, upower and other us. Maybe they become available as interfaces on FreeBSD too, but my fear is... as soon as they are usable, there's already something else obsoleting them right away. :-( Those Linux developments often serve functionalities that have been present in FreeBSD for many years. One of the often cited things is automounting. FreeBSD's automounter amd, in combination with devd, can already automount things independently from desktop environments. It could do that already 5 years ago. This setup can also handle webcams and USB mass storage. The question is: How to interface that with a desktop environment? Those IDE's development is also mainly driven on Linux. An example is Xfce which lost some functionality on FreeBSD because those parts have been "rewritten" with Linux-only "back-ends" in mind. Maybe other things will follow, maybe Gnome 3? Who knows... > And migrating from Windows and Mac might be > discouraging if there isn't a working desktop with visible text at least > within an hour or two after installation. :) No problem in that, see FreeSBIE - all what you said, plus you don't need to install anything. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: X server and xinit works excellent....almost.
On Wed, 09 Nov 2011 13:19:44 +0100, Samuel Magnusson wrote: > This works for me: > X :0 -terminate > Ctrl-Alt-F1 > xterm -display :0 > Ctrl-Alt-F9 > exit xterm.. which brings me back to the first console. > > But this doesn't work: > X :0 -terminate vt4 > Ctrl-Alt-F1 (doesn't respond) > Ctrl-Alt-Backspace (doesn't respond) Do you have ``Option "DontVTSwitch" "false"'' in xorg.conf? > Any clue why? Is my command "X :0 vt4" wrong or not supposed to work? What is the correct notation for the terminal device to start it on? Maybe ttyv4 (as in /etc/ttys)? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: X server and xinit works excellent....almost.
On Wed, 09 Nov 2011 12:06:37 +0100, Samuel Magnusson wrote: > Is it then so that in the "new style" Xorg the XML-method will override > HAL, and this is the new default way of providing opitons that formerly > were in the InputDevice sections in xorg.conf? I hope not! :-) As far as I understood the _current_ mechanism, the precedence is 1st xorg.conf, 2nd XML stuff, 3rd autodetect. You have X without HAL and DBUS? Use xorg.conf because this has worked for many years to centralize X configuration. You have X with HAL and DBUS, but don't want to use it? Reflect this choice in xorg.conf and continue with previous settings. You have X with HAL and DBUS, but some things aren't detected properly? Dive into the fun of XML and enter your settings in the appropriate files, whichever they currently may be. :-) There _are_ things that cannot be autodetected, and HAL needs to be configured to "notice" a localization "deviation" from the standard, which is en_US. That's what you are going to use the XML stuff for. In case you're _not_ using HAL with X, you have to make the settings in xorg.conf, like this: Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout""de" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection Note that putting the "Zap key" into this file seems to be more comfortable than putting it into some obscure XML files scattered across the file system. And completely independent from all those options, you still can _always_ use [ -f ~/.xmodmaprc ] && xmodmap ~/.xmodmaprc in your X initialization file (usually ~/.xinitrc). This does _not_ say anything about what might become current when HAL is fully out of support (as it is already considered deprecated in Linux). > And should HAL have discovered my swedish keyboard automatically in the > first place, so there was something going wrong there? Can you tell me _how_ anything in software is supposed to know what characters are printed on the key caps of the keyboard? I'm not sure keyboard vendors do code localization variants into their USB identification numbers... This makes me assume the following: It's not possible to determine the localized layout of a keyboard. Just imagine I pop the german keycaps from my IBM model M keyboard and put a set of swedish caps on, would the system notice that change? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: operapluginwraper
On Wed, 9 Nov 2011 05:28:43 -0600, ajtiM wrote: > But as I nderstand the Opera should be FreeBSD native. I didn't installed > Linux version. And I don't have flash plugin installed either. BTW I use > gnash. I'm also using the native BSD version of Opera, but with the following set of packages and wrappers: opera-11.50 opera-linuxplugins-11.50 nspluginwrapper-1.4.4 linux-f10-flashplugin-10.3r183.5 This was mainly because of following the handbook. So I think the dependency to the Linux /proc comes from the "Flash" plugin (Linux). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: "Unprintable" 8-bit characters
texts.
Example:
Mißwirtschaft -> Miszwirtschaft -> Mißwirtschaft ===> good.
Messer -> Meßer ===> wrong.
In names (e. g. of towns): Staßfurt (right) != Stassfurt (wrong).
Note that !("sz" <-> "ß") in all cases, and !("ss" <-> "ß")
as well, as the rule states that only a non-truncatable "ss"
is to be set as Eszett. There are only few "sz" that are
"real 'sz'", typically in word gaps, e. g. Reiszange. :-)
The "funny" things start when diacritic marks and other
non-US-ASCII representable elements change the meaning
of a word. In such cases, it's often justified to use
the proper localized representation. However, this is
also the point where problems may start if you're doing
it wrong (which means: others do not conform to the
language settings or fonts you're using).
The (limited) US-ASCII set of characters is the only
easy way to avoid that. It may not _always_ look pretty,
but in worst cases, it works - and you can RELY on that.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: "Unprintable" 8-bit characters
On Tue, 8 Nov 2011 19:58:04 -0600, Conrad J. Sabatier wrote:
> So, what would be the safest bet as far as the most "universal"
> representation for these characters? Something I've long wondered
> about when I've e-mailed people and copied/pasted these characters (are
> they really seeing what I'm seeing?). :-)
With lots of experience in "how not to do it", I would
like to suggest the following: Use US-ASCII letters only.
This makes _sure_ they will display correctly everywhere
and even on ultra-worst conditions (e. g. you are at a
real serial console, a real DEC vt100).
Filenames like kloesze_mit_muesli_foerdern_baerenhunger.mp3
can be processed by _any_ ls or mailer program. There is
no need to worry about... hmmm... do they have the same
character settings that I use? Do they have a font installed
that can show the file names properly?
Rules: Substitute umlauts properly (*e). Substitute ß
to sz ("teletype convention"). Remove accents or other
marks completely, as well as "strokes through characters"
or similar typographical specialities. If you can, use
lowercase only. No spaces, use _ instead. Avoid any other
special characters. Make everything plain ASCII, and you
can _still_ easily get the meaning.
The file system ITSELF doesn't care for the meaning of
the characters. SAVING them and DISPLAYING them are two
fully different things. Nobody stops you from making
filenames like öÜÖß߀Łµ³¼`łøæſđ̣ĸ»¢.mp3, but they can
cause trouble you can't predict. You _never_ know...
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: "Unprintable" 8-bit characters
On Wed, 09 Nov 2011 02:51:31 +0100, Michael Ross wrote:
> Am 09.11.2011, 01:42 Uhr, schrieb Conrad J. Sabatier :
>
> > Pardon me if this may seem like a stupid question, but this is
> > something that's been bugging me for a long time, and none of my
> > research has turned up anything useful yet.
> >
> > I've been trying to understand what the deal is with regards to the
> > displaying of the "extended" 8-bit character set, i.e., 8-bit characters
> > with the MSB set.
> >
> > More specifically, I'm trying to figure out how to get the "ls" command
> > to properly display filenames containing characters in this extended
> > set. I have some MP3 files, for instance, whose names contain certain
> > European characters, such as the lowercase "u" with umlaut (code 0xfc
> > in the Latin set, according to gucharmap), that I just can't get ls to
> > display properly. These characters seem to be considered by ls as
> > "unprintable", and the best I've been able to produce in the ls
> > output is backslash interpretations of the characters using either the
> > -B or -b options, otherwise the default "?" is displayed in their place.
>
> Unsure if I understand you correctly.
> ("extended" 8-bit character set with MSB? utf-16?)
> I'm confused by this charset stuff in general.
>
> Assuming you want \0xfc displayed as "ü",
>
> > cat test.py && python test.py && ls -l
>
> #!/usr/local/bin/python
> # -*- coding: utf-8 -*-
>
> f=open('\xfc','w')
> f.close()
> total 2
>
> -rw-r--r-- 1 michael wheel 29 9 Nov 02:43 test.py
> -rw-r--r-- 1 michael wheel 0 9 Nov 02:44 ü
>
>
> here is what works for me:
>
> in my login class in /etc/login.conf:
>
> :charset=ISO-8859-1:\
> :lang=de_DE.ISO8859-1:\
>
> ``cap_mkdb /etc/login.conf'' after changes
Ah, thanks - that seems to be the proper way to have
the environmental variables set - instead of my (ab)use
of setenv's in the csh config file. :-)
Note the "precedence" of $LANG vs. $LC_* (as they can
be used to configure things more precisely, e. g.
regarding system messages or date formats; see example
following).
> in /etc/rc.conf:
>
> scrnmap="iso-8859-1_to_cp437"
Hm? CP437? Codepage? Isn't that some MS-DOS thing?
I've never needed a screenmap to make "extended
characters" (everything beyong US-ASCII) work.
> font8x8="cp850-8x8"
> font8x14="cp850-8x14"
> font8x16="cp850-8x16"
>
>
> and in /etc/ttys, console type is set to ``cons25l1''
I have a similar setting here, but that does _not_ work
wuth UTF-8 codec characters. If I want to use them, I
have to change some environmental variables, from
#---GERMAN/ENGLISH <=== DEFAULT
setenv LC_ALL en_US.ISO8859-1
setenv LC_MESSAGES en_US.ISO8859-1
setenv LC_COLLATE de_DE.ISO8859-1
setenv LC_CTYPEde_DE.ISO8859-1
setenv LC_MONETARY de_DE.ISO8859-1
setenv LC_NUMERIC de_DE.ISO8859-1
setenv LC_TIME de_DE.ISO8859-1
unsetenv LANG
to
#---INTERNATIONAL-
setenv LC_ALL en_US.UTF-8
setenv LC_MESSAGES en_US.UTF-8
setenv LC_COLLATE de_DE.UTF-8
setenv LC_CTYPEde_DE.UTF-8
setenv LC_MONETARY de_DE.UTF-8
setenv LC_NUMERIC de_DE.UTF-8
setenv LC_TIME de_DE.UTF-8
setenv LANGde_DE.UTF-8
Then I can use UTF-8 characters inside rxvt-unicode. Of
course, text mode console is limited to the first set
of configuration, using the ISO 8859-1 character set.
This worked long before UTF-8 arrived with the glorious
idea that I should have 2 bytes where one is sufficient,
to describe our (german) 6 umlauts and the Eszett ligature. :-)
Improper settings will result in [][] or A-tilde three
quarters upside-down question mark, depending on editor
or terminal used.
But returning to the original question, I think Robert
did explain it very well: There is no real consensus
about what the different codings should mean. They
were meant to unify the representation of a very large
set of characters, but basically there are many inter-
pretations now, and how they show up to the user depends
on the font in use, _if_ it has this mapping or that,
or none.
For running ls, -w is the right option to use - but IN
COMBINATION with correct settings for the terminal
emulation AND the presence of a font that will do.
Again a fine demonstration why file names should be
limited to printable ASCII and no spaces if you want
them to work everywhere. :-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: operapluginwraper
On Tue, 8 Nov 2011 15:33:01 -0600, ajtiM wrote: > I don't have /proc on my system and I don't know why I should have it? You'll need it in case you're using Linux ABI stuff, and if I remember correctly, this is required for the Opera "Flash" plugin. I'm using such a combination here. That's why I have # Device Mountpoint FStype Options Dump Pass # - -- --- --- - linproc /compat/linux/proc linprocfsrw 00 in /etc/fstab. This requires options COMPAT_LINUX options LINPROCFS options LINSYSFS in your kernel config, or load the corresponding kernel modules. The line linux_enable="YES" in /etc/rc.conf should do that. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011 13:33:55 -0700 (MST), Warren Block wrote: > On Tue, 8 Nov 2011, Warren Block wrote: > > > On Tue, 8 Nov 2011, Polytropon wrote: > > > >> And according to the handbook, this does _not_ remove the > >> need for a X configuration file (usually /etc/X11/xorg.conf) > >> including ``Option "DontZap" "off"'' in the "ServerFlags" > >> section. > > > > For at least the most recent Xorg, it's not needed. Can't recall whether > > it > > is for the one before that. > > Nope, just tested and I'm wrong. DontZap Off is needed with X.Org X > Server 1.7.7. Sorry about that. > > I recommend adding the option to ServerLayout and doing away with the > extra complication of a ServerFlags section. Good suggestion, the Handbook should be changed according to that if it really works (and is, in my opinion, easier). My statement regarding the xorg.conf _and_ XML fun wasn't a personal experience and testing (xorg-server-1.7.7_2,1 here), but the Handbook said so: http://www.freebsd.org/doc/handbook/x-config.html It's mentioned directly beneath the XML fun in 6.4.2. There's also a ServerLayout _or_ ServerFlags statement for the ``Option "AutoAddDevices" "false"'' setting, right before the XML fun for setting a localized keyboard begins... :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: X server and xinit works excellent....almost.
On Tue, 8 Nov 2011 08:14:48 -0700 (MST), Warren Block wrote: > On Tue, 8 Nov 2011, Samuel Magnusson wrote: > > > 1. I can?t zap the server with Ctrl-Alt-Backspace. Nothing at all happens. > > I > > have checked that it isn't disabled in xorg.conf, and even tried to put in > > the reverse boolean value there. Not that I couldn't live without zapping, > > but...when I know about it that it should be there and it is taken fom me I > > feel an URGE to get the zap! > > Zapping is still allowed by default, but a key combination is not > assigned. That can be done in .xinitrc or .xsession: > >setxkbmap -option terminate:ctrl_alt_bksp > > It can also be done in xorg.conf: > >Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > Option "XkbOptions" "terminate:ctrl_alt_bksp" >EndSection There is a 3rd option, especially "useful" when X is run with DBUS and HAL (the default configuration, as well as the package configuration), and it involves fun with XML. :-) File /usr/local/etc/hal/fdi/policy/x11-input.fdi terminate:ctrl_alt_bksp And according to the handbook, this does _not_ remove the need for a X configuration file (usually /etc/X11/xorg.conf) including ``Option "DontZap" "off"'' in the "ServerFlags" section. So, as you're already dealing with xorg.conf, use Warren's suggestion, as it works independently of all the "new" things required by X, and also conforms to the concept of concentrating X's configuration in one configuration file (rather than scattering settings across the file system). > vesa is very limited, only supporting standard modes up to 1024x768 or > 1280x1024. Some vendors add other modes, but they aren't common. > nouveau is an open driver for the very closed Nvidia hardware. The > closed Nvidia drivers (x11/nvidia-driver*) are supposed to work quite > well. I'm using nvidia-driver here which works better than nouveau and nv (the one that comes with X.org); I haven't tested VESA as in most cases, it's _not_ what one wants. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Burning CD
On Mon, 7 Nov 2011 12:59:23 -0800 (PST), C Horman wrote: > Hi, > I am interested in trying FreeBSD version 8.2 for an older > computer that I have. Pentium 4, with 400MB of RAM and 2G > harddrive. Should run fine there - I had a similar system obsoleted in summer this year. :-) > There is no other operating system on the computer. When > I put the CD in to boot I get the message Non System disk - > disk error. Look at your BIOS settings to make sure a boot attempt from CD will be done. Check related options in the CMOS setup program. > I have looked at the files on the CD and I see boot files > and loader files, so it looks like the files are available > to use? I used a free program for Windows XP to burn the > ISO image to CD. The ISO file is a "pre-mastered" image that will boot, if recorded properly. > Could the way the ISO image was burned onto the CD cause > the disk error problem? If the writer did something wrong, or the media is damaged, this is possible. Some burner programs allow you to re-read the CD after burning for comparison with the ISO file. You could try that in order to make sure you're recorded the CD properly. > Do you have any free software suggestions for burning a CD > in Windows XP if this is the issue? Sorry, I'm not a "Windows" person and I don't use 10 years old software, so I can't give you any suggestion here. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Get list of ethernet devices
On Mon, 07 Nov 2011 01:46:14 +0100, Michael Ross wrote: > Moin, > > I'm setting up a system on an external USB drive, > serving as fallback in case of a server failure: > > Customer takes USB drive, plugs it into any of his PCs and boots of it. > > Now I am looking for a good method to configure the network: > > I could just start dhclient on any NIC which could possibly be there, > thus cramming rc.conf with > ifconfig_em0="DHCP" > ifconfig_em1="DHCP" > ifconfig_fxp0="DHCP" > and so on. > > Or I could grep ifconfig or dmesg output for ethernet interfaces and > dhclient these. > > Both sound like a very messy solution. > > So I would step beyond my current area of expertise, grep some source from > sysinstall, bsdinstall or somewhere and do it in C. > But I'm kind of hoping anybody can point me to a readymade solution yet > unknown to me. You could look at how FreeSBIE does it - it contains "autodetect magic" also for graphics and sound. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with X
On Sun, 6 Nov 2011 13:42:48 -0300, Zantgo wrote: > The synaptics mouse and the keyboard not found when I > tap "startx" in my user, this is the mensaje: > > xauth: file /home/user/.Xauthority does not exist That message is _not_ in relation to the problems you're experiencing. Depending on how you setup X (full autodetecion, no config file, HAL and DBOS -or- xorg.conf file with proper settings), you should make sure everything is in place. See chapter 6.4 of the FreeBSD Handbook: http://www.freebsd.org/doc/handbook/x-config.html For the Synaptics touchpad: http://wiki.freebsd.org/SynapticsTouchpad The (missing) presence of the X authority file has nothing to do with keyboard or mouse problems. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Urgent!. Problem with / etc / rc.conf
On Sun, 6 Nov 2011 05:23:54 -0800 (PST), Bill Tillman wrote: > Wow, to reinstall everything is like throwing the baby out > with the bath water. Rather drastic. There are some simple > steps you could have taken to get things back to normal but > without knowing what you had in your original rc.conf file > that's probably oversimplifying things. The defaults in /etc/defaults/rc.conf should be fully sufficient to bring the system up. From this state, running sysinstall could be used to choose settings that will cause /etc/rc.conf to be updated. Furthermore /etc/defaults/rc.conf can be used as a template for settings. Depending on what a system actually will be used for, there can be some "strange" settings required, such as keymap or services to be enabled at boot. Using some web web search, usabe /etc/rc.conf templates can also be revealed. Of course they need changes to conform to local needs. > I keep a little script in my /root/bin folder to backup > my config files periodically to another server. This is > something you should look into. We all make mistakes and > when we do, a backup copy can make the difference between > "oh wow" and "oh f***". I also have a copy /root/etc for the files I have changed, and I keep my changes in a CVS repository. I know this may sound overcomplex at _this_ particular problem, but it helps when you have to deal with various systems and sometimes need to undo changes. >From that repository, I can restore any version from any system. Even in worst case obtaining a complete set of configuration files is possible. The difference in the RESULT between > and >> can be immense, and having a backup you can _quickly_ access is really a happy "oh wow", which is more pleasant than "oh f***", especially if the last one is expressed by others. :-) Politely I'd also like to mention that there are no things called "folder" on FreeBSD in particular, and on operating systems in general. Those things are properly called directories. ;-) PS. Please wrap your lines < 72. Some MUAs don't do that automatically. Thanks! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: recursive copy with spaces in descendants
On Sat, 5 Nov 2011 15:47:20 -0400, Chris wrote: > I'm having difficulty copying a directory tree from my FreeBSD server to > USB storage. The problem is that the tree contains file and folder names > which have spaces, similar to the following: The thing you're intending to name are properly called directories, not "folders". :-) > ./foo bar/some name.tar.gz > ./foo bar/child dir/some other name.tar.gz > > I've tried various combinations of cp with enclosing the top level > directory in quotations, along with other commands like tar or xargs to no > avail. The problem seems to be with creating the destination directories > and folders, where mkdir/cp terminates with an invalid argument response. That's a typical problem caused by those who put spaces into filenames: Scripting requires more work to do what you intend. I may point you to the following articles that deal with the _result_ of your problem: David A. Wheeler Filenames and Pathnames in Shell: How to do it correctly http://www.dwheeler.com/essays/filenames-in-shell.html David A. Wheeler: Fixing Unix/Linux/POSIX Filenames: Control Characters (such as Newline), Leading Dashes, and Other Problems http://www.dwheeler.com/essays/fixing-unix-linux-filenames.html However, if you _can_, solve the _cause_ of your problem, i. e. educate those who create that kind of trouble-carrying file and directory names _not_ to use spaces! > Any ideas would be greatly appreciated, since I'm pretty much out of them > at this point. The articles should help you to deal with the problem, as they present properly working solutions. Good luck! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with mergemaster-p
On Fri, 4 Nov 2011 22:14:10 -0300, Zantgo wrote:
> I have an other problem, when I key "make installworld", get this message:
> make: don't know how to make installworld. Stop
Please read the instructions in the Handbook, or refer
to the comment header in /usr/src/Makefile.
1. `cd /usr/src' (or to the directory containing your source tree).
2. `make buildworld'
3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
[steps 3. & 4. can be combined by using the "kernel" target]
5. `reboot'(in single user mode: boot -s from the loader prompt).
6. `mergemaster -p'
7. `make installworld'
8. `make delete-old'
9. `mergemaster'(you may wish to use -i, along with -U or -F).
10. `reboot'
11. `make delete-old-libs' (in case no 3rd party program uses them anymore)
Make sure you also do step 1 when calling mergemaster
and make:
# cd /usr/src
# mergemaster -p
# make installworld
# make delete-old
# mergemaster
Then reboot into the new OS version.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem with mergemaster-p
On Fri, 4 Nov 2011 21:55:03 -0300, Zantgo wrote: > I'm trying to upgrade to 9.0 stable, but when I run "mergemaster-p" in single > mode, I get the following error message: > > *** Creating the temporary root environment in / var / tmp / temproot > mkdir / var / tmp / temproot: Read-only file system > > *** FATAL ERROR: Can not create / var / tmp / temproot According to the handbook and the comment header of /usr/src/Makefile, after you've booted into single user mode, run "fsck", then "mount -a", and all partitions should be mounted rw. You can check this using the "mount -v" command. (Of course this depends on the partitioning scheme you're using.) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
