Hi,
Max Nikulin wrote:
> Out of curiosity, does the requirement of specific GUID exist for removable
> drives?
It is disputed, whether the specs say that the partitions must be marked
by 0xEF in legacy MBR tables and by C12A7328-F81F-11D2-BA4B-00A0C93EC93B
in GPT.
In practice there seems to be
Hi,
Luis Muñoz Fuente wrote:
> I assume the problem is the debian link, which points to the same directory:
> $ ls -l tmp/debian
> lrwxrwxrwx 1 user user 1 Apr 22 20:47 tmp/debian -> .
> and creates a loop,
That's not a link loop, because "." is not a symbolic link.
But if a tree traversal is
Hi,
Luis Muñoz Fuente wrote:
> why does extracting the files from the debian iso increase the
> size so much?
Hard to say if you do not show what you do in particular.
In general an increase of about 120 MB is to be expected because of
expansion of hardlinks:
$ du
Hi,
Luis Muñoz Fuente wrote:
> I recently used clonezilla and followed these instructions:
> https://clonezilla.org/liveusb.php#linux-setup
The variation for "uEFI", i assume.
This aims at an undocumented habit of EFI implementations to look in
any FAT filesystem for a \EFI\BOOT directory with
Hi,
Vincent Lefevre wrote:
> Is there any reason why LibreOffice has been removed from Debian???
https://tracker.debian.org/pkg/libreoffice
says
The dependencies of libuno-cppuhelpergcc3-3=4:24.2.0-1 cannot be
satisfied in unstable on arm64, s390x, i386, ppc64el, armel, amd64,
and
Hi,
Nicholas Geovanis wrote:
> But what if next time the back-doored software _does_ build without error?
The initial build problems did not cause suspicion.
It was the CPU load of sshd and an obscure complaint by valgrind which
caused the discovery.
Hi,
i read from bytes 2085412 to 2085479:
"Info rrmation Syste rm VolumeSYSTEM~"
which is similar to the alterations of one of the USB sticks shown in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998#35
The web knows about a Microsoft folder named "System Volume Information".
Hi,
David Christensen wrote:
> # cmp --verbose debian-11.3.0-amd64-netinst.iso /dev/sdb
I got my copy from
https://get.debian.org/images/archive/11.3.0/amd64/iso-cd/debian-11.3.0-amd64-netinst.iso
SHA256 matches:
7892981e1da216e79fb3a1536ce5ebab157afdd20048fe458f2ae34fbc26c19b
In a further
Hi,
David Christensen wrote:
> It's a relatively simple experiment to confirm that a USB flash drive with
> d-i changes after the first boot.
This could still be
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998
where Lenovo BIOS and/or MS-Windows altered the USB stick.
> Same for
Hi,
Chung Jonathan wrote:
> Yes, I think the local fix is the way to go.
I wrote:
> > (You forgot to Cc: debian-user@lists.debian.org.
> > Consider to send your mail to the list address, too. I too would then
> > resend my following reply to the list.)
Since my "following reply" is quoted in
Hi,
David Christensen wrote:
> > the Debian installer modifies the contents of the USB flash drive when
> > it runs.
Do you mean inside the range of the ISO image or outside by creating a
new partition ?
songbird wrote:
> if it is an iso image copied to the USB stick it should not
> be
Hi,
Jonathan Chung wrote:
> > pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
> > upstream https://github.com/madler/pigz/issues/111
> > Installing the version from sid resolves the issue which is clearly not
> > optimal. I think the fix should be backported.
> > Can someone help
Hi,
Max Nikulin wrote:
> I admit "dithering" may be incorrect term, [...]
> Consider 2 squares having size of 2.5×2.5 pixels. Non-even sizes and fuzzy
> lines variants:
> █████
> ██████
> ████ ██
>██ ██
>█████
> Second variant might have sense if an
Hi,
Marco Moock wrote:
> The libs will have a suffix of t64
I wonder whether those suffixes will go away at some stage of this effort.
(Further i wonder when the package tracker appearance of libisoburn
will become less ugly than currently:
https://tracker.debian.org/pkg/libisoburn
and how
Hi,
Max Nikulin wrote:
> When vector graphics, that does not match device resolution, is rasterized,
> the result is either non-even sizes of similar elements or fuzzy lines due
> to dithering.
Nitpicking:
"Dithering" in raster graphics is emulation of color resolution at the
expense of space
Hi,
Curt wrote:
> as I believe Paul Valéry once noted, even the past isn't what it used
> to be.
That's why i want everything back exactly the way as it never was.
Have a nice day :)
Thomas
Hi,
when i was a young Babyboomer in the late 1970s we were accused of
destroying society by a "twin culture of sexual license and cannabis".
The big Decline of the West was a sure thing, accelerated by excessive
tv consumption.
Other future threats were drying up oil wells, a comming ice age,
Hi,
Andy Smith wrote:
> [...] I argue that at present it
> isn't a good idea to just reject all DKIM failures like OP's mailbox
> provider appears to be doing.
Just for the records:
The mails in question don't get rejected but rather marked as spam
and then get delivered.
The currently best
Hi,
Hans wrote:
> Re: *SPAM* Re: Spam from the list?
> In-Reply-To: <20240306112253.55e25...@earth.stargate.org.uk>
referring the mail
> > Date: Wed, 6 Mar 2024 11:22:53 +
> > From: Brad Rogers
> > Message-ID: <20240306112253.55e25...@earth.stargate.org.uk>
I assume that this mail
Hi,
Hans wrote:
> I changed nothing and suddenly many mails from debian-user
> (but not all, only some) are recognized as spam.
But the one you posted here did not come from debian-user.
So maybe what changed is an inadverted subscription to one of
debian-bugs-d...@lists.debian.org
Hi,
Hans wrote:
> during the last moonths I get more mails from the debian-user list marked as
> spam than before.
> [...]
> Below I send the header of an example of such a mail, maybe you can see the
> reason?
The message does not look like it came to you via debian-user:
> X-Original-To:
Hi,
> when cfdisk reports:
> Device Start End Sectors Size Type
> /dev/sda2 1785522176 1786245119 722944 353M EFI System
> /dev/sda3 1786245120 1933045759 146800640 70G EFI System
> I don't understand the 'EFI System' note /dev/sda3 is /
The partition type
Hi,
Clayton Penn wrote:
> I have attempted to register for the Debian Forums, but have not received a
> verification email
Did you try wether your new account is already working ?
(Sorry, i'm not familiar with the current registration procedure.)
If not:
There seems to be some problem with
Hi,
Albretch Mueller wrote:
> > How can you update the initramfs on read-only media?
to...@tuxteam.de wrote:
> You can't. Initramfs resides in the boot medium. To update it,
> you have to write to said medium.
One will have to create a new read-only medium.
In case the original is a Debian
Hi,
Gene Heskett wrote:
> Next experiment is a pair of 4T Silicon Power SSD's
When f3 has (hopefully) given its OK, the topic of a full write-and-read
test will come up again. I'm looking forward to all the spin-off topics.
Have a nice day :)
Thomas
Hi,
Greg Wooledge wrote:
> Heh. Don't forget your own attempts to use a shredder as a PRNG stream.
My original idea was to watch a minimal shred run by teeing its work into
a checksummer.
But then topic drift came in. So we got a farm show of random generators
and a discussion about what
Hi,
Greg Wooledge wrote:
> Let me write out the example again, but with the bug fixed, and then
> explain what each line does, [... lecture about advanced shell
> programming ...]
And this all because Gene Heskett was adventurous enough to buy a cheap
fake USB disk. :))
Have a nice day :)
Hi,
"info shred" says:
> > > i=$(mktemp)
> > > exec 3<>"$i"
> > > rm -- "$i"
> > > echo "Hello, world" >&3
> > > shred - >&3
> > > exec 3>-
Greg Wooledge wrote:
> In fact, that last line is
> written incorrectly. It should say "exec 3>&-" and what that does
>
Hi,
> https://en.wikipedia.org/wiki/Everything_is_a_file
> But, there is more than one kind of file.
"All files are equal.
But some files are more equal than others."
(George Orwell in his dystopic novel "Server Farm".)
Have a nice day :)
Thomas
Hi,
Steve Matzura wrote:
> I thought it'd be a nice idea to combine any and all distribution media for
> a release into a single medium--a USB drive, of course.
The initial situation will depend much on the distro ...
But given that Debian is about the last one i know with all its packages
in
Hi,
John Boxall wrote:
> I am aware that the label and uuid (drive and partition) are replicated on
> the cloned drive, but I can't find the model number (in text format) stored
> anywhere on the drive.
Maybe the grub-pc package takes its configuration from a different drive
which is attached to
Hi,
John Boxall wrote:
> Setting up grub-pc (2.06-3~deb11u6) ...
> /dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_21185R801540 does not
> exist, so cannot grub-install to it!
> What is confusing to me is that the error indicates the source SDD even
> though I have updated the boot
Hi,
to...@tuxteam.de wrote:
> Still there's the discrepancy between doc and behaviour.
Depends at which documentation you look. Obviously stemming from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155175#36
i read in
Hi,
debian-u...@howorth.org.uk wrote:
> Maybe it is unstated but mandatory to use -n 1 as well?
> And optionally -s N?
Naw. It just doesn't want to work pipes.
Initially i tried with these options:
shred -n 1 -s 1K -v - | sha256sum
as preparation for a proposal to Gene Heskett, like:
Hi,
Linux-Fan wrote:
> I wrote a program to automatically generate random bytes in multiple
> threads:
> https://masysma.net/32/big4.xhtml
> ...
> || Wrote 102400 MiB in 13 s @ 7812.023 MiB/s
That's impressive.
> Secure Random can be obtained from OpenSSL:
>
> | $ time for i in `seq 1 100`; do
Hi,
David Christensen wrote:
> Concurrency:
> threads throughput
> 8 205+198+180+195+205+184+184+189=1,540 MB/s
There remains the question how to join these streams without losing speed
in order to produce a single checksum. (Or one would have to divide the
target into 8 areas which get
Hi,
David Christensen wrote:
> $ time dd if=/dev/urandom bs=8K count=128K | wc -c
> [...]
> 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 4.30652 s, 249 MB/s
This looks good enough for practical use on spinning rust and slow SSD.
Maybe the "wc" pipe slows it down ?
... not much on 4 GHz Xeon with
Hi,
i wrote:
> > In the other thread about the /dev/sdm test:
Gene Heskett wrote:
> > > Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32
> > > [...]
> > > $ sudo f3probe --destructive --time-ops /dev/sdm
> > > Bad news: The device `/dev/sdm' is a counterfeit of type limbo
> > > Device
Hi,
gene heskett wrote:
> my fading eyesight couldn't see
> the diffs between () and {} in a 6 point font. I need a bigger, more
> legible font in t-bird.
That's why i propose to copy+paste problematic command lines.
Your mouse can read it, your mail client can send it, and we have
youngsters
Hi,
to...@tuxteam.de wrote:
> Ah, it seems to be this one, from 2002:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155175
So it's not a bug but a feature. :(
I'm riddling over the code about the connection to an old graphics
algorithm (Bresenham's Algorithm) and how shred produces a
Hi,
i wrote:
> > shred: -: invalid file type
to...@tuxteam.de wrote:
> Hmm. This looks like a genuine bug: the man page mentions it.
Even the help text in
https://sources.debian.org/src/coreutils/9.4-3/src/shred.c/
says
If FILE is -, shred standard output.
The name "-" is recognized in
Hi,
Gene Heskett wrote:
> Is bash not actually bash these days? It is not doing for loops for me.
Come on Gene, be no sophie. Copy+paste your failing line here. :))
IIRC the for-loop in question writes several copies of the same file.
(
Hi,
Greg Wooledge wrote:
> > The readline library is released under the full GPL, not the LGPL. If
> > you dynamically link it with a program, then you can only release that
> > program under terms compatible with the GPL. This is an intentional
> > choice.
to...@tuxteam.de wrote:
>
Hi,
Van Snyder wrote:
> Years ago, I knew the name of the routines one could use to have some stdin
> history and be able to edit it, like you can do in XTerm or gnuplot or
Sounds like readline:
https://en.wikipedia.org/wiki/GNU_Readline
https://tracker.debian.org/pkg/readline
An
Hi,
gene heskett wrote:
> GPT fdisk (gdisk) version 1.0.9
>
> Partition table scan:
> MBR: MBR only
> [...]
> Found invalid GPT and valid MBR; converting MBR to GPT format
> in memory.
> [...]
> Warning! Secondary partition table overlaps the last partition by 33 blocks!
> You will need to
Hi,
Loris Bennett wrote:
> As many have pointed out, it is short for 'Steuerung', but I have met
> many Germans who refer to this key as 'String'. I am not sure why
BASIC ?
Or the popular bundle theory:
[Strg] (= [Ctrl]) means "String",
[AltGr] (= right side [Alt]) means "Altgriechisch" (=
Hi,
Patrice Duroux wrote:
> Out of curiosity, I started this transition on some packages from
> experimental and I observed that deborphan is not without
> «disruption».
> [...]
> Is this something to be reported to deborphan as it could also be in
> some other cases than this time_t transition?
Hi,
Dmitry wrote:
> Yep. `dd` copy partitions table. Amazing.
Not so amazing after you realize that a partition table is just data on
the storage medium and not some special property of the storage device.
dd copies data. If these data contain a partition table and get copied to
the right place
Hi,
Andy Smith wrote:
> It is hard to understand how what Michael/Sophie/Tobias does can in
> any way be "fun" for them, though maybe that is just our lack of
> understanding.
I expressed my suspicion of a "Hurz" performance in
https://lists.debian.org/debian-user/2023/05/msg00100.html
Have
Hi,
Nicolas George wrote:
> You seem to be assuming that the system will first check sector 0 to
> parse the MBR and then, if the MBR declares a GPT sector try to use the
> GPT.
That's what the UEFI specs prescribe. GPT is defined by UEFI-2.8 in
chapter 5 "GUID Partition Table (GPT) Disk
Hi,
i hate to put in question the benefit of my proposal, but:
Nicolas George wrote:
> The firmware would never write in parts of the
> drive that might contain data.
See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998
"cdrom: Installation media changes after booting it"
Two
Hi,
Nicolas George wrote:
> Interesting. Indeed, “table-length: 4” causes sfdisk to only write 3
> sectors at the beginning and 2 at the end. I checked it really does not
> write elsewhere.
> That makes it possible to use full-disk RAID on a UEFI boot drive. Very
> good news.
\o/
(Nearly as
Hi,
i cannot make qualified proposals for the GRUB question, but stumble over
your technical statements.
Nicolas George wrote:
> Since mdadm can only put its superblock at the end of the device (1.0),
> at the beginning of the device (1.1) and 4 Ko from the beginning (1.2),
> but they still have
Hi,
David Christensen wrote:
> I have a SOHO file server with ~1 TB of data. I would like archive the data
> by burning it to a series of optical discs organized by time (e.g. mtime).
> I expect to periodically burn additional discs in the future, each covering
> a span of time from the previous
Hi,
Hans wrote:
> does anyone know, if there is a limit of the size an iso may have?
With xorriso: 4 TiB = 4096 GiB.
An ISO 9660 filesystem may have 2 exp 32 data blocks. The usual block
size is 2 exp 11 = 2048 bytes. That would be 2 exp 43 = 8 TiB in total.
But xorriso uses libburn for writing
Hi,
Greg Wooledge wrote:
> unicorn:~$ string="apple,banana,cherry,date"
> unicorn:~$ commas=${string//[!,]/}
> unicorn:~$ echo "${#commas}"
> 3
Always astonishing what a good bashism can do.
> But at this point, we have to wonder what the *actual* goal is.
Up to now we only know about the
Hi,
Anssi Saari
> It does seem strange to me, even in MS-DOS era I was able to set a
> terminal scrollback to 5000 lines without issue, when RAM was maybe 4 MB
> and a DOS terminal program probably had access to way less than that.
I have no problems with 130 xterms of 10,000 lines each.
> So
Hi,
to...@tuxteam.de wrote:
> > > I coopted the otherwise useless "Windows" key (aka "Left Super" for
> > > WM things: Super-L makes an xterm:
> > > # Terminal
> > > Key "t" A 4 Exec exec xterm
i wrote:
> > For me the Flying Windows keys pop up or push down the affected window:
> >
Hi,
fxkl4...@protonmail.com wrote:
> why doesn't grep count 2 commas
> echo 'Kích thước máy xay cỏ, giá máy thế nào , phụ tùng máy mua ở đâu' |
> grep -c ,
> 1
Happens with much simpler text too:
$ echo ',,,' | grep -c ','
1
The man page explains it:
-c, --count
Suppress normal
Hi,
to...@tuxteam.de wrote:
> I coopted the otherwise useless "Windows" key (aka "Left Super" for
> WM things: Super-L makes an xterm:
> # Terminal
> Key "t" A 4 Exec exec xterm
For me the Flying Windows keys pop up or push down the affected window:
Key Super_L A N RaiseLower
Key
Hi,
i wrote:
> > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg
> > wheat -fg black -sl 1 +sb
John Conover wrote:
>
>Action 'Exec exec xterm ...'
The framework of this line probably
Hi,
i wrote:
> >xterm -ls -geometry 80x24 -bg wheat -fg black -sl 1 +sb &
Max Nikulin wrote:
> Options may be put into ~/.Xresources
> xterm*vt100.saveLines: 1
> xterm*VT100.background: wheat
> xterm*VT100.foreground: black
I have it in ~/.fvwm2rc as:
*FvwmButtons xterm_ts5
Hi,
gene heskett wrote:
> > where did the extra 19.4G's come from? Can filesystem
> > ext4's overhead account for that?
In an earlier mail:
> > > command line: rsync -a --bwlimit=10m --fsync --progress /home/
> > > /mnt/homevol
David Christensen wrote:
> Please RTFM rsync(1) to choose your
Hi,
i wrote:
> > What did finally help ? Just the shorter terminal scroll back memory ?
gene heskett wrote:
> That, and possibly the --bwlimit=10m, giving the SSD time to keep their
> stuff in one sock.
Then i place my bet on the terminal alone.
Linux is able to handle disk-to-disk copies that
Hi,
i see that i messed up "h" and "k" in my explanation of the fight over
the link targets in /dev/disk/by-id. So another attempt:
sdh has a unique serial number GSTD02TB230102. Thus we see in
https://lists.debian.org/debian-user/2024/01/msg00667.html
these two links:
/dev/sdh
Hi,
David Christensen wrote:
> I suspect the conflicting serial numbers are causing problems in the kernel,
> as indicated by the /dev/disk/by-id/* problems.
That's not in the kernel but in udev/systemd's process of creating the
symbolic links in /dev/disk/by-id/.
It gets /dev/sd[h-l] and
Hi,
Curt wrote:
> I discovered a couple of discussions of the phenomenon, the upshot of which
> were:
> 1) That's what you get when you purchase cheap SSDs.
> https://www.reddit.com/r/truenas/comments/s0rrpo/two_sata_ssds_with_identical_serial_numbers/
> 2) SSDs belonging to the same software
Hi,
after i began enumerating suspects, gene heskett wrote:
> terminals scroll back memory, I purposely set this
> particular terminals scrollback to 200 lines with that in mind.
How large was it set when your runs caused the OOM killer to act ?
I have a good number of xterms with 10,000 lines
Hi,
Gene Heskett wrote:
> lsblk, which I've published several times, shows 5 drives.
Duh. Obviously this thread overstretches my mental capacity.
> And I've since tried cp in addition to rsync, does the same thing, killing
> the sysytem with the OOM but much quicker. cp using all system memory
Hi,
i, too, wondered where there should be a duplicate serial number.
But indeed:
David Wright wrote:
> > /dev/sdi53 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146
> > /dev/sdj1 54 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1
> ↑ that is /really/ bad!
Does the
Hi,
Andy Smith wrote:
> what I meant was that fdisk showed a single partition of
> 3.2TB size, while the entire disk being only the 400G
Then it's what i would expect from fdisk.
> I did try using fdisk on the destination to delete the partition and
> recreate it with the correct numbers, but
Hi,
Andy Smith wrote:
> I've got a disk image that sits on top of an LVM logical volume
> that is on top of an mdadm RAID-1 that is on top of a pair of:
> Device Model: Samsung SSD 870 EVO 4TB
> Sector Size: 512 bytes logical/physical
> so let';s say that is at /dev/foo/disk_image (where
Hi,
Bret Busby wrote:
> Whilst, as I previously made the point, this is all off-topic for a Debian
> operating system users mailing list
But i found a premium excuse in the debian-cd and debian-live ISOs. :o)
> the last seven versions of a file, being retained, was a
> useful tool for software
Hi,
Nicholas Geovanis wrote:
> You ruined my day :-)
It was not my fault. Send complaints to the people who convened as
"High Sierra Group" in 1986.
> Something similar to IBM's kludgiest relic of the early 1960s has appeared
> in linux?
The unixoid community added System Use Protocol and
Hi,
i cannot contribute much to the practical issues with playing music.
But i'd like to clarify technical properties of CD-DA media:
Nicolas George wrote:
> compared to data CDs, audio CDs lack one layer of error-correcting code
True.
Another drawback is that CD-DA sectors cannot be read by
Hi,
Bret Busby wrote:
> > .;
Jeremy Nicoll wrote:
> IBM's MVS & its successors, most recently z/OS, have something
> similar called a GDG (or Generation Data Group).
The principle made it into ISO 9660 specifications.
To make this thread relevant for Debian, let's assume that somebody
asked
Hi,
Albretch Mueller wrote:
> But how do you strace a program saving the output (of the stracing)
> in a logfile while you also save that program's output without making
> it part of the stracing?
man strace says:
-o filename Write the trace output to the file filename rather
Hi,
to...@tuxteam.de wrote:
> [...] (it's actually a logistic function [1]).
> [1] https://en.wikipedia.org/wiki/Logistic_function
> Looking forward to Yet Another Of Those Nerdy Monster Threads ;-)
Since it's happening periodically with about the same participants,
shouldn't we rather try to
Hi,
(Cc-ing poc...@columbus.rr.com just in case the unsubscription strikes
again.)
Pocket wrote:
> I spend several days trying to subscribed to the list, with the web signup
> ALWAYS time out with a gateway error.
The mails from the list have these informational headers:
List-Subscribe:
Hi,
Andrew M.A. Cater wrote:
> * It may also be useful to for someone to post a summary email from time to
> time to explain long threads.
You did not move the old "to" but rather added a new one during the change
from the text in 2023/12/msg00045.html to the new one:
> > * It may also be
Hi,
to...@tuxteam.de wrote:
> Remember
> Apple's "fat binaries", which contained a binary for 68K and another
> for PowerPC? Those were made with "forks", which was Apple's variant
> of "several streams in one file". And so on.
The most extreme example i know is Solaris:
Hi,
gene heskett wrote:
> > In the FWIW dept this time formula is pretty accurate back to the
> > middle of 4713 BC.
Greg Wooledge wrote:
> Even the *Julian* calendar used in ancient Rome wouldn't have been in
> use in 4713 BC. Any calendar would have been locally defined, if one
> existed at
Hi,
David Wright wrote:
> I'm subscribed, but I don't receive that badge of honour.
> This is from my other post in this thread—no LDOSUBSCRIBER:
>
> > X-Spam-Status: No, score=-4.9 required=4.0 tests=CAPINIT,FOURLA,
> > HEADER_FROM_DIFFERENT_DOMAINS,LDO_WHITELIST,RCVD_IN_DNSWL_LOW,
> >
Hi,
Andrew M.A. Cater wrote:
> * Before posting, it may be useful to check your post for spelling mistakes
> and scan it for redundancy, duplicate words and redundancy.
Some wisdom cannot be repeated enough.
Have a nice day :)
Thomas
Hi,
there is a new surplus word "private" in these lines:
> * Please post answers back to the list so others can benefit: private
> private conversations don't benefit people who may only be following
Have a nice day :)
Thomas
Hi,
> Anyone one else having trouble with the mailing list?
I got your message via the list.
> Have received any messages since Nov 30
Normal traffic yesterday and today, i'd say.
> I can not tell if I am still subscribed
The "From:" address poc...@columbus.rr.com seems not to be recognized
Hi,
Karen Lewellen wrote:
> ..ah, typo indeed.
> it should be rsh.
Quite a while ago rsh has been put in the pillory for not encrypting the
connection. The town crier urged everybody to use ssh instead.
Found in the web:
https://fossies.org/linux/alpine/imap/docs/FAQ.txt
_4.3 How does the
Hi,
Karen Lewellen wrote:
> I cannot find out what rhs means.
> Getting an rhs to imap server timeout with one of the new office emails.
Can it be that "rhs" is a typo and should rather be "rsh" ?
The web has old messages which resemble what you describe:
Subject:
"[Alpine-info] Why do I
Hi,
Zenaan Harkness wrote:
> > > all of the grub menu options (Graphical
> > > install, Graphical expert install, Expert install, etc) give 2 errors:
> > > 1) "..invalid buffer alignment... " with some long number beginning with
> > > minus.
> > > 2) kernel fail to load error, presumably due to
Hi,
Hans wrote:
> I want to automatically create a bootable USB-stick using dd from an
> ISO-file.
The landscape of ISO files is wide and varied.
An URL for getting the ISO would help to make more specific statements.
> However, after generating the stick the UUID of the first partition
>
Hi,
> On Sat, Nov 11, 2023 at 08:16:20PM +, Gareth Evans wrote:
> > > On 9 Nov 2023, at 13:47, Byung-Hee HWANG wrote:
> > >
> > > 220 bendel.debian.org ESMTP Postfix
> > > ehlo penguin
> > > 250-bendel.debian.org
> > > 250-PIPELINING
> > > 250-SIZE 3072
> > > 250-STARTTLS
> > >
Hi,
Max Nikulin wrote:
> Are there obstacles making implementation of proper SIGINT and
> SIGTERM signals handler prohibitively difficult? Ctrl+C is a common part of
> UI familiar to the most of users. There are should be serious reasons if it
> is necessary to teach them to touch an application
Hi,
David Christensen wrote:
> Are there tools other than xorriso(1) that can create a compatible checksum?
> Read the checksum?
Not yet. The data format is documented in
https://dev.lovelyhq.com/libburnia/libisofs/raw/branch/master/doc/checksums.txt
For the general concept of AAIP attributes
Hi,
David Christensen wrote:
> Adding checksum file(s) to the contents burned to disc is an important step
> that should not be omitted
I let xorriso compute and store the checksums in a non-file block range
at the end of the ISO filesystem. Each file gets an AAIP attribute which
points to an
Hi,
Gene Heskett wrote:
> > I have 3 100 disk spindles of dvd's bought years ago, that are
> > no longer recognized in any of the 4 or 5 dvd writers I have, but one box
> > of rewritables about the same age, stored n a light tight cardboard box,
> > will likely outlast me.
Unwritten write-once
Hi,
Nicolas George wrote:
> > Ear, ear!
Curt wrote:
> An ear c'est une oreille.
C'est probablement because les frenchais ne cannot pas prononcer le "H".
Have a nice day :)
Thomas
Hi,
to...@tuxteam.de wrote:
> > I concur with Nicolas: every time you say "folder", a unicorn dies.
Loris Bennett wrote:
> In German there are also two words: 'Ordner' (folder/binder) and
> 'Verzeichnis' (directory/catalogue). People also use both more or less
> interchangeably.
But if you say
Hi,
Greg Wooledge wrote:
> This is what's causing the loop to iterate more times than it should,
> and to re-process input.
That's not what i see in my experiments.
I see stuttering output which first repeats the lines put out so far
before it adds a new line.
The getline() loop iterates as
Hi,
tom kronmiller wrote:
> I ended up using setvbuf(stdin, NULL, _IONBF, 0) in the parent process and
> that seems to have fixed the actual program I was having trouble with.
stdin ? Not setvbuf(stdout, NULL, _IONBF, 0) ?
That would be one of the weirder remedies and explanations which can be
Hi,
it helps to do
fflush((stdout);
after each printf(), or to run before the loop:
setvbuf(stdout, NULL, _IONBF, 0);
So it is obvious that the usual output buffering of printf() causes the
repetitions of text.
The loop does not do any extra cycles, as i could confirm by inserting
a stderr
1 - 100 of 1720 matches
Mail list logo
