Kirill is about to be a popular guy...
;-)
On Sun, Oct 24, 2010 at 10:06 PM, Jeffrey Lynn Parke Jr. <
jeffrey.pa...@gmail.com> wrote:
> On Sun, Oct 24, 2010 at 8:26 PM, Kirill Churin >wrote:
>
> > LinkedIn
> >
> >
> >
> > General,
> >
> > I'd like to add you to my professional netw
On Mon, Oct 25, 2010 at 8:06 AM, Jeffrey Lynn Parke Jr. <
jeffrey.pa...@gmail.com> wrote:
> On Sun, Oct 24, 2010 at 8:26 PM, Kirill Churin >wrote:
>
> > LinkedIn
> >
> >
> >
> > General,
> >
> > I'd like to add you to my professional network on LinkedIn.
> >
> > - Kirill Churin
> >
>
On Sun, Oct 24, 2010 at 8:26 PM, Kirill Churin wrote:
> LinkedIn
>
>
>
> General,
>
> I'd like to add you to my professional network on LinkedIn.
>
> - Kirill Churin
>
> Kirill Churin
> Independent Information Technology and Services Professional
> Russian Federation
>
> Confirm that
LinkedIn
General,
I'd like to add you to my professional network on LinkedIn.
- Kirill Churin
Kirill Churin
Independent Information Technology and Services Professional
Russian Federation
Confirm that you know Kirill Churin
https://www.linkedin.com/e/j2jirp-gfoo3eku-30/isd/181
On 10/24/2010 10:45 AM, Lukas Fleischer wrote:
On Sun, Oct 24, 2010 at 05:38:35PM +0300, jesse jaara wrote:
I think i miss understoid you, if you wang the output og make to file you
can put>/file/path to end if iy
">" won't work since errors are printed to stderr (not stdout) in most
cases. "2
On 10/24/10 11:20, Johannes Held wrote:
Christian:
I know that I have to use piping for this, but I want to output the
errors I get while compiling a program into atext file.
What to type after make then?
You could try "tee". man tee.
your_command | tee file_1 file_2
If you need to bail fr
Am Sun, 24 Oct 2010 16:33:10 +0200
schrieb Christian :
> Hi all,
> I know that I have to use piping for this, but I want to output the
> errors I get while compiling a program into atext file.
> What to type after make then?
> Many thanks for any help,
> Christian
The easiest way in Arch Linux i
Christian :
> I know that I have to use piping for this, but I want to output the
> errors I get while compiling a program into atext file.
> What to type after make then?
You could try "tee". man tee.
your_command | tee file_1 file_2
--
Gruß, Johannes
http://hehejo.de
signature.asc
Descript
Following Building in a clean chroot I have encountered the following
issue, which is related to using sudo mkarchroot
The full path is not included (code posted from mkarchroot) should this
be fixed?
After patching mkarchroot it works with sudo.
BUILD=/home/devtools
$ sudo mkdir -vp ${BUILD}
Hi,
On 2010-10-24 16:45, Lukas Fleischer wrote:
On Sun, Oct 24, 2010 at 05:38:35PM +0300, jesse jaara wrote:
I think i miss understoid you, if you wang the output og make to file you
can put>/file/path to end if iy
">" won't work since errors are printed to stderr (not stdout) in most
cases. "2
On Sun, Oct 24, 2010 at 05:38:35PM +0300, jesse jaara wrote:
> I think i miss understoid you, if you wang the output og make to file you
> can put >/file/path to end if iy
">" won't work since errors are printed to stderr (not stdout) in most
cases. "2>" should do the trick. If there are some erro
I think i miss understoid you, if you wang the output og make to file you
can put >/file/path to end if iy
On 24.10.2010 17.36, "jesse jaara" wrote:
> If you build it in some terminal emulator you might be ableto save the
whole
> output into file. If i remember right atleast kdes konsole and yakua
On Sun, Oct 24, 2010 at 04:33:10PM +0200, Christian wrote:
> I know that I have to use piping for this, but I want to output the
> errors I get while compiling a program into atext file.
> What to type after make then?
`make 2> foobar` will put them errors in a text file called "foobar".
If you build it in some terminal emulator you might be ableto save the whole
output into file. If i remember right atleast kdes konsole and yakuake can
do that
On 24.10.2010 17.33, "Christian" wrote:
> Hi all,
> I know that I have to use piping for this, but I want to output the
> errors I get whi
Hi all,
I know that I have to use piping for this, but I want to output the
errors I get while compiling a program into atext file.
What to type after make then?
Many thanks for any help,
Christian
On Sat, Oct 23, 2010 at 11:00 PM, Caleb Cushing wrote:
> (6/6) checking for file conflicts
> [] 100%
> error: failed to commit transaction (conflicting files)
> man-pages: /usr/share/man/man3/aio_init.3.gz exists in filesystem
>
> pacman -Qo /usr/share/man/man3/aio_
On Fri, Oct 22, 2010 at 14:54, Thomas Jost wrote:
> Hope this helps.
I removed openntpd completely and disabled time sync. The vm still
freezes eventually.
Also, I cannot set clocksource to anything else than acpi_pm
Let's go back to brainstorming mode, i welcome any new ideas.
--
János
17 matches
Mail list logo